regenerate initramfs after moving boot partition
up vote
1
down vote
favorite
I've recently moved my linux system from hdd to ssd. I managed to get it booting and everything was fine until I deleted old boot partitions from hdd. Now when I try to boot I end up in dracut shell with /dev/disk/by-uuid/xxxxx doesn't exist error, where xxxxx is UUID of my former /boot or /boot/efi partition (I'm not exactly sure which one is it since I no longer have them).
Now I need to regenerate initramfs to use the new partitions I cloned from hdd to ssd. I tried running dracut --regenerate-all --force from rescue boot but it didn't help.
I'm using Fedora 21, so how can I do it? Or is there problem in something else?
linux initramfs-tools
edited Jul 8 '15 at 15:33
marbu
14329
asked Apr 13 '15 at 19:24
user437209
612
add a comment |
up vote
1
down vote
favorite
I've recently moved my linux system from hdd to ssd. I managed to get it booting and everything was fine until I deleted old boot partitions from hdd. Now when I try to boot I end up in dracut shell with /dev/disk/by-uuid/xxxxx doesn't exist error, where xxxxx is UUID of my former /boot or /boot/efi partition (I'm not exactly sure which one is it since I no longer have them).
Now I need to regenerate initramfs to use the new partitions I cloned from hdd to ssd. I tried running dracut --regenerate-all --force from rescue boot but it didn't help.
I'm using Fedora 21, so how can I do it? Or is there problem in something else?
linux initramfs-tools
edited Jul 8 '15 at 15:33
marbu
14329
asked Apr 13 '15 at 19:24
user437209
612
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I've recently moved my linux system from hdd to ssd. I managed to get it booting and everything was fine until I deleted old boot partitions from hdd. Now when I try to boot I end up in dracut shell with /dev/disk/by-uuid/xxxxx doesn't exist error, where xxxxx is UUID of my former /boot or /boot/efi partition (I'm not exactly sure which one is it since I no longer have them).
Now I need to regenerate initramfs to use the new partitions I cloned from hdd to ssd. I tried running dracut --regenerate-all --force from rescue boot but it didn't help.
I'm using Fedora 21, so how can I do it? Or is there problem in something else?
linux initramfs-tools
edited Jul 8 '15 at 15:33
marbu
14329
asked Apr 13 '15 at 19:24
user437209
612
I've recently moved my linux system from hdd to ssd. I managed to get it booting and everything was fine until I deleted old boot partitions from hdd. Now when I try to boot I end up in dracut shell with /dev/disk/by-uuid/xxxxx doesn't exist error, where xxxxx is UUID of my former /boot or /boot/efi partition (I'm not exactly sure which one is it since I no longer have them).
Now I need to regenerate initramfs to use the new partitions I cloned from hdd to ssd. I tried running dracut --regenerate-all --force from rescue boot but it didn't help.
I'm using Fedora 21, so how can I do it? Or is there problem in something else?
linux initramfs-tools
linux initramfs-tools
edited Jul 8 '15 at 15:33
marbu
14329
asked Apr 13 '15 at 19:24
user437209
612
edited Jul 8 '15 at 15:33
marbu
14329
asked Apr 13 '15 at 19:24
user437209
612
edited Jul 8 '15 at 15:33
marbu
14329
edited Jul 8 '15 at 15:33
marbu
14329
edited Jul 8 '15 at 15:33
marbu
14329
14329
asked Apr 13 '15 at 19:24
user437209
612
asked Apr 13 '15 at 19:24
user437209
612
asked Apr 13 '15 at 19:24
user437209
612
612
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
Do you still have a F21 install media?
If so do the following:
boot to "troubleshooting" > Rescue a Fedora System
Allow for mounting (normally not r/o)
chroot /mnt/sysimage
dracut --regenerate-all -f && grub2-mkconfig -o /boot/grub2/grub.cfg ( if you are SURE it is not throwing errors on the dracut --regenerate-all previous made (i.e. ls /boot show them but won't boot) just rebuild grub with the second command.
~ Sent from a Fedora 22 box
answered Apr 14 '15 at 10:04
linuxdev2013
944819
That's basically what I did (although I ran dracut --regenerate-all -f from the rescue boot option that was installed), however it didn't help. I reinstalled now anyway as I realized that it's just not possible to ensure 100% compatibility when virtually anything could be relying on properties of the hdd (eg, UUIDs, partition names, partion sizes, ...) that's just not possible to reliably handle without deeper understaning.
– user437209
Apr 17 '15 at 21:43
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
Do you still have a F21 install media?
If so do the following:
boot to "troubleshooting" > Rescue a Fedora System
Allow for mounting (normally not r/o)
chroot /mnt/sysimage
dracut --regenerate-all -f && grub2-mkconfig -o /boot/grub2/grub.cfg ( if you are SURE it is not throwing errors on the dracut --regenerate-all previous made (i.e. ls /boot show them but won't boot) just rebuild grub with the second command.
~ Sent from a Fedora 22 box
answered Apr 14 '15 at 10:04
linuxdev2013
944819
That's basically what I did (although I ran dracut --regenerate-all -f from the rescue boot option that was installed), however it didn't help. I reinstalled now anyway as I realized that it's just not possible to ensure 100% compatibility when virtually anything could be relying on properties of the hdd (eg, UUIDs, partition names, partion sizes, ...) that's just not possible to reliably handle without deeper understaning.
– user437209
Apr 17 '15 at 21:43
add a comment |
up vote
0
down vote
Do you still have a F21 install media?
If so do the following:
boot to "troubleshooting" > Rescue a Fedora System
Allow for mounting (normally not r/o)
chroot /mnt/sysimage
dracut --regenerate-all -f && grub2-mkconfig -o /boot/grub2/grub.cfg ( if you are SURE it is not throwing errors on the dracut --regenerate-all previous made (i.e. ls /boot show them but won't boot) just rebuild grub with the second command.
~ Sent from a Fedora 22 box
answered Apr 14 '15 at 10:04
linuxdev2013
944819
That's basically what I did (although I ran dracut --regenerate-all -f from the rescue boot option that was installed), however it didn't help. I reinstalled now anyway as I realized that it's just not possible to ensure 100% compatibility when virtually anything could be relying on properties of the hdd (eg, UUIDs, partition names, partion sizes, ...) that's just not possible to reliably handle without deeper understaning.
– user437209
Apr 17 '15 at 21:43
add a comment |
up vote
0
down vote
up vote
0
down vote
Do you still have a F21 install media?
If so do the following:
boot to "troubleshooting" > Rescue a Fedora System
Allow for mounting (normally not r/o)
chroot /mnt/sysimage
dracut --regenerate-all -f && grub2-mkconfig -o /boot/grub2/grub.cfg ( if you are SURE it is not throwing errors on the dracut --regenerate-all previous made (i.e. ls /boot show them but won't boot) just rebuild grub with the second command.
~ Sent from a Fedora 22 box
answered Apr 14 '15 at 10:04
linuxdev2013
944819
Do you still have a F21 install media?
If so do the following:
boot to "troubleshooting" > Rescue a Fedora System
Allow for mounting (normally not r/o)
chroot /mnt/sysimage
dracut --regenerate-all -f && grub2-mkconfig -o /boot/grub2/grub.cfg ( if you are SURE it is not throwing errors on the dracut --regenerate-all previous made (i.e. ls /boot show them but won't boot) just rebuild grub with the second command.
~ Sent from a Fedora 22 box
answered Apr 14 '15 at 10:04
linuxdev2013
944819
answered Apr 14 '15 at 10:04
linuxdev2013
944819
answered Apr 14 '15 at 10:04
linuxdev2013
944819
answered Apr 14 '15 at 10:04
linuxdev2013
944819
944819
That's basically what I did (although I ran dracut --regenerate-all -f from the rescue boot option that was installed), however it didn't help. I reinstalled now anyway as I realized that it's just not possible to ensure 100% compatibility when virtually anything could be relying on properties of the hdd (eg, UUIDs, partition names, partion sizes, ...) that's just not possible to reliably handle without deeper understaning.
– user437209
Apr 17 '15 at 21:43
add a comment |
That's basically what I did (although I ran dracut --regenerate-all -f from the rescue boot option that was installed), however it didn't help. I reinstalled now anyway as I realized that it's just not possible to ensure 100% compatibility when virtually anything could be relying on properties of the hdd (eg, UUIDs, partition names, partion sizes, ...) that's just not possible to reliably handle without deeper understaning.
– user437209
Apr 17 '15 at 21:43
That's basically what I did (although I ran dracut --regenerate-all -f from the rescue boot option that was installed), however it didn't help. I reinstalled now anyway as I realized that it's just not possible to ensure 100% compatibility when virtually anything could be relying on properties of the hdd (eg, UUIDs, partition names, partion sizes, ...) that's just not possible to reliably handle without deeper understaning.
– user437209
Apr 17 '15 at 21:43
That's basically what I did (although I ran dracut --regenerate-all -f from the rescue boot option that was installed), however it didn't help. I reinstalled now anyway as I realized that it's just not possible to ensure 100% compatibility when virtually anything could be relying on properties of the hdd (eg, UUIDs, partition names, partion sizes, ...) that's just not possible to reliably handle without deeper understaning.
– user437209
Apr 17 '15 at 21:43
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f901162%2fregenerate-initramfs-after-moving-boot-partition%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
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
