Bugzilla – Bug 1060156
Unable to unlock encrypt disk with latest systemd package
Last modified: 2017-10-30 14:29:46 UTC
Hi, On latest systemd package 228.35 or 228.32 Gnome screen that allow to enter decrypt password not appear. devmapper goes loop and fail at the end. Go back to systemd version 228.29 solve problem but i've got to lock the package to avoid any upgrade Best
(In reply to Nicolas Rochard from comment #0) > Hi, > > On latest systemd package 228.35 or 228.32 Gnome screen that allow to enter > decrypt password not appear. > devmapper goes loop and fail at the end. Re-assigned the bug to the systemd maintainers; GNOME is not responsible for unlocking devices; and as you already know that upgrading systemd causes it, there is no reason to believe GNOME would be involved > Go back to systemd version 228.29 solve problem but i've got to lock the > package to avoid any upgrade
Sorry for that mistake. It's because i've open some other bugs on the same template. Thanks for re-assigned it.
That does sound a duplicate of bsc#1046268.... But the fix should be released by now even for 42.3. On an affected version of systemd, can you try ? $ rpm -q --changelog udev | grep 1046268 If it prints the log entry that is supposed to fix the original issue then it's something else. In that case it would be better if you provide a better description of your issue and also provide the debug log when the problem is happening. You can enable the debug logs with appending "debug printk.devkmsg=on" on the kernel command line if the problem happens during the boot process.
ping
Yes I'm still here, I've got only one laptop, no backup computer is available and I must finish a project before risk to crash my OS. I try to do what you've ask Friday or next Monday. Please do not close this ticket. Thanks !
Hi, I've done fresh upgrade and problem still here. When i enter : rpm -q --changelog udev | grep 1046268 Here that i got : 7a4935268 compat-rules: drop the boggus 'import everything' rule (bsc#1046268) If activate debug mode in kernel, what could I copy paste here to help you ?
(In reply to Nicolas Rochard from comment #6) > If activate debug mode in kernel, what could I copy paste here to help you ? The output of "journalctl -b" after "devmapper goes loop and fail at the end." would be a good start. Also please describe your storage setup: which drives are involved, the device mapper stuff etc...
Here some information at boot : Oct 15 21:16:44 dev01-2017 kernel: snd_hda_intel 0000:00:1f.3: azx_get_response timeout, switching to polling mode: last cmd=0x208f8100 Oct 15 21:16:45 dev01-2017 kernel: snd_hda_intel 0000:00:1f.3: No response from codec, disabling MSI: last cmd=0x208f8100 Oct 15 21:16:46 dev01-2017 kernel: snd_hda_intel 0000:00:1f.3: azx_get_response timeout, switching to single_cmd mode: last cmd=0x208f8100 Oct 15 21:16:46 dev01-2017 kernel: azx_single_wait_for_response: 117 callbacks suppressed Oct 15 21:16:46 dev01-2017 kernel: snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f0d00. -5 Oct 15 21:16:46 dev01-2017 rtkit-daemon[2161]: Supervising 1 threads of 1 processes of 1 users. Oct 15 21:16:46 dev01-2017 rtkit-daemon[2161]: Successfully made thread 2175 of process 2160 (/usr/bin/pulseaudio) owned by 'gdm' RT at priority 5. Oct 15 21:16:46 dev01-2017 rtkit-daemon[2161]: Supervising 2 threads of 1 processes of 1 users. Oct 15 21:16:46 dev01-2017 rtkit-daemon[2161]: Supervising 2 threads of 1 processes of 1 users. Oct 15 21:16:46 dev01-2017 rtkit-daemon[2161]: Successfully made thread 2176 of process 2160 (/usr/bin/pulseaudio) owned by 'gdm' RT at priority 5. Oct 15 21:16:46 dev01-2017 rtkit-daemon[2161]: Supervising 3 threads of 1 processes of 1 users. Oct 15 21:16:46 dev01-2017 bluetoothd[997]: Endpoint registered: sender=:1.28 path=/MediaEndpoint/A2DPSource Oct 15 21:16:46 dev01-2017 bluetoothd[997]: Endpoint registered: sender=:1.28 path=/MediaEndpoint/A2DPSink Oct 15 21:16:46 dev01-2017 kernel: Bluetooth: RFCOMM TTY layer initialized Oct 15 21:16:46 dev01-2017 kernel: Bluetooth: RFCOMM socket layer initialized Oct 15 21:16:46 dev01-2017 kernel: Bluetooth: RFCOMM ver 1.11 Oct 15 21:16:46 dev01-2017 rtkit-daemon[2161]: Successfully made thread 2181 of process 2181 (/usr/bin/pulseaudio) owned by 'gdm' high priority at nice level -11. Oct 15 21:16:46 dev01-2017 rtkit-daemon[2161]: Supervising 4 threads of 2 processes of 1 users. Oct 15 21:16:46 dev01-2017 pulseaudio[2181]: [pulseaudio] pid.c: Daemon already running. Oct 15 21:16:47 dev01-2017 dbus[1022]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' Oct 15 21:16:47 dev01-2017 systemd[1]: Starting Location Lookup Service... Oct 15 21:18:07 dev01-2017 systemd[1]: dev-disk-by\x2did-\x2dTHNSN5512GPUK_NVMe_TOSHIBA_512GB_371B405QKSJU\x2dpart3.device: Job dev-disk-by\x2did-\x2dTHNSN5512GPUK_NV Oct 15 21:18:07 dev01-2017 systemd[1]: Timed out waiting for device dev-disk-by\x2did-\x2dTHNSN5512GPUK_NVMe_TOSHIBA_512GB_371B405QKSJU\x2dpart3.device. Oct 15 21:18:07 dev01-2017 systemd[1]: Dependency failed for Cryptography Setup for cr_home. Oct 15 21:18:07 dev01-2017 systemd[1]: Dependency failed for dev-mapper-cr_home.device. Oct 15 21:18:07 dev01-2017 systemd[1]: Dependency failed for /home. Oct 15 21:18:07 dev01-2017 systemd[1]: home.mount: Job home.mount/start failed with result 'dependency'. Oct 15 21:18:07 dev01-2017 systemd[1]: Dependency failed for File System Check on /dev/mapper/cr_home. Oct 15 21:18:07 dev01-2017 systemd[1]: systemd-fsck@dev-mapper-cr_home.service: Job systemd-fsck@dev-mapper-cr_home.service/start failed with result 'dependency'. Oct 15 21:18:07 dev01-2017 systemd[1]: Startup finished in 2.711s (kernel) + 2.107s (initrd) + 3min 433ms (userspace) = 8min 49.897s. Oct 15 21:18:07 dev01-2017 systemd[1]: dev-mapper-cr_home.device: Job dev-mapper-cr_home.device/start failed with result 'dependency'. Oct 15 21:18:07 dev01-2017 systemd[1]: systemd-cryptsetup@cr_home.service: Job systemd-cryptsetup@cr_home.service/start failed with result 'dependency'. Oct 15 21:18:07 dev01-2017 systemd[1]: dev-disk-by\x2did-\x2dTHNSN5512GPUK_NVMe_TOSHIBA_512GB_371B405QKSJU\x2dpart3.device: Job dev-disk-by\x2did-\x2dTHNSN5512GPUK_NV Oct 15 21:19:30 dev01-2017 kernel: pcieport 0000:00:1c.0: AER: Multiple Corrected error received: id=00e0 Oct 15 21:19:30 dev01-2017 kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e0(Transmitter ID) Oct 15 21:19:30 dev01-2017 kernel: pcieport 0000:00:1c.0: device [8086:a110] error status/mask=00003000/00002000 Oct 15 21:19:30 dev01-2017 kernel: pcieport 0000:00:1c.0: [12] Replay Timer Timeout Oct 15 21:19:30 dev01-2017 kernel: pcieport 0000:00:1c.0: AER: Multiple Corrected error received: id=00e0 Oct 15 21:19:30 dev01-2017 kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e0(Transmitter ID) Oct 15 21:19:30 dev01-2017 kernel: pcieport 0000:00:1c.0: device [8086:a110] error status/mask=00003000/00002000 Oct 15 21:19:30 dev01-2017 kernel: pcieport 0000:00:1c.0: [12] Replay Timer Timeout Oct 15 21:19:31 dev01-2017 kernel: pcieport 0000:00:1c.0: AER: Corrected error received: id=00e0 Oct 15 21:19:31 dev01-2017 kernel: pcieport 0000:00:1c.0: PCIe Bus Error: severity=Corrected, type=Data Link Layer, id=00e0(Transmitter ID) Oct 15 21:19:31 dev01-2017 kernel: pcieport 0000:00:1c.0: device [8086:a110] error status/mask=00001000/00002000 Oct 15 21:19:31 dev01-2017 kernel: pcieport 0000:00:1c.0: [12] Replay Timer Timeout My Laptop is a DELL XPS15 (2017) with Intel® Core™ i7-7700HQ CPU @ 2.80GHz × 8 16 Go RAM 512 SSD / partition is ext4 (non encrypted) /home partition is also in ext4 (encrypted) Filesystem Size Used Avail Use% Mounted on devtmpfs 7.7G 0 7.7G 0% /dev tmpfs 7.8G 68K 7.8G 1% /dev/shm tmpfs 7.8G 2.6M 7.8G 1% /run tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup /dev/nvme0n1p2 30G 11G 18G 37% / /dev/nvme0n1p1 496M 106M 391M 22% /boot/efi tmpfs 1.6G 12K 1.6G 1% /run/user/478 tmpfs 1.6G 24K 1.6G 1% /run/user/0
Nicolas, what's the version of dracut ? Also you probably get the emergency shell when it fails. If so, can you show the output of "ls -l /dev/disk/by-id" ? Thanks.
Franck, My Dracut version is latest : 044.1-26.1 Here's command you ask me to enter : dev01-2017:~ # ls -l /dev/disk/by-id total 0 lrwxrwxrwx 1 root root 13 Oct 23 15:36 nvme-200080d03000f9db7 -> ../../nvme0n1 lrwxrwxrwx 1 root root 15 Oct 23 15:36 nvme-200080d03000f9db7-part1 -> ../../nvme0n1p1 lrwxrwxrwx 1 root root 15 Oct 23 15:36 nvme-200080d03000f9db7-part2 -> ../../nvme0n1p2 lrwxrwxrwx 1 root root 15 Oct 23 15:36 nvme-200080d03000f9db7-part3 -> ../../nvme0n1p3 lrwxrwxrwx 1 root root 15 Oct 23 15:36 nvme-200080d03000f9db7-part4 -> ../../nvme0n1p4 lrwxrwxrwx 1 root root 15 Oct 23 15:36 nvme-200080d03000f9db7-part6 -> ../../nvme0n1p6 lrwxrwxrwx 1 root root 13 Oct 23 15:36 nvme-THNSN5512GPUK_NVMe_TOSHIBA_512GB_371B405QKSJU -> ../../nvme0n1 lrwxrwxrwx 1 root root 15 Oct 23 15:36 nvme-THNSN5512GPUK_NVMe_TOSHIBA_512GB_371B405QKSJU-part1 -> ../../nvme0n1p1 lrwxrwxrwx 1 root root 15 Oct 23 15:36 nvme-THNSN5512GPUK_NVMe_TOSHIBA_512GB_371B405QKSJU-part2 -> ../../nvme0n1p2 lrwxrwxrwx 1 root root 15 Oct 23 15:36 nvme-THNSN5512GPUK_NVMe_TOSHIBA_512GB_371B405QKSJU-part3 -> ../../nvme0n1p3 lrwxrwxrwx 1 root root 15 Oct 23 15:36 nvme-THNSN5512GPUK_NVMe_TOSHIBA_512GB_371B405QKSJU-part4 -> ../../nvme0n1p4 lrwxrwxrwx 1 root root 15 Oct 23 15:36 nvme-THNSN5512GPUK_NVMe_TOSHIBA_512GB_371B405QKSJU-part6 -> ../../nvme0n1p6 lrwxrwxrwx 1 root root 13 Oct 23 15:36 nvme-eui.00080d03000f9db7 -> ../../nvme0n1 lrwxrwxrwx 1 root root 15 Oct 23 15:36 nvme-eui.00080d03000f9db7-part1 -> ../../nvme0n1p1 lrwxrwxrwx 1 root root 15 Oct 23 15:36 nvme-eui.00080d03000f9db7-part2 -> ../../nvme0n1p2 lrwxrwxrwx 1 root root 15 Oct 23 15:36 nvme-eui.00080d03000f9db7-part3 -> ../../nvme0n1p3 lrwxrwxrwx 1 root root 15 Oct 23 15:36 nvme-eui.00080d03000f9db7-part4 -> ../../nvme0n1p4 lrwxrwxrwx 1 root root 15 Oct 23 15:36 nvme-eui.00080d03000f9db7-part6 -> ../../nvme0n1p6
Could you show the content of /etc/crypttab ?
Sure : cr_home /dev/disk/by-id/-THNSN5512GPUK_NVMe_TOSHIBA_512GB_371B405QKSJU-part3 none none Thx for your patience :)
My guess is that your issue is a duplicate of bug 1063249. Could you try the recipe given in bug 1063249, comment #39 ? Meanwhile I'll prepare a fix but I would still suggest you to change the name of the symlink as the one used in your crypttab is broken. Thanks.
Many thanks Franck for your help !
Nicolas, it sounds that you fixed your issue, could you describe how exactly ? Did you install the test package ?
Ok I'm pretty sure it's a duplicate of bug #1063249 *** This bug has been marked as a duplicate of bug 1063249 ***
Indeed use your repository and your fix package solved my problem ! Many thanks for your support