Web lists-archives.com

Re: What's going on with dm-crypt?!




On Mon, 24 Dec 2018 10:26:18 +0100
Pascal Hambourg <pascal@xxxxxxxxxxxxxxx> wrote:

> Le 24/12/2018 à 05:45, Celejar a écrit :
> > 
> > I have / on a luks volume, mounted with dm-crypt (automatically,
> > via /etc/fstab - /etc/crypttab). As recently as kernel 4.18.0-3,
> > everything was normal. With 4.19.0-1-amd64, the volume mounts, and the
> > system seems basically functional - but /dev/mapper is empty besides for
> > 'control'!
> (...)
> > Despite the fact that 'mount' shows that the dm-crypt mount is present:
> (...)
> > This situation causes update-initramfs to fail:
> > 
> > ~# update-initramfs -u
> > update-initramfs: Generating /boot/initrd.img-4.19.0-1-amd64
> > mkinitramfs: failed to determine device for /
> 
> I don't know what is going on, but as a workaround you can run
> 
> dmsetup mknodes
> 
> to try to create the missing nodes (actually symlinks to actual 
> /dev/dm-* device nodes) in /dev/mapper.

That works - thanks!

I also observe that running cryptsetup manually on a running 4.19
system (to open a different dm-crypt volume) properly creates
the /dev/mapper symlink.

Celejar