Comment 21 for bug 1768230
Revision history for this message
| sonicsteve (slougheed-bcs) wrote Re: [Bug 1768230] Re: Long time booting : Failed to connect to lvmetad. Falling back to device scanning. | #21 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
35a32c5
(Get the code!)
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 <email address hidden>
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:/
>
> 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-
> (a55353d837cbf7
> affected
> - xubuntu-
> (7c24318d3b1de1
> affected
> - ubuntu-
> (a7f5c7b0cdd0e9
> affected
>
> To manage notifications about this bug go to:
>
> https:/
>
--
Steve Lougheed
<email address hidden>
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.