Bug 1259911

Summary:	Moving fedora install from non-RAID to RAID array rd.md.uuid not set automatically
Product:	[Fedora] Fedora	Reporter:	srakitnican <samuel.rakitnican>
Component:	grubby	Assignee:	Peter Jones <pjones>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	22	CC:	alan, bcl, dustymabe, dwmw2, fche, jerry, pjones
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-07-19 17:46:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description srakitnican 2015-09-03 18:49:00 UTC

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

Comment 1 David Woodhouse 2015-09-04 13:44:33 UTC

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.

Comment 2 srakitnican 2015-09-04 14:03:59 UTC

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.

Comment 3 alan 2015-11-25 22:00:38 UTC

Hit the same mess upgrading my mail server. Been working for years for loads of releases and F22 broke it.

Comment 4 Fedora End Of Life 2016-07-19 17:46:33 UTC

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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.