The officially official Devuan Forum!

You are not logged in.

#1 2017-07-19 01:27:32

zenkaon
Member
Registered: 2017-07-17
Posts: 9  

Encrypted volume shutdown issue going from Jessie to ascii

Hi all,

I like to setup an encrypted volume with an LVM containing swap and /, as can be seen at:
https://ibb.co/iALmzk

When I boot in Jessie, I see this:
https://ibb.co/cb2MX5

This gives no problems on shutdown. However, once upgraded to ascii I see on boot:
https://ibb.co/c8SoC5
Note the additional line "WARNING: Failed to connect to lvmetad"

This results in a long shutdown time (2 minutes or so) with the screen looking like:
https://ibb.co/hYNAQQ

Any ideas?

This is really annoying on shutdown - it takes ages. The encrypted volume and LVM appear to work fine, indeed I'm typing this on the encrypted ascii system experiencing the shutdown problem.

Offline

#2 2017-07-22 00:40:14

zenkaon
Member
Registered: 2017-07-17
Posts: 9  

Re: Encrypted volume shutdown issue going from Jessie to ascii

This *feature* is discussed extensively at https://bugs.debian.org/cgi-bin/bugrepo … bug=791944, which seems to point the blame at udev.

The udev in strecth/ascci is 232-25, whereas in Buster/Ceres it's 234-1, with the changelog http://metadata.ftp-master.debian.org/c … _changelog suggesting that bug #791944 was fixed in udev 233.

After setting some pin priorities, apt-get -t ceres install udev, updated me to 234-1. I still get the annoying long shutdown, so this has not resolved the issue.

I've just put stretch back on my laptop with the same encrypted LVM partitioning as shown in the first image above, with udev 232-25, and I have no problems shutting down at all.

Incidentally, the "WARNING: Failed to connect to lvmetad" message is also present when stretch boots, so I think that's a red herring here.

Offline

#3 2018-04-10 16:04:11

Geoff 42
Member
Registered: 2016-12-15
Posts: 177  

Re: Encrypted volume shutdown issue going from Jessie to ascii

I am not using encrytion, but I am using LVM2 (for occasional use of Xen). Since upgrading from Jessie to Ascii, I am also seeing the WARNING: Failed to connect to lvmetad message. I can also see a message in daemon.log lvmetad[2207]: Failed to accept connection errno 11.. lvmetad does appear in a ps listing. messages report random: lvm: uninitialized urandom read (4 bytes read). There do appear to be some pauses in booting. I vaguely recall reading something about random being slower in order to get some good data.

Geoff

Offline

#4 2018-04-10 16:58:34

fsmithred
Administrator
Registered: 2016-11-25
Posts: 781  

Re: Encrypted volume shutdown issue going from Jessie to ascii

Similar issue, possible fix for delayed shutdown of encrypted system:
https://dev1galaxy.org/viewtopic.php?pid=8289#p8289

Offline

#5 2018-04-13 13:33:02

Geoff 42
Member
Registered: 2016-12-15
Posts: 177  

Re: Encrypted volume shutdown issue going from Jessie to ascii

If I have read the docs correctly, lvmetad is used to remember your lvm set-up, so that it can boot faster. If it can't talk to lvmetad, then lvm has to search the hardware itself, which is slower. lvmetad uses udev to get its information. As Ascii uses eudev instead of udev, the question must be, "has eudev been tested against lvmetad?"

Geoff

Offline

#6 2018-04-14 10:36:14

Geoff 42
Member
Registered: 2016-12-15
Posts: 177  

Re: Encrypted volume shutdown issue going from Jessie to ascii

A quick look around shows that there are rules in /lib/udev/rules.d/69-lvm-metad.rules so that it would appear that eudev is supposed to work with lvmetad.

Geoff

Offline

Board footer