Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #238523

Can't boot following re-install to LVM on LUKS [was: can't login via gdm]

From Morgan Read <mstuff@read.org.nz>
Newsgroups linux.debian.user
Subject Can't boot following re-install to LVM on LUKS [was: can't login via gdm]
Date 2021-08-11 16:10 +0200
Message-ID <CKX5E-3BP-19@gated-at.bofh.it> (permalink)
References <CKuwG-1HV-7@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Hi List,
Since my cry for (fairly minor) help here:
https://lists.debian.org/debian-user/2021/08/msg00461.html
I think I've dug myself into a bit of a deep hole.

After having overcome a fairly fundamental bug with calamares as described here:
https://github.com/calamares/calamares/issues/1564#issuecomment-846321060
And, (unnecessarily as it turned out) re-installed my system, I find
I'm unable to boot.  Instead of getting a password prompt for my luks
lvm partition, I get dropped to the shell with the following error:

cryptsetup: ERROR: luks-[some UUID]: cryptsetup failed, bad password or options?
/bin/cat: /crypto_keyfile.bin: No such file or directory
Nothing to read on input

In
(initramfs) /cryptroot/crypttab
There is
luks-[some UUID] UUID=[some UUID] /crypto_keyfile.bin luks,keyscript=/bin/cat

I can manually mount my my luks volume so:
cryptsetup open /dev/sda3 --type luks [some UUID]
Enter passphrase for /dev/sda3:
To here:
/dev/mapper/[some UUID]
But, from there the LVM LVs don't get mounted and if I exit to boot
then I get dropped back to the shell.  And, lvm2 doesn't seem to be in
initramfs.

I can reboot to the live install usb image and when I do:
sudo cryptsetup open /dev/sda3 --type luks [some UUID]
Enter passphrase for /dev/sda3:
>From the terminal, then the lvm on luks volumes pop up as expected
immediately decrypted, named under /dev/mapped/[some VG-LV-name],
/dev/[some VG]/[some LV], enumerated at /dev/dm-xyz etc and mounted
under /media/user/[partition label]

So, may be calamares has more than one bug with LVM on LUKS?  Or, as
the above bug only refers to LVM and not LUKS, perhaps I've done (or
not done) something silly during the install with calamares and LUKS
(though, it does seem a pretty pedestrian walk through of the install
process).

I guess, there's something not referenced in the initramfs?

Any pointers to a way back from Armageddon would be great :)

Thanks.
--
Morgan Read
E mstuff@read.org.nz
(GM)

Back to linux.debian.user | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

can't login via gdm Morgan Read <mstuff@read.org.nz> - 2021-08-10 09:40 +0200
  Re: can't login via gdm IL Ka <kazakevichilya@gmail.com> - 2021-08-10 12:40 +0200
    Re: can't login via gdm Zoltán Herman <zoltanhbz@gmail.com> - 2021-08-10 13:00 +0200
  Can't boot following re-install to LVM on LUKS [was: can't login via gdm] Morgan Read <mstuff@read.org.nz> - 2021-08-11 16:10 +0200
    Re: Can't boot following re-install to LVM on LUKS [was: can't login  via gdm] David Christensen <dpchrist@holgerdanske.com> - 2021-08-12 00:30 +0200
      Re: Can't boot following re-install to LVM on LUKS [was: can't login  via gdm] Morgan Read <morgan@read.nz> - 2021-08-16 16:50 +0200
        Re: Can't boot following re-install to LVM on LUKS [was: can't login  via gdm] "Andrew M.A. Cater" <amacater@einval.com> - 2021-08-16 17:20 +0200
          Re: Can't boot following re-install to LVM on LUKS [was: can't login  via gdm] Morgan Read <mstuff@read.org.nz> - 2021-08-19 12:30 +0200

csiph-web