[Bug 1573982] Re: LVM boot problem - volumes not activated after upgrade to Xenial

[martin short]

I ran to the same issue yesterday with up-to-date (May 24,2019) 18.04.02
LTS. As mentioned above problem is /usr being on a separate LV.

packages:
initramfs-tools-bin 0.130ubuntu3.7
linux-image-generic 4.15.0.50.52
udev 237-3ubuntu10.21
libdevmapper1.02.1:amd64 2:1.02.145-4.1ubuntu3

It drops to the initramfs shell because it can't find the /usr. 
>From initramfs:

init:268

if read_fstab_entry /usr; then
        log_begin_msg "Mounting /usr file system"
        mountfs /usr
        log_end_msg
fi

scripts/local:260

local_mount_fs()


It fails because it can't find the device. Mapper didn't create any device either - there's no /dev/dm-X for that LV. 

/etc/fstab entries use devices by UUID by default. There's no such UUID
on the system during this time. It seems scripts can't handle it and
drop to the shell.

If I change the entry to:

/dev/vg00/lv_usr  /usr ext4 defaults 0 0

system is able to activate the device during the boot. But still it
seems other modules (like btrfs) have precedence and it takes few
seconds for system to pick up this LV.

It beats me why VG is not activated as a whole (vgchange -a y vg00),
maybe there's some reasoning behind it.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1573982

Title:
  LVM boot problem - volumes not activated after upgrade to Xenial

Status in curtin:
  Incomplete
Status in MAAS:
  Invalid
Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Soon after upgrade to Xenial (from 15.10) the boot process got broken.
  I'm using LVM for /root swap and other partitions.

  ===
  The current behaviour is:

  When I boot short after the Grub login screen I'm getting log messages
  like:

  ---
  Scanning for Btrfs filesystems
  resume: Could not state the resume device file: '/dev/mapper/VolGroup....'
  Please type in the full path...
  ---

  Then I press ENTER, for a few minutes some errors about floppy device
  access are raised (for some reason it tries to scan fd0 when floppy
  drive is empty). And then:

  ---
  Gave up waiting for root device. Common problems: ...
  ...
  ALERT! UUID=xxx-xxx.... does not exist.
  Dropping to a shell.
  ---

  From the BusyBox shell I managed to recover the boot by issuing "lvm
  vgchange -ay", then exit and then boot continues fine (all LVM file
  systems are successfully mounted).

  ===
  One workaround so far is creating /etc/initramfs-tools/scripts/local-top/lvm2-manual script doing "lvm vgchange -ay". But I'm looking for cleaner solution.

  Boot used to work fine with 15.10. Actually the first boot after
  upgrading to Xenial actually worked OK too, I'm not sure what might
  changed meanwhile (I've been fixing some packages installation since
  mysql server upgrade has failed).

  ===
  # lsb_release -rd
  Description:	Ubuntu 16.04 LTS
  Release:	16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1573982/+subscriptions