https://bugzilla.novell.com/show_bug.cgi?id=656536 https://bugzilla.novell.com/show_bug.cgi?id=656536#c8 Neil Brown <nfbrown@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |bwiedemann@novell.com --- Comment #8 from Neil Brown <nfbrown@novell.com> 2011-03-01 20:26:39 UTC --- The mdadm boot script in the initrd tries to assemble 'resumedev' and then 'rootdev'. So the message: mdadm: /dev/md0 has been started with 4 drives. should be for resumedev. It appears that it is picking the right drives, but the wrong name (/dev/md0 rather than /dev/md1). That means the command $mdadm -A $mdconf --uuid=$uuid "$dev" must have the correct $uuid for the resumedev, but the wrong $dev. The only way I can see it getting /dev/md0 for $dev is if the immediately preceeding: if test -z "$dev"; then # fallback dev=/dev/md0 fi set dev, so: dev=$(get_md_name "$uuid") must leave dev as empty. I can only see that happening if /etc/mdadm.conf doesn't exist in the initrd. Yet you say that it does....and the setup script certainly seems to create it... however it will definitely look different from what it on the root filesystem. Can you please report exactly the /etc/mdadm.conf from the initrd? Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.