Wily LVM-RAID1 – md: personality for level 1 is not loaded
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | initramfs-tools (Ubuntu) |
High
|
Andy Whitcroft | ||
| | linux (Ubuntu) |
Undecided
|
Unassigned | ||
| | lvm2 (Ubuntu) |
High
|
Andy Whitcroft | ||
Bug Description
After upgrading to Wily, raid1 LVs don't activate during the initrd phase. Since the root LV is also RAID1-mirrored, the system doesn't boot.
I get the following message each time LVM tries to activate a raid1 LV:
md: personality for level 1 is not loaded!
Everything was fine with Vivid. I had to downgrade to Vivid kernel (3.19.0-30) to get my system to a usable state. I pretty much hope it to be a temporary workaround and I'll get the new 4.2.0 kernel work with Wily in days.
| Changed in linux (Ubuntu): | |
| status: | New → Incomplete |
| MegaBrutal (qbu6to) wrote : | #2 |
I can't collect logs on non-booting system.
| Changed in linux (Ubuntu): | |
| status: | Incomplete → Confirmed |
| tags: | added: regression-release wily |
| MegaBrutal (qbu6to) wrote : | #3 |
Reproducible: upgraded another Ubuntu installation in VM and got the same result.
Since the bug prevents booting, I suggest to increase priority to High.
| Andy Whitcroft (apw) wrote : | #4 |
It seems that that module is built and installed into /lib/modules, but is not in the initramfs. Sounds like an initramfs-tools bug.
| Changed in initramfs-tools (Ubuntu): | |
| status: | New → In Progress |
| importance: | Undecided → High |
| assignee: | nobody → Andy Whitcroft (apw) |
| milestone: | none → ubuntu-15.11 |
| Changed in lvm2 (Ubuntu): | |
| status: | New → Invalid |
| Changed in linux (Ubuntu): | |
| status: | Confirmed → Invalid |
| Changed in lvm2 (Ubuntu): | |
| status: | Invalid → In Progress |
| importance: | Undecided → High |
| assignee: | nobody → Andy Whitcroft (apw) |
| milestone: | none → ubuntu-15.11 |
| Changed in lvm2 (Ubuntu): | |
| milestone: | ubuntu-15.11 → ubuntu-15.12 |
| Changed in initramfs-tools (Ubuntu): | |
| milestone: | ubuntu-15.11 → ubuntu-15.12 |
| Thomas Johnson (ntmatter) wrote : | #5 |
As a workaround, you can add the relevant modules to the initramfs. A quick walkthrough is as follows:
- Boot from the install media, and choose "Rescue a broken system."
- Run through all of the basic configuration steps, configuring location, keyboard, networking, timezone, etc.
- When prompted for root filesystem, select your usual root volume (eg, /dev/my-vg/root)
- Also mount a separate /boot partition
- Execute a shell in /dev/my-vg/root
- Type "mount" and ensure that the correct / and /boot volumes are actually mounted.
- Add the raid1 and mirror modules to /etc/initramfs-
# echo raid1 >> /etc/initramfs-
# echo dm_mirror >> /etc/initramfs-
# update-initramfs -u
- Exit out of the shell, and reboot the system. Don't forget to remove the install media!
| Changed in lvm2 (Ubuntu): | |
| milestone: | ubuntu-15.12 → ubuntu-16.01 |
| Changed in initramfs-tools (Ubuntu): | |
| milestone: | ubuntu-15.12 → ubuntu-16.01 |
| MegaBrutal (qbu6to) wrote : | #6 |
Thanks for the workaround! It seems adding raid1 is enough.
| Changed in lvm2 (Ubuntu): | |
| milestone: | ubuntu-16.01 → ubuntu-16.02 |
| Changed in initramfs-tools (Ubuntu): | |
| milestone: | ubuntu-16.01 → ubuntu-16.02 |
| Changed in lvm2 (Ubuntu): | |
| milestone: | ubuntu-16.02 → ubuntu-16.03 |
| Changed in initramfs-tools (Ubuntu): | |
| milestone: | ubuntu-16.02 → ubuntu-16.03 |


This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1509717
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.