*** This bug is a duplicate of bug 120504 ***
https://bugs.launchpad.net/bugs/120504
vol_id has been replaced with blkid by now
** This bug has been marked a duplicate of bug 120504
mdadm : boot failed sometimes, no devices found
--
No devices listed in conf file were found due to mdadm
I tried to follow the fix. After which my box could not reboot since it
now cannot find /dev/md0
--
No devices listed in conf file were found due to mdadm RAID1 array UUID
different from actual UUID reported by vol_id
https://bugs.launchpad.net/bugs/126499
You received this bug notification
mdadm --update=uuid (plus replacing the uuid in /etc/mdadm/mdadm.conf)
fixes the problem.
However, that still leaves people who had a perfectly working Feisty
system, which happened to have this inconsistency, with a machine that
cannot boot after upgrading to Gutsy.
--
No devices listed in
NB: I have two affected MD partitions; I've tested the --update solution
with one, but left the other alone, so that I can test whether a distro
upgrade solves the problem.
--
No devices listed in conf file were found due to mdadm RAID1 array UUID
different from actual UUID reported by vol_id
** Changed in: mdadm (Ubuntu)
Status: New = Confirmed
--
No devices listed in conf file were found due to mdadm RAID1 array UUID
different from actual UUID reported by vol_id
https://bugs.launchpad.net/bugs/126499
You received this bug notification because you are a member of Ubuntu
Regarding the fix, after updating mdadm.conf, one also needs to
regenerate the initrd.img files:
update-initramfs -k all -u
--
No devices listed in conf file were found due to mdadm RAID1 array UUID
different from actual UUID reported by vol_id
https://bugs.launchpad.net/bugs/126499
You
