@ Christopher M. Penalver:
Because this bug renders the system temporally unusable, it looks like
it should have an importance of "critical".
** Changed in: lvm2 (Ubuntu)
Importance: Undecided => Medium
** Also affects: hundredpapercuts
Importance: Undecided
Status: New
** Changed in: hundredpapercuts
Status: New => Confirmed
** Changed in: hundredpapercuts
Importance: Undecided => Medium
--
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/1396213
Title:
LVM VG is not activated during system boot
Status in One Hundred Papercuts:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Status in lvm2 package in Ubuntu:
Confirmed
Bug description:
Hi all,
I open this report based on the linked conversation I had on the linux-lvm
mailing list, and the Ask Ubuntu question I posted regarding this case.
https://www.redhat.com/archives/linux-lvm/2014-November/msg00023.html
https://www.redhat.com/archives/linux-lvm/2014-November/msg00024.html
http://askubuntu.com/questions/542656/lvm-vg-is-not-activated-during-system-boot
I have 2 VGs on my system, and for some reason, only one of them gets
activated during the initrd boot sequence, which doesn't have my root
LV, so my boot sequence halts with an initrd prompt.
When I get to the initrd BusyBox prompt, I can see my LVs are inactive
with "lvm lvscan" – then, "lvm vgchange -ay" brings them online. The
boot sequence continues as I exit the BusyBox prompt. The expected
behaviour would be that both VGs should activate automatically.
On LVM mailing list, I've been advised it may be a problem with Ubuntu
initrd scripts, hence I report this problem here. (I'm not sure if I'm
reporting it to the correct place by assigning it to "linux", but I
didn't find a package directly related to the initrd only, so I
assumed initrd scripts are maintained by the kernel team. If you think
it's an error, and know the correct package, please reassign!) Our
suspicion is, initrd prematurely issues "vgchange -ay" before all the
PVs come online. This makes sense.
I already tried to set the "rootdelay" kernel parameter to make initrd
wait longer for the boot LV to come up, but it didn't work. Note
however, it worked with previous kernel versions.
The problem came up when I upgraded to Utopic, and got kernel
vmlinuz-3.16.0-23-generic. When I boot with the old kernel from Trusty
(vmlinuz-3.13.0-37-generic), it works fine.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version
k3.16.0-23-generic.
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
'/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1c', '/dev/snd/pcmC1D0c',
'/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/hwC0D0',
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/timer'] failed with exit
code 1:
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.values: Error: [Errno 2] No such file or directory
Card1.Amixer.info: Error: [Errno 2] No such file or directory
Card1.Amixer.values: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=/dev/mapper/vmhost--vg-vmhost--swap0
InstallationDate: Installed on 2013-12-06 (354 days ago)
InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64
(20131016)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: WinFast 6150M2MA
Package: linux (not installed)
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-23-generic
root=/dev/mapper/hostname--vg-hostname--rootfs ro rootflags=subvol=@
rootdelay=300
ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
RelatedPackageVersions:
linux-restricted-modules-3.16.0-23-generic N/A
linux-backports-modules-3.16.0-23-generic N/A
linux-firmware 1.138
RfKill: Error: [Errno 2] No such file or directory
Tags: utopic utopic
Uname: Linux 3.16.0-23-generic x86_64
UnreportableReason: The report belongs to a package that is not installed.
UpgradeStatus: Upgraded to utopic on 2014-10-28 (28 days ago)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 01/19/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 686W1D28
dmi.board.name: 6150M2MA
dmi.board.vendor: WinFast
dmi.board.version: FAB2.0
dmi.chassis.type: 3
dmi.chassis.vendor: WinFast
dmi.modalias:
dmi:bvnPhoenixTechnologies,LTD:bvr686W1D28:bd01/19/2008:svnWinFast:pn6150M2MA:pvrFAB2.0:rvnWinFast:rn6150M2MA:rvrFAB2.0:cvnWinFast:ct3:cvr:
dmi.product.name: 6150M2MA
dmi.product.version: FAB2.0
dmi.sys.vendor: WinFast
---
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
DistroRelease: Ubuntu 14.10
InstallationDate: Installed on 2013-12-06 (355 days ago)
InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64
(20131016)
Package: linux (not installed)
ProcEnviron:
LANGUAGE=en_US:en
TERM=linux
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
Tags: utopic
Uname: Linux 3.18.0-031800rc6-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to utopic on 2014-10-28 (29 days ago)
UserGroups:
_MarkForUpload: True
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1396213/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
