Boot-Repair hangs, possible alternative?











up vote
1
down vote

favorite












My overall goal is to dual boot Linux Mint and Windows 10. The motherboard is legacy bios only.



Firstly I installed Linux Mint then Windows 10 on a secondary partition.

Because I forgot to make a separate boot partition... I moved everything 1000MB to the right, and created a ext4 boot partition at the beginning of sda.

Running boot repair on a live Ubuntu USB with the options:




  • Separate /boot partition: sda4 (the first partition on disk)

  • GRUB Legacy (figured that was for legacy bios)

  • Reinstall GRUB (default)

  • Unhide boot menu: 10s (default)


Boot Repair hangs at Purge kernels then reinstall last kernel sda1 (ins). This may require several minuets...



I have let this running overnight, the process is still running. I have done a reboot and tried again, let the process run for 3 days. Nothing different.



Boot Info Summary: http://paste.ubuntu.com/17678629/



I have had gparted open at the same time, assuming that wouldn't have an affect.










share|improve this question




























    up vote
    1
    down vote

    favorite












    My overall goal is to dual boot Linux Mint and Windows 10. The motherboard is legacy bios only.



    Firstly I installed Linux Mint then Windows 10 on a secondary partition.

    Because I forgot to make a separate boot partition... I moved everything 1000MB to the right, and created a ext4 boot partition at the beginning of sda.

    Running boot repair on a live Ubuntu USB with the options:




    • Separate /boot partition: sda4 (the first partition on disk)

    • GRUB Legacy (figured that was for legacy bios)

    • Reinstall GRUB (default)

    • Unhide boot menu: 10s (default)


    Boot Repair hangs at Purge kernels then reinstall last kernel sda1 (ins). This may require several minuets...



    I have let this running overnight, the process is still running. I have done a reboot and tried again, let the process run for 3 days. Nothing different.



    Boot Info Summary: http://paste.ubuntu.com/17678629/



    I have had gparted open at the same time, assuming that wouldn't have an affect.










    share|improve this question


























      up vote
      1
      down vote

      favorite









      up vote
      1
      down vote

      favorite











      My overall goal is to dual boot Linux Mint and Windows 10. The motherboard is legacy bios only.



      Firstly I installed Linux Mint then Windows 10 on a secondary partition.

      Because I forgot to make a separate boot partition... I moved everything 1000MB to the right, and created a ext4 boot partition at the beginning of sda.

      Running boot repair on a live Ubuntu USB with the options:




      • Separate /boot partition: sda4 (the first partition on disk)

      • GRUB Legacy (figured that was for legacy bios)

      • Reinstall GRUB (default)

      • Unhide boot menu: 10s (default)


      Boot Repair hangs at Purge kernels then reinstall last kernel sda1 (ins). This may require several minuets...



      I have let this running overnight, the process is still running. I have done a reboot and tried again, let the process run for 3 days. Nothing different.



      Boot Info Summary: http://paste.ubuntu.com/17678629/



      I have had gparted open at the same time, assuming that wouldn't have an affect.










      share|improve this question















      My overall goal is to dual boot Linux Mint and Windows 10. The motherboard is legacy bios only.



      Firstly I installed Linux Mint then Windows 10 on a secondary partition.

      Because I forgot to make a separate boot partition... I moved everything 1000MB to the right, and created a ext4 boot partition at the beginning of sda.

      Running boot repair on a live Ubuntu USB with the options:




      • Separate /boot partition: sda4 (the first partition on disk)

      • GRUB Legacy (figured that was for legacy bios)

      • Reinstall GRUB (default)

      • Unhide boot menu: 10s (default)


      Boot Repair hangs at Purge kernels then reinstall last kernel sda1 (ins). This may require several minuets...



      I have let this running overnight, the process is still running. I have done a reboot and tried again, let the process run for 3 days. Nothing different.



      Boot Info Summary: http://paste.ubuntu.com/17678629/



      I have had gparted open at the same time, assuming that wouldn't have an affect.







      boot grub-legacy






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Jun 28 '16 at 11:45

























      asked Jun 22 '16 at 6:17









      Harry

      64




      64






















          2 Answers
          2






          active

          oldest

          votes

















          up vote
          0
          down vote













          I've had exactly the same issue today. Digging through boot-repair tool logs I've found this error:



          gui-actions-purge.sh: line 441: ${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic: bad substitution


          The logs are stored in the varlogboot-savlogYYYY-MM-DD__HHhMMboot-repairXXboot-repair.log file.



          The package linux${$KERNELTOREINST}-generic doesn't look like a valid package. It probably should be just linux-generic.



          So I've modified usrshareboot-savgui-actions-purge.sh, replacing line 441:



          local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic"


          with:



          local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux-generic linux-headers-generic"


          and restarted boot-repair from taskbar menu.



          It worked OK and fixed my boot issues, restoring grub on my cloned disk.



          Quick how-to




          1. Boot Boot-Repair as usual, but close autostarted boot-repair tool

          2. Open terminal from taskbar menu

          3. Type sudo su - to get root shell

          4. Type leafpad &

          5. Text-editor will open. Open usrshareboot-savgui-actions-purge.sh file with it.


          6. Find



            local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic"



          7. Replace with:



            local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux-generic linux-headers-generic"


          8. Save file, close Leafpad

          9. Leave root terminal open, you will need it later, as boot-repair will ask you to run some commands.

          10. Run boot-repair from taskbar menu and follow it's instructions.






          share|improve this answer





















          • Made the change and still getting the same output. Searched for other peoples experiences and found this comment stating that you cannot use a legacy bios system. And the following comment suggests that I may need the live os in legacy?
            – Harry
            Jun 30 '16 at 7:50












          • @Harry Well, in my case it was legacy all the way down - it worked OK. Could you post boot-repair.log? I've used TeamViewer to get it: wget https://download.teamviewer.com/download/teamviewer_i386.deb && apt-get install ./teamviewer_i386.deb && teamviewer
            – beatcracker
            Jun 30 '16 at 10:13




















          up vote
          0
          down vote













          My general approach to these quagmires is image the disks involved, then just start fresh.



          Not technically helpful I know, but my advice nonetheless.






          share|improve this answer





















            Your Answer








            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "106"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            convertImagesToLinks: false,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: null,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














             

            draft saved


            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f291295%2fboot-repair-hangs-possible-alternative%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes








            up vote
            0
            down vote













            I've had exactly the same issue today. Digging through boot-repair tool logs I've found this error:



            gui-actions-purge.sh: line 441: ${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic: bad substitution


            The logs are stored in the varlogboot-savlogYYYY-MM-DD__HHhMMboot-repairXXboot-repair.log file.



            The package linux${$KERNELTOREINST}-generic doesn't look like a valid package. It probably should be just linux-generic.



            So I've modified usrshareboot-savgui-actions-purge.sh, replacing line 441:



            local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic"


            with:



            local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux-generic linux-headers-generic"


            and restarted boot-repair from taskbar menu.



            It worked OK and fixed my boot issues, restoring grub on my cloned disk.



            Quick how-to




            1. Boot Boot-Repair as usual, but close autostarted boot-repair tool

            2. Open terminal from taskbar menu

            3. Type sudo su - to get root shell

            4. Type leafpad &

            5. Text-editor will open. Open usrshareboot-savgui-actions-purge.sh file with it.


            6. Find



              local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic"



            7. Replace with:



              local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux-generic linux-headers-generic"


            8. Save file, close Leafpad

            9. Leave root terminal open, you will need it later, as boot-repair will ask you to run some commands.

            10. Run boot-repair from taskbar menu and follow it's instructions.






            share|improve this answer





















            • Made the change and still getting the same output. Searched for other peoples experiences and found this comment stating that you cannot use a legacy bios system. And the following comment suggests that I may need the live os in legacy?
              – Harry
              Jun 30 '16 at 7:50












            • @Harry Well, in my case it was legacy all the way down - it worked OK. Could you post boot-repair.log? I've used TeamViewer to get it: wget https://download.teamviewer.com/download/teamviewer_i386.deb && apt-get install ./teamviewer_i386.deb && teamviewer
              – beatcracker
              Jun 30 '16 at 10:13

















            up vote
            0
            down vote













            I've had exactly the same issue today. Digging through boot-repair tool logs I've found this error:



            gui-actions-purge.sh: line 441: ${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic: bad substitution


            The logs are stored in the varlogboot-savlogYYYY-MM-DD__HHhMMboot-repairXXboot-repair.log file.



            The package linux${$KERNELTOREINST}-generic doesn't look like a valid package. It probably should be just linux-generic.



            So I've modified usrshareboot-savgui-actions-purge.sh, replacing line 441:



            local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic"


            with:



            local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux-generic linux-headers-generic"


            and restarted boot-repair from taskbar menu.



            It worked OK and fixed my boot issues, restoring grub on my cloned disk.



            Quick how-to




            1. Boot Boot-Repair as usual, but close autostarted boot-repair tool

            2. Open terminal from taskbar menu

            3. Type sudo su - to get root shell

            4. Type leafpad &

            5. Text-editor will open. Open usrshareboot-savgui-actions-purge.sh file with it.


            6. Find



              local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic"



            7. Replace with:



              local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux-generic linux-headers-generic"


            8. Save file, close Leafpad

            9. Leave root terminal open, you will need it later, as boot-repair will ask you to run some commands.

            10. Run boot-repair from taskbar menu and follow it's instructions.






            share|improve this answer





















            • Made the change and still getting the same output. Searched for other peoples experiences and found this comment stating that you cannot use a legacy bios system. And the following comment suggests that I may need the live os in legacy?
              – Harry
              Jun 30 '16 at 7:50












            • @Harry Well, in my case it was legacy all the way down - it worked OK. Could you post boot-repair.log? I've used TeamViewer to get it: wget https://download.teamviewer.com/download/teamviewer_i386.deb && apt-get install ./teamviewer_i386.deb && teamviewer
              – beatcracker
              Jun 30 '16 at 10:13















            up vote
            0
            down vote










            up vote
            0
            down vote









            I've had exactly the same issue today. Digging through boot-repair tool logs I've found this error:



            gui-actions-purge.sh: line 441: ${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic: bad substitution


            The logs are stored in the varlogboot-savlogYYYY-MM-DD__HHhMMboot-repairXXboot-repair.log file.



            The package linux${$KERNELTOREINST}-generic doesn't look like a valid package. It probably should be just linux-generic.



            So I've modified usrshareboot-savgui-actions-purge.sh, replacing line 441:



            local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic"


            with:



            local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux-generic linux-headers-generic"


            and restarted boot-repair from taskbar menu.



            It worked OK and fixed my boot issues, restoring grub on my cloned disk.



            Quick how-to




            1. Boot Boot-Repair as usual, but close autostarted boot-repair tool

            2. Open terminal from taskbar menu

            3. Type sudo su - to get root shell

            4. Type leafpad &

            5. Text-editor will open. Open usrshareboot-savgui-actions-purge.sh file with it.


            6. Find



              local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic"



            7. Replace with:



              local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux-generic linux-headers-generic"


            8. Save file, close Leafpad

            9. Leave root terminal open, you will need it later, as boot-repair will ask you to run some commands.

            10. Run boot-repair from taskbar menu and follow it's instructions.






            share|improve this answer












            I've had exactly the same issue today. Digging through boot-repair tool logs I've found this error:



            gui-actions-purge.sh: line 441: ${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic: bad substitution


            The logs are stored in the varlogboot-savlogYYYY-MM-DD__HHhMMboot-repairXXboot-repair.log file.



            The package linux${$KERNELTOREINST}-generic doesn't look like a valid package. It probably should be just linux-generic.



            So I've modified usrshareboot-savgui-actions-purge.sh, replacing line 441:



            local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic"


            with:



            local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux-generic linux-headers-generic"


            and restarted boot-repair from taskbar menu.



            It worked OK and fixed my boot issues, restoring grub on my cloned disk.



            Quick how-to




            1. Boot Boot-Repair as usual, but close autostarted boot-repair tool

            2. Open terminal from taskbar menu

            3. Type sudo su - to get root shell

            4. Type leafpad &

            5. Text-editor will open. Open usrshareboot-savgui-actions-purge.sh file with it.


            6. Find



              local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux${$KERNELTOREINST}-generic linux-headers-generic"



            7. Replace with:



              local COMMAND="${APTTYP[$USRPART]} ${INSTALLTYP[$USRPART]} ${YESTYP[$USRPART]} linux-generic linux-headers-generic"


            8. Save file, close Leafpad

            9. Leave root terminal open, you will need it later, as boot-repair will ask you to run some commands.

            10. Run boot-repair from taskbar menu and follow it's instructions.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Jun 29 '16 at 13:21









            beatcracker

            1012




            1012












            • Made the change and still getting the same output. Searched for other peoples experiences and found this comment stating that you cannot use a legacy bios system. And the following comment suggests that I may need the live os in legacy?
              – Harry
              Jun 30 '16 at 7:50












            • @Harry Well, in my case it was legacy all the way down - it worked OK. Could you post boot-repair.log? I've used TeamViewer to get it: wget https://download.teamviewer.com/download/teamviewer_i386.deb && apt-get install ./teamviewer_i386.deb && teamviewer
              – beatcracker
              Jun 30 '16 at 10:13




















            • Made the change and still getting the same output. Searched for other peoples experiences and found this comment stating that you cannot use a legacy bios system. And the following comment suggests that I may need the live os in legacy?
              – Harry
              Jun 30 '16 at 7:50












            • @Harry Well, in my case it was legacy all the way down - it worked OK. Could you post boot-repair.log? I've used TeamViewer to get it: wget https://download.teamviewer.com/download/teamviewer_i386.deb && apt-get install ./teamviewer_i386.deb && teamviewer
              – beatcracker
              Jun 30 '16 at 10:13


















            Made the change and still getting the same output. Searched for other peoples experiences and found this comment stating that you cannot use a legacy bios system. And the following comment suggests that I may need the live os in legacy?
            – Harry
            Jun 30 '16 at 7:50






            Made the change and still getting the same output. Searched for other peoples experiences and found this comment stating that you cannot use a legacy bios system. And the following comment suggests that I may need the live os in legacy?
            – Harry
            Jun 30 '16 at 7:50














            @Harry Well, in my case it was legacy all the way down - it worked OK. Could you post boot-repair.log? I've used TeamViewer to get it: wget https://download.teamviewer.com/download/teamviewer_i386.deb && apt-get install ./teamviewer_i386.deb && teamviewer
            – beatcracker
            Jun 30 '16 at 10:13






            @Harry Well, in my case it was legacy all the way down - it worked OK. Could you post boot-repair.log? I've used TeamViewer to get it: wget https://download.teamviewer.com/download/teamviewer_i386.deb && apt-get install ./teamviewer_i386.deb && teamviewer
            – beatcracker
            Jun 30 '16 at 10:13














            up vote
            0
            down vote













            My general approach to these quagmires is image the disks involved, then just start fresh.



            Not technically helpful I know, but my advice nonetheless.






            share|improve this answer

























              up vote
              0
              down vote













              My general approach to these quagmires is image the disks involved, then just start fresh.



              Not technically helpful I know, but my advice nonetheless.






              share|improve this answer























                up vote
                0
                down vote










                up vote
                0
                down vote









                My general approach to these quagmires is image the disks involved, then just start fresh.



                Not technically helpful I know, but my advice nonetheless.






                share|improve this answer












                My general approach to these quagmires is image the disks involved, then just start fresh.



                Not technically helpful I know, but my advice nonetheless.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jul 7 at 11:41









                Luke Mlsna

                1013




                1013






























                     

                    draft saved


                    draft discarded



















































                     


                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f291295%2fboot-repair-hangs-possible-alternative%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    Morgemoulin

                    Scott Moir

                    Souastre