Bug 594228

Summary:	initrd: mdadm not run
Product:	[openSUSE] openSUSE 11.2	Reporter:	Jan Engelhardt <jengelh>
Component:	Basesystem	Assignee:	E-mail List <bnc-team-screening>
Status:	VERIFIED FIXED	QA Contact:	E-mail List <qa-bugs>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	x86-64
OS:	Linux
Whiteboard:
Found By:	Beta-Customer	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Jan Engelhardt 2010-04-07 01:22:59 UTC

Assuming /dev/disk/by-label/myraidfs is a link to, say, /dev/md3, put

 /dev/disk/by-label/myraidfs / ext4 ...

into /etc/fstab, run mkinitrd, and have grub/menu.lst also use root=/dev/disk/by-label/myraidfs if it does not yet (yast2 would have added this on the initial install already), then boot. The resulting system will not start the raid device and fail to boot. Running `mdadm -As` in the initramfs emergency shell and then continuing to boot works.

As I see it: $rootdev=/dev/disk/by-label/myraidfs. 03-storage.sh checks $rootdev, but does not find /dev/md, thus md_dev="", leading to 51-md.sh doing nothing.

Comment 1 Jan Engelhardt 2010-04-07 01:37:35 UTC

Subsequently I removed root=... from grub/menu.lst, because I remember this parameter is integrated into the initramfs image anyway. Rerunning mkinitrd yields:

Root device: /dev/disk/by-label/myraidfs (/dev/md30 (mounted on / as xfs)

Despite being smart enough to figure out it points to md3, it still record /dev/disk/by-label/myraidfs into the rootdev variable, giving another reason for the boot to fail (i.e. even when there's no root= parameter in menu.lst)

Comment 2 Michal Marek 2010-04-07 07:42:04 UTC

Can you try with mdadm from Factory?

*** This bug has been marked as a duplicate of bug 583424 ***

Comment 3 Jan Engelhardt 2010-07-27 21:46:32 UTC

Seems to be solved in 11.3 indeed, where /dev/disk/by-id/md-uuid:.... is used by default.