Your message dated Sat, 15 May 2021 06:09:37 -0700 (PDT) with message-id <[email protected]> and subject line Closing this bug (BTS maintenance for src:linux bugs) has caused the Debian Bug report #863843, regarding bugs.debian.org: Encrypted partition not accessible after resume to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 863843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863843 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: bugs.debian.org Severity: serious Justification: 4 Dear Maintainer, Hi, I am using Debian Stretch on a laptop with a HDD (/dev/sda) and an SSD (/dev/sdd). My swap and home partitions are encrypted with lvm. The ouput of lsblk is: NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 931.5G 0 disk ├─sda1 8:1 0 243M 0 part /boot ├─sda2 8:2 0 1K 0 part └─sda5 8:5 0 931.3G 0 part └─sda5_crypt 254:0 0 931.3G 0 crypt ├─pc--117--162--vg-root 254:1 0 893.6G 0 lvm /home └─pc--117--162--vg-swap_1 254:2 0 37.7G 0 lvm [SWAP] sdb 8:16 0 477G 0 disk └─sdb1 8:17 0 477G 0 part / For several weeks now I have been having issues after resume (both from RAM or from disk): my /home seems not to be accessible (at least for writing). This does not happen every time, but more something like once every 10 or 20 resume cycles. At first, I thought this was related to an initramfs-tools (0.129) update where it was mentioned that the RESUME variable had to be set in the configuration, but this should only affect resuming from disk. I however tried to set this to different values (the /dev/XXX, auto, none) but nothing changes with my issue. Since I also have a warning at boot time saying "Failing to connect to lvmetad" I set use_lvmetad = 0 in /etc/lvm/lvm.conf. Again, nothing changes. My /etc/crypttab reads as follows: sda5_crypt UUID=11a52b25-26f4-41ae-b52e-2aa5d0a4d35d none luks which seems OK since ls -l /dev/disk/by-uuid/ total 0 lrwxrwxrwx 1 root root 10 May 31 10:45 11a52b25-26f4-41ae-b52e-2aa5d0a4d35d -> ../../sda5 lrwxrwxrwx 1 root root 10 May 31 10:45 136599d4-9b3b-4a74-a0dc-6bc48fb227f3 -> ../../sda1 lrwxrwxrwx 1 root root 10 May 31 10:45 2b70ec10-751f-4670-8000-1c59d7307f29 -> ../../dm-2 lrwxrwxrwx 1 root root 10 May 31 10:45 98ae6177-1de0-4af2-b905-687df457f1ca -> ../../sdb1 lrwxrwxrwx 1 root root 10 May 31 10:45 d3415b5d-e1fe-4ce6-98c8-a8645f358524 -> ../../dm-1 Thanks -- System Information: Debian Release: 9.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---Hi This bug was filed for a very old kernel or the bug is old itself without resolution. If you can reproduce it with - the current version in unstable/testing - the latest kernel from backports please reopen the bug, see https://www.debian.org/Bugs/server-control for details. Regards, Salvatore
--- End Message ---
