0

I have 2 partitions, /dev/sda1 named as data1 in /etc/crypttab, and /dev/sdb1 named as data2, that I have encrypted using VeraCrypt, and more precisely I have encrypted them as hidden volumes. I would like to automount both at boot, but I get an error: when Arch asks me to type the decryption password for one of the two partitions, it then cannot decrypt the second one, resulting in an error. At boot, it selects the first partition to decrypt randomly: one time it asks for the password of /dev/sda1 first, another time for that of /dev/sdb1, but it never decrypts the second one, only the first one.

Here is my /etc/crypttab:

data1       /dev/sda1                                    none          tcrypt-hidden,tcrypt-veracrypt

data2       /dev/sdb1                                    none          tcrypt-hidden,tcrypt-veracrypt

and here are the relevant logs of the systemd journal (in this example, data2 was first loaded):

Apr 29 10:43:04 mach systemd[1]: Stopped target Block Device Preparation for /dev/mapper/data1.
Apr 29 10:43:04 mach kernel: audit: type=1130 audit(1588149784.463:41): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-cryptsetup@data1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 29 10:43:04 mach systemd[1]: Reached target Block Device Preparation for /dev/mapper/data1.
Apr 29 10:43:04 mach audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-cryptsetup@data1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 29 10:43:04 mach systemd[1]: cryptsetup.target: Job cryptsetup.target/start failed with result 'dependency'.
Apr 29 10:43:04 mach systemd[1]: Dependency failed for Local Encrypted Volumes.
Apr 29 10:43:04 mach systemd[1]: Failed to start Cryptography Setup for data1.
Apr 29 10:43:04 mach systemd[1]: systemd-cryptsetup@data1.service: Failed with result 'exit-code'.
Apr 29 10:43:04 mach systemd[1]: systemd-cryptsetup@data1.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 10:43:04 mach systemd-cryptsetup[4964]: Failed to load tcrypt superblock on device /dev/sda1: Invalid argument
Apr 29 10:43:04 mach systemd-cryptsetup[4964]: PBKDF2 hash algorithm stribog512 not available, skipping.
Apr 29 10:42:55 mach systemd-cryptsetup[4964]: PBKDF2 hash algorithm stribog512 not available, skipping.
Apr 29 10:42:47 mach systemd[1]: Condition check resulted in Update is Completed being skipped.
Apr 29 10:42:47 mach systemd[1]: Condition check resulted in Create System Users being skipped.
Apr 29 10:42:47 mach systemd[1]: Condition check resulted in FUSE Control File System being skipped.
Apr 29 10:42:47 mach systemd[1]: Condition check resulted in Load Kernel Modules being skipped.
Apr 29 10:42:47 mach systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
Apr 29 10:42:47 mach systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
Apr 29 10:42:47 mach systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Apr 29 10:42:47 mach systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
Apr 29 10:42:47 mach systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.
Apr 29 10:42:47 mach systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
Apr 29 10:42:47 mach systemd[1]: Condition check resulted in First Boot Wizard being skipped.
Apr 29 10:42:47 mach systemd[1]: Starting Cryptography Setup for data1...
Apr 29 10:42:40 mach audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-hostnamed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 29 10:42:40 mach systemd[1]: systemd-hostnamed.service: Succeeded.
Apr 29 10:42:38 mach kernel: audit: type=1131 audit(1588149758.234:33): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 29 10:42:38 mach audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 29 10:42:36 mach login[3615]: FAILED LOGIN 2 FROM tty1 FOR bob, Authentication failure
Apr 29 10:42:33 mach kernel: audit: type=1100 audit(1588149753.521:32): pid=3615 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=? acct="bob" exe="/usr/bin/login" hostname=mach addr=? terminal=tty1 res=failed'
Apr 29 10:42:33 mach audit[3615]: USER_AUTH pid=3615 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=? acct="bob" exe="/usr/bin/login" hostname=mach addr=? terminal=tty1 res=failed'
Apr 29 10:42:28 mach login[3615]: FAILED LOGIN 1 FROM tty1 FOR bob, Authentication failure
Apr 29 10:42:28 mach dbus-daemon[2279]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Apr 29 10:42:28 mach dbus-daemon[2279]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.2' (uid=0 pid=2280 comm="/usr/bin/NetworkManager --no-daemon ")
Apr 29 10:42:28 mach kernel: audit: type=1130 audit(1588149748.071:30): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-cryptsetup@data1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 29 10:42:28 mach systemd[1]: Stopped target Block Device Preparation for /dev/mapper/data1.
Apr 29 10:42:28 mach systemd[1]: Starting Network Manager Script Dispatcher Service...
Apr 29 10:42:28 mach systemd[1]: Reached target Block Device Preparation for /dev/mapper/data1.
Apr 29 10:42:28 mach systemd[1]: cryptsetup.target: Job cryptsetup.target/start failed with result 'dependency'.
Apr 29 10:42:28 mach audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-cryptsetup@data1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 29 10:42:28 mach systemd[1]: Dependency failed for Local Encrypted Volumes.
Apr 29 10:42:28 mach systemd[1]: Failed to start Cryptography Setup for data1.
Apr 29 10:42:28 mach systemd[1]: systemd-cryptsetup@data1.service: Failed with result 'exit-code'.
Apr 29 10:42:28 mach systemd[1]: systemd-cryptsetup@data1.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 10:42:28 mach systemd-cryptsetup[3624]: Failed to load tcrypt superblock on device /dev/sda1: Invalid argument
Apr 29 10:42:28 mach systemd-cryptsetup[3624]: PBKDF2 hash algorithm stribog512 not available, skipping.
Apr 29 10:42:26 mach kernel: audit: type=1100 audit(1588149746.548:29): pid=3615 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=? acct="bob" exe="/usr/bin/login" hostname=mach addr=? terminal=tty1 res=failed'
Apr 29 10:42:26 mach audit[3615]: USER_AUTH pid=3615 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=? acct="bob" exe="/usr/bin/login" hostname=mach addr=? terminal=tty1 res=failed'
Apr 29 10:42:26 mach login[3615]: pam_unix(login:auth): authentication failure; logname=LOGIN uid=0 euid=0 tty=tty1 ruser= rhost=  user=bob
Apr 29 10:42:22 mach dbus-daemon[2279]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Apr 29 10:42:22 mach dbus-daemon[2279]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.2' (uid=0 pid=2280 comm="/usr/bin/NetworkManager --no-daemon ")
Apr 29 10:42:19 mach systemd-cryptsetup[3624]: PBKDF2 hash algorithm stribog512 not available, skipping.
Apr 29 10:42:17 mach dbus-daemon[2279]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.resolve1.service': Unit dbus-org.freedesktop.resolve1.service not found.
Apr 29 10:42:17 mach dbus-daemon[2279]: [system] Activating via systemd: service name='org.freedesktop.resolve1' unit='dbus-org.freedesktop.resolve1.service' requested by ':1.2' (uid=0 pid=2280 comm="/usr/bin/NetworkManager --no-daemon ")
Apr 29 10:42:10 mach systemd[1]: Condition check resulted in Update is Completed being skipped.
Apr 29 10:42:10 mach systemd[1]: Condition check resulted in Create System Users being skipped.
Apr 29 10:42:10 mach systemd[1]: Condition check resulted in FUSE Control File System being skipped.
Apr 29 10:42:10 mach systemd[1]: Condition check resulted in Load Kernel Modules being skipped.
Apr 29 10:42:10 mach systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
Apr 29 10:42:10 mach systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
Apr 29 10:42:10 mach systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Apr 29 10:42:10 mach systemd[1]: Condition check resulted in First Boot Wizard being skipped.
Apr 29 10:42:10 mach systemd[1]: Starting Cryptography Setup for data1...
Apr 29 10:42:10 mach systemd[1]: Stopped target Block Device Preparation for /dev/mapper/data1.
Apr 29 10:42:10 mach kernel: audit: type=1130 audit(1588149730.751:21): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-cryptsetup@data1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 29 10:42:10 mach systemd[1]: Reached target Block Device Preparation for /dev/mapper/data1.
Apr 29 10:42:10 mach audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-cryptsetup@data1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 29 10:42:10 mach systemd[1]: cryptsetup.target: Job cryptsetup.target/start failed with result 'dependency'.
Apr 29 10:42:10 mach systemd[1]: Dependency failed for Local Encrypted Volumes.
Apr 29 10:42:10 mach systemd[1]: Failed to start Cryptography Setup for data1.
Apr 29 10:42:10 mach systemd[1]: systemd-cryptsetup@data1.service: Failed with result 'exit-code'.
Apr 29 10:42:10 mach systemd[1]: systemd-cryptsetup@data1.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 10:42:10 mach systemd-cryptsetup[2287]: Failed to load tcrypt superblock on device /dev/sda1: Invalid argument
Apr 29 10:42:10 mach systemd-cryptsetup[2287]: PBKDF2 hash algorithm stribog512 not available, skipping.
Apr 29 10:41:53 mach audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-user-sessions comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 29 10:41:53 mach systemd[1]: Finished Permit User Sessions.
Apr 29 10:41:53 mach systemd[1]: Condition check resulted in Update is Completed being skipped.
Apr 29 10:41:53 mach systemd[1]: Condition check resulted in Create System Users being skipped.
Apr 29 10:41:53 mach systemd[1]: Condition check resulted in FUSE Control File System being skipped.
Apr 29 10:41:53 mach systemd[1]: Condition check resulted in Load Kernel Modules being skipped.
Apr 29 10:41:53 mach systemd[1]: Condition check resulted in Commit a transient machine-id on disk being skipped.
Apr 29 10:41:53 mach systemd[1]: Condition check resulted in Rebuild Journal Catalog being skipped.
Apr 29 10:41:53 mach systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
Apr 29 10:41:53 mach systemd[1]: Condition check resulted in Store a System Token in an EFI Variable being skipped.
Apr 29 10:41:53 mach systemd[1]: Condition check resulted in Rebuild Dynamic Linker Cache being skipped.
Apr 29 10:41:53 mach systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
Apr 29 10:41:53 mach systemd[1]: Condition check resulted in First Boot Wizard being skipped.
Apr 29 10:41:53 mach systemd[1]: Starting Cryptography Setup for data1...
Apr 29 10:41:53 mach kernel: audit: type=1130 audit(1588149713.651:13): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-cryptsetup@data1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 29 10:41:53 mach systemd[1]: Reached target System Initialization.
Apr 29 10:41:53 mach systemd[1]: Reached target Block Device Preparation for /dev/mapper/data1.
Apr 29 10:41:53 mach audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-cryptsetup@data1 comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Apr 29 10:41:53 mach systemd[1]: cryptsetup.target: Job cryptsetup.target/start failed with result 'dependency'.
Apr 29 10:41:53 mach systemd[1]: Dependency failed for Local Encrypted Volumes.
Apr 29 10:41:53 mach systemd[1]: Failed to start Cryptography Setup for data1.
Apr 29 10:41:53 mach systemd[1]: systemd-cryptsetup@data1.service: Failed with result 'exit-code'.
Apr 29 10:41:53 mach systemd[1]: systemd-cryptsetup@data1.service: Main process exited, code=exited, status=1/FAILURE
Apr 29 10:41:53 mach systemd-cryptsetup[473]: Failed to load tcrypt superblock on device /dev/sda1: Invalid argument
Apr 29 10:41:53 mach systemd-cryptsetup[473]: PBKDF2 hash algorithm stribog512 not available, skipping.
Apr 29 10:41:45 mach systemd-cryptsetup[473]: PBKDF2 hash algorithm stribog512 not available, skipping.
Apr 29 10:41:10 mach systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
Apr 29 10:41:10 mach audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-ask-password-console comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Apr 29 10:41:37 mach systemd[1]: Finished Cryptography Setup for data2.
Apr 29 10:41:10 mach systemd[1]: Starting Cryptography Setup for data1...
Apr 29 10:41:10 mach systemd[1]: Starting Cryptography Setup for data2...

Otherwise, I have no problem when mounting both using cryptsetup.

Would you know how I can solve this issue in order to automount both my partitions at boot please?

Thank you in advance.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.