[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I get this error on a new minimal VM install with all LVM disks except '/boot': -- root@img-ults18:/var/log# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:00 89.1M 1 loop /snap/core/8268 loop1 7:10 88.5M 1 loop /snap/core/7270 sda 8:001G 0 disk ├─sda1 8:101M 0 part └─sda2 8:20 1021M 0 part /boot sdb 8:16 0 32G 0 disk ├─VGroot-LVroot 253:007G 0 lvm / ├─VGroot-LVtmp253:103G 0 lvm /tmp ├─VGroot-LVvar253:204G 0 lvm /var ├─VGroot-LVvartmp 253:303G 0 lvm /var/tmp ├─VGroot-VGlog253:404G 0 lvm /var/log ├─VGroot-LVaudit 253:502G 0 lvm /var/log/audit ├─VGroot-LVswap 253:604G 0 lvm [SWAP] └─VGroot-LVhome 253:705G 0 lvm /home sr011:01 1024M 0 rom root@img-ults18:/var/log# pvs PV VG Fmt Attr PSize PFree /dev/sdb VGroot lvm2 a-- <32.00g0 root@img-ults18:/var/log# vgs VG #PV #LV #SN Attr VSize VFree VGroot 1 8 0 wz--n- <32.00g0 root@img-ults18:/var/log# lvs -a LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert LVaudit VGroot -wi-ao 2.00g LVhome VGroot -wi-ao <5.00g LVroot VGroot -wi-ao 7.00g LVswap VGroot -wi-ao 4.00g LVtmpVGroot -wi-ao 3.00g LVvarVGroot -wi-ao 4.00g LVvartmp VGroot -wi-ao 3.00g VGlogVGroot -wi-ao 4.00g -- ... 0 packages can be updated. 0 updates are security updates. No mail. Last login: Thu Jan 9 21:09:04 2020 from 137.82.124.99 root@img-ults18:~# root@img-ults18:~# apt-get install selinux Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: policycoreutils selinux-policy-dummy selinux-utils The following packages will be REMOVED: apparmor snapd The following NEW packages will be installed: policycoreutils selinux selinux-policy-dummy selinux-utils 0 upgraded, 4 newly installed, 2 to remove and 0 not upgraded. Need to get 544 kB of archives. After this operation, 62.7 MB disk space will be freed. Do you want to continue? [Y/n] Get:1 http://mirror.it.ubc.ca/ubuntu bionic/universe amd64 selinux-utils amd64 2.7-2build2 [81.7 kB] Get:2 http://mirror.it.ubc.ca/ubuntu bionic/universe amd64 policycoreutils amd64 2.7-1 [450 kB] Get:3 http://mirror.it.ubc.ca/ubuntu bionic/universe amd64 selinux all 1:0.11 [11.2 kB] Get:4 http://mirror.it.ubc.ca/ubuntu bionic/universe amd64 selinux-policy-dummy all 0.1 [1,730 B] Fetched 544 kB in 0s (7,670 kB/s) Preconfiguring packages ... ... (Reading database ... 102901 files and directories currently installed.) Removing snapd (2.42.1+18.04) ... Removing apparmor (2.12-4ubuntu5.1) ... Selecting previously unselected package selinux-utils. (Reading database ... 102812 files and directories currently installed.) Preparing to unpack .../selinux-utils_2.7-2build2_amd64.deb ... Unpacking selinux-utils (2.7-2build2) ... Selecting previously unselected package policycoreutils. Preparing to unpack .../policycoreutils_2.7-1_amd64.deb ... Unpacking policycoreutils (2.7-1) ... Selecting previously unselected package selinux. Preparing to unpack .../selinux_1%3a0.11_all.deb ... Unpacking selinux (1:0.11) ... Selecting previously unselected package selinux-policy-dummy. Preparing to unpack .../selinux-policy-dummy_0.1_all.deb ... Unpacking selinux-policy-dummy (0.1) ... Setting up selinux-utils (2.7-2build2) ... Setting up selinux-policy-dummy (0.1) ... Setting up policycoreutils (2.7-1) ... selinux-autorelabel-mark.service is a disabled or a static unit, not starting it. Setting up selinux (1:0.11) ... Sourcing file `/etc/default/grub' Generating grub configuration file ... File descriptor 3 (pipe:[34729]) leaked on vgs invocation. Parent PID 2167: /usr/sbin/grub-probe File descriptor 3 (pipe:[34729]) leaked on vgs invocation. Parent PID 2167: /usr/sbin/grub-probe File descriptor 3 (pipe:[34729]) leaked on vgs invocation. Parent PID 2172: /usr/sbin/grub-probe File descriptor 3 (pipe:[34729]) leaked on vgs invocation. Parent PID 2172: /usr/sbin/grub-probe File descriptor 3 (pipe:[34729]) leaked on vgs invocation. Parent PID 2177: /usr/sbin/grub-probe File descriptor 3 (pipe:[34729]) leaked on vgs invocation. Parent PID 2177: /usr/sbin/grub-probe File descriptor 3 (pipe:[34729]) leaked on vgs invocation. Parent PID 2182: /usr/sbin/grub-probe File descriptor 3
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Resolved by tossing the entire VM and then performing a fresh install of the latest Ubuntu Desktop 18.04 with default deviations: - minimal installation - NO LVM (this is the default selection) - do NOT install updates while installing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
2019 May 15 Ubuntu 18.04 (VM snapshot) - works well. 2019 Sep 04: $ sudo apt update && sudo apt upgrade -y ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.0.0-27-generic I: The initramfs will attempt to resume from /dev/dm-1 I: (/dev/mapper/ubuntu--vg-swap_1) I: Set the RESUME variable to override this. /etc/kernel/postinst.d/zz-update-grub: Sourcing file `/etc/default/grub' Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.0.0-27-generic Found initrd image: /boot/initrd.img-5.0.0-27-generic Found linux image: /boot/vmlinuz-4.18.0-15-generic Found initrd image: /boot/initrd.img-4.18.0-15-generic Found memtest86+ image: /boot/memtest86+.elf Found memtest86+ image: /boot/memtest86+.bin done Processing triggers for initramfs-tools (0.130ubuntu3.8) ... update-initramfs: Generating /boot/initrd.img-5.0.0-27-generic I: The initramfs will attempt to resume from /dev/dm-1 I: (/dev/mapper/ubuntu--vg-swap_1) I: Set the RESUME variable to override this. Processing triggers for dbus (1.12.2-1ubuntu1.1) ... $ sudo reboot Baseline: Fail: ``` WARNING: Failed to connect to lvmetad. Falling back to device scanning. WARNING: Failed to connect to lvmetad. Falling back to device scanning. /dev/mapper/ubuntu--vg-root: clean, 1934309/4136960 files, 1775141/16522240 blocks ``` Test 00: # Drop into the shell with ctrl+alt+f3 sudo rm /etc/initramfs-tools/conf.d/resume sudo update-initramfs -u sudo reboot Result: Fail Test 01: # Drop into the shell with ctrl+alt+f3 sudo rm /etc/initramfs-tools/conf.d/resume sudo reboot Result: Fail Test 02: # Add this RESUME config sudo vim /etc/initramfs-tools/conf.d/resume RESUME=/dev/mapper/ubuntu--vg-swap_1 # Update sudo update-initramfs -u Result: Fail ** Attachment added: "Screen Shot 2019-09-04 at 10.01.10 PM.png" https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+attachment/5286901/+files/Screen%20Shot%202019-09-04%20at%2010.01.10%20PM.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
This is really crippling. Please help! I can't work! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I'm experiencing this on Linux Mint 19.1 fully updated and NOT encrypted disk or home. This is an LVM install though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I'm having the same problem as @morozov-ml. Starting from recovery mode seems to work though. This seems to be caused by an update because I've reverted to an old backup which boots just fine, but after installing updates it hangs after entering the LUKS password just like before. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I've tried to boot up the recently upgraded Ubuntu Disco system in the text mode and found, that the delay happens after the script: 1. fails to connect to lvmetad 2. falls back to device scanning 3. probes for btrfs. I DO NOT have any btrfs volumes in the system so I would like to simply avoid this step. I'd like to keep the ability to hibernate/resume though, that's why I'd prefer to keep all configuration options needed for RESUME. I will continue to experiment and probably will take a look into the booting script, but maybe the information gathered so far will be useful for someone. Installed packages [probably related to the problem]: initramfs-tools_0.131ubuntu19 initramfs-tools-bin_0.131ubuntu19 initramfs-tools-core_0.131ubuntu19 lvm2_2.02.176-4.1ubuntu4 udisks2-lvm2_2.8.2-1 systemd_240-6ubuntu5 btrfs-progs_4.20.2-1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
This looks likely to be some kind of incompatibility with full-disk encrypted systems. I just spotted that the errors I am getting are not about the swap partition at all, but instead about /dev/mapper/xubuntu --vg-root, which is the encrypted root. From /etc/fstab: /dev/mapper/xubuntu--vg-root / ext4errors=remount-ro 0 1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I'm on "Ubuntu 19.04" (disco), with initramfs-rools at version 0.131ubuntu19, and this is still broken for me. lvdisplay gives /dev/xubuntu-vg/swap_1 as the swap logical volume path and dzVm4y-Xeh5-o9UB-jLnI-0ldX-azSN-9w6QZq as the UUIS. I've tried separately with /etc/initramfs-tools/conf.d/resume as RESUME=UUID=dzVm4y-Xeh5-o9UB-jLnI-0ldX-azSN-9w6QZq and RESUME=/dev/xubuntu-vg/swap_1 and RESUME=none each time running sudo update-initramfs after updating the resume file. But, I always get a 30 second delay and the following in boot.log at the following boot: WARNING: Failed to connect to lvmetad. Falling back to device scanning. Volume group "xubuntu-vg" not found Cannot process volume group xubuntu-vg WARNING: Failed to connect to lvmetad. Falling back to device scanning. Reading all physical volumes. This may take a while... Found volume group "xubuntu-vg" using metadata type lvm2 WARNING: Failed to connect to lvmetad. Falling back to device scanning. 2 logical volume(s) in volume group "xubuntu-vg" now active /dev/mapper/xubuntu--vg-root: clean, 465752/30736384 files, 67280723/122926080 blocks WARNING: Failed to connect to lvmetad. Falling back to device scanning. Volume group "xubuntu-vg" not found ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Then I tried to download ubuntu-18.04.2 LTS Desktop image, and did a fresh installation. Over there I couldn't find the lvmetad problem during startup. Then I checked the kernel it installed with HWE - 4.18.0.15 and initramfs-tools - 0.130ubuntu3.6 version. Then tried to download 4.15.0.46 generic kernel and removed the HWE kernel and then rebooted and see the issue persists. Then tried to install initramfs-tools - 0.130ubuntu3.7 version with 4.15.0.46 generic kernel then the issue resolved. But in my #92 , i tried with ubuntu-18.04.1 LTS desktop image and installed only initramfs-tools - 0.130ubuntu3.7 over there the delay issue still persist. So my question, even in my case fresh installation of 18.04.2 works fine even after installed initramfs-tools 3.7 vers. But in fresh installation of 18.04.1 failed after installed initramfs-tools 3.7 vers. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Issue still persists in initramfs-tools - 0.130ubuntu3.7 version $18.04.1 LTS (Bionic Beaver)" $4.15.0-46-generic $dpkg -l | grep initramfs-tools ii initramfs-tools0.130ubuntu3.7 ii initramfs-tools-bin0.130ubuntu3.7 ii initramfs-tools-core 0.130ubuntu3.7 $cat /etc/initramfs-tools/conf.d/resume RESUME=UUID=115a16f5-bb9a-4ff2-a7b7-cf143deefcd4 RESUME=auto / none works fine as a workaround. Also removing this file "/etc/initramfs-tools/conf.d/resume " also fixed the issue. I tested on virtual box. tested with 4.15.0.29 generic kernel also. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
18.04 and mint 19 x64 newly installed 5 notebooks with ssd have. alex@NOUT:~$ systemd-analyze time Startup finished in 10.388s (kernel) + 8.148s (userspace) = 18.536s graphical.target reached after 8.134s in userspace REAL STARTUP TIME 5 MINUTES! it's really annoy mint 18 n ubuntu 16 work normal.(without systemd?) systemd-analyze blame 6.416s NetworkManager-wait-online.service 3.319s dev-sda1.device 1.700s vboxdrv.service [x]alex@NOUT:~$ /etc/initramfs-tools/conf.d/resume bash: /etc/initramfs-tools/conf.d/resume: Нет такого файла или каталога создал no file resume, i create it,update initramfs, but it not helped me [x]systemctl disable fstrim.timer -this too not helped me [x]install new kernel - not helped alex@NOUT:~$ uname -a Linux NOUT 5.0.0-05rc1-generic #201901062130 SMP Mon Jan 7 02:32:47 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux alex@NOUT:~$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
This bug was fixed in the package initramfs-tools - 0.130ubuntu3.7 --- initramfs-tools (0.130ubuntu3.7) bionic; urgency=medium [ Steve Langasek ] * hooks/resume: cherry-pick patch from upstream git to fix auto-configuration of resume devices that are on LVM; always refer to them by name, never by UUID. LP: #1768230. [ Thadeu Lima de Souza Cascardo ] * Do not include graphical drivers when FRAMEBUFFER is not set. (LP: #1561643) -- Brian Murray Thu, 17 Jan 2019 12:26:22 -0800 ** Changed in: initramfs-tools (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Finaly I was able to get rid of the 30s delay. TL;DR 1. Changed RESUME=UUID=... to RESUME=none in /etc/initramfs-tools/conf.d/resume (removing the file didn't help) 2. sudo update-initramfs -u --- I've got a custom LVM layout. $ cat /etc/lsb-release DISTRIB_ID=neon DISTRIB_RELEASE=18.04 DISTRIB_CODENAME=bionic DISTRIB_DESCRIPTION="KDE neon User Edition 5.15" $ uname -r 4.15.0-45-generic $ sudo apt-cache policy initramfs-tools initramfs-tools: Installed: 0.130ubuntu3.6 Candidate: 0.130ubuntu3.6 ... $ sudo cat /etc/initramfs-tools/conf.d/resume RESUME=none $ sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-4.15.0-45-generic $ With "RESUME=UUID..." in /etc/initramfs-tools/conf.d/resume: [3.418544] Btrfs loaded, crc32c=crc32c-intel [3.487208] BTRFS: device fsid ... devid 1 transid 272021 /dev/mapper/vg_00-lv_root [ 34.587759] BTRFS info (device dm-0): disk space caching is enabled With "RESUME=none" in /etc/initramfs-tools/conf.d/resume: [3.422572] Btrfs loaded, crc32c=crc32c-intel [3.487216] BTRFS: device fsid ... devid 1 transid 272833 /dev/mapper/vg_00-lv_root [3.501201] BTRFS info (device dm-0): disk space caching is enabled Hope it helps someone. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Bug persists on 18.04.2 with kernel 4.18.05-15 and initframfs-tools 130ubuntu3.6. Kernel was upgraded via the HWE stack -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Well, if you're a LVM user i recommend to leave ubuntu/debian. I know this sounds somewhat hard, but this nasty bug inside the ramdisk mouning script exist now more or less since a year! I can't accept a 30 seconds delay on boot for nothing and moved on to other distros. Yes you can fix it inside the script which will be copied, but with a new package the file will be overwritten without any warning or save/new file. Time to untrack this bug now. Good luck! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Hello Steve, > * still showing WARNING:Failed to connect to lvmetad. Falling back to device scanning. > That is NOT the defining symptom of the bug. This message would always be shown. The question is whether there is an unreasonable and unnecessary boot delay after the message is displayed. I have followed the same steps as Marc Pignat (who you quoted) and can confirm that I am still getting the problem. To clarify, I am getting the same unreasonable and unnecessary boot delay after the message is displayed, as I was getting before upgrading the package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Affects me on Ubuntu Budgie 18.04.2 after manually upgrading the kernel to 4.20.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
This bug was fixed in the package ubiquity - 18.04.14.11 --- ubiquity (18.04.14.11) bionic; urgency=medium [ Steve Langasek ] * scripts/plugininstall.py: don't hard-code a resume partition in /etc/initramfs-tools/conf.d/resume at install time. In bionic and later, initramfs-tools will autodetect an appropriate resume partition at initramfs generation time, so ubiquity's resume setting is redundant and possibly wrong. LP: #1768230. -- Dimitri John Ledkov Mon, 21 Jan 2019 20:25:03 + ** Changed in: ubiquity (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
> * still showing WARNING:Failed to connect to lvmetad. Falling back to device scanning. That is NOT the defining symptom of the bug. This message would always be shown. The question is whether there is an unreasonable and unnecessary boot delay after the message is displayed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Installed system using latest bionic daily, which contains ubiquity 18.04.14.11. There is no /etc/initramfs-tools/conf.d/resume file created, and grepping for RESUME= setting, there are none hardcoded. ** Tags removed: verification-needed verification-needed-bionic ** Tags added: verification-done verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
On 29/01/2019 13.44, Marc Pignat wrote: > If I understand well, ubiquity is the installer, so the iso image must > be tested. > > Where can I find a 18.04-daily iso image? As I understand it (might be wrong), the normal daily ISO is not the correct one to test with because it is not based on the /proposed/ repository. The correct procedure is documented here: https://wiki.ubuntu.com/Testing/EnableProposed#Installation_testing_using_-proposed Looks like there are no normal ISOs available. Thus there is a requirement to set up a netboot environment, which is documented here: https://help.ubuntu.com/community/Installation/Netboot However, the expected location for the /proposed/ netboot installer does not have recent enough version to include this fix: http://archive.ubuntu.com/ubuntu/dists/bionic-proposed/main/installer-amd64/ Maybe it will appear there at a later time... Janne Snabb sn...@epipe.com -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Hello Brian, On 1/26/19 12:47 AM, Brian Murray wrote: > Hello Marc, or anyone else affected, > > Accepted ubiquity into bionic-proposed. The package will build now and > be available at > https://launchpad.net/ubuntu/+source/ubiquity/18.04.14.11 in a few > hours, and then in the -proposed repository. If I understand well, ubiquity is the installer, so the iso image must be tested. Where can I find a 18.04-daily iso image? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Similar issue appears when zram swap is used, see bug #1781746 This bug is already fixed in Debian initramfs-tools ver 0.132, please accept this simple 3 lines patch from Debian into Ubuntu 18.04 LTS https://salsa.debian.org/kernel-team/initramfs-tools/commit/312393b0cf1231125eeff3d1a2b6b778a935c21d -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
** Tags removed: rls-bb-incoming rls-cc-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Hello Marc, or anyone else affected, Accepted ubiquity into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubiquity/18.04.14.11 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: ubiquity (Ubuntu Bionic) Status: New => Fix Committed ** Tags removed: verification-failed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Hello Łukasz, The problem persists. * installed sha256sum ubuntu-18.04.1-desktopmd64.iso (5748706937539418ee5707bd538c4f5eabae485d17aa49fb13ce2c9b70532433) * used update-manager to enable proposed-update * sudo apt-get update * sudo apt-get install initramfs-tools (initramfs-tools is now in version 0.130ubuntu3.7) * reboot * still showing WARNING:Failed to connect to lvmetad. Falling back to device scanning. Best regards Marc ** Tags added: verification-failed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Hello Marc, or anyone else affected, Accepted initramfs-tools into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.130ubuntu3.7 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: initramfs-tools (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-failed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
** Changed in: initramfs-tools (Ubuntu Bionic) Assignee: (unassigned) => Brian Murray (brian-murray) ** Changed in: initramfs-tools (Ubuntu Bionic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
** Changed in: initramfs-tools (Ubuntu Bionic) Milestone: None => ubuntu-18.04.2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I'm in 18.10 Adding my volume to the resume file with RESUME=/dev/mapper/ubuntu-swap doesn't work. Something to add to my story, /etc/initramfs-tools/conf.d/resume did not exist until I created it after reading this. Also, I had started using /var/swap/swap.img file for swap, could that have anything to do with it? My booting time is far greater than 30seconds. It just takes about 3 to 4 minutes if not more. Any help is greatly appreciated. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Hey Dennis, the value you put in RESUME variable must match your logical volume path. /dev/vg_system/lv_swap matches mine, but yours might be different. Check with lvdisplay what is the name of your logical volume and then use it inside the resume file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
my /etc/initramfs-tools/conf.d/resume file contains one line RESUME=UUID=99a2d3b2-0f29-4080-977c-35a5744279a8 I have tried several suggestions in this thread but I haven't found anything that works. I tried RESUME=/dev/vg_system/lv_swap then I ran the update-initramfs -u, as suggested. I got this: update-initramfs: Generating /boot/initrd.img-4.15.0-43-generic W: initramfs-tools configuration sets RESUME=/dev/vg_system/lv_swap W: but no matching swap device is available. I: The initramfs will attempt to resume from /dev/dm-1 I: (UUID=99a2d3b2-0f29-4080-977c-35a5744279a8) I: Set the RESUME variable to override this. I'm not what to do from here. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Just as an additional confirmation, having the full LVM device path inside /etc/initramfs-tools/conf.d/resume like: RESUME=/dev/vg_system/lv_swap and running: sudo update-initramfs -u fixed the issue (also) for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I'm still on 18.04, but this problem remains for me, as well. Grub with noresume doesn't work RESUME=none doesn't work RESUME=/dev/mapper/ubuntu-root doesn't work RESUME=/dev/mapper/ubuntu-swap doesn't work -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I upgraded to ubuntu 18.10 last night, and I had this problem all over again. Grub with noresume doesn't work RESUME=none doesn't work RESUME=/dev/mapper/ubuntu-root doesn't work RESUME=/dev/mapper/ubuntu-swap doesn't work changing /etc/initramfs-tools/conf.d/resume to none or to any lvm volume doesn't work. I always have the lvmetad can't connect, and then the kernel tries to find DHCP leases (now I actually have messages about it unlike 18.04). After a lonnng while it ends up booting. Is there any way I can do a grub boot to stop trying to boot from the network? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
System: Ubuntu 18.04 4.15.0-42-generic #45-Ubuntu SMP I also was able to fix it with the "=none" and then running update- initramfs -u -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I have this exact same problem too. Upgraded from 16.04 (which ran just fine) to 18.04, now get a 30 second delay before boot, with this "failed to connect to lvmetad. Falling back to device scanning Gave up waiting for suspend/resume" error. Not sure what help I can be at this point, but should anybody think they could do with additional data in this regard, give me a shout. I have logged a question about the problem here: https://askubuntu.com/questions/1097013/error-on-boot-failed-to-connect-to-lvmetad-after-18-04-install -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
tl;dr: initramfs-tools 0.130ubuntu3.5 and running update-initramfs -u seems to have fixed it. I have been putting up with this problem for months, thinking it was due to a kernel update (from 4.13 to 4.15). Finally, I find this thread today. Anyhow, here's my info: OS: Linux Mint 19 (based on Ubuntu 18.04) Kernel: 4.18.15-041815-generic kernel initramfs-tools version: 0.130ubuntu3.5 LVM root and swap partitions setup during install Symptom: waiting 30 sec during boot, with message "failed to connect to lvmetad" ... "falling back". After reading previous comments, I did following: sudo vim /etc/initramfs-tools/conf.d/resume .. changed from RESUME=UUID=e6675202-6e2f-4c1b-b6e6-4ffe3ef7c882 .. to RESUME=/dev/mint-vg/swap_1 sudo update-initramfs -u ,, (this indicated that it would only apply to latest kernel, not older ones, which is what I wanted in case it borked my boot) reboot It now boots without the 30sec delay, but does display a message about "[something something] disabled by BIOS" or somesuch. This seems to override the mint logo that would normally display during boot if one did not press del to see boot messages. Note that I only guessed that RESUME=/dev/mint-vg/swap_1 would work, since I do want to be able to resume from sleep, but not sure if that's the correct syntax for the resume file, but it is a valid symlink for my swap partition, the alternatives being /dev/dm-1 and /dev/mapper/mint--vg-swap_1. Resume from sleep still works, not sure if it'd affected by this anyhow. Finally, I apologise if reporting on mint 19 is not welcome/appropriate here, but it is based on ubuntu 18.04 and I did have relevant info to contribute. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Seems okay now, after typing exit and following the commands to run the (fsck.ext4 /dev/mapper... something) command that it had listed and following the prompt to fix. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Yes can’t boot into system after updating this morning. Initramfs Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
After the update to the latest available version of the package .. initramfs-tools/bionic-updates,bionic-updates,now 0.130ubuntu3.5 all [installed] the problem still exists! Distributor ID: Ubuntu Description: Ubuntu 18.04.1 LTS Release: 18.04 Codename: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I agree. It appears that version 0.130ubuntu3.3 is broken again. When looking at the changelog here: http://changelogs.ubuntu.com/changelogs/pool/main/i/initramfs-tools /initramfs-tools_0.130ubuntu3.3/changelog ...and comparing it to the changelog at: http://changelogs.ubuntu.com/changelogs/pool/main/i/initramfs-tools /initramfs-tools_0.130ubuntu3.2/changelog ...it looks like the Steve Langasek's fixes introduced in version 0.130ubuntu3.2 to fix this bug are lost in package version 0.130ubuntu3.3. ** Changed in: initramfs-tools (Ubuntu Bionic) Status: Fix Committed => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I can confirm that the bug is back in initramfs-tools 0.130ubuntu3.3 (it was OK with 0.130ubuntu3.2) The difference is even visible when running update-initramfs -u -k all (on 3.2 you see LVM name, on 3.3 you see UUID). with initramfs-tools 0.130ubuntu3.2: update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-4.15.0-34-generic I: The initramfs will attempt to resume from /dev/dm-1 I: (/dev/mapper/vg_system-lv_swap) I: Set the RESUME variable to override this. => no delay while booting and with initramfs-tools 0.130ubuntu3.3: update-initramfs -u -k all update-initramfs: Generating /boot/initrd.img-4.15.0-34-generic I: The initramfs will attempt to resume from /dev/dm-1 I: (UUID=c2849fd0-bfeb-11e8-82df-e63cc106402d) I: Set the RESUME variable to override this. => delay 30s while booting -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
After the update to the latest available version of the package .. initramfs-tools/bionic-updates,bionic-updates,now 0.130ubuntu3.3 all [installed] the problem still exists! Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Hi, I am running Lubuntu 18.04 with LVM as a VM in VirtualBox 5.2.18 r124319. I encountered the above problem and I triedusing guillermo suggestion of 1. editing /etc/initramfs-tools/conf.d/resume to RESUME=none 2. regenerating initramfs with sudo update-initramfs -u and it seems to fix it for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I have installed a fresh system (Ubuntu 18.04, with LVM) on a virtual machine and this machine is also affected. I have updated the initramfs-tools to version: 0.130ubuntu3.3 but this doesnt solve the issue. Other things i have done without success: 1.) Delete resume file: > rm /etc/initramfs-tools/conf.d/resume > sudo update-initramfs -u 2.) Change resume file: > vim /etc/initramfs-tools/conf.d/resume RESUME=none > sudo update-initramfs -u 3.) Another change to the resume file: > vim /etc/initramfs-tools/conf.d/resume RESUME=auto > sudo update-initramfs -u -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I had the same problem after the update from 16.04 to 18.04. I was able to solve this with RESUME = none and sudo update-initramfs -u. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
For me it looks like, that steve's patch got lost in version 3.3 of initramfs-tools: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/0.130ubuntu3.3 When will this patch be released? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Is there a way to re-create the resume file? The commands I mentioned earlier removed it, so I can't try the edit option. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Used Ubuntu 18.04 in my 8 year old Toshiba Satellite L675 laptop for months without issues, progressed to 18.04.1, no problems, until upgraded to kernel 4.15.0-32-generic 2 days ago, then, same bug as described. only in my case the waiting didn't finished automatically so I had to manually hit the keyboard to obtain a message for press the Enter key to boot. I fixed it editing /etc/initramfs-tools/conf.d/resume to RESUME=none and then regenerating initramfs with sudo update- initramfs -u. Now I boot again without delays. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Same issue - only latest Ubunutu updates and OS (GUI based) as of today. Did following: > rm /etc/initramfs-tools/conf.d/resume > sudo update-initramfs -u Resume file is gone and issue still happens. Please help with any other solutions to this issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I tried today Aug 5, 2018 to upgrade from 16.04 to 18.04. I have been using 16.04 in this machine for the last 10 months without any issues. Installed from LiveCD. I did the upgrade not the LiveCD. It went through the entire upgrade/installation without any issues. It finished and asked to reboot. After it rebooted and after the Dell logo the screen went blank and I could see text popping up on the top left corner of the display, disappearing, popping up again. This repeats every 2-3 seconds. The message is "Gave up waiting for suspend/resume device /dev/sda2/: clean, 213855/14712832 files, 3013745/58847488 blocks". This message keeps appearing continuously. Did not wait 30 seconds to see if it rebooted (my fault for not being patient). I tried the 16.04 LiveCD to try to fix. Changed the conf.d resume to RESUME=none as suggested by someone, did not work. So had to do a clean re-install of 16.04 again. My machine is a Dell Inspiron 15 5000 series with Intel Core i5 8th Gen. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Ubuntu 18.04.1 It takes a long time to boot, then enter the password to unlock the disk. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
> rm /etc/initramfs-tools/conf.d/resume > sudo update-initramfs -u I tried this method, but the bug still exists -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Ubuntu 18.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
initramfs-tools-0.130ubuntu3.2 seems to remove the wait time on my system as well! What I did: > rm /etc/initramfs-tools/conf.d/resume > sudo update-initramfs -u -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I am using a custom LVM setup. Similar to what https://launchpad.net /~daniel-mehrmann described in https://bugs.launchpad.net/ubuntu/+source /initramfs-tools/+bug/1768230/comments/42. I've manually installed the debs from https://launchpad.net/ubuntu/+source/initramfs- tools/0.130ubuntu3.2/+build/15032391: initramfs-tools-bin_0.130ubuntu3.2_amd64.deb (13.3 KiB) initramfs-tools-core_0.130ubuntu3.2_all.deb (46.7 KiB) initramfs-tools_0.130ubuntu3.2_all.deb (9.1 KiB) $ apt list initramfs-tools -a Listing... Done initramfs-tools/now 0.130ubuntu3.2 all [installed,local] initramfs-tools/bionic-updates,bionic-updates 0.130ubuntu3.1 all initramfs-tools/bionic,bionic 0.130ubuntu3 all I've followed https://bugs.launchpad.net/ubuntu/+source/initramfs- tools/+bug/1768230/comments/45 and there's no 30s delay anymore. Thanks https://launchpad.net/~vorlon and others! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Hello everyone, I'm struggling for a few days to find a solution to my problem on a ubuntu 18.04 I have tried all the suggestions on many forums, but unfortunately I have not found a simple solution to solve this problem. I have recently upgraded Ubuntu 16.04 to Ubuntu 18.04 with enabling full disk encryption and with LVM. After this upgrade, every time I'm starting the machine, I see some messages appearing on the boot screen. (for more details, please see the attached photo) I need yours precious help, I hope someone help me with a simple solution! Please let me know, Dan. ** Attachment added: "bug screen" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1768230/+attachment/5163578/+files/lvm%20error.jpg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I ran into the same bug (30 sec boot delay) running Bionic with Mate desktop. The following steps solved the problem for now: 1. Edit /etc/initramfs-tools/conf.d/resume 2. Change as follows: RESUME=none 3. Run sudo update-initramfs -u 4. Reboot - no more delay -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I've tested this on a system while testing the other SRU that goes with this upload (bug 1769682). I don't have any delays with the SRU installed, and see no lvmetad warnings. I do have an /etc/initramfs- tools/conf.d/resume file that points to my swap partition, but that doesn't seem to adversely affect the behavior at all. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
May I add a comment to this bug as this was marked on bug 1763611 to be a duplicate of this. I can confirm comment #10 here. I got long boot time after upgrading from Ubuntu 16.04 LTS to 18.04 LTS but there was one release in between. I just followed the update announcements. I use Mate. I don't use LVM.1763611 I did solve my problem by editing /etc/initramfs-tools/conf.d/resume. You can also read my comments #30 and #31 on bug 1763611. Maybe you find it helpful. Andreas -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
@Steve I'm using another LVM setup, which i created manual while using Ubunuts live system ;-) I wrote this in my first comment already. But basicly i was the same problem with the "30 seconds" problem and my system falls back twice to scanning devices :-(. But to be honest, yes, i don't in this case and you can ignore me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
This bug was fixed in the package ubiquity - 18.10.4 --- ubiquity (18.10.4) cosmic; urgency=medium [ Chen-Han Hsiao (Stanley) ] * Add efivars to mountpoints loaded at bootloader install time. (LP: #1772374) [ Steve Langasek ] * scripts/plugininstall.py: don't hard-code a resume partition in /etc/initramfs-tools/conf.d/resume at install time. In bionic and later, initramfs-tools will autodetect an appropriate resume partition at initramfs generation time, so ubiquity's resume setting is redundant and possibly wrong. LP: #1768230. [ Łukasz 'sil2100' Zemczak ] * Make sure that grub-pc is not removed after installation for both EFI and legacy BIOS cases as we now technically need it even for EFI installs. (LP: #1775743) [ Mathieu Trudel-Lapierre ] * Automatic update of included source packages: grub-installer 1.128ubuntu9. -- Mathieu Trudel-Lapierre Mon, 25 Jun 2018 13:57:40 -0400 ** Changed in: ubiquity (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Daniel, Silvio, can you please confirm that your disk configuration matches that of Marc, with full-disk LVM selected at install time? It's possible you have boot delays due to some other cause. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Thanks! Now tested with versuion 3.2 and the bug is still there. :-( -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
https://wiki.ubuntu.com/Testing/EnableProposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Ooops, i was testing with version 3.1! Where can i get version 3.2? It's still not in the update channel -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I can confirm that the bug is still there with version 3.2! :-( I did "update-initramfs -u". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
On 06/25/2018 07:56 AM, Silvio Moioli wrote: > I can still reproduce the problem after upgrading to 3.2 and manually > deleting /etc/initramfs-tool/conf.d/resume. Help appreciated! > Did you run "initrams -u" after deleting the file? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I can still reproduce the problem after upgrading to 3.2 and manually deleting /etc/initramfs-tool/conf.d/resume. Help appreciated! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Please note that there is a change between 0.130ubuntu3.1 and 0.130ubuntu3.2 0.130ubuntu3.1 (/etc/initramfs-tool/conf.d/resume not deleted by hand) : 30s delay at boot 0.130ubuntu3.1 (/etc/initramfs-tool/conf.d/resume deleted by hand) : 30s delay at boot 0.130ubuntu3.2 (/etc/initramfs-tool/conf.d/resume not deleted by hand) : 30s delay at boot 0.130ubuntu3.2 (/etc/initramfs-tool/conf.d/resume deleted by hand) : no delay at boot Please note that once the /etc/initramfs-tool/conf.d/resume file has been removed neither 3.1 nor 3.2 will re-create it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
As you requested, the full output of sudo update-initramfs -u : pim@pim:~$ sudo update-initramfs -u [sudo] password for pim: update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic pim@pim:~$ After that the 30 second delay is still there. The warning messages only appears when I manually remove the /etc/initramfs-tool/conf.d/resume file. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1768230 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Upgrading initramfs-tools to 0.130ubuntu3.2 should be sufficient to resolve the symptom of this bug, even with a broken /etc/initramfs- tools/conf.d/resume still on disk. Marc, when you are able to still reproduce this bug with initramfs-tools 0.130ubuntu3.2, what is the full output of 'sudo update-initramfs -u'? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
If the output is that which you posted in comment #25: I: The initramfs will attempt to resume from /dev/dm-1 I: (/dev/mapper/xubuntu--vg-swap_1) ... then that is exactly what we *expect* to see as the output and it needs investigating why this does not take precedence over /etc /initramfs-tool/conf.d/resume for you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Tested http://cdimage.ubuntu.com/daily-live/20180620/cosmic-desktop- amd64.iso, which includes initramfs-tools 0.130ubuntu3.2. It is still affected. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
[Test case] 1. Install using the "Use LVM" option in the desktop installer. - installed using xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. - sure it does - file /etc/initramfs-tools/conf.d/resume exists 6. Install initramfs-tools from bionic-proposed. - file /etc/initramfs-tools/conf.d/resume still exists 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. - problem persists. apt list initramfs-tools Listing... Done initramfs-tools/bionic-proposed,bionic-proposed,now 0.130ubuntu3.2 all [installed] The workaround is to delete /etc/initramfs-tools/conf.d/resume. ** Tags added: verification-failed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Hello Marc, or anyone else affected, Accepted initramfs-tools into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/initramfs- tools/0.130ubuntu3.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: initramfs-tools (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
And this warning is not really reassuring: sudo update-initramfs -u update-initramfs: Generating /boot/initrd.img-4.15.0-20-generic I: The initramfs will attempt to resume from /dev/dm-1 I: (/dev/mapper/xubuntu--vg-swap_1) I: Set the RESUME variable to override this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
@vorlon, I can't get it work Tested that: [Test case] 1. Install using the "Use LVM" option in the desktop installer. 4. Reboot. 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. 6. Install initramfs-tools from bionic-proposed. Downloaded: initramfs-tools_0.130ubuntu10_all.deb initramfs-tools-bin_0.130ubuntu10_amd64.deb initramfs-tools-core_0.130ubuntu10_all.deb done : dpkg -i *.deb 7. Reboot. 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. 30 second delay still there /etc/initramfs-tools/conf.d/resume still exists If the file `/etc/initramfs-tools/conf.d/resume` is deleted manually, it is not re-created by update-initramfs -u -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
This bug was fixed in the package initramfs-tools - 0.130ubuntu10 --- initramfs-tools (0.130ubuntu10) cosmic; urgency=medium * Avoid redundant call to dmsetup. -- Steve Langasek Thu, 14 Jun 2018 22:26:51 -0700 ** Changed in: initramfs-tools (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
** Changed in: ubiquity (Ubuntu) Status: Triaged => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
** Merge proposal linked: https://code.launchpad.net/~vorlon/ubiquity/+git/ubiquity/+merge/348033 ** Merge proposal linked: https://code.launchpad.net/~vorlon/ubiquity/+git/ubiquity/+merge/348034 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
** Description changed: + [SRU Justification] + A regression in initramfs-tools causes it to autogenerate config in the initramfs saying to resume from any available swap devices, but references the swap device by UUID, which is not a canonical form for referring to LVM volumes (because of snapshotting, they are not unique). Ubiquity also generates a file in /etc at install time which references the swap partition in the same way. Since the lvm2 initramfs hooks also only activate precisely those LVs that are detected as needed at boot, this adds an inappropriate 30-second boot delay to any system with swap on LVM, which includes any desktop system that was configured with LVM (but not full-disk encryption) at install time. + + [Test case] + 1. Install using the "Use LVM" option in the desktop installer. + 4. Reboot. + 5. Verify that dmesg shows a 30-second delay before mounting the root filesystem. + 6. Install initramfs-tools from bionic-proposed. + 7. Reboot. + 8. Verify that dmesg no longer shows a 30-second delay before mounting the root filesystem. + 9. Install using the bionic daily image that contains the ubiquity from bionic-proposed. + 10. Reboot. + 11. Verify that /etc/initramfs-tools/conf.d/resume is not present and that there is no delay before mounting the root filesystem. + + [Regression potential] + This makes changes to shell scripts, and shell is a perilous language. An unnoticed bug could cause all initramfs generation, and thus all kernel installation, to fail for some users. A regression could also cause a user to lose hiberation support that they currently have. + + [Original description] After choosing "Erase disk and install ubuntu" + "Use LVM with the new Ubuntu installation", the system is very slow to reboot. It shows the message : "WARNING:Failed to connect to lvmetad. Falling back to device scanning.", then waits 32 seconds, then continues as it should. I think this is a ubiquity bug, since the d-i based installer is not affected. - - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected - - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected - - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected + - ubuntu-18.04-desktop-amd64.iso (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : affected + - xubuntu-18.04-desktop-amd64.iso (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : affected + - ubuntu-18.04-server-amd64.iso (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not affected -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
** Changed in: initramfs-tools (Ubuntu) Status: Confirmed => In Progress ** Changed in: initramfs-tools (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Two bugs: - ubiquity creates an /etc/initramfs-tools/conf.d/resume which lists the swap device by UUID; this is not the correct way to reference a device that's on LVM, and with the current lvm initramfs hooks it fails because it won't be found to be activated. - if /etc/initramfs-tools/conf.d/resume is absent, initramfs-tools itself auto-creates a file on update-initramfs -u that references the uuid. We need to fix both. I'm not sure if we should add some upgrade handling to detect broken /etc/initramfs-tools/conf.d/resume for this case and remove it on upgrade. ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Changed in: ubiquity (Ubuntu) Importance: Undecided => High ** Changed in: ubiquity (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
** Changed in: initramfs-tools (Ubuntu) Assignee: (unassigned) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
I should add that my system was an upgrade, using LVM with EXT4. I'm honestly debating about backing up, blowing it up and installing fresh without LVM, I'm not sure I see the advantage to using it. On Thu, Jun 14, 2018 at 10:31 AM Marc Pignat <1768...@bugs.launchpad.net> wrote: > This bug seems wrongly linked to ubiquity since updating the system can > also lead to the bug. Can someone find a better package to link this bug > to? the kernel? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1768230 > > Title: > Long time booting : Failed to connect to lvmetad. Falling back to > device scanning. > > Status in ubiquity package in Ubuntu: > Confirmed > > Bug description: > After choosing "Erase disk and install ubuntu" + "Use LVM with the new > Ubuntu installation", the > system is very slow to reboot. > > It shows the message : "WARNING:Failed to connect to lvmetad. Falling > back to device scanning.", > then waits 32 seconds, then continues as it should. > > I think this is a ubiquity bug, since the d-i based installer is not > affected. >- ubuntu-18.04-desktop-amd64.iso > (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : > affected >- xubuntu-18.04-desktop-amd64.iso > (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : > affected >- ubuntu-18.04-server-amd64.iso > (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not > affected > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1768230/+subscriptions > -- Steve Lougheed sloughee...@gmail.com BCS Junior High Computer Science 905-843-3771 This email, including any attachments, is for the sole use of the intended recipient and may contain confidential information. If you are not the intended recipient, please immediately notify us by reply email or by telephone, delete this email and destroy any copies. Thank-you. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
** Package changed: ubiquity (Ubuntu) => initramfs-tools (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
This bug seems wrongly linked to ubiquity since updating the system can also lead to the bug. Can someone find a better package to link this bug to? the kernel? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
** Tags added: rls-bb-incoming rls-cc-incoming -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Same bug here, firstly after upgrading from 17.10 to 18.04, then I installed fresh ubuntu from .iso - the same result. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Same bug after upgrading 16.04 to 18.04, using lvm with ext4 filesystem -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Same issue here, from a fresh install on Lenovo T460. I have tried to add "noresume" to the kernel command line as proposed here (https://askubuntu.com/questions/1034359/boot-hangs-for-30-seconds-at- begin-running-scripts-local-premount) but only got a tiny bit faster. Any other workaround? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Fresh install on my Laptop 18.04 and using lvm with ext4 filesystem. Boot is slowdown about 30 seconds while display the error message in bug desscription. I'm using a manual created lvm setup druing installation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
This bug also affects me; clean install of Bionic onto real hardware. Let me know if I can supply any data that would be helpful in debugging. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Facing the same issue with multiple clean installs of bionic on esxi hosts. The warning message persists even after adding `noresume` to the kernel command line! I also tried changing `use_lvmetad` to 0 in `/etc/lvm/lvm.conf` and removing `/etc/initramfs-tools/conf.d/resume` and updating initramfs with no luck! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
Happens to my install that is on older dell hardware, with a 120 GB SSD. Optiplex 3010 On Wed, May 23, 2018, 5:11 AM thinkpad, <1768...@bugs.launchpad.net> wrote: > Is this bug only occuring in a virtual setting (e.g. 17.10 to 18.04 in > VirtualBox) or also on non-virtual upgrade (from 17.10 to 18.04) ? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1768230 > > Title: > Long time booting : Failed to connect to lvmetad. Falling back to > device scanning. > > Status in ubiquity package in Ubuntu: > Confirmed > > Bug description: > After choosing "Erase disk and install ubuntu" + "Use LVM with the new > Ubuntu installation", the > system is very slow to reboot. > > It shows the message : "WARNING:Failed to connect to lvmetad. Falling > back to device scanning.", > then waits 32 seconds, then continues as it should. > > I think this is a ubiquity bug, since the d-i based installer is not > affected. >- ubuntu-18.04-desktop-amd64.iso > (a55353d837cbf7bc006cf49eeff05ae5044e757498e30643a9199b9a25bc9a34) : > affected >- xubuntu-18.04-desktop-amd64.iso > (7c24318d3b1de1efd584b5aea034ce1aafd2d0f06c59812d989a5fc95bf947e3) : > affected >- ubuntu-18.04-server-amd64.iso > (a7f5c7b0cdd0e9560d78f1e47660e066353bb8a79eb78d1fc3f4ea62a07e6cbc) : not > affected > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1768230/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning.
This bug exists on real machines, but it's far more easier to test in on a virtual one. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1768230 Title: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1768230/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
