I have been working on this for days now and can't seem to work it out.
I followed the instructions for Mounting network shares for OpenELEC since I read multiple times that this would also work on LibreELEC. I created a *.mount file for each NFS share I want to mount just as described there using the hostname for the NFS share path and tried several things:
- Mounting during runtime using systemd: systemctl start storage-backup.mount
- Mounting during runtime using mount: mount -t nfs <nfs share path using hostname> /storage/backup/ -o nolock
- Enabling mounting on startup (boot) using systemd: systemctl enable storage-backup.mount
Of course I used systemctl daemon-reload when it was necessary.
The first two methods work flawlessly (not depending on whether I use hostname or IP address in the NFS share path). The third one, however, finishes without any errors but if I reboot the path(s) are not mounted.
Here are my specs:
- Kodi version: Kodi 17.5 Git:5bd45ab compiled on Oct 29 2017
- OS: LibreELEC (official): 126.96.36.199 (kernel: Linux 4.9.59, architecture: RPi2.arm)
- Hardware: Raspberry Pi 3 Model B Rev 1.2
- NFS share provided by: QNAP TS659 with firmware version 4.2.6 Build 20171026
Does anyone know why the mount won't take place during boot and how to fix it?
It is even worse. I disabled all symlinks for systemd mounts and tried again with only one. After the first reboot everything was fine. The folder was mounted. On the next reboots the mount disappeared again even if I enabled it again before the next reboot. It just doesn't want to come (back) up. But the symlink persists in ~/.config/system.d/multi-user.target.wants.
I definitely don't know how to help myself anymore. This feels oddly random and strange.
I just found this using either systemctl status storage-backup.mount or journalctl -x:
So it does actually try to mount the unit (meaning it ist truely enabled) but it does fail on doing so. Why is that?