← Back to team overview

kernel-packages team mailing list archive

[Bug 1509717] [NEW] Wily LVM-RAID1 – md: personality for level 1 is not loaded

 

Public bug reported:

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.

** Affects: initramfs-tools (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: lvm2 (Ubuntu)
     Importance: Undecided
         Status: New

** Also affects: lvm2 (Ubuntu)
   Importance: Undecided
       Status: New

** Also affects: initramfs-tools (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1509717

Title:
  Wily LVM-RAID1 – md: personality for level 1 is not loaded

Status in initramfs-tools package in Ubuntu:
  New
Status in linux package in Ubuntu:
  New
Status in lvm2 package in Ubuntu:
  New

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1509717/+subscriptions


Follow ups