Results 1 to 3 of 3

Thread: lvmetad is not active yet (message at boot)

  1. #1
    Join Date
    2016-Feb
    Posts
    1

    lvmetad is not active yet (message at boot)

    Hi,

    During boot I am getting the following message:

    lvmetad is not active yet, using direct activation during sysinit
    "disk/by-uuid-<snip>": Invalid path for Logical Volume.

    But I have no logical volumes on my system (Stretch on sdb). The system eventually boots and all is good, except for this message. At one time, I had installed lvm2 (it has since been removed) in Stretch on sdb because I had previously installed a version of Stretch on another drive (sda) that did use logical volumes. The Stretch on sda was using the swap area on sdb at the time and grub2 was and is still installed on sda so I can boot into either system. I have since reinstalled Stretch on sda using partitions rather than logical volumes. However I get the above message every time I boot into Stretch on sdb.

    It seems that sysinit is trying to mount a logical volume that is not there. The uuid in the message is the path for my root filesystem partition on sdb with mount point "/" and is not a logical volume.

    Hope this is clear. Would appreciate any suggestions you may have.

    thanks
    Last edited by haken29a; 2016-02-04 at 22:35. Reason: Title

  2. #2
    Thought I was the only person with this problem, there seems to be no discussion happening whatsoever anywhere about it...
    Are you running a dual-boot with GRUB like me? I assumed it was due to an error somewhere along the formatting/partitioning process, either when removing an old OS (I kicked out ubuntu and replaced it with Kali) or when installing the new one, however I have nowhere near enough partitioning know-how to go about troubleshooting it.
    Here's what I get...

    Warning: failed to connect to lvmetad , no such file or directory, falling back to internal scanning...
    It then gives the same spiel of "Invalid path for logical volume".
    While this isnt a catastrophic error by any means, its quite annoying as it happens on every single boot without fail, while my windows7 continues to boot fine.
    I hope we can get some tips on whats going on soon...

  3. #3
    Join Date
    2016-Sep
    Posts
    2

    Question

    Hello, I have the same message at boot. Searching I've found this:
    http://askubuntu.com/questions/76986...during-sysinit

    One person proposes:
    In /etc/default/grub, change:

    GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to
    GRUB_CMDLINE_LINUX_DEFAULT="nomodeset"

    Then add this line:

    GRUB_TERMINAL_INPUT="console serial"

    Run sudo update-grub and reboot for the changes to take effect.
    What do you think?

Similar Threads

  1. Replies: 0
    Last Post: 2020-09-27, 16:45
  2. Replies: 1
    Last Post: 2017-04-04, 05:01
  3. How to enable boot message log?
    By tr00n3r in forum TroubleShooting Archive
    Replies: 2
    Last Post: 2015-10-27, 17:30

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •