Changed Partition Number and now Grub fails to start

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP











up vote
0
down vote

favorite












I deleted a partition on my hard disk, causing the partition numbers of the 2 Linux installations to decrement. When attempting to boot the computer I get the message error: no such partition and I am dropped to the grub rescue> prompt. How can I fix this?







share|improve this question
























    up vote
    0
    down vote

    favorite












    I deleted a partition on my hard disk, causing the partition numbers of the 2 Linux installations to decrement. When attempting to boot the computer I get the message error: no such partition and I am dropped to the grub rescue> prompt. How can I fix this?







    share|improve this question






















      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I deleted a partition on my hard disk, causing the partition numbers of the 2 Linux installations to decrement. When attempting to boot the computer I get the message error: no such partition and I am dropped to the grub rescue> prompt. How can I fix this?







      share|improve this question












      I deleted a partition on my hard disk, causing the partition numbers of the 2 Linux installations to decrement. When attempting to boot the computer I get the message error: no such partition and I am dropped to the grub rescue> prompt. How can I fix this?









      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 5 at 1:37









      user261205

      11




      11




















          3 Answers
          3






          active

          oldest

          votes

















          up vote
          0
          down vote













          You could try running update-grub either at the rescue prompt or from a Live USB/CD. Don´t know if it will work but it is a good starting point. Best thing to do is always backup before modifying partitions.



          Good way to backup is boot on a Live USB and run



          dd if=/[location of computer harddrive (example /sda)] of=[location of external harddrive (example /sdb)]


          Hopefully update-grub helps :)






          share|improve this answer



























            up vote
            0
            down vote













            @River-rush is right of course, fixing the numbering in your grub config to reflect the current situation will allow you to boot. As soon as you assign that disk space to a new partition though you'll have to renumber again. Presumably you want to do something with it?



            You could boot from a rescue disk and create a partition in the space where the old one was, which would put your numbering back how it was before, and allow you to boot with the existing grub config.



            If you are extending an existing partition to fill the space, then go with the approach of fixing your grub config.






            share|improve this answer



























              up vote
              0
              down vote













              Thanks to the existing answers. Since I used the partition number, I used the guide from https://help.ubuntu.com/community/Grub2/Troubleshooting:




              1. set prefix=(hdX,Y)/boot/grub where X is hard drive number starting with 0 and Y is known partition number


              2. set root=(hdX,Y) with the same numbers

              3. insmod normal

              4. normal

              From here, I pressed e to edit the boot parameters and changed the partition number in 5 places on 3 lines.



              It booted normally and I then ran update-grub.



              I found out that despite the rather cryptic error given by parted, you should not restart and should instead run update-grub.






              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: false,
                showLowRepImageUploadWarning: true,
                reputationToPostImages: null,
                bindNavPrevention: true,
                postfix: "",
                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%2f414897%2fchanged-partition-number-and-now-grub-fails-to-start%23new-answer', 'question_page');

                );

                Post as a guest






























                3 Answers
                3






                active

                oldest

                votes








                3 Answers
                3






                active

                oldest

                votes









                active

                oldest

                votes






                active

                oldest

                votes








                up vote
                0
                down vote













                You could try running update-grub either at the rescue prompt or from a Live USB/CD. Don´t know if it will work but it is a good starting point. Best thing to do is always backup before modifying partitions.



                Good way to backup is boot on a Live USB and run



                dd if=/[location of computer harddrive (example /sda)] of=[location of external harddrive (example /sdb)]


                Hopefully update-grub helps :)






                share|improve this answer
























                  up vote
                  0
                  down vote













                  You could try running update-grub either at the rescue prompt or from a Live USB/CD. Don´t know if it will work but it is a good starting point. Best thing to do is always backup before modifying partitions.



                  Good way to backup is boot on a Live USB and run



                  dd if=/[location of computer harddrive (example /sda)] of=[location of external harddrive (example /sdb)]


                  Hopefully update-grub helps :)






                  share|improve this answer






















                    up vote
                    0
                    down vote










                    up vote
                    0
                    down vote









                    You could try running update-grub either at the rescue prompt or from a Live USB/CD. Don´t know if it will work but it is a good starting point. Best thing to do is always backup before modifying partitions.



                    Good way to backup is boot on a Live USB and run



                    dd if=/[location of computer harddrive (example /sda)] of=[location of external harddrive (example /sdb)]


                    Hopefully update-grub helps :)






                    share|improve this answer












                    You could try running update-grub either at the rescue prompt or from a Live USB/CD. Don´t know if it will work but it is a good starting point. Best thing to do is always backup before modifying partitions.



                    Good way to backup is boot on a Live USB and run



                    dd if=/[location of computer harddrive (example /sda)] of=[location of external harddrive (example /sdb)]


                    Hopefully update-grub helps :)







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Jan 5 at 3:54









                    Liam O'Luachra

                    134




                    134






















                        up vote
                        0
                        down vote













                        @River-rush is right of course, fixing the numbering in your grub config to reflect the current situation will allow you to boot. As soon as you assign that disk space to a new partition though you'll have to renumber again. Presumably you want to do something with it?



                        You could boot from a rescue disk and create a partition in the space where the old one was, which would put your numbering back how it was before, and allow you to boot with the existing grub config.



                        If you are extending an existing partition to fill the space, then go with the approach of fixing your grub config.






                        share|improve this answer
























                          up vote
                          0
                          down vote













                          @River-rush is right of course, fixing the numbering in your grub config to reflect the current situation will allow you to boot. As soon as you assign that disk space to a new partition though you'll have to renumber again. Presumably you want to do something with it?



                          You could boot from a rescue disk and create a partition in the space where the old one was, which would put your numbering back how it was before, and allow you to boot with the existing grub config.



                          If you are extending an existing partition to fill the space, then go with the approach of fixing your grub config.






                          share|improve this answer






















                            up vote
                            0
                            down vote










                            up vote
                            0
                            down vote









                            @River-rush is right of course, fixing the numbering in your grub config to reflect the current situation will allow you to boot. As soon as you assign that disk space to a new partition though you'll have to renumber again. Presumably you want to do something with it?



                            You could boot from a rescue disk and create a partition in the space where the old one was, which would put your numbering back how it was before, and allow you to boot with the existing grub config.



                            If you are extending an existing partition to fill the space, then go with the approach of fixing your grub config.






                            share|improve this answer












                            @River-rush is right of course, fixing the numbering in your grub config to reflect the current situation will allow you to boot. As soon as you assign that disk space to a new partition though you'll have to renumber again. Presumably you want to do something with it?



                            You could boot from a rescue disk and create a partition in the space where the old one was, which would put your numbering back how it was before, and allow you to boot with the existing grub config.



                            If you are extending an existing partition to fill the space, then go with the approach of fixing your grub config.







                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered Jan 5 at 6:16









                            mc0e

                            656512




                            656512




















                                up vote
                                0
                                down vote













                                Thanks to the existing answers. Since I used the partition number, I used the guide from https://help.ubuntu.com/community/Grub2/Troubleshooting:




                                1. set prefix=(hdX,Y)/boot/grub where X is hard drive number starting with 0 and Y is known partition number


                                2. set root=(hdX,Y) with the same numbers

                                3. insmod normal

                                4. normal

                                From here, I pressed e to edit the boot parameters and changed the partition number in 5 places on 3 lines.



                                It booted normally and I then ran update-grub.



                                I found out that despite the rather cryptic error given by parted, you should not restart and should instead run update-grub.






                                share|improve this answer
























                                  up vote
                                  0
                                  down vote













                                  Thanks to the existing answers. Since I used the partition number, I used the guide from https://help.ubuntu.com/community/Grub2/Troubleshooting:




                                  1. set prefix=(hdX,Y)/boot/grub where X is hard drive number starting with 0 and Y is known partition number


                                  2. set root=(hdX,Y) with the same numbers

                                  3. insmod normal

                                  4. normal

                                  From here, I pressed e to edit the boot parameters and changed the partition number in 5 places on 3 lines.



                                  It booted normally and I then ran update-grub.



                                  I found out that despite the rather cryptic error given by parted, you should not restart and should instead run update-grub.






                                  share|improve this answer






















                                    up vote
                                    0
                                    down vote










                                    up vote
                                    0
                                    down vote









                                    Thanks to the existing answers. Since I used the partition number, I used the guide from https://help.ubuntu.com/community/Grub2/Troubleshooting:




                                    1. set prefix=(hdX,Y)/boot/grub where X is hard drive number starting with 0 and Y is known partition number


                                    2. set root=(hdX,Y) with the same numbers

                                    3. insmod normal

                                    4. normal

                                    From here, I pressed e to edit the boot parameters and changed the partition number in 5 places on 3 lines.



                                    It booted normally and I then ran update-grub.



                                    I found out that despite the rather cryptic error given by parted, you should not restart and should instead run update-grub.






                                    share|improve this answer












                                    Thanks to the existing answers. Since I used the partition number, I used the guide from https://help.ubuntu.com/community/Grub2/Troubleshooting:




                                    1. set prefix=(hdX,Y)/boot/grub where X is hard drive number starting with 0 and Y is known partition number


                                    2. set root=(hdX,Y) with the same numbers

                                    3. insmod normal

                                    4. normal

                                    From here, I pressed e to edit the boot parameters and changed the partition number in 5 places on 3 lines.



                                    It booted normally and I then ran update-grub.



                                    I found out that despite the rather cryptic error given by parted, you should not restart and should instead run update-grub.







                                    share|improve this answer












                                    share|improve this answer



                                    share|improve this answer










                                    answered Jan 6 at 4:35









                                    user261205

                                    11




                                    11






















                                         

                                        draft saved


                                        draft discarded


























                                         


                                        draft saved


                                        draft discarded














                                        StackExchange.ready(
                                        function ()
                                        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f414897%2fchanged-partition-number-and-now-grub-fails-to-start%23new-answer', 'question_page');

                                        );

                                        Post as a guest













































































                                        Popular posts from this blog

                                        How to check contact read email or not when send email to Individual?

                                        Bahrain

                                        Postfix configuration issue with fips on centos 7; mailgun relay