I saw this pop up in other threads, but didn’t find anything I could apply, or at least that I knew how to apply. So here is another thread…
I get this on boot:
**] A start job is running for dev-disk-by\x2duuid-d0129dc8\x2d17f1\x2d4393\x2d92b1\x2d993288330b06.device (1min 30s / 1min 30s TIME ] Timed out waiting for device dev-disk-by\x2duuid-d0129dc8\x2d17f1\x2d4393\x2d92b1\x2d993288330b06.device.
[DEPEND] Dependency failed for Cryptography Setup for cr_sda1.
[DEPEND] Dependency failed for Local Encrypted Volumes.
so the thing waits 90 seconds, and then everything seems to boot fine.
[FAILED] Failed to mount /mnt/nashome.
See 'systemctl status mnt-nashome.mount' for details.
[DEPEND] Dependency failed for Remote File Systems.
Once the system is up and I can log in I ran:
# systemctl status mnt-nashome.mount
● mnt-nashome.mount - /mnt/nashome
Loaded: loaded (/etc/fstab; generated)
Active: active (mounted) (Result: exit-code) since Sun 2018-04-08 11:22:17 BST; 19min ago
Process: 1276 ExecMount=/usr/bin/mount 192.168.1.61:/share/nashome /mnt/nashome -t nfs4 (code=exited, status=32)
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
So, waiting a little time, also the NFS partition seems to be mounted… So why does it take so long to mount both?
that shouldn’t be the case, it’s on a fast SSD… anyway, I ended up doing a clean installation, so that now the drive is not encrypted and everything seems fine.
Thanks! I looked into that and set it up, really nice. I tried with _netdev but that didn’t seem to make a difference. I read somewhere that netfs has to be installed and up, I looked it up in yast and didn’t find it, so gave up and went with autofs, and seems to be working fine… for now!