"Warning": Failed to connect to lvmetad

turbo · 2019-12-30 20:31:27

Hello,

just new to Devuan with a fresh ASCII desktop install. Installation went smooth and after the first reboot I got the following warning message at boot time.

"Warning": Failed to connect to lvmetad. Falling back to internal scanning.

Booting is otherwise fine without any hick-ups. Too new to "try" something to get this message to disappear.
Any suggestions ?

Thank you.
Johannes

Altoid · 2019-12-31 10:45:47

Hello:

turbo wrote:

Any suggestions ?

I have not come across this and from what I have read, if the system boots without issues, it is just a harmless warning.
Maybe someone else knows better.

Cheers,

A.

HevyDevy · 2019-12-31 11:52:02

from reading up on this it sounds like a grub erroneous message. From the gentoo forum its quite possible this is the problem.

https://forums.gentoo.org/viewtopic-t-1 … art-0.html

That's a feature, not a fatal error. Internal scanning will work for some time yet.
When you install grub, it wants to consult /etc/mtab, which is missing in the chroot, since all the mounts happened and were recorded in the /etc/mtab outside the chroot.
/etc/mtab is not usually a file any more, its a symbolic link.

I wonder what the output of /etc/mtab is ?

cat /etc/mtab

and

ls /etc/mtab -l

Last edited by HevyDevy (2019-12-31 11:56:30)

Head_on_a_Stick · 2019-12-31 14:09:12

/etc/mtab should be a symlink to /proc/self/mounts

If you're not using LVM then remove the package and re-configure GRUB:

# apt purge lvm2
# update-grub

HevyDevy · 2019-12-31 14:19:02

Head_on_a_Stick wrote:

/etc/mtab should be a symlink to /proc/self/mounts
If you're not using LVM then remove the package and re-configure GRUB:
# apt purge lvm2
# update-grub

Im not using LVM but have the package installed and do not get this error. Im on Beowulf Refracta though.

I dont believe removing lvm2 is a solution head on a stick.

Head_on_a_Stick · 2019-12-31 14:22:15

HevyDevy wrote:

I dont believe removing lvm2 is a solution head on a stick.

Yeah, you're probably right. It was just a stab in the dark tbh.

HevyDevy · 2019-12-31 14:26:00

Head_on_a_Stick wrote:

HevyDevy wrote:
I dont believe removing lvm2 is a solution head on a stick.
Yeah, you're probably right. It was just a stab in the dark tbh.

Its probably something t do with os-prober.

turbo · 2019-12-31 17:32:21

HevyDevy wrote:

from reading up on this it sounds like a grub erroneous message. From the gentoo forum its quite possible this is the problem.
https://forums.gentoo.org/viewtopic-t-1 … art-0.html
That's a feature, not a fatal error. Internal scanning will work for some time yet.
When you install grub, it wants to consult /etc/mtab, which is missing in the chroot, since all the mounts happened and were recorded in the /etc/mtab outside the chroot.
/etc/mtab is not usually a file any more, its a symbolic link.
I wonder what the output of /etc/mtab is ?
cat /etc/mtab
the output is
cat /etc/mtab
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
udev /dev devtmpfs rw,nosuid,relatime,size=2055536k,nr_inodes=209431,mode=755 0 0
devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
tmpfs /run tmpfs rw,nosuid,noexec,relatime,size=413008k,mode=755 0 0
/dev/mapper/devuan--vg-root / ext4 rw,relatime,errors=remount-ro,data=ordered 0 0
tmpfs /run/lock tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k 0 0
pstore /sys/fs/pstore pstore rw,relatime 0 0
tmpfs /run/shm tmpfs rw,nosuid,nodev,noexec,relatime,size=826000k 0 0
/dev/sda1 /boot ext2 rw,relatime 0 0
/dev/mapper/devuan--vg-home /home ext4 rw,relatime,data=ordered 0 0
/dev/mapper/devuan--vg-tmp /tmp ext4 rw,relatime,data=ordered 0 0
/dev/mapper/devuan--vg-var /var ext4 rw,relatime,data=ordered 0 0
tmpfs /sys/fs/cgroup tmpfs rw,nosuid,nodev,noexec,mode=755 0 0
cgroup /sys/fs/cgroup/elogind cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/usr/lib/elogind/elogind-cgroups-agent,name=elogind 0 0
tmpfs /run/user/1000 tmpfs rw,nosuid,nodev,relatime,size=413004k,mode=700,uid=1000,gid=1000 0 0
and
ls /etc/mtab -l 

ls /etc/mtab -l
lrwxrwxrwx 1 root root 12 Dec 29 16:58 /etc/mtab -> /proc/mounts

As said earlier, this is a fresh install and I chose the LVM option at graphical install. And I finished with my desktop install using the xfce desktop.

Johannes

HevyDevy · 2020-01-01 06:29:31

Maybe run update-grub again and see if the message disappears.

sudo update-grub

Head_on_a_Stick · 2020-01-01 12:16:19

turbo wrote:

ls /etc/mtab -l
lrwxrwxrwx 1 root root 12 Dec 29 16:58 /etc/mtab -> /proc/mounts

That's strange, the Refracta beowulf beta also does that.

From my Debian buster system:

empty@E485:~ $ ls -l /etc/mtab
lrwxrwxrwx 1 root root 19 Sep 23 17:11 /etc/mtab -> ../proc/self/mounts
empty@E485:~ $

/proc/mounts is a symlink to /proc/self/mounts so for your system /etc/mtab is symlinked to a symlink, which doesn't sound right.

Does linking it correctly fix things?

cd /etc
# ln -sf ../proc/self/mounts mtab

EDIT: use the force, Luke.

Last edited by Head_on_a_Stick (2020-01-01 12:16:54)

HevyDevy · 2020-01-01 12:44:01

Hold on there head on a stick, there must be a good explanation of why /etc/mtab is symlinked to /proc/mounts ?

http://man7.org/linux/man-pages/man5/proc.5.html

Head_on_a_Stick · 2020-01-01 12:49:21

HevyDevy wrote:

there must be a good explanation of why /etc/mtab is symlinked to /proc/mounts ?

Probably so but that isn't the case for Debian buster and symlinking to another symlink just sounds wrong.

The content would be the same either way.

HevyDevy · 2020-01-01 12:53:15

Head_on_a_Stick wrote:

HevyDevy wrote:
there must be a good explanation of why /etc/mtab is symlinked to /proc/mounts ?
Probably so but that isn't the case for Debian buster and symlinking to another symlink just sounds wrong.
The content would be the same either way.

So far all ive been able to understand is that it is easier to have /etc/mtab symlinked to /proc/self/mounts in the case of loop devices / losetup. Debian buster uses systemd, so maybe there is a difference in devuan having these symlinks?

You may be right on this, sorry. Man page says....

/proc/mounts
              Before kernel 2.4.19, this file was a list of all the filesys‐
              tems currently mounted on the system.  With the introduction
              of per-process mount namespaces in Linux 2.4.19 (see
              mount_namespaces(7)), this file became a link to
              /proc/self/mounts, which lists the mount points of the
              process's own mount namespace.  The format of this file is
              documented in fstab(5).

Last edited by HevyDevy (2020-01-01 12:59:24)

rolfie · 2020-01-01 15:29:43

@OP: as you say you are using a LVM, then the message is normal. As long as the LVM finally is opened, everything is fine.

rolfie

turbo · 2020-01-01 19:42:41

Hey guys,

thank you for your feedback. I think I will leavei t as is for now, as all is running without problems.

Happy New Year to All.

Johannes

The officially official Devuan Forum!

#1 2019-12-30 20:31:27

"Warning": Failed to connect to lvmetad

#2 2019-12-31 10:45:47

Re: "Warning": Failed to connect to lvmetad

#3 2019-12-31 11:52:02

Re: "Warning": Failed to connect to lvmetad

#4 2019-12-31 14:09:12

Re: "Warning": Failed to connect to lvmetad

#5 2019-12-31 14:19:02

Re: "Warning": Failed to connect to lvmetad

#6 2019-12-31 14:22:15

Re: "Warning": Failed to connect to lvmetad

#7 2019-12-31 14:26:00

Re: "Warning": Failed to connect to lvmetad

#8 2019-12-31 17:32:21

Re: "Warning": Failed to connect to lvmetad

#9 2020-01-01 06:29:31

Re: "Warning": Failed to connect to lvmetad

#10 2020-01-01 12:16:19

Re: "Warning": Failed to connect to lvmetad

#11 2020-01-01 12:44:01

Re: "Warning": Failed to connect to lvmetad

#12 2020-01-01 12:49:21

Re: "Warning": Failed to connect to lvmetad

#13 2020-01-01 12:53:15

Re: "Warning": Failed to connect to lvmetad

#14 2020-01-01 15:29:43

Re: "Warning": Failed to connect to lvmetad

#15 2020-01-01 19:42:41

Re: "Warning": Failed to connect to lvmetad

Board footer