Asked twice for Password on boot screen | LUKS decryption

Ask Fedora
, , , ,
1

So I have observed strange behaviour on boot. I have Luks encryption and have been asked twice for the password, but the first time was correct. So i rebooted and tried to reproduce this issue.

Instead of providing the password twice, I hit Esc to watch the boot sequence instead. I booted like normal.

here is the journalctl -b | grep -i password

journalctl -b | grep -i password
May 31 10:19:13 definitive-group systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid).
May 31 10:19:13 definitive-group systemd[1]: Started systemd-ask-password-plymouth.path - Forward Password Requests to Plymouth Directory Watch.
May 31 10:19:13 definitive-group systemd[1]: Started systemd-ask-password-plymouth.service - Forward Password Requests to Plymouth.
May 31 10:19:27 definitive-group systemd[1]: systemd-ask-password-plymouth.service: Deactivated successfully.
May 31 10:19:27 definitive-group systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid).
May 31 10:19:27 definitive-group systemd[1]: Started systemd-ask-password-wall.path - Forward Password Requests to Wall Directory Watch.
May 31 10:19:27 definitive-group systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid).
May 31 10:19:27 definitive-group systemd[1]: Started systemd-ask-password-plymouth.service - Forward Password Requests to Plymouth.
May 31 10:19:27 definitive-group audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-ask-password-plymouth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 31 10:19:27 definitive-group systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid).
May 31 10:19:27 definitive-group systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid).
May 31 10:19:27 definitive-group systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid).
May 31 10:19:35 definitive-group systemd[1]: Starting systemd-ask-password-wall.service - Forward Password Requests to Wall...
May 31 10:19:35 definitive-group systemd[1]: systemd-ask-password-plymouth.path: Deactivated successfully.
May 31 10:19:35 definitive-group systemd[1]: Stopped systemd-ask-password-plymouth.path - Forward Password Requests to Plymouth Directory Watch.
May 31 10:19:35 definitive-group systemd[1]: Stopping systemd-ask-password-plymouth.service - Forward Password Requests to Plymouth...
May 31 10:19:38 definitive-group systemd-tty-ask-password-agent[1515]: Failed to query password: Input/output error
May 31 10:19:38 definitive-group systemd-tty-ask-password-agent[1515]: Failed to process password: Input/output error
May 31 10:19:38 definitive-group systemd[1]: systemd-ask-password-plymouth.service: Deactivated successfully.
May 31 10:19:38 definitive-group systemd[1]: Stopped systemd-ask-password-plymouth.service - Forward Password Requests to Plymouth.
May 31 10:19:38 definitive-group audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-ask-password-plymouth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 31 10:19:38 definitive-group systemd[1]: Started systemd-ask-password-wall.service - Forward Password Requests to Wall.
May 31 10:19:38 definitive-group audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-ask-password-wall comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 31 10:19:46 definitive-group gdm-password][4960]: gkr-pam: unable to locate daemon control file
May 31 10:19:46 definitive-group gdm-password][4960]: gkr-pam: stashed password to try later in open session
May 31 10:19:46 definitive-group gdm-password][4960]: pam_unix(gdm-password:session): session opened for user definitive_group(uid=1000) by definitive_group(uid=0)
May 31 10:19:46 definitive-group gdm-password][4960]: gkr-pam: gnome-keyring-daemon started properly and unlocked keyring

Here is the journalctl -b | grep -i plymouth

journalctl -b | grep -i plymouth
May 31 10:19:13 definitive-group systemd[1]: Starting plymouth-start.service - Show Plymouth Boot Screen...
May 31 10:19:13 definitive-group systemd[1]: Received SIGRTMIN+20 from PID 567 (plymouthd).
May 31 10:19:13 definitive-group systemd[1]: Started plymouth-start.service - Show Plymouth Boot Screen.
May 31 10:19:13 definitive-group systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid).
May 31 10:19:13 definitive-group systemd[1]: Started systemd-ask-password-plymouth.path - Forward Password Requests to Plymouth Directory Watch.
May 31 10:19:13 definitive-group systemd[1]: Started systemd-ask-password-plymouth.service - Forward Password Requests to Plymouth.
May 31 10:19:25 definitive-group systemd[1]: Starting plymouth-switch-root.service - Plymouth switch root service...
May 31 10:19:25 definitive-group systemd[1]: Finished plymouth-switch-root.service - Plymouth switch root service.
May 31 10:19:27 definitive-group systemd[1]: systemd-ask-password-plymouth.service: Deactivated successfully.
May 31 10:19:27 definitive-group systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid).
May 31 10:19:27 definitive-group systemd[1]: plymouth-switch-root.service: Deactivated successfully.
May 31 10:19:27 definitive-group systemd[1]: Stopped plymouth-switch-root.service - Plymouth switch root service.
May 31 10:19:27 definitive-group systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid).
May 31 10:19:27 definitive-group systemd[1]: Started systemd-ask-password-plymouth.service - Forward Password Requests to Plymouth.
May 31 10:19:27 definitive-group audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-ask-password-plymouth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 31 10:19:27 definitive-group systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid).
May 31 10:19:27 definitive-group systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid).
May 31 10:19:27 definitive-group systemd[1]: systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch was skipped because of an unmet condition check (ConditionPathExists=!/run/plymouth/pid).
May 31 10:19:28 definitive-group systemd[1]: Starting plymouth-read-write.service - Tell Plymouth To Write Out Runtime Data...
May 31 10:19:28 definitive-group systemd[1]: Received SIGRTMIN+20 from PID 567 (plymouthd).
May 31 10:19:28 definitive-group systemd[1]: Finished plymouth-read-write.service - Tell Plymouth To Write Out Runtime Data.
May 31 10:19:28 definitive-group audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=plymouth-read-write comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 31 10:19:35 definitive-group systemd[1]: Starting plymouth-quit-wait.service - Hold until boot process finishes up...
May 31 10:19:35 definitive-group systemd[1]: systemd-ask-password-plymouth.path: Deactivated successfully.
May 31 10:19:35 definitive-group systemd[1]: Stopped systemd-ask-password-plymouth.path - Forward Password Requests to Plymouth Directory Watch.
May 31 10:19:35 definitive-group systemd[1]: Stopping systemd-ask-password-plymouth.service - Forward Password Requests to Plymouth...
May 31 10:19:35 definitive-group systemd[1]: Received SIGRTMIN+21 from PID 567 (plymouthd).
May 31 10:19:38 definitive-group systemd[1]: Received SIGRTMIN+21 from PID 567 (plymouthd).
May 31 10:19:38 definitive-group systemd[1]: Finished plymouth-quit-wait.service - Hold until boot process finishes up.
May 31 10:19:38 definitive-group audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=plymouth-quit-wait comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
May 31 10:19:38 definitive-group systemd[1]: systemd-ask-password-plymouth.service: Deactivated successfully.
May 31 10:19:38 definitive-group systemd[1]: Stopped systemd-ask-password-plymouth.service - Forward Password Requests to Plymouth.
May 31 10:19:38 definitive-group audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-ask-password-plymouth comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'

Honestly not sure what else to provide relevant to boot and password so any information is greatly appreciated.

I guess I can provide inxi -Fzxx

inxi -Fzxx
System:
  Kernel: 6.8.9-300.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.41-34.fc40
  Desktop: GNOME v: 46.2 tk: GTK v: 3.24.41 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 40 (Workstation Edition)
Machine:
  Type: Laptop System: LENOVO product: 82K2 v: IdeaPad Gaming 3 15ACH6
    serial: <filter> Chassis: type: 10 v: IdeaPad Gaming 3 15ACH6
    serial: <filter>
  Mobo: LENOVO model: LNVNB161216 v: SDK0T76465 WIN serial: <filter>
    part-nu: LENOVO_MT_82K2_BU_idea_FM_IdeaPad Gaming 3 15ACH6 UEFI: LENOVO
    v: H3CN32WW(V2.02) date: 02/23/2022
Battery:
  ID-1: BAT1 charge: 41.0 Wh (100.0%) condition: 41.0/45.0 Wh (91.0%)
    volts: 13.0 min: 11.5 model: 0x43 0x65 0x6C 0x78 0x70 0x72 0x74 0x00 0x32
    0x30 0x4C 0x32 0x30 0x43 0x33 0x50 serial: <filter> status: charging
CPU:
  Info: 6-core model: AMD Ryzen 5 5600H with Radeon Graphics bits: 64
    type: MT MCP arch: Zen 3 rev: 0 cache: L1: 384 KiB L2: 3 MiB L3: 16 MiB
  Speed (MHz): avg: 661 high: 3536 min/max: 400/4280 cores: 1: 400 2: 400
    3: 400 4: 400 5: 3536 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400
    bogomips: 79055
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: NVIDIA GA107M [GeForce RTX 3050 Ti Mobile] vendor: Lenovo
    driver: nvidia v: 550.78 arch: Ampere pcie: speed: 8 GT/s lanes: 8
    bus-ID: 01:00.0 chip-ID: 10de:25a0
  Device-2: AMD Cezanne [Radeon Vega Series / Radeon Mobile Series]
    vendor: Lenovo driver: amdgpu v: kernel arch: GCN-5 pcie: speed: 8 GT/s
    lanes: 16 ports: active: eDP-1 empty: HDMI-A-1 bus-ID: 05:00.0
    chip-ID: 1002:1638 temp: 42.0 C
  Device-3: IMC Networks Integrated Camera driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 1-3:3 chip-ID: 13d3:56ff
  Display: wayland server: X.org v: 1.20.14 with: Xwayland v: 23.2.6
    compositor: gnome-shell driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,vesa dri: radeonsi gpu: amdgpu display-ID: 0
  Monitor-1: eDP-1 model: BOE Display 0x0a81 res: 1920x1080 dpi: 142
    diag: 395mm (15.5")
  API: OpenGL v: 4.6 vendor: amd mesa v: 24.0.7 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: AMD Radeon Graphics (radeonsi renoir LLVM
    18.1.1 DRM 3.57 6.8.9-300.fc40.x86_64) device-ID: 1002:1638
    display-ID: :0.0
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: AMD Renoir Radeon High Definition Audio vendor: Lenovo
    driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
    bus-ID: 05:00.1 chip-ID: 1002:1637
  Device-2: AMD ACP/ACP3X/ACP6x Audio Coprocessor vendor: Lenovo driver: N/A
    pcie: speed: 8 GT/s lanes: 16 bus-ID: 05:00.5 chip-ID: 1022:15e2
  Device-3: AMD Family 17h/19h HD Audio vendor: Lenovo driver: snd_hda_intel
    v: kernel pcie: speed: 8 GT/s lanes: 16 bus-ID: 05:00.6 chip-ID: 1022:15e3
  API: ALSA v: k6.8.9-300.fc40.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.6 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: Lenovo driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: 2000 bus-ID: 02:00.0 chip-ID: 10ec:8168
  IF: enp2s0 state: down mac: <filter>
  Device-2: MEDIATEK MT7921 802.11ax PCI Express Wireless Network Adapter
    vendor: Lenovo driver: mt7921e v: kernel pcie: speed: 5 GT/s lanes: 1
    bus-ID: 03:00.0 chip-ID: 14c3:7961
  IF: wlo1 state: up mac: <filter>
Bluetooth:
  Device-1: Foxconn / Hon Hai MediaTek Bluetooth Adapter driver: btusb v: 0.8
    type: USB rev: 2.1 speed: 480 Mb/s lanes: 1 bus-ID: 1-4:4 chip-ID: 0489:e0cd
  Report: btmgmt ID: hci0 rfk-id: 2 state: up address: <filter> bt-v: 5.2
    lmp-v: 11
Drives:
  Local Storage: total: 7.74 TiB used: 288.9 GiB (3.6%)
  ID-1: /dev/nvme0n1 vendor: Samsung model: MZVLQ512HBLU-00B00
    size: 476.94 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 31.9 C
  ID-2: /dev/sda vendor: Western Digital model: WD80EMAZ-00WJTA0
    size: 7.28 TiB type: USB rev: 2.1 spd: 480 Mb/s lanes: 1 serial: <filter>
Partition:
  ID-1: / size: 69.94 GiB used: 34.21 GiB (48.9%) fs: xfs dev: /dev/dm-1
    mapped: fedora_localhost--live00-root
  ID-2: /boot/efi size: 1.58 GiB used: 236 MiB (14.6%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-3: /home size: 405.14 GiB used: 254.46 GiB (62.8%) fs: xfs
    dev: /dev/dm-2 mapped: fedora_localhost--live00-home
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 51.4 C mobo: 42.0 C gpu: amdgpu temp: 43.0 C
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 28 GiB available: 27.25 GiB used: 3.93 GiB (14.4%)
  Processes: 391 Power: uptime: 16m wakeups: 0 Init: systemd v: 255
    target: graphical (5) default: graphical
  Packages: pm: flatpak pkgs: 96 Compilers: gcc: 14.1.1 Shell: Bash
    v: 5.2.26 running-in: ptyxis-agent inxi: 3.3.34
2

Removed amdgpu, audio, bluetooth, flatpak, gnome

3

EDIT

journalctl -b | grep -i luks

journalctl -b | grep -i luks
May 31 10:19:13 definitive-group kernel: Command line: initrd=\ecc5b5e914994eb48de9d5fda2cd1ae6\6.8.9-300.fc40.x86_64\initrd root=/dev/mapper/fedora_localhost--live00-root ro rd.lvm.lv=fedora_localhost-live00/root rd.luks.uuid=luks-8a65df35-e8da-4bed-80fe-b18094496236 rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau systemd.machine_id=ecc5b5e914994eb48de9d5fda2cd1ae6
May 31 10:19:13 definitive-group kernel: Kernel command line: initrd=\ecc5b5e914994eb48de9d5fda2cd1ae6\6.8.9-300.fc40.x86_64\initrd root=/dev/mapper/fedora_localhost--live00-root ro rd.lvm.lv=fedora_localhost-live00/root rd.luks.uuid=luks-8a65df35-e8da-4bed-80fe-b18094496236 rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau systemd.machine_id=ecc5b5e914994eb48de9d5fda2cd1ae6
May 31 10:19:13 definitive-group dracut-cmdline[332]: Using kernel command line parameters:    initrd=\ecc5b5e914994eb48de9d5fda2cd1ae6\6.8.9-300.fc40.x86_64\initrd root=/dev/mapper/fedora_localhost--live00-root ro rd.lvm.lv=fedora_localhost-live00/root rd.luks.uuid=luks-8a65df35-e8da-4bed-80fe-b18094496236 rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau systemd.machine_id=ecc5b5e914994eb48de9d5fda2cd1ae6
May 31 10:19:13 definitive-group systemd-escape[425]: Input 'luks-8a65df35-e8da-4bed-80fe-b18094496236' is not an absolute file system path, escaping is likely not going to be reversible.
May 31 10:19:13 definitive-group systemd[1]: Starting systemd-cryptsetup@luks\x2d8a65df35\x2de8da\x2d4bed\x2d80fe\x2db18094496236.service - Cryptography Setup for luks-8a65df35-e8da-4bed-80fe-b18094496236...
May 31 10:19:24 definitive-group systemd[1]: Finished systemd-cryptsetup@luks\x2d8a65df35\x2de8da\x2d4bed\x2d80fe\x2db18094496236.service - Cryptography Setup for luks-8a65df35-e8da-4bed-80fe-b18094496236.
May 31 10:19:27 definitive-group systemd-cryptsetup-generator[1294]: Failed to create unit file '/run/systemd/generator/systemd-cryptsetup@luks\x2db4cfbd01\x2d4628\x2d416f\x2d94d3\x2defe39ea1ee29.service': File exists
May 31 10:19:27 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2d8a65df35\x2de8da\x2d4bed\x2d80fe\x2db18094496236.target - Block Device Preparation for /dev/mapper/luks-8a65df35-e8da-4bed-80fe-b18094496236.
May 31 10:19:27 definitive-group systemd[1]: Starting systemd-cryptsetup@luks\x2d234be24f\x2d87df\x2d4c53\x2d8f58\x2d95cc52f4f5f1.service - Cryptography Setup for luks-234be24f-87df-4c53-8f58-95cc52f4f5f1...
May 31 10:19:27 definitive-group systemd-fsck[1508]: sda: fsck.crypto_LUKS doesn't exist, not checking file system.
May 31 10:19:28 definitive-group systemd[1]: Dependency failed for systemd-cryptsetup@luks\x2dfdb97312\x2d15a0\x2d486e\x2dad6e\x2d0763e0a8ec38.service - Cryptography Setup for luks-fdb97312-15a0-486e-ad6e-0763e0a8ec38.
May 31 10:19:28 definitive-group systemd[1]: systemd-cryptsetup@luks\x2dfdb97312\x2d15a0\x2d486e\x2dad6e\x2d0763e0a8ec38.service: Job systemd-cryptsetup@luks\x2dfdb97312\x2d15a0\x2d486e\x2dad6e\x2d0763e0a8ec38.service/start failed with result 'dependency'.
May 31 10:19:28 definitive-group systemd[1]: Dependency failed for systemd-cryptsetup@luks\x2ddcff94f5\x2d0354\x2d4501\x2dae13\x2d5d91b9eb2fbb.service - Cryptography Setup for luks-dcff94f5-0354-4501-ae13-5d91b9eb2fbb.
May 31 10:19:28 definitive-group systemd[1]: systemd-cryptsetup@luks\x2ddcff94f5\x2d0354\x2d4501\x2dae13\x2d5d91b9eb2fbb.service: Job systemd-cryptsetup@luks\x2ddcff94f5\x2d0354\x2d4501\x2dae13\x2d5d91b9eb2fbb.service/start failed with result 'dependency'.
May 31 10:19:28 definitive-group systemd[1]: Dependency failed for systemd-cryptsetup@luks\x2d11109ea0\x2ddbb9\x2d4ffe\x2d9d24\x2dd65f5d5ad48b.service - Cryptography Setup for luks-11109ea0-dbb9-4ffe-9d24-d65f5d5ad48b.
May 31 10:19:28 definitive-group systemd[1]: systemd-cryptsetup@luks\x2d11109ea0\x2ddbb9\x2d4ffe\x2d9d24\x2dd65f5d5ad48b.service: Job systemd-cryptsetup@luks\x2d11109ea0\x2ddbb9\x2d4ffe\x2d9d24\x2dd65f5d5ad48b.service/start failed with result 'dependency'.
May 31 10:19:28 definitive-group systemd[1]: Dependency failed for systemd-cryptsetup@luks\x2dc1273de7\x2d809a\x2d42eb\x2db9c0\x2da3142d0f60c0.service - Cryptography Setup for luks-c1273de7-809a-42eb-b9c0-a3142d0f60c0.
May 31 10:19:28 definitive-group systemd[1]: systemd-cryptsetup@luks\x2dc1273de7\x2d809a\x2d42eb\x2db9c0\x2da3142d0f60c0.service: Job systemd-cryptsetup@luks\x2dc1273de7\x2d809a\x2d42eb\x2db9c0\x2da3142d0f60c0.service/start failed with result 'dependency'.
May 31 10:19:28 definitive-group systemd[1]: Dependency failed for systemd-cryptsetup@luks\x2dc08b2f28\x2d9f21\x2d4f00\x2dbe7b\x2ded3f94c19c62.service - Cryptography Setup for luks-c08b2f28-9f21-4f00-be7b-ed3f94c19c62.
May 31 10:19:28 definitive-group systemd[1]: systemd-cryptsetup@luks\x2dc08b2f28\x2d9f21\x2d4f00\x2dbe7b\x2ded3f94c19c62.service: Job systemd-cryptsetup@luks\x2dc08b2f28\x2d9f21\x2d4f00\x2dbe7b\x2ded3f94c19c62.service/start failed with result 'dependency'.
May 31 10:19:28 definitive-group systemd[1]: Dependency failed for systemd-cryptsetup@luks\x2d99b11c61\x2dfb67\x2d4170\x2db82e\x2da214cdd21c0c.service - Cryptography Setup for luks-99b11c61-fb67-4170-b82e-a214cdd21c0c.
May 31 10:19:28 definitive-group systemd[1]: systemd-cryptsetup@luks\x2d99b11c61\x2dfb67\x2d4170\x2db82e\x2da214cdd21c0c.service: Job systemd-cryptsetup@luks\x2d99b11c61\x2dfb67\x2d4170\x2db82e\x2da214cdd21c0c.service/start failed with result 'dependency'.
May 31 10:19:28 definitive-group systemd[1]: Dependency failed for systemd-cryptsetup@luks\x2d99488ccf\x2d856b\x2d4c0c\x2d9afd\x2dce854306d730.service - Cryptography Setup for luks-99488ccf-856b-4c0c-9afd-ce854306d730.
May 31 10:19:28 definitive-group systemd[1]: systemd-cryptsetup@luks\x2d99488ccf\x2d856b\x2d4c0c\x2d9afd\x2dce854306d730.service: Job systemd-cryptsetup@luks\x2d99488ccf\x2d856b\x2d4c0c\x2d9afd\x2dce854306d730.service/start failed with result 'dependency'.
May 31 10:19:28 definitive-group systemd[1]: Dependency failed for systemd-cryptsetup@luks\x2d480b562b\x2d5af5\x2d4ed7\x2da0e0\x2d11095e5e1e97.service - Cryptography Setup for luks-480b562b-5af5-4ed7-a0e0-11095e5e1e97.
May 31 10:19:28 definitive-group systemd[1]: systemd-cryptsetup@luks\x2d480b562b\x2d5af5\x2d4ed7\x2da0e0\x2d11095e5e1e97.service: Job systemd-cryptsetup@luks\x2d480b562b\x2d5af5\x2d4ed7\x2da0e0\x2d11095e5e1e97.service/start failed with result 'dependency'.
May 31 10:19:28 definitive-group systemd[1]: Dependency failed for systemd-cryptsetup@luks\x2d899414e0\x2dfa2c\x2d496f\x2d9e0f\x2d6f8d9809b58f.service - Cryptography Setup for luks-899414e0-fa2c-496f-9e0f-6f8d9809b58f.
May 31 10:19:28 definitive-group systemd[1]: systemd-cryptsetup@luks\x2d899414e0\x2dfa2c\x2d496f\x2d9e0f\x2d6f8d9809b58f.service: Job systemd-cryptsetup@luks\x2d899414e0\x2dfa2c\x2d496f\x2d9e0f\x2d6f8d9809b58f.service/start failed with result 'dependency'.
May 31 10:19:28 definitive-group systemd[1]: Dependency failed for systemd-cryptsetup@luks\x2d871d1b0f\x2db4d3\x2d4814\x2d9b63\x2d44d6e0c2cb52.service - Cryptography Setup for luks-871d1b0f-b4d3-4814-9b63-44d6e0c2cb52.
May 31 10:19:28 definitive-group systemd[1]: systemd-cryptsetup@luks\x2d871d1b0f\x2db4d3\x2d4814\x2d9b63\x2d44d6e0c2cb52.service: Job systemd-cryptsetup@luks\x2d871d1b0f\x2db4d3\x2d4814\x2d9b63\x2d44d6e0c2cb52.service/start failed with result 'dependency'.
May 31 10:19:28 definitive-group systemd[1]: Dependency failed for systemd-cryptsetup@luks\x2d850738fc\x2de60b\x2d4c5b\x2d817d\x2dff3fd55d6f5a.service - Cryptography Setup for luks-850738fc-e60b-4c5b-817d-ff3fd55d6f5a.
May 31 10:19:28 definitive-group systemd[1]: systemd-cryptsetup@luks\x2d850738fc\x2de60b\x2d4c5b\x2d817d\x2dff3fd55d6f5a.service: Job systemd-cryptsetup@luks\x2d850738fc\x2de60b\x2d4c5b\x2d817d\x2dff3fd55d6f5a.service/start failed with result 'dependency'.
May 31 10:19:28 definitive-group systemd[1]: Dependency failed for systemd-cryptsetup@luks\x2dc87df51a\x2d15f1\x2d4ef9\x2d929b\x2da372c56cdd72.service - Cryptography Setup for luks-c87df51a-15f1-4ef9-929b-a372c56cdd72.
May 31 10:19:28 definitive-group systemd[1]: systemd-cryptsetup@luks\x2dc87df51a\x2d15f1\x2d4ef9\x2d929b\x2da372c56cdd72.service: Job systemd-cryptsetup@luks\x2dc87df51a\x2d15f1\x2d4ef9\x2d929b\x2da372c56cdd72.service/start failed with result 'dependency'.
May 31 10:19:28 definitive-group systemd[1]: Dependency failed for systemd-cryptsetup@luks\x2d5d45d0e8\x2d39be\x2d46ca\x2db8f9\x2d4ab7aad85568.service - Cryptography Setup for luks-5d45d0e8-39be-46ca-b8f9-4ab7aad85568.
May 31 10:19:28 definitive-group systemd[1]: systemd-cryptsetup@luks\x2d5d45d0e8\x2d39be\x2d46ca\x2db8f9\x2d4ab7aad85568.service: Job systemd-cryptsetup@luks\x2d5d45d0e8\x2d39be\x2d46ca\x2db8f9\x2d4ab7aad85568.service/start failed with result 'dependency'.
May 31 10:19:28 definitive-group systemd[1]: Dependency failed for systemd-cryptsetup@luks\x2d68665b56\x2d5cee\x2d4a93\x2d8c04\x2d2fc50c437fc5.service - Cryptography Setup for luks-68665b56-5cee-4a93-8c04-2fc50c437fc5.
May 31 10:19:28 definitive-group systemd[1]: systemd-cryptsetup@luks\x2d68665b56\x2d5cee\x2d4a93\x2d8c04\x2d2fc50c437fc5.service: Job systemd-cryptsetup@luks\x2d68665b56\x2d5cee\x2d4a93\x2d8c04\x2d2fc50c437fc5.service/start failed with result 'dependency'.
May 31 10:19:28 definitive-group systemd[1]: Dependency failed for systemd-cryptsetup@luks\x2db4cfbd01\x2d4628\x2d416f\x2d94d3\x2defe39ea1ee29.service - Cryptography Setup for luks-b4cfbd01-4628-416f-94d3-efe39ea1ee29.
May 31 10:19:28 definitive-group systemd[1]: systemd-cryptsetup@luks\x2db4cfbd01\x2d4628\x2d416f\x2d94d3\x2defe39ea1ee29.service: Job systemd-cryptsetup@luks\x2db4cfbd01\x2d4628\x2d416f\x2d94d3\x2defe39ea1ee29.service/start failed with result 'dependency'.
May 31 10:19:28 definitive-group systemd[1]: Dependency failed for systemd-cryptsetup@luks\x2d31203453\x2dcf8f\x2d48ca\x2dade5\x2d573784fd75c4.service - Cryptography Setup for luks-31203453-cf8f-48ca-ade5-573784fd75c4.
May 31 10:19:28 definitive-group systemd[1]: systemd-cryptsetup@luks\x2d31203453\x2dcf8f\x2d48ca\x2dade5\x2d573784fd75c4.service: Job systemd-cryptsetup@luks\x2d31203453\x2dcf8f\x2d48ca\x2dade5\x2d573784fd75c4.service/start failed with result 'dependency'.
May 31 10:19:28 definitive-group systemd[1]: Dependency failed for systemd-cryptsetup@luks\x2d8e9db940\x2ddd44\x2d430f\x2d9a37\x2d984e8d645898.service - Cryptography Setup for luks-8e9db940-dd44-430f-9a37-984e8d645898.
May 31 10:19:28 definitive-group systemd[1]: systemd-cryptsetup@luks\x2d8e9db940\x2ddd44\x2d430f\x2d9a37\x2d984e8d645898.service: Job systemd-cryptsetup@luks\x2d8e9db940\x2ddd44\x2d430f\x2d9a37\x2d984e8d645898.service/start failed with result 'dependency'.
May 31 10:19:28 definitive-group systemd[1]: Dependency failed for systemd-cryptsetup@luks\x2d293d3728\x2d6fb3\x2d4b44\x2d8a4f\x2dd980f02b1fce.service - Cryptography Setup for luks-293d3728-6fb3-4b44-8a4f-d980f02b1fce.
May 31 10:19:28 definitive-group systemd[1]: systemd-cryptsetup@luks\x2d293d3728\x2d6fb3\x2d4b44\x2d8a4f\x2dd980f02b1fce.service: Job systemd-cryptsetup@luks\x2d293d3728\x2d6fb3\x2d4b44\x2d8a4f\x2dd980f02b1fce.service/start failed with result 'dependency'.
May 31 10:19:28 definitive-group systemd[1]: Dependency failed for systemd-cryptsetup@luks\x2d09b57503\x2d6fb9\x2d4a97\x2db025\x2d091e47aa312a.service - Cryptography Setup for luks-09b57503-6fb9-4a97-b025-091e47aa312a.
May 31 10:19:28 definitive-group systemd[1]: systemd-cryptsetup@luks\x2d09b57503\x2d6fb9\x2d4a97\x2db025\x2d091e47aa312a.service: Job systemd-cryptsetup@luks\x2d09b57503\x2d6fb9\x2d4a97\x2db025\x2d091e47aa312a.service/start failed with result 'dependency'.
May 31 10:19:28 definitive-group systemd[1]: Dependency failed for systemd-cryptsetup@luks\x2d2d1fc47c\x2d8eba\x2d463a\x2da5d0\x2d1faca8a25250.service - Cryptography Setup for luks-2d1fc47c-8eba-463a-a5d0-1faca8a25250.
May 31 10:19:28 definitive-group systemd[1]: systemd-cryptsetup@luks\x2d2d1fc47c\x2d8eba\x2d463a\x2da5d0\x2d1faca8a25250.service: Job systemd-cryptsetup@luks\x2d2d1fc47c\x2d8eba\x2d463a\x2da5d0\x2d1faca8a25250.service/start failed with result 'dependency'.
May 31 10:19:28 definitive-group systemd[1]: Dependency failed for systemd-cryptsetup@luks\x2d33d31fff\x2d5486\x2d45eb\x2dbd17\x2d2c8a610ae19d.service - Cryptography Setup for luks-33d31fff-5486-45eb-bd17-2c8a610ae19d.
May 31 10:19:28 definitive-group systemd[1]: systemd-cryptsetup@luks\x2d33d31fff\x2d5486\x2d45eb\x2dbd17\x2d2c8a610ae19d.service: Job systemd-cryptsetup@luks\x2d33d31fff\x2d5486\x2d45eb\x2dbd17\x2d2c8a610ae19d.service/start failed with result 'dependency'.
May 31 10:19:28 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2d09b57503\x2d6fb9\x2d4a97\x2db025\x2d091e47aa312a.target - Block Device Preparation for /dev/mapper/luks-09b57503-6fb9-4a97-b025-091e47aa312a.
May 31 10:19:28 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2d11109ea0\x2ddbb9\x2d4ffe\x2d9d24\x2dd65f5d5ad48b.target - Block Device Preparation for /dev/mapper/luks-11109ea0-dbb9-4ffe-9d24-d65f5d5ad48b.
May 31 10:19:28 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2d293d3728\x2d6fb3\x2d4b44\x2d8a4f\x2dd980f02b1fce.target - Block Device Preparation for /dev/mapper/luks-293d3728-6fb3-4b44-8a4f-d980f02b1fce.
May 31 10:19:28 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2d2d1fc47c\x2d8eba\x2d463a\x2da5d0\x2d1faca8a25250.target - Block Device Preparation for /dev/mapper/luks-2d1fc47c-8eba-463a-a5d0-1faca8a25250.
May 31 10:19:28 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2d31203453\x2dcf8f\x2d48ca\x2dade5\x2d573784fd75c4.target - Block Device Preparation for /dev/mapper/luks-31203453-cf8f-48ca-ade5-573784fd75c4.
May 31 10:19:28 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2d33d31fff\x2d5486\x2d45eb\x2dbd17\x2d2c8a610ae19d.target - Block Device Preparation for /dev/mapper/luks-33d31fff-5486-45eb-bd17-2c8a610ae19d.
May 31 10:19:28 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2d480b562b\x2d5af5\x2d4ed7\x2da0e0\x2d11095e5e1e97.target - Block Device Preparation for /dev/mapper/luks-480b562b-5af5-4ed7-a0e0-11095e5e1e97.
May 31 10:19:28 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2d5d45d0e8\x2d39be\x2d46ca\x2db8f9\x2d4ab7aad85568.target - Block Device Preparation for /dev/mapper/luks-5d45d0e8-39be-46ca-b8f9-4ab7aad85568.
May 31 10:19:28 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2d68665b56\x2d5cee\x2d4a93\x2d8c04\x2d2fc50c437fc5.target - Block Device Preparation for /dev/mapper/luks-68665b56-5cee-4a93-8c04-2fc50c437fc5.
May 31 10:19:28 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2d850738fc\x2de60b\x2d4c5b\x2d817d\x2dff3fd55d6f5a.target - Block Device Preparation for /dev/mapper/luks-850738fc-e60b-4c5b-817d-ff3fd55d6f5a.
May 31 10:19:28 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2d871d1b0f\x2db4d3\x2d4814\x2d9b63\x2d44d6e0c2cb52.target - Block Device Preparation for /dev/mapper/luks-871d1b0f-b4d3-4814-9b63-44d6e0c2cb52.
May 31 10:19:28 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2d899414e0\x2dfa2c\x2d496f\x2d9e0f\x2d6f8d9809b58f.target - Block Device Preparation for /dev/mapper/luks-899414e0-fa2c-496f-9e0f-6f8d9809b58f.
May 31 10:19:28 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2d8e9db940\x2ddd44\x2d430f\x2d9a37\x2d984e8d645898.target - Block Device Preparation for /dev/mapper/luks-8e9db940-dd44-430f-9a37-984e8d645898.
May 31 10:19:28 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2d99488ccf\x2d856b\x2d4c0c\x2d9afd\x2dce854306d730.target - Block Device Preparation for /dev/mapper/luks-99488ccf-856b-4c0c-9afd-ce854306d730.
May 31 10:19:28 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2d99b11c61\x2dfb67\x2d4170\x2db82e\x2da214cdd21c0c.target - Block Device Preparation for /dev/mapper/luks-99b11c61-fb67-4170-b82e-a214cdd21c0c.
May 31 10:19:28 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2db4cfbd01\x2d4628\x2d416f\x2d94d3\x2defe39ea1ee29.target - Block Device Preparation for /dev/mapper/luks-b4cfbd01-4628-416f-94d3-efe39ea1ee29.
May 31 10:19:28 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2dc08b2f28\x2d9f21\x2d4f00\x2dbe7b\x2ded3f94c19c62.target - Block Device Preparation for /dev/mapper/luks-c08b2f28-9f21-4f00-be7b-ed3f94c19c62.
May 31 10:19:28 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2dc1273de7\x2d809a\x2d42eb\x2db9c0\x2da3142d0f60c0.target - Block Device Preparation for /dev/mapper/luks-c1273de7-809a-42eb-b9c0-a3142d0f60c0.
May 31 10:19:28 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2dc87df51a\x2d15f1\x2d4ef9\x2d929b\x2da372c56cdd72.target - Block Device Preparation for /dev/mapper/luks-c87df51a-15f1-4ef9-929b-a372c56cdd72.
May 31 10:19:28 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2ddcff94f5\x2d0354\x2d4501\x2dae13\x2d5d91b9eb2fbb.target - Block Device Preparation for /dev/mapper/luks-dcff94f5-0354-4501-ae13-5d91b9eb2fbb.
May 31 10:19:28 definitive-group systemd[1]: Reached target blockdev@dev-mapper-luks\x2dfdb97312\x2d15a0\x2d486e\x2dad6e\x2d0763e0a8ec38.target - Block Device Preparation for /dev/mapper/luks-fdb97312-15a0-486e-ad6e-0763e0a8ec38.
May 31 10:19:28 definitive-group systemd[1]: Stopped target blockdev@dev-mapper-luks\x2d09b57503\x2d6fb9\x2d4a97\x2db025\x2d091e47aa312a.target - Block Device Preparation for /dev/mapper/luks-09b57503-6fb9-4a97-b025-091e47aa312a.
May 31 10:19:28 definitive-group systemd[1]: Stopped target blockdev@dev-mapper-luks\x2d11109ea0\x2ddbb9\x2d4ffe\x2d9d24\x2dd65f5d5ad48b.target - Block Device Preparation for /dev/mapper/luks-11109ea0-dbb9-4ffe-9d24-d65f5d5ad48b.
May 31 10:19:28 definitive-group systemd[1]: Stopped target blockdev@dev-mapper-luks\x2d293d3728\x2d6fb3\x2d4b44\x2d8a4f\x2dd980f02b1fce.target - Block Device Preparation for /dev/mapper/luks-293d3728-6fb3-4b44-8a4f-d980f02b1fce.
May 31 10:19:28 definitive-group systemd[1]: Stopped target blockdev@dev-mapper-luks\x2d2d1fc47c\x2d8eba\x2d463a\x2da5d0\x2d1faca8a25250.target - Block Device Preparation for /dev/mapper/luks-2d1fc47c-8eba-463a-a5d0-1faca8a25250.
May 31 10:19:28 definitive-group systemd[1]: Stopped target blockdev@dev-mapper-luks\x2d31203453\x2dcf8f\x2d48ca\x2dade5\x2d573784fd75c4.target - Block Device Preparation for /dev/mapper/luks-31203453-cf8f-48ca-ade5-573784fd75c4.
May 31 10:19:28 definitive-group systemd[1]: Stopped target blockdev@dev-mapper-luks\x2d33d31fff\x2d5486\x2d45eb\x2dbd17\x2d2c8a610ae19d.target - Block Device Preparation for /dev/mapper/luks-33d31fff-5486-45eb-bd17-2c8a610ae19d.
May 31 10:19:28 definitive-group systemd[1]: Stopped target blockdev@dev-mapper-luks\x2d480b562b\x2d5af5\x2d4ed7\x2da0e0\x2d11095e5e1e97.target - Block Device Preparation for /dev/mapper/luks-480b562b-5af5-4ed7-a0e0-11095e5e1e97.
May 31 10:19:28 definitive-group systemd[1]: Stopped target blockdev@dev-mapper-luks\x2d5d45d0e8\x2d39be\x2d46ca\x2db8f9\x2d4ab7aad85568.target - Block Device Preparation for /dev/mapper/luks-5d45d0e8-39be-46ca-b8f9-4ab7aad85568.
May 31 10:19:28 definitive-group systemd[1]: Stopped target blockdev@dev-mapper-luks\x2d68665b56\x2d5cee\x2d4a93\x2d8c04\x2d2fc50c437fc5.target - Block Device Preparation for /dev/mapper/luks-68665b56-5cee-4a93-8c04-2fc50c437fc5.
May 31 10:19:28 definitive-group systemd[1]: Stopped target blockdev@dev-mapper-luks\x2d850738fc\x2de60b\x2d4c5b\x2d817d\x2dff3fd55d6f5a.target - Block Device Preparation for /dev/mapper/luks-850738fc-e60b-4c5b-817d-ff3fd55d6f5a.
May 31 10:19:28 definitive-group systemd[1]: Stopped target blockdev@dev-mapper-luks\x2d871d1b0f\x2db4d3\x2d4814\x2d9b63\x2d44d6e0c2cb52.target - Block Device Preparation for /dev/mapper/luks-871d1b0f-b4d3-4814-9b63-44d6e0c2cb52.
May 31 10:19:28 definitive-group systemd[1]: Stopped target blockdev@dev-mapper-luks\x2d899414e0\x2dfa2c\x2d496f\x2d9e0f\x2d6f8d9809b58f.target - Block Device Preparation for /dev/mapper/luks-899414e0-fa2c-496f-9e0f-6f8d9809b58f.
May 31 10:19:28 definitive-group systemd[1]: Stopped target blockdev@dev-mapper-luks\x2d8e9db940\x2ddd44\x2d430f\x2d9a37\x2d984e8d645898.target - Block Device Preparation for /dev/mapper/luks-8e9db940-dd44-430f-9a37-984e8d645898.
May 31 10:19:28 definitive-group systemd[1]: Stopped target blockdev@dev-mapper-luks\x2d99488ccf\x2d856b\x2d4c0c\x2d9afd\x2dce854306d730.target - Block Device Preparation for /dev/mapper/luks-99488ccf-856b-4c0c-9afd-ce854306d730.
May 31 10:19:28 definitive-group systemd[1]: Stopped target blockdev@dev-mapper-luks\x2d99b11c61\x2dfb67\x2d4170\x2db82e\x2da214cdd21c0c.target - Block Device Preparation for /dev/mapper/luks-99b11c61-fb67-4170-b82e-a214cdd21c0c.
May 31 10:19:28 definitive-group systemd[1]: Stopped target blockdev@dev-mapper-luks\x2db4cfbd01\x2d4628\x2d416f\x2d94d3\x2defe39ea1ee29.target - Block Device Preparation for /dev/mapper/luks-b4cfbd01-4628-416f-94d3-efe39ea1ee29.
May 31 10:19:28 definitive-group systemd[1]: Stopped target blockdev@dev-mapper-luks\x2dc08b2f28\x2d9f21\x2d4f00\x2dbe7b\x2ded3f94c19c62.target - Block Device Preparation for /dev/mapper/luks-c08b2f28-9f21-4f00-be7b-ed3f94c19c62.
May 31 10:19:28 definitive-group systemd[1]: Stopped target blockdev@dev-mapper-luks\x2dc1273de7\x2d809a\x2d42eb\x2db9c0\x2da3142d0f60c0.target - Block Device Preparation for /dev/mapper/luks-c1273de7-809a-42eb-b9c0-a3142d0f60c0.
May 31 10:19:28 definitive-group systemd[1]: Stopped target blockdev@dev-mapper-luks\x2dc87df51a\x2d15f1\x2d4ef9\x2d929b\x2da372c56cdd72.target - Block Device Preparation for /dev/mapper/luks-c87df51a-15f1-4ef9-929b-a372c56cdd72.
May 31 10:19:28 definitive-group systemd[1]: Stopped target blockdev@dev-mapper-luks\x2ddcff94f5\x2d0354\x2d4501\x2dae13\x2d5d91b9eb2fbb.target - Block Device Preparation for /dev/mapper/luks-dcff94f5-0354-4501-ae13-5d91b9eb2fbb.
May 31 10:19:28 definitive-group systemd[1]: Stopped target blockdev@dev-mapper-luks\x2dfdb97312\x2d15a0\x2d486e\x2dad6e\x2d0763e0a8ec38.target - Block Device Preparation for /dev/mapper/luks-fdb97312-15a0-486e-ad6e-0763e0a8ec38.
4

Please show lsblk -f
I am wondering if you have 2 partitions that are luks encrypted.

5

The external USB is Luks encrypted, although this behaviour has occured when it’s not present as well.

lsblk -f
NAME                                          FSTYPE      FSVER    LABEL UUID                                   FSAVAIL FSUSE% MOUNTPOINTS
sda                                           crypto_LUKS 1              234be24f-87df-4c53-8f58-95cc52f4f5f1                  
zram0                                                                                                                          [SWAP]
nvme0n1                                                                                                                        
├─nvme0n1p1                                   vfat        FAT32          C710-1353                                 1.4G    15% /boot/efi
└─nvme0n1p3                                   crypto_LUKS 2              8a65df35-e8da-4bed-80fe-b18094496236                  
  └─luks-8a65df35-e8da-4bed-80fe-b18094496236 LVM2_member LVM2 001       868FvZ-8rZc-ntGy-5czY-QvZh-5dsf-b3fFR3                
    ├─fedora_localhost--live00-root           xfs                        fa8c56f8-b894-4f3b-8173-083ff82ead79     35.7G    49% /
    └─fedora_localhost--live00-home           xfs                        72df63af-9943-437f-bbe2-a96baf290254    150.7G    63% /home

Here is a snippet of the /etc/fstab :

UUID=234be24f-87df-4c53-8f58-95cc52f4f5f1   
/run/media/definitive_group/EasyStore  
xfs  nofail,x-systemd.device-timeout=1s     0 2

This fstab has been going since F31 :thinking: so I know there’s no issues there. Also, /etc/crypttab is fine. My keys are still the same.

6

It asks 3 times if you enter wrong password to open LUKS I think I reported this issue 4-5 months ago when it started. Sometimes just need to hit LUKS password and enter again even it is correct

No idea why this happens tho

1 Like
7

But, I did not enter the wrong password. I entered it correctly, and watched it ask again and then proceed to the desktop ! That’s what’s crazy.

8

Yeah happened me today and also LUKS screen was hmm different

Link on today post same/similar issue might be same might not since my issue is silverblue based

1 Like
9

If you type ESC so that you can see the kernel messages look to see whick partition the prompt is asking for a passphrase for.

Does it ask once for each luks partition?

I believe the kernel is not supposed to ask if you already provided a passphrase that will unlock.

1 Like
10

It only ask for the one on the system. I provided the fstab row for that 1 drive to rule that out. I might go as far as to provide screenshots. It’s very weird.

11

yeah this has happened to me once or twice in the past month running rawhide.

1 Like
12

/etc/fstab does not drive luks decrypt, it is the /etc/crypttab

What do you have in your crypt setup file?
Edit: fix filename.

13

Well, the reason I showed the fstab was to show the

xfs nofail,x-systemd.device-timeout=1s 0 2 → important only for the external drives. There is no need to check for keys that are not present. :bulb:

My crypttab has the usual :
luks-XXXXXXX-XXX UUID=XXXXXXX-XXX and the keys, name and location, and the encryption luks

Which is typical, and has not changed since I started adding a ton of external drives to my setups around Fedora 31 :thinking:

14

I fedora server has 4 entries in crypttab and I have been prompted more then once to enter passphrases in the past.

As i use tang/clevis to unlock on my home network i do not need to type the passphrases that often.
So I am not sure how often its asking at the moment.
If I get a spare moment I will try without clevis and count the prompts.

1 Like
15

I appreciate it, but it looks like it’s some sort of bug. I honestly posted to have a deeper look tonight and tomorrow as I was busy with a project that needd to get done.

I have rebooted twice to no problems. So we’ll see. Although my last reboot was a crash of the Display maybe due to how abrubtly i needed to leave the Library.

Thanks for the help though !

16

I have tested on 3 systems with luks encrypted partitions.
I only get prompted once on each system.
2 have a single partition, the other has 4 partitions.

1 Like
17

Yeah, Unfortunately I’ll have to wait till it happens again. I don’t typically have the External drives connected at boot because I am not in possession of the key. So I unlock the drives the traditional way on the desktop.

Since posting this, I have only attempted twice, once was a forced reboot due to a crash ( supposed Nvidia driver?! not waking from sleep ) yesterday and once this morning. It has happened about 5x, and only twice did I have the External drive connected.