*** This bug is a duplicate of bug 103177 ***
https://bugs.launchpad.net/bugs/103177
[Expired for mdadm (Ubuntu) because there has been no activity for 60
days.]
--
/dev/md0 fails to mount on boot
https://bugs.launchpad.net/bugs/102933
You received this bug notification because you are a
*** This bug is a duplicate of bug 103177 ***
https://bugs.launchpad.net/bugs/103177
This sounds like an exact duplicate of #103177, so I'm merging the two
bugs ... the hack of adding a sleep between init-premount and local-top
works for both, that implies that the mdadm/mdrun scripts are
(1) doesn't make sense, since the system already loops for up to three
minutes doing exactly this -- so breaking out of the initramfs shouldnt
make a difference.
Anyway, please do that so your system boots, and then provide the output
of:
dpkg-query -W udev volumeid libvolume-id0 mdadm evms
Scott, although it doesn't make sense, my Dell 390 Workstation shows
exactly the same behaviour. / is on md0 (Two drive RAID1).
Here's the output from dpkg-query -W udev volumeid libvolume-id0 mdadm
evms lvm2 lvm-common dmsetup libdevmapper1.02
udev108-0ubuntu3
volumeid108-0ubuntu3
udev108-0ubuntu3
volumeid108-0ubuntu3
libvolume-id0 108-0ubuntu3
mdadm 2.5.6-7ubuntu5
No packages found matching evms.
No packages found matching lvm2.
No packages found matching lvm-common.
dmsetup 2:1.02.08-1ubuntu10
libdevmapper1.022:1.02.08-1ubuntu10
--
/dev/md0 fails
** Description changed:
Binary package hint: udev
Since upgrading from edgy to feisty beta1, my system gets thrown to
busybox when booting. In busybox, /dev/md0 is missing, as well as the
/dev/sd? drives that would normally constitute the array. This issue
remains present with udev
