touch-packages team mailing list archive

[Thomas Johnson <NTmatter@xxxxxxxxx>]

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-tools/modules, and rebuild the initramfs
# echo raid1 >> /etc/initramfs-tools/modules
# echo dm_mirror >> /etc/initramfs-tools/modules
# update-initramfs -u
- Exit out of the shell, and reboot the system. Don't forget to remove the install media!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lvm2 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:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  In Progress

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