Re: RAID50 boot problems

[Roy Sigurd Karlsbakk <roy@karlsbakk.net>]

> > > /lib/udev/rules.d/64-md-raid.rules is here
> > > http://paste.ubuntu.com/5592227/
> >
> > Bug tested positive also on Ubuntu Precise (12.04) and reported to
> > https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1171945
> 
> This will run "mdadm --incremental $tempnode" on any device for which
> ID_FS_TYPE is set to "linux_raid_member", which certainly seems
> reasonable.
> 
> What does:
> udevadm info --query=property --path=/dev/mdXXX | grep ID_FS_TYPE
> 
> report for the raid5 arrays?

root@raidtest:~# udevadm info --query=property --path=/dev/md0
device path not found
root@raidtest:~# udevadm info --query=property --path=/dev/md1
device path not found

> Looking bug report I see that md0 and md1 have
> ID_FS_TYPE=linux_raid_member
> 
> So that should be working.
> 
> The fact that rootdelay=10 makes a difference suggests that it is
> successfully assembling the raid0, but just taking a bit too long.
> Maybe the script in the initrd needs "udevadm settle" just before it
> attempts
> to mount.
> 
> Can you look inside the initrd and see if "udevadm settle" is used
> anywhere?

mdadm settle doesn't seem to be used there. I really don't know my way around the bootup scripts that well, so I'm unsure where to add it…
-- 
Vennlige hilsener / Best regards

roy
--
Roy Sigurd Karlsbakk
(+47) 98013356
roy@karlsbakk.net
http://blogg.karlsbakk.net/
GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt
--
I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med xenotyp etymologi. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk.
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html