Hi Carlos,
Did you look at the logs?
Yes. Here is a snippet: ,----[ Output of journalctl -xb ] | Nov 01 04:01:31 karnak systemd[1]: | dev-disk-by\x2did-scsi\x2d1WD_My_Book_1140_WCAZA8742496\x2dpart1.device: | Job dev-disk | -by\x2did-scsi\x2d1WD_My_Book_1140_WCAZA8742496\x2dpart1.device/start timed out. | Nov 01 04:01:31 karnak systemd[1]: Timed out waiting for device | dev-disk-by\x2did-scsi\x2d1WD_My_Book_1140_WCAZA8742496\ | x2dpart1.device. | -- Subject: Unit dev-disk-by\x2did-scsi\x2d1WD_My_Book_1140_WCAZA8742496\x2dpart1.device has failed | -- Defined-By: systemd | -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel | -- | -- Unit dev-disk-by\x2did-scsi\x2d1WD_My_Book_1140_WCAZA8742496\x2dpart1.device has failed. | -- | -- The result is timeout. | Nov 01 04:01:31 karnak systemd[1]: Dependency failed for /data3. | -- Subject: Unit data3.mount has failed | -- Defined-By: systemd | -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel | -- | -- Unit data3.mount has failed. | -- | -- The result is dependency. | Nov 01 04:01:31 karnak systemd[1]: data3.mount: Job data3.mount/start failed with result 'dependency'. | Nov 01 04:01:31 karnak systemd[1]: Dependency failed for File System | Check on /dev/disk/by-id/scsi-1WD_My_Book_1140_WCAZA8742496-part1. | -- Subject: Unit | systemd-fsck@dev-disk-by\x2did-scsi\x2d1WD_My_Book_1140_WCAZA8742496\x2dpart1.service | has failed | -- Defined-By: systemd | -- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel | -- | -- Unit systemd-fsck@dev-disk-by\x2did-scsi\x2d1WD_My_Book_1140_WCAZA8742496\x2dpart1.service has failed. | -- | -- The result is dependency. `---- I have: 1. Verified the system can see the drive with "fdisk -l". 2. Ran fsck on it with no problems. However, the drive would not mount at boot nor with the "mount" command. However, it mounts immediately with "udiskctl mount -b <device>". This is all very strange. Charles -- Avoid the Gates of Hell. Use Linux (Unknown source)