Hello everybody,
I have a problem since last major update to LE 11 on a Raspberry Pi 4. I have a couple of sshfs shares that were automatically mounted via systemd service files at boot time. Now they do not start automatically anymore, and I cannot start them manually neither through systemd. I can mount the drives via command line using the 'sshfs' command (in fact, using the same command that is specified on the unit file). I saw previous problems with a similar setup, but again, this was working OK until I updated last week.
Any ideas? Thanks
systemd status:
Code
× storage-nfs-Folder.mount - Mount folder from drive
Loaded: loaded (/storage/.config/system.d/storage-nfs-Folder.mount; enabled; preset: disabled)
Active: failed (Result: exit-code) since Sun 2023-03-19 11:13:53 CET; 11min ago
Where: /storage/nfs/Folder
What: /storage/.kodi/addons/virtual.network-tools/bin/sshfs#root@drive:/shares/Folder
CPU: 4ms
Mar 19 11:13:53 libreelec systemd[1]: Mounting storage-nfs-Folder.mount...
Mar 19 11:13:53 libreelec mount[1137]: /storage/.kodi/addons/virtual.network-tools/bin/sshfs: error while loading shared libraries: libfuse3.so.3: cannot open shared object file: No such file or directory
Mar 19 11:13:53 libreelec mount[1133]: mount: mounting /storage/.kodi/addons/virtual.network-tools/bin/sshfs on /storage/nfs/Folder failed
Mar 19 11:13:53 libreelec systemd[1]: storage-nfs-Folder.mount: Mount process exited, code=exited, status=127/n/a
Mar 19 11:13:53 libreelec systemd[1]: storage-nfs-Folder.mount: Failed with result 'exit-code'.
Mar 19 11:13:53 libreelec systemd[1]: Failed to mount storage-nfs-Folder.mount.
Display More
systemd unit file:
Code
# This is a sample service script to mount NFS shares.
# Please read carefully the comments in this file. For production usage
# you can remove all comments (lines beginning with "#") from this file.
[Unit]
# The description should be used to explain what this servicefile is for
Description=Mount folder from drive
# if we do network mounts like here we *require* 'network-online.service'
# which checks if the network is online
Requires=network-online.service
# our scripts must start *after* 'network-online.service', on timeout and if
# 'network-online.service' fails we can not mount and this scripts fails too
After=network-online.service
# usually we mount networks shares because we want they avaible *before* XBMC starts.
# so XBMC has access to this mounts from beginning. Note: this slows down the boot!
Before=kodi.service
[Mount]
# The share we want mount
What=/storage/.kodi/addons/virtual.network-tools/bin/sshfs#root@drive:/shares/Folder
# Where we want mount this share
Where=/storage/nfs/Folder
# Any options you usually use with the "-o" parameter in the mount command
Options=allow_other,reconnect,default_permissions,IdentityFile=/storage/.ssh/drive
# filesystem type
Type=fuse.sshfs
[Install]
# The target is used by 'systemctl enable <name_of_this_file.mount>' to link
# this service to a runlevel for starting on boot. usually 'multi-user.target'
# is ok here.
WantedBy=multi-user.target
# Important:
# this file must be renamed to <mountpoint>.mount where <mountpoint>, is the FULL path
# where the share will be mounted but slashes "/" MUST BE REPLACED with dashes "-" with .mount
# as extension.
# This means, if we want mount to "/storage/movies2" (see above "Where=/storage/movies2")
# then this file must be renamed to 'storage-movies2.mount' and can be enabled via ssh with the
# command 'systemctl enable storage-movies2.mount'
Display More
currently working manual command (what + options + where):