LVM VG is not activated during system boot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
One Hundred Papercuts |
Fix Released
|
High
|
Unassigned | ||
initramfs-tools (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
lvm2 (Ubuntu) |
Fix Released
|
High
|
Unassigned |
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:/
https:/
http://
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-
---
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/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info: Error: [Errno 2] No such file or directory
Card0.Amixer.
Card1.Amixer.info: Error: [Errno 2] No such file or directory
Card1.Amixer.
DistroRelease: Ubuntu 14.10
HibernationDevice: RESUME=
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-
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
RelatedPackageV
linux-
linux-
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:bvnPhoenixT
dmi.product.name: 6150M2MA
dmi.product.
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-
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: Upgraded to utopic on 2014-10-28 (29 days ago)
UserGroups:
_MarkForUpload: True
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
description: | updated |
tags: | added: kernel-bug-exists-upstream kernel-bug-exists-upstream-3.18-rc6 |
Changed in initramfs-tools (Ubuntu): | |
status: | New → Confirmed |
Changed in initramfs-tools (Ubuntu): | |
importance: | Undecided → High |
Changed in hundredpapercuts: | |
importance: | Medium → High |
Changed in initramfs-tools (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in linux (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in lvm2 (Ubuntu): | |
status: | Confirmed → Fix Released |
Changed in hundredpapercuts: | |
status: | Confirmed → Fix Released |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 1396213
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.