Public bug reported:
Binary package hint: dmraid
As the title says.
I work for a hardware reviews site and I've could reproduce this bug on
3 machines already.
It is pretty simple:
On any machine based on Intel ICH8R-ICH9R with Matrix RAID active
installing windows on a separate disk, do a clean UPDATE after
installation and then Install DMRAID (apt-get install dmraid) and
configure with dmraid -ay and try to boot the machine and see what
happens.
What happens on the 3 machines ive tested it is this:
Ubuntu boots directly into busybox and a detailed boot into recovery
shows that "/root partition could not be mounted due to the device being
busy"
I cannot manually mount the device in busybox
any attempt at manually mounting by uuid or by direct /dev/sda2 (in
which ubuntu resides) tells me "device is busy"
Waiting is not an option as some users said, since, booting does not
resume and device "never" becomes ready.
To make matters worse, dmraid destroys all kernels installed so, the
only solution is to re-install ubuntu.
This bug is still present either by full install or by wubi install and it is
STRICTLY happening with DMRAID and Matrix RAID (ubuntu installation is NOT done
in the RAID array but a separate disk on the same controller).
I've been using dmraid since feisty and I've never had any of this
issues, but, as of now, the dmraid package is totally useless and pretty
harmful to Intel Matrix RAID users.
This should be pinned as serious.
** Affects: dmraid (Ubuntu)
Importance: Undecided
Status: New
--
dmraid package destroys initrd and render system unbooteable (ubuntu Hardy)
https://bugs.launchpad.net/bugs/245842
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
