Changed Partition Number and now Grub fails to start
Clash 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?
partition grub move-partition
add a comment |Â
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?
partition grub move-partition
add a comment |Â
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?
partition grub move-partition
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?
partition grub move-partition
asked Jan 5 at 1:37
user261205
11
11
add a comment |Â
add a comment |Â
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 :)
add a comment |Â
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.
add a comment |Â
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:
set prefix=(hdX,Y)/boot/grub
where X is hard drive number starting with 0 and Y is known partition numberset root=(hdX,Y)
with the same numbersinsmod normal
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.
add a comment |Â
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 :)
add a comment |Â
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 :)
add a comment |Â
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 :)
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 :)
answered Jan 5 at 3:54
Liam O'Luachra
134
134
add a comment |Â
add a comment |Â
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.
add a comment |Â
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.
add a comment |Â
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.
@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.
answered Jan 5 at 6:16
mc0e
656512
656512
add a comment |Â
add a comment |Â
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:
set prefix=(hdX,Y)/boot/grub
where X is hard drive number starting with 0 and Y is known partition numberset root=(hdX,Y)
with the same numbersinsmod normal
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.
add a comment |Â
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:
set prefix=(hdX,Y)/boot/grub
where X is hard drive number starting with 0 and Y is known partition numberset root=(hdX,Y)
with the same numbersinsmod normal
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.
add a comment |Â
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:
set prefix=(hdX,Y)/boot/grub
where X is hard drive number starting with 0 and Y is known partition numberset root=(hdX,Y)
with the same numbersinsmod normal
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.
Thanks to the existing answers. Since I used the partition number, I used the guide from https://help.ubuntu.com/community/Grub2/Troubleshooting:
set prefix=(hdX,Y)/boot/grub
where X is hard drive number starting with 0 and Y is known partition numberset root=(hdX,Y)
with the same numbersinsmod normal
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.
answered Jan 6 at 4:35
user261205
11
11
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
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
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password