$ uname -a Linux xyz-hppavilionnotebook 5.10.0-8-amd64 #1 SMP Debian 5.10.46-2 (2021-07-20) x86_64 GNU/Linux
7.7 GiB
Intel® Core™ i3-5157U CPU @ 2.50GHz × 4
Mesa Intel® Iris® Graphics 6100 (BDW GT3)
500.1 GB
PureOS 10
64-bit
3.38.5
Wayland
Attached boot.log{F827345}
I just did a fresh install onto a new HDD. I choose to encrypt the swap volume and got a peculiar set up with the boot timing out waiting for a phantom luks volume group. iirc, the swap partition was luks only with it showing as mounted as a separate volume with the gnome disks gui - unlike the luks root partition which showed as I expected as a luks partition with an ext4 partition beneath it (but, with swap beneath the unlocked luks). I'm really sorry about all this gui description.
I've deleted the swap partition and the luks partition it was under and started again. This is what I have now:
:~$ lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
sda
├─sda1 vfat FAT32 NO_LABEL 8C5E-B242 299.1M 0% /boot/efi
├─sda2 ext4 1.0 fe52a0e2-357b-4bb0-83bf-45bb7922d92f 913.7M 10% /boot
├─sda3 crypto_LUKS 1 04dfabd8-94fe-42e9-ad9c-c68111157f7c
│ └─luks-04dfabd8-94fe-42e9-ad9c-c68111157f7c
│ ext4 1.0 0f7135e4-c2a5-4001-9ef0-6d8270af25c2 412.5G 3% /
└─sda4 crypto_LUKS 1 1e3960f9-89fa-4ffb-a77e-c829d2f1ca73
└─luks-1e3960f9-89fa-4ffb-a77e-c829d2f1ca73
swap 1 edc868b4-996a-43bb-b6bb-264ab9c0e8a8 [SWAP]
sr0
:~$Which looks pretty sensible to me. I've come to that after manually editing fstab, crypttab and grub. Grub looks like this:
GRUB_DEFAULT=0 GRUB_HIDDEN_TIMEOUT=0 GRUB_HIDDEN_TIMEOUT_QUIET=true GRUB_TIMEOUT=1 GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian` GRUB_CMDLINE_LINUX_DEFAULT="quiet splash resume=/dev/mapper/luks-1e3960f9-89fa-4ffb-a77e-c829d2f1ca73" GRUB_CMDLINE_LINUX=""
The systems booting, suspending and resuming, but it's wasting 1'30" waiting for
Volume group "luks" not found Cannot process volume group luks
Attached also fstab{F827348} and crypttab{F827347} (btw, I did some editing of those files between the boot.log at 17:44:21 and 17:53:15).
Any ideas where this phantom lvm group comes from (if that's what it is):
:~$ sudo lvm vgscan :~$