Arch Linux

aftsak

Member

Registered: 2014-08-04

Posts: 10

[SOLVED] Cannot mount luks home volume after grub upgrade

Good Morning Arch Community !

My laptop is setup with dual boot. After the last Windows update, my grub was broken (went straight into the rescue mode).
I re-installed grub (following https://wiki.archlinux.org/title/GRUB#Installation).
My system is booting again but now I cannot mount my encrypted home partition.

I did not change anything, I still have the same line in

/etc/security/pam_mount.conf.xml

<volume user="john" fstype="crypt" path="/dev/nvme0n1p7" mountpoint="/data" options="rw,relatime" />

When I login (with pam_mount debug enabled), I am getting this:

Oct 20 09:47:38 slim7 systemd[1]: Started Getty on tty3.
Oct 20 09:47:40 slim7 login[951]: (pam_mount.c:365): pam_mount 2.20: entering auth stage
Oct 20 09:47:41 slim7 systemd[1]: getty@tty2.service: Deactivated successfully.
Oct 20 09:47:41 slim7 systemd[1]: run-credentials-getty\x40tty2.service.mount: Deactivated successfully.
Oct 20 09:47:41 slim7 systemd[1]: getty@tty2.service: Scheduled restart job, restart counter is at 1.
Oct 20 09:47:41 slim7 systemd[1]: Started Getty on tty2.
Oct 20 09:47:43 slim7 login[951]: pam_systemd_home(login:auth): New sd-bus connection (system-bus-pam-systemd-home-951) opened.
Oct 20 09:47:43 slim7 login[951]: (pam_mount.c:568): pam_mount 2.20: entering session stage
Oct 20 09:47:43 slim7 login[951]: (mount.c:261): Mount info: globalconf, user=john <volume fstype="crypt" server="(null)" path="/dev/nvme0n1p7" mountpoint="/dat>
Oct 20 09:47:43 slim7 login[951]: (mount.c:675): Password will be sent to helper as-is.
Oct 20 09:47:43 slim7 login[951]: command: 'mount' '-t' 'crypt' '-orw,relatime' '/dev/nvme0n1p7' '/data'
Oct 20 09:47:43 slim7 login[951]: (mount.c:68): Messages from underlying mount program:
Oct 20 09:47:43 slim7 login[951]: (mount.c:72): /usr/bin/mount.crypt: No dmcrypt cipher specified (use -o cipher=xxx)
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 23 29 0:22 / /proc rw,nosuid,nodev,noexec,relatime shared:5 - proc proc rw
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 24 29 0:23 / /sys rw,nosuid,nodev,noexec,relatime shared:6 - sysfs sys rw
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 25 29 0:6 / /dev rw,nosuid,relatime shared:2 - devtmpfs dev rw,size=8070452k,nr_inodes=2017613,mode=755,inode64
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 26 29 0:24 / /run rw,nosuid,nodev,relatime shared:12 - tmpfs run rw,mode=755,inode64
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 27 24 0:25 / /sys/firmware/efi/efivars rw,nosuid,nodev,noexec,relatime shared:7 - efivarfs efivarfs rw
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 29 1 259:4 / / rw,relatime shared:1 - ext4 /dev/nvme0n1p4 rw
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 30 24 0:7 / /sys/kernel/security rw,nosuid,nodev,noexec,relatime shared:8 - securityfs securityfs rw
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 31 25 0:27 / /dev/shm rw,nosuid,nodev shared:3 - tmpfs tmpfs rw,inode64
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 32 25 0:28 / /dev/pts rw,nosuid,noexec,relatime shared:4 - devpts devpts rw,gid=5,mode=620,ptmxmode=000
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 33 24 0:29 / /sys/fs/cgroup rw,nosuid,nodev,noexec,relatime shared:9 - cgroup2 cgroup2 rw,nsdelegate,memory_rec>
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 34 24 0:30 / /sys/fs/pstore rw,nosuid,nodev,noexec,relatime shared:10 - pstore pstore rw
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 35 24 0:31 / /sys/fs/bpf rw,nosuid,nodev,noexec,relatime shared:11 - bpf bpf rw,mode=700
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 36 23 0:32 / /proc/sys/fs/binfmt_misc rw,relatime shared:13 - autofs systemd-1 rw,fd=39,pgrp=1,timeout=0,minpro>
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 37 25 0:20 / /dev/mqueue rw,nosuid,nodev,noexec,relatime shared:14 - mqueue mqueue rw
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 38 25 0:33 / /dev/hugepages rw,nosuid,nodev,relatime shared:15 - hugetlbfs hugetlbfs rw,pagesize=2M
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 39 24 0:8 / /sys/kernel/debug rw,nosuid,nodev,noexec,relatime shared:16 - debugfs debugfs rw
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 40 24 0:13 / /sys/kernel/tracing rw,nosuid,nodev,noexec,relatime shared:17 - tracefs tracefs rw
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 79 26 0:34 / /run/credentials/systemd-journald.service ro,nosuid,nodev,noexec,relatime,nosymfollow shared:18 - >
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 81 26 0:35 / /run/credentials/systemd-udev-load-credentials.service ro,nosuid,nodev,noexec,relatime,nosymfollow>
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 41 24 0:36 / /sys/fs/fuse/connections rw,nosuid,nodev,noexec,relatime shared:20 - fusectl fusectl rw
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 42 24 0:37 / /sys/kernel/config rw,nosuid,nodev,noexec,relatime shared:21 - configfs configfs rw
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 66 26 0:38 / /run/credentials/systemd-tmpfiles-setup-dev-early.service ro,nosuid,nodev,noexec,relatime,nosymfol>
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 68 26 0:39 / /run/credentials/systemd-tmpfiles-setup-dev.service ro,nosuid,nodev,noexec,relatime,nosymfollow sh>
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 70 26 0:40 / /run/credentials/systemd-sysctl.service ro,nosuid,nodev,noexec,relatime,nosymfollow shared:24 - tm>
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 43 29 0:41 / /efi rw,relatime shared:25 - autofs systemd-1 rw,fd=52,pgrp=1,timeout=120,minproto=5,maxproto=5,di>
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 45 29 0:42 / /tmp rw,nosuid,nodev shared:48 - tmpfs tmpfs rw,size=8085764k,nr_inodes=1048576,inode64
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 104 26 0:43 / /run/credentials/systemd-tmpfiles-setup.service ro,nosuid,nodev,noexec,relatime,nosymfollow share>
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 107 26 0:44 / /run/credentials/systemd-vconsole-setup.service ro,nosuid,nodev,noexec,relatime,nosymfollow share>
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 71 43 259:1 / /efi rw,nosuid,nodev,noexec,relatime,nosymfollow shared:327 - vfat /dev/nvme0n1p1 rw,fmask=0077,d>
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 172 26 0:57 / /run/user/968 rw,nosuid,nodev,relatime shared:384 - tmpfs tmpfs rw,size=1617152k,nr_inodes=404288>
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 279 172 0:58 / /run/user/968/gvfs rw,nosuid,nodev,relatime shared:397 - fuse.gvfsd-fuse gvfsd-fuse rw,user_id=9>
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 453 26 0:60 / /run/user/1000 rw,nosuid,nodev,relatime shared:421 - tmpfs tmpfs rw,size=1617152k,nr_inodes=40428>
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 241 26 0:47 / /run/credentials/getty@tty3.service ro,nosuid,nodev,noexec,relatime,nosymfollow shared:129 - tmpf>
Oct 20 09:47:43 slim7 login[951]: (mount.c:564): 251 26 0:48 / /run/credentials/getty@tty2.service ro,nosuid,nodev,noexec,relatime,nosymfollow shared:160 - tmpf>
Oct 20 09:47:43 slim7 login[951]: (pam_mount.c:522): mount of /dev/nvme0n1p7 failed
Oct 20 09:47:43 slim7 login[951]: command: 'pmvarrun' '-u' 'john' '-o' '1'
Oct 20 09:47:43 slim7 login[951]: (pam_mount.c:441): pmvarrun says login count is 3
Oct 20 09:47:43 slim7 login[951]: (pam_mount.c:660): done opening session (ret=0)

I am able to manually mount the encrypted volume:

cryptsetup luksOpen /dev/nvme0n1p6 data
cryptsetup -v status data

  type:    LUKS1
  cipher:  aes-xts-plain64
  keysize: 512 bits
  key location: dm-crypt
  device:  /dev/nvme0n1p6
  sector size:  512
  offset:  4096 sectors
  size:    1041270784 sectors
  mode:    read/write
Command successful.

I also tried to manually set the cipher in the pam_mount entry but it doesn't help.

Any idea ?

Last edited by aftsak (2024-10-20 07:59:22)

aftsak

Member

Registered: 2014-08-04

Posts: 10

Re: [SOLVED] Cannot mount luks home volume after grub upgrade

lol... issue solved. For some reason the partition scheme changed and now my encrypted home is located at /dev/nvme0n1p6 instead of /dev/nvme0n1p7.

Putting down all the logs in one page here helped me notice it !

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 23,447

Re: [SOLVED] Cannot mount luks home volume after grub upgrade

You should in general not rely on paths under /dev to remain stable and should opt for something more persistent wherever possible: https://wiki.archlinux.org/title/Persis … ice_naming