By moving fedora from single disk to RAID array and then re-installing grub does not set automatically rd.md.uuid kernel parameter resulting in an unbootable state.
For scenario like following:
# mount /dev/md126p2 /mnt
# for d in /sys /dev /run /proc ; do mount -v --bind "$d" /mnt"$d" ; done
# chroot /mnt
# dracut -v --force --regenerate-all
# grub2-install /dev/md126
# grub2-mkconfig -o /boot/grub2/grub.cfg
It would be nice if grub2-mkconfig detects that its / is an RAID array and automatically adds corresponding rd.md.uuid to GRUB_CMDLINE_LINUX in file /etc/default/grub.
For more info see: https://bugzilla.redhat.com/show_bug.cgi?id=1201962
This isn't just when moving from a single disk to a RAID array. Upgrades of existing systems from earlier versions of Fedora to F22 are breaking.
This is a serious "fails to boot after upgrade" regression, not a "nice to have if I do dangerous stuff no sane person should expect to work out of the box" RFE, as one might infer from the above description.
I was just moving my install from single disk to RAID, so I was reporting bug for that. Did not know (or I knew but forget) that upgrading fedora breaks also. I am not sure if that is grub2-mkconf job or Fedora update script, but sure this would solve both cases.
Hit the same mess upgrading my mail server. Been working for years for loads of releases and F22 broke it.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.