Red Hat Bugzilla – Bug 981824
fedup upgrade does not boot if root is an MD RAID partition
Last modified: 2013-07-08 12:41:42 EDT
Description of problem:
[21:38] <mrnuke> the fedup boot couldn't find my root partition as mdadm did not automatically scan/assembled it
[21:38] <mrnuke> when I told mdadm to scan and assembled, I couldn't tell which of my arrays was the one with root
[21:39] <mrnuke> and as most tools are unavailable in initramfs, I was stuck
[21:39] <mrnuke> no way to check
[21:39] <mrnuke> reboot with Ctrl-Alt-Del, and the fedup option is gone from the boot screen
Version-Release number of selected component (if applicable):
Only tried once
Steps to Reproduce:
1. fedup --network 19
3. select fedup
4. wait until dracut realizes it cannot boot and drops you to a shell
I win the lottery.
root "/" partition is on an MD RAID array.
I also ran into this problem.
At the rescue console, I did the following to kick it back into gear:
1. My mdadm.conf was there in the initramfs. I inspected that to see what arrays were available with "cat /etc/mdadm.conf".
2. For each of the listed /dev/mdn devices I did "mdadm --assemble /dev/mdn"
3. I then restarted systemd with "kill 1"
4. It continued with the upgrade until it said it was restarting the computer but it got stuck there. I had to pull the power to restart it.
After reboot the new initramfs automatically assembled my arrays and it all seems to "work".
For my upgrade attempt, the kernel parameters in grub for the "System Upgrade (fedup)" boot option included root=/dev/md1. This was set by fedup before reboot and was correct.
I can confirm the behaviour described in the first comment.
I found that:
# mdadm --assemble --scan
was sufficient to continue booting.
*** This bug has been marked as a duplicate of bug 970580 ***