Multiple Software RAID problems on 14.04.2
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mdadm (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
edit:
NB. this report is inaccurate - please see the following instead:
https:/
Re. mdadm 3.2.5-5ubuntu4.1 (or possibly kernel bug(s)?)
Firstly,
/etc/initramfs-
1. Encrypted LVM RAID fails to boot
2. LVM RAID fails to boot when degraded
I have had various issues re. (2) tested with VirtualBox and KVM (with and on 14.04.2)
(1) gets so far in the boot process then keeps displaying "No volume groups found"
(2) if virtual disk is removed from the VM, I've managed to get it to boot once and remove the offending disk from mdX using mdadm ... but couldn't reproduce this behaviour a second (or third) time - now it just keeps printing...
Incrementally starting RAID arrays...
mdadm: CREATE user root not found
mdadm: CREATE group disk not found
Incrementally started RAID arrays
...every few seconds.
That symptom seems to be fixable in other reports in circumstances where the system is bootable after a soft reset (Ctrl+Alt+Del) but no such luck in my case.
It seems that software RAID is a mess in 14.04 - can someone take a good look at it?
description: | updated |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1466803/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]