Ubuntu
mdadm package

  1. Bug #75681
  2. Comment #69

Comment 69 for bug 75681

Revision history for this message
Drew Hess (dhess) wrote : Re: [Bug 75681] Re: boot-time race condition initializing md

Oliver Brakmann <email address hidden> writes:

> Same here. I added a "sleep 3" to the mdadm script and my system now
> consistently boots. Previously, I got an error message from mdadm that
> it couldn't find the devices that made up my RAID.

Ditto here, running up-to-date Feisty on amd64. I use "break=mount"
and hit ctrl-d almost immediately after the output stops, and
everything works fine. If I don't do that, 7 times out of 10 my
machine will hang for a few minutes and then drop to the (initramfs)
prompt, complaining that my /dev/mapper/main-root LVM root isn't
found. It's on a software RAID1, /dev/md1, and it comes up degraded
in these cases, even if I shut the machine down cleanly before the
reboot.

Here's my /proc/mdstat:

Personalities : [raid1]
md1 : active raid1 sda2[0] sdb2[1]
      312472192 blocks [2/2] [UU]

md0 : active raid1 sda1[0] sdb1[1]
      96256 blocks [2/2] [UU]

unused devices: <none>

/dev/md0 is my /boot, a software RAID1 running ext3fs.

d