While waiting for a solution, the following workaround seems to work for
Stretch at least:
Step 1.)
Copy /usr/share/initramfs-tools/scripts/local-top/cryptroot to
/etc/initramfs-tools/scripts/local-top/cryptroot.
# cp /usr/share/initramfs-tools/scripts/local-top/cryptroot \
/etc/initramfs-tools/scripts/local-top/
Step 2.)
Modify the copied version as follows:
--- /usr/share/initramfs-tools/scripts/local-top/cryptroot
2017-05-09 14:50:59.000000000 +0300
+++ /etc/initramfs-tools/scripts/local-top/cryptroot 2018-07-04
13:29:15.787061513 +0300
@@ -172,8 +172,9 @@
fi
# Detect and activate available volume groups
- /sbin/lvm vgscan
- /sbin/lvm vgchange -a y --sysinit
+ # Workaround: disable use of lvmetad since it's not running yet
+ /sbin/lvm vgscan --config 'global{use_lvmetad=0}'
+ /sbin/lvm vgchange -a y --sysinit --config 'global{use_lvmetad=0}'
return $?
}
In other words, add a --config 'global{use_lvmetad=0}' option to any LVM
commands that are executed before mounting the root filesystem and
starting lvmetad.
The modified version in /etc/initramfs-tools will override the
corresponding standard file in /usr/share/initramfs-tools.
Step 3.)
Rebuild your initramfs.
# update-initramfs -u -k $(uname -r)
--
matti.kurk...@fi.fujitsu.com Tel: 045 7880 5596 Mobile: 046 878 5596
Fujitsu Finland Oy FJ EMEIA DTS HI&NTS ST, EMEIA
