Encrypted home partition no longer auto-mounts

English Install/Boot/Login
#1

My encrypted home partition stopped auto-mounting at boot. This occurred after a kernel panic forced a hard shut down. The system now boots to the login screen, after which I can reach tty1,mount the /home partition manually, and then everything is fine. I thought this may be a problem with my fstab configuration, but I can’t figure out what, or why this started happening after a hard shut down. I am running OpenSUSE Tumbleweed, kernel version 4.13.12-1-default.

Here are some relevant outputs:

blkid:


/dev/sda1: LABEL="SYSTEM_DRV" UUID="5E40244B40242BE9" TYPE="ntfs" PARTUUID="23beda74-01"
/dev/sda2: LABEL="NTFS-Data" UUID="1ABE933DBE93107D" TYPE="ntfs" PARTUUID="23beda74-02"
/dev/sda3: LABEL="Lenovo_Recovery" UUID="5ECE2FE0CE2FAEE9" TYPE="ntfs" PARTUUID="23beda74-03"
/dev/sda5: UUID="d2406634-49ef-430e-941f-d94be2590591" TYPE="crypto_LUKS" PARTUUID="23beda74-05"
/dev/sda6: UUID="149c33b6-18af-4ccc-9443-8de65b599cdb" TYPE="crypto_LUKS" PARTUUID="23beda74-06"
/dev/sdb1: LABEL="SYSTEM_DRV" UUID="D69C8E5A9C8E3551" TYPE="ntfs" PARTUUID="16ac31d6-01"
/dev/sdb2: LABEL="Windows7_OS" UUID="12B694F1B694D697" TYPE="ntfs" PARTUUID="16ac31d6-02"
/dev/sdb3: UUID="28aedd49-55d6-4d0c-a566-ddd97c13c1cd" TYPE="ext4" PTTYPE="dos" PARTUUID="16ac31d6-03"
/dev/sdb5: UUID="d9b479ee-5a99-437a-8fc0-85b64fd6af38" TYPE="ext4" PARTUUID="16ac31d6-05"
/dev/mapper/cr_swap_1: UUID="09dbb538-acc4-424f-86ce-dd42c2b95c51" TYPE="swap"
/dev/mapper/cr_home_1: UUID="47993fcf-2a5c-4775-8892-df76cb5c0ee4" TYPE="ext4"

/dev/sda5 is the partition that should be mounted to /home

/etc/crypttab:


# cr_home_1       /dev/disk/by-id/ata-ST9500420AS_5VJDK7SN-part5 none       none
cr_swap_1       /dev/disk/by-id/ata-ST9500420AS_5VJDK7SN-part6 none       none
cr_home_1       /dev/sda5            none       none

The first line was there originally. I ran the YaST partition configuration in case that would solve the problem. It generated the alternative entry for cr_home_1, which did not solve the problem.

/etc/fstab:


/dev/disk/by-id/ata-INTEL_SSDMAEMC080G2_CVSC129200Q9080D-part5 /                    ext4       acl,user_xattr,noatime,discard        1 1
/dev/mapper/cr_home_1 /home                ext4       noatime,acl,user_xattr,nofail 0 2
/dev/mapper/cr_swap_1 swap                 swap       defaults              0 0
/dev/disk/by-id/ata-INTEL_SSDMAEMC080G2_CVSC129200Q9080D-part3 /boot                ext4       acl,user_xattr,noatime,discard        1 2
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0

I don’t recall why those mount parameters are used for /home. Maybe they are causing the issue, but I’m hoping for advice before changing things.

The following command successfully mounts the partition to /home, after which I can log in and use the system normally:


mount /dev/mapper/cr_home_1 /home

Any help is appreciated!

#2

Others have reported something similar. I am not having any problems here. I’m using an encrypted LVM, which is a little different from what you are doing, so perhaps not a good comparison.

Maybe try this in “/etc/crypttab”, as the entry for “cr_home_1”.


cr_home_1       UUID=d2406634-49ef-430e-941f-d94be2590591  none       none

I don’t know whether that will fix the problem. But it is worth a try. Just comment out the existing line, and insert this as a replacement.

And if that does help, then try a similar change for your swap partition. Note that I got that UUID from the “blkid” output that you posted. (I hope I got if from the correct partition).

#3

I modified the “/etc/crypttab” entries for the home and swap partitions as you suggested, but unfortunately neither changed the system behavior. Whether the partitions are referred to by device or by UUID, everything appears to work, except cr_home_1 is not mounted to /home at boot, despite the entry appearing correct in “/etc/fstab”. I updated to the latest Tumbleweed snapshot, and the problem persists.

#4

I suggest that you file a bug report on this.

You can use this link: Submitting Bug Reports