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
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
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:
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
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
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
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 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 /
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
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
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-bin
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
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
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
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
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
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
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.
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,
> * 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
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:
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
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
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
** 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.
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
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
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
** 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
** 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.
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
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
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
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
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
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
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:
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
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
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.
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.
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
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:
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
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
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
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
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:
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
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
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
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
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
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
> 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 :
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
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.
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-
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
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
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
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
@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 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
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
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
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
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
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
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
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
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
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
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
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
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
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.
[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
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
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
@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:
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
** 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
** 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
** 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
** 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.
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
** 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
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
** 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
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.
** 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
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
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
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?
--
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,
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
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
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
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
1 - 100 of 111 matches
Mail list logo
