[Bug 1573982] Re: LVM boot problem - volumes not activated after upgrade to Xenial
Chris Sanders
chris.sanders at canonical.com
Mon Nov 6 03:10:23 UTC 2017
I've run across this today and it affects MAAS.
MAAS version: 2.2.2 (6099-g8751f91-0ubuntu1~16.04.1)
Configuring an LVM based drive with a raid on top of it for the root
partition will trigger this. Deploying the default kernel / OS will fail
due to inactive volume groups.
The fix as expected:
lvm vgchange -ay
mdadm --assemble --scan
exit
Then apply the above mentioned script to make it stick.
** Also affects: maas (Ubuntu)
Importance: Undecided
Status: New
--
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 lvm2 package in Ubuntu:
Confirmed
Status in maas package in Ubuntu:
New
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/ubuntu/+source/lvm2/+bug/1573982/+subscriptions
More information about the foundations-bugs
mailing list