Wily LVM-RAID1 – md: personality for level 1 is not loaded
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bionic |
Invalid
|
Undecided
|
Unassigned | ||
Cosmic |
Invalid
|
Undecided
|
Unassigned | ||
Disco |
Invalid
|
Undecided
|
Unassigned | ||
Eoan |
Invalid
|
Undecided
|
Unassigned | ||
lvm2 (Debian) |
Fix Released
|
Unknown
|
|||
lvm2 (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Cosmic |
Won't Fix
|
Undecided
|
Unassigned | ||
Disco |
Won't Fix
|
Undecided
|
Unassigned | ||
Eoan |
Fix Released
|
High
|
Unassigned |
Bug Description
[Impact]
system does not boot after converting lvm volume to raid1 w/o having mdadm installed.
[Test case]
1. Install server to LVM
2. Add second disk to it
3. Run pvcreate /dev/vdb
4. Run vgextend ubuntu-vg /dev/vdb
5. Run lvconvert -m1 --type raid1 ubuntu-vg/ubuntu-lv
Reboot and check that it still boots.
6. Remove mdadm
7. Upgrade to lvm2 from proposed
Reboot and check that it still boots.
8. Downgrade lvm2 to release
Reboot and check that it fails to boot
[Regression potential]
Not really anything, we just add the raid1 module to initramfs, so it might be loaded during boot, and raid1 logical volumes might appear earlier.
[Original bug report]
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.
tags: | added: regression-release wily |
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 |
Changed in lvm2 (Ubuntu): | |
milestone: | ubuntu-15.12 → ubuntu-16.01 |
Changed in initramfs-tools (Ubuntu): | |
milestone: | ubuntu-15.12 → ubuntu-16.01 |
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 |
tags: | added: rls-bb-incoming |
no longer affects: | initramfs-tools (Ubuntu) |
no longer affects: | initramfs-tools (Ubuntu Bionic) |
no longer affects: | initramfs-tools (Ubuntu Cosmic) |
no longer affects: | initramfs-tools (Ubuntu Disco) |
no longer affects: | initramfs-tools (Ubuntu Eoan) |
tags: | removed: rls-bb-incoming |
Changed in lvm2 (Ubuntu Eoan): | |
assignee: | Andy Whitcroft (apw) → nobody |
milestone: | ubuntu-16.03 → none |
tags: | added: id-5d0ba914f340e31a8e9f2cf1 |
Changed in lvm2 (Debian): | |
status: | Unknown → Incomplete |
tags: | added: cscc |
Changed in linux (Ubuntu Bionic): | |
status: | New → Invalid |
Changed in linux (Ubuntu Cosmic): | |
status: | New → Invalid |
Changed in linux (Ubuntu Disco): | |
status: | New → Invalid |
Changed in lvm2 (Ubuntu Cosmic): | |
status: | New → Won't Fix |
Changed in lvm2 (Ubuntu Eoan): | |
status: | In Progress → Triaged |
Changed in lvm2 (Ubuntu Disco): | |
status: | New → Won't Fix |
description: | updated |
Changed in lvm2 (Ubuntu Eoan): | |
status: | Triaged → In Progress |
Changed in lvm2 (Ubuntu Bionic): | |
status: | New → In Progress |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
tags: | added: id-5d0ba914f340e31a8e9f2cf1 |
Changed in lvm2 (Debian): | |
status: | Incomplete → Fix Released |
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.