touch-packages team mailing list archive

[dblade <listmail@xxxxxxxxxxxx>]

here is an interesting find:

replacing the missing disk (mdadm --add /dev/md0 /dev/sdb1) and waiting for sync to complete leads to proper booting system
the system continued boot even after I --failed and --removed the second disk.

I could not return the system to it's original boot fail state until I
zero'd the super block on the second disk.


some additional messages that I had not seen before (after boot is failing again)

device-mapper: table: 252:0: linear: dm-linear: Device lookup failed
device-mapper: ioctl: error adding target to table
device-mapper: table: 252:1: linear: dm-linear: Device lookup failed
device-mapper: ioctl: error adding target to table
(then repeats the above once more)

-- 
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/1351528

Title:
  boot fails on raid (md raid1) + LVM (combined / + /boot) + degraded

Status in “lvm2” package in Ubuntu:
  New

Bug description:
  Trusty installation is combined root + /boot within LVM on top of mdraid (type 1.x) RAID1 with one missing disk (degraded).
  [method:  basically create the setup in shell first then point install at the lvm.  at end of install create a chroot and add mdadm pkg]

  boot fails with the following messages:
   Incrementally starting RAID arrays...
   mdadm: CREATE user root not found
   mdadm: CREATE group disk not found
   Incrementally starting RAID arrays...
  and slowly repeats the above at this point.

  workaround:
  - add break=premount to grub kernel line entry
  - for continue visibility of boot output also remove quiet,  splash and possibly set gxmode 640x480

  now @ initramfs prompt:
  mdadm --detail /dev/md0 should indicate a state of clean, degraded, array is started so this part is ok

  lvm lvs output attributes are as follows:
  -wi-d----  (instead of the expected -wi-a----)
  lvs manpage this means device tables are missing (device mapper?)

  FIX: simply run lvm vgchange -ay and exit initramsfs.  This will lead
  to a booting system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1351528/+subscriptions