The bug I encounter is like #446445 reported for karmic (raid partition
is not recognized during system startup) but this is for lucid; on the
same machine, karmic works correctly and I nerver got a problem.
As I have more than 1 RAID array, I can confirm the erratic behaviour of
this bug: at
** Changed in: mdadm (Ubuntu)
Status: New = Fix Released
--
raid partition is not recognized during system startup
https://bugs.launchpad.net/bugs/446445
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
It seems to be related to bug #108553.
The problem stopped occuring when I installed updates a few days after
reporting this bug, so maybe it is already solved
--
raid partition is not recognized during system startup
https://bugs.launchpad.net/bugs/446445
You received this bug notification
Is this possibly related to bug #442735?
--
raid partition is not recognized during system startup
https://bugs.launchpad.net/bugs/446445
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Oct 21 2009
This also happens to me on my amd64 karmic release with all the latest
patches
In Syslog : DeviceDisappeared event detected on md device /dev/md0
(twice with the same timestamp)
--
raid partition is not recognized during system startup
https://bugs.launchpad.net/bugs/446445
You
Oct 21 2009
This also happens to me on my amd64 karmic release with all the latest
patches
syslog: DeviceDisappeared event detected on md device /dev/md0
The above message appears twice with the same timestamp in the log.
--
raid partition is not recognized during system startup
** Attachment added: BootDmesg.txt
http://launchpadlibrarian.net/33305194/BootDmesg.txt
** Attachment added: CurrentDmesg.txt
http://launchpadlibrarian.net/33305195/CurrentDmesg.txt
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/33305196/Dependencies.txt
**
