Page MenuHomePureOS Tracker
Create Task
Maniphest T537

Fails to connect to lvmetd on startup but still runs
Closed, InvalidPublic
Actions

Description

After the recent update, I get the following errors in boot.log

  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  Volume group "luks" not found
  Cannot process volume group luks
  WARNING: Failed to connect to lvmetad. Falling back to device scanning.
  Volume group "luks" not found
  Cannot process volume group luks
/dev/mapper/luks-2ad2d1b8-9969-4645-b888-82a3b3fcdbd3: clean, 502475/59850752 files, 28808448/239400242 blocks

After this pureOS starts normally has no further issues. The main problem here is that it has increased boot time by a few seconds

Event Timeline

• tasty created this task.Aug 8 2018, 10:42
• tasty created this object with edit policy "Subscribers".
jonas.smedegaard closed this task as Invalid.Sep 11 2018, 06:02
jonas.smedegaard added a subscriber: jonas.smedegaard.

Hi tasty,

Thanks for reporting this!

The warning about lvmetad is only cosmetic: lvm is started early, before the lvmetad daemon is running - which is by design, daemons are started only later, after the root filesystem is setup.

The few seconds is not time waiting for lvmetad, but time spent decrypting the root filesystem.

Closing as a non-issue.

NB! Please don't get discouraged by this: Your reporting issues is highly appreciated, and it is easy to close bugs so don't worry about the risk that you might report things that turn out not really to me an issue.

• tasty added a comment.Sep 11 2018, 09:37

Just to check is

volume group luks not found

Boot error another cosmetic thing or is there a problem in my fstab/crypttab (note computer boots fine)

jonas.smedegaard added a comment.Sep 11 2018, 10:33

Yes, it is harmless.

It is tracked (and likely fixed soon) upstream in Debian: https://bugs.debian.org/799295