[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot
im not sure, but looks the problem i have here is the same problem 14.04 gave up waiting for root device common problems: --boot arts (cat /proc/cmdline) -check root delay (did the system wait long enough?) -check root (did the system wait for the right device?) -missing modules ls/dev ALERT! /dev/mapper/ubuntu-vg-root noes not exist! droping to a shell. budt box 1.21.1 (ubuntu 1.1.21.0-1ubuntu1) built-in-shell (ash) enter 'help' for a list of built-in- commants (initramfs) on a live cd> ubuntu@ubuntu:~$ sudo lvm lvscan ACTIVE'/dev/ubuntu-vg2/root' [929.36 GiB] inherit ubuntu@ubuntu:~$ sudo mkdir /newroot ubuntu@ubuntu:~$ sudo mount /dev/ubuntu-vg2/root /newroot mount: special device /dev/ubuntu-vg2/root does not exist -- 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: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in lvm2 package in Ubuntu: Fix Released 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
[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot
** 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 -- 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: Fix Released Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in lvm2 package in Ubuntu: Fix Released 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:
[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot
I have this problem as well on my 14.04.2 Dom0 cloud1. The VG that holds all VMs does not come up active on boot so no VMs set to autostart are started. I have another 14.04.2 which is on matching hardware and configured very similar to cloud1. It reboots and starts up the VMs properly. like this one but without LVM snapshots. This seems to basically mean that servers with LVM snapshots can not be counted on to boot properly and activate the VG. Please reply and let me know if this understanding is incorrect. -- 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 initramfs-tools package in Ubuntu: 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
[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot
I don't get this bug. I have at least 1 snapshot going on my /home partition all the time. The VG that /home is in contains most of my partitions (26), with 2 more partitions on a separate (VG+PD's) VG. Now, I've noticed when I am booting, it *does* take a bit of time to mount bring up and mount all of the lvs, but you can the root mount is NOT in an VG/LV -- It's on a regular device (numbers on left are w/kernel time printing turned on -- so they are in seconds after boot): [4.207621] XFS (sdc1): Mounting V4 Filesystem [4.278746] XFS (sdc1): Starting recovery (logdev: internal) [4.370757] XFS (sdc1): Ending recovery (logdev: internal) [4.379839] VFS: Mounted root (xfs filesystem) on device 8:33. .. [4.449462] devtmpfs: mounted ... last msg before my long pause where pretty much everything get activated: [4.591580] input: Dell Dell USB Keyboard as /devices/pci:00/:00:1a.7/usb1/1-3/1-3.2/1-3.2:1.0/0003:413C:2003.0002/input/input4 [4.604588] hid-generic 0003:413C:2003.0002: input,hidraw1: USB HID v1.10 Keyboard [Dell Dell USB Keyboard] on usb-:00:1a.7-3.2/input0 [ 19.331731] showconsole (170) used greatest stack depth: 13080 bytes left [ 19.412411] XFS (sdc6): Mounting V4 Filesystem [ 19.505374] XFS (sdc6): Ending clean mount more mostly unrelated messages... then you start seeing dm's mixed in with the mounting messages -- just before kernel logging stops: [ 22.205351] XFS (sdc2): Mounting V4 Filesystem [ 22.205557] XFS (sdc3): Mounting V4 Filesystem [ 22.216414] XFS (dm-5): Mounting V4 Filesystem [ 22.217893] XFS (dm-6): Mounting V4 Filesystem [ 22.237345] XFS (dm-1): Mounting V4 Filesystem [ 22.245201] XFS (dm-8): Mounting V4 Filesystem [ 22.267971] XFS (dm-13): Mounting V4 Filesystem [ 22.293152] XFS (dm-15): Mounting V4 Filesystem [ 22.299737] XFS (sdc8): Mounting V4 Filesystem [ 22.340692] XFS (sdc2): Ending clean mount [ 22.373169] XFS (sdc3): Ending clean mount [ 22.401381] XFS (dm-5): Ending clean mount [ 22.463974] XFS (dm-13): Ending clean mount [ 22.474813] XFS (dm-1): Ending clean mount [ 22.494807] XFS (dm-8): Ending clean mount [ 22.505380] XFS (sdc8): Ending clean mount [ 22.544059] XFS (dm-15): Ending clean mount [ 22.557865] XFS (dm-6): Ending clean mount [ 22.836244] Adding 8393924k swap on /dev/sdc5. Priority:-1 extents:1 across:8393924k FS Kernel logging (ksyslog) stopped. Kernel log daemon terminating. - A couple of things different about my setup from the 'norm' -- 1) since my distro(openSuSE) jumped to systemd, (and I haven't), I had to write some rc scripts to help bring up the system. 2) one reason for this was my /usr partition is separate from root and my distro decided to move many libs/bins -usr and leave symlinks on the root device to the programs in /usr. One of those was 'mount' (and its associated libs). That meant that once the rootfs was booted I had no way to mount /usr, where most of the binaries are (I asked why they didn't do it the safe way and move most of the binaries to /bin /lib64 and put symlinks in /usr but they evaded answering that question for ~2 years . So one script I run after updating my system is a dependency checker that checks mount orders and tries to make sure that early mounted disks don't have dependencies on later mounted disks. 3) adding to my problem was that I don't use an initrd to boot. I boot from my hard disk. My distro folks thought they had solved the problem by hiding the mount of /usr in the initrd, so when they start systemd to control the boot, it is happy. But if you boot from HD, I was told my ~15 year old configuration was no longer supported. Bleh!, One thing that might account for speed diffs, is that I don't wait for udev to start my VG's, ... and here is where I think I see my ~15 second pause: if test -d /etc/lvm -a -x /sbin/vgscan -a -x /sbin/vgchange ; then # Waiting for udev to settle if [ $LVM_DEVICE_TIMEOUT -gt 0 ] ; then echo Waiting for udev to settle... /sbin/udevadm settle --timeout=$LVM_DEVICE_TIMEOUT fi echo Scanning for LVM volume groups... /sbin/vgscan --mknodes echo Activating LVM volume groups... /sbin/vgchange -a y $LVM_VGS_ACTIVATED_ON_BOOT mount -c -a -F ... So at the point where I have a pause, I'm doing vgscan and vgchange, then a first shot at mounting all (it was the easiest thing to fix/change). Without that mount all attempt in my 4th boot script to execute -- boot.lvm, I often had long timeouts in the boot process. But as you can see, I tell mount to go fork(-F) and try to mount all FS's at the same time. I'm pretty sure that's where the pause is given that right after the pause, XFS starts issuing messages about DM's being mounted. Somewhere around script #8 is my distro's localfs mounts -- but for me, that was way too late, since many of the boot utils not only used /usr, but /usr/share (another partition after
[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot
@Astara: Now, I've noticed when I am booting, it *does* take a bit of time to mount bring up and mount all of the lvs, but you can the root mount is NOT in an VG/LV -- It's on a regular device (numbers on left are w/kernel time printing turned on -- so they are in seconds after boot): [ 4.207621] XFS (sdc1): Mounting V4 Filesystem [ 4.278746] XFS (sdc1): Starting recovery (logdev: internal) [ 4.370757] XFS (sdc1): Ending recovery (logdev: internal) [ 4.379839] VFS: Mounted root (xfs filesystem) on device 8:33. If I understand you well, you have your root FS on a regular partition, thus you are not affected by this bug, as partitions don't need to be „activated”. You need to have your root FS on an LV to be affected. if test -d /etc/lvm -a -x /sbin/vgscan -a -x /sbin/vgchange ; then # Waiting for udev to settle if [ $LVM_DEVICE_TIMEOUT -gt 0 ] ; then echo Waiting for udev to settle... /sbin/udevadm settle --timeout=$LVM_DEVICE_TIMEOUT fi echo Scanning for LVM volume groups... /sbin/vgscan --mknodes echo Activating LVM volume groups... /sbin/vgchange -a y $LVM_VGS_ACTIVATED_ON_BOOT mount -c -a -F Well, this is some interesting stuff. At first I thought you quoted it from an initrd script, but then I read you don't use an initrd. So where this script comes from? Did you write it, or is it shipped with the distro? Maybe the timeouts can be tweaked to allow a longer activation time, and it is also sane to only allow the root VG to activate at boot time and then activating the data VG later (probably asynchronously), after the root LV was successfully mounted. -- 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 initramfs-tools package in Ubuntu: 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
[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot
With the knowledge that the hang is caused by snapshots, some googling has brought up some duplicates: https://bugs.launchpad.net/lvm2/+bug/360237 https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/995645 It seems the issue was hanging around since 2009 or earlier. In Trusty (or probably even earlier distros) it was possible to work around by setting a sufficiently long rootdelay, and eventually all the LVs in all VGs came online. But since Utopic, initrd gives up altogether. No matter how long my rootdelay is, my 2nd VG never gets activated after the snapshot came online in the 1st VG. -- 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 initramfs-tools package in Ubuntu: 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
[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot
Got an interesting reply from the Red Hat LVM mailing list: https://www.redhat.com/archives/linux-lvm/2015-March/msg00022.html Haven't tested the suggestion yet. -- 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 initramfs-tools package in Ubuntu: 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 ---
[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot
Turns out, the suggested --setactivationskip option is not present in Utopic, as Utopic comes with an LVM version which dates back to 2012 (2.02.98(2) (2012-10-15)), while the feature was implemented in 2013. Vivid will come with a newer LVM: 2.02.111(2) (2014-09-01). Activation skip could be a nice workaround if it would be backported. -- 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 initramfs-tools package in Ubuntu: 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:
[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot
** Changed in: initramfs-tools (Ubuntu) Importance: Undecided = High ** Changed in: hundredpapercuts Importance: Medium = High -- 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 initramfs-tools package in Ubuntu: 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
[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot
** Also affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Changed in: initramfs-tools (Ubuntu) Status: New = Confirmed -- 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 initramfs-tools package in Ubuntu: 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 ---
[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot
Now I have some more info about this. What actually makes the VG activation so long is that I have a snapshot. Activating the snapshot takes very long, and bringing up the entire VG takes about 5 minutes. This wouldn't be such a big problem, as I could just patiently wait for the activation (with rootdelay). But I think the problem is that something kills vgchange before it could finish bringing up all VGs. I had the fortune to boot a developmental Vivid, and I've seen some 'watershed' messages stating that 'vgchange' was killed because it was taking too long. If we'd let 'vgchange' to finish properly, I had the 2nd VG, which contains my root FS. -- 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
[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot
Alberto Salvia Novella, thanks for the QA, and helpful suggestion. From my understanding, the Ubuntu Kernel Team prefers to mark reports like these High (not sure why I marked it Medium initially, probably was on auto-pilot) as defined in https://wiki.ubuntu.com/Bugs/Bug%20importances : Makes a default Ubuntu installation generally unusable for some users ... if the system fails to boot ... on a certain make and model of computer If this was reproducible across multiple hardware types, and affected a large group of users, I would agree it better fits the criteria of Critical. Despite this, let this be marked High across all the marked packages, and the UKT/root package maintainers may mark it further as they see fit. ** Changed in: linux (Ubuntu) Importance: Medium = High ** Changed in: lvm2 (Ubuntu) Importance: Medium = High -- 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
[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lvm2 (Ubuntu) Status: New = Confirmed -- 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 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
[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot
@ 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:
[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot
MegaBrutal, you may want to ping an lvm2 maintainer about this. As per https://launchpad.net/ubuntu/+source/lvm2/+changelog the most recent person to commit to this is Dave Chiluk chi...@canonical.com . ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- 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 linux package in Ubuntu: Confirmed Status in lvm2 package in Ubuntu: New 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 ---
[Touch-packages] [Bug 1396213] Re: LVM VG is not activated during system boot
I've had a backup of my old Trusty system, and I've built an initrd for 3.16.0-23-generic in that environment. With that initrd, the kernel booted properly. Note, still it takes several minutes for the VG to activate, but it eventually comes up if the kernel waits enough with rootdelay=300. Now, kernel bisection would take me to nowhere, as it seems the problem is not with the kernel itself. Any initrd I build under Utopic has the symptom, even older kernels from the 3.13 series. Could you advise how could I investigate further? I have no idea how could I debug/bisect initrd-s. As I found, the lvm2 package hasn't changed between Trusty and Utopic, so it's not lvm2's initrd scripts themselves. ** Also affects: lvm2 (Ubuntu) Importance: Undecided Status: New -- 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 linux package in Ubuntu: Incomplete Status in lvm2 package in Ubuntu: New 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:
