Other posts for reference:
LUKS Automount no longer working on new hardware
RE: LUKS + KeyFile + AutoMount? [SOLVED]
I moved my omv setup from an intel server to a new hp small form factor pc, now 3 of my data drives will not auto mount anymore.
My current fstab is:CodeDisplay More
/dev/mapper/sda3_crypt / ext4 errors=remount-ro 0 1 # /boot was on /dev/sda1 during installation UUID=d61a4271-e5f7-4c46-9b52-791e5ee0fc36 /boot ext4 defaults 0 2 /dev/mapper/sda2_crypt none swap sw 0 0 # >>> [openmediavault] /dev/disk/by-label/data1 /srv/dev-disk-by-label-data1 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2 /dev/disk/by-label/data2 /srv/dev-disk-by-label-data2 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2 /dev/disk/by-label/data3 /srv/dev-disk-by-label-data3 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2 /dev/disk/by-label/data4 /srv/dev-disk-by-label-data4 ext4 defaults,nofail,user_xattr,usrjquota=aquota.user,grpjquota=aquota.group,jqfmt=vfsv0,acl 0 2 # <<< [openmediavault]
In addition I have crypttab setup for auto unlocking:Code
# <target name> <source device> <key file> <options> #System disks - DO NOT EDIT sda2_crypt UUID=e07a2c60-9fb4-4ff6-85b1-e2ad4c767ebf none luks,swap,discard sda3_crypt UUID=716b232a-f44a-4f46-a276-4e563856c0c6 none luks,discard #Data disks data1 UUID=1dfccdef-7d88-4d5e-9f42-59bd36020c37 /root/keyfile.key luks data2 UUID=298a0d0f-52ce-48f8-817f-d75d293a4836 /root/keyfile.key luks data3 UUID=134a1f5e-46b1-422a-b08d-ccc8476340b9 /root/keyfile.key luks data4 UUID=b9eb750a-5c20-4673-b652-e7e7915cb470 /root/keyfile.key luks
This always worked before on the old server.
Now syslog shows:Code
Dec 15 17:39:03 omv-server monit: Filesystem '/srv/dev-disk-by-label-data1' not mounted Dec 15 17:39:03 omv-server monit: 'filesystem_srv_dev-disk-by-label-data1' unable to read filesystem '/srv/dev-disk-by-label-data1' state Dec 15 17:39:03 omv-server monit: 'filesystem_srv_dev-disk-by-label-data1' trying to restart Dec 15 17:39:03 omv-server monit: 'mountpoint_srv_dev-disk-by-label-data1' status failed (1) -- /srv/dev-disk-by-label-data1 is not a mountpoint
Repeating for each drive. Every time OMV starts it shows "a start job is running for /dev/disk/" cycling through the uuid and label of each drive for 90 seconds before it fails. the data1 partition on the system drive still works for some reason I don't understand.
Now OMV doesn't load because of an issue with trying to load mergerfs while the drives aren't mounted, so i tried to remove the unionfs from the omv config manually, now it shows a bunch of errors and the file systems and luks tabs arent loading in the web interface.
Couldn't extract an UUID from the provided path '/dev/disk/by-label/data2'.
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color quota 2>&1' with exit code '1': omv-server: Data failed to compile: ---------- Rendering SLS 'base:omv.deploy.quota.default' failed: while constructing a mapping in "<unicode string>", line 42, column 1 found conflicting ID 'quota_off_no_quotas_' in "<unicode string>", line 69, column 1
So essentially the entire omv system is now broken, and I even tried creating a new omv install on a flash drive, and it still won't auto mount the data drives. At this point I'm better off just running a media server off Windows 10 but cant convert my ext4 drives back to ntfs. This is too much troubleshooting for a simple media server with basic encryption.
I don't understand how just using a different motherboard has caused automounting to stop working.
You should drop to terminal and start testing the disks. See how if unlocking manually works, then test the key file. Just go one by one. Maybe remove the key file from the crypttab change it to - and test to be prompted at boot for unlock n