Public bug reported:
Binary package hint: mdadm
I am unsure to which package this belongs. I have a system with 3 drives
that are set up by mdadm to various raid levels and on top of this lvm2.
The problem began I think around vol-id to blkid transition in Karmic.
The first thing that was strange is multiple blkid processes went into
inf. loop and consuming 100% CPU when upgrading the system. The next
thing that happend at the next reboot where the boot process drops into
busybox shell. When I examined the devices I noticed that all partitions
that had mdadm were not present at all (/dev/sda1, /dev/sda2 and
/dev/sda4 were not present but there was /dev/sda3 which was a swap
partition). Booting the old kernel did not help as every kernel got
updated so it must be the fault of one of the tools included in the init
image.
At this stage I had no choice than to reinstall Jaunty where everything
worked again.
Alpha 1 (alternative) installation disk has the same problem and doesn't
even boot at all.
** Affects: mdadm (Ubuntu)
Importance: Undecided
Status: New
--
Drives with md raid not found during boot
https://bugs.launchpad.net/bugs/380748
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
