I erased all the NTP-entries in System/Settings/LibreELEC/Network, but this doesn't work either.
Posts by johan.viberg
-
-
I added date -s "2019-02-06 09:48:42" to autostart.sh. It still doesn't work. Here's the log:
I will try resetting the nfs servers later today.
-
Thanks for helping me out!
I did as you said using vers=3.0. Here's the link:
Here's a screen dump of my ntp settings:
-
I think I've found a solution:
It works if I add vers=1.0 to the mount options.
Weird...
-
I use cifs.mount.sample as a template:
Code
Display MoreLibreELEC:~/.config/system.d # cp cifs.mount.sample storage-Pi.mount LibreELEC:~/.config/system.d # mkdir /storage/Pi LibreELEC:~/.config/system.d # vi storage-Pi.mount LibreELEC:~/.config/system.d # systemctl start storage-Pi.mount LibreELEC:~/.config/system.d # ls /storage/Pi/ Desktop Pictures Videos Documents Public python_games Downloads Synology useful_commands.txt Music Templates vpnrouting.sh LibreELEC:~/.config/system.d # systemctl stop storage-Pi.mount LibreELEC:~/.config/system.d # systemctl enable storage-Pi.mount Created symlink /storage/.config/system.d/multi-user.target.wants/storage-Pi.mount → /storage/.config/system.d/storage-Pi.mount. LibreELEC:~/.config/system.d # reboot
storage-Pi.mount looks like this:
Code
Display More# This is a sample service script to mount CIFS/SAMBA 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=test cifs mount script # 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=//192.168.8.4/pi # Where we want mount this share Where=/storage/Pi # Any options you usually use with the "-o" parameter in the mount command Options=username=pi,password=raspberry # filesystem type Type=cifs [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/music2" (see above "Where=/storage/music2") # then this file must be renamed to 'storage-music2.mount' and can be enabled via ssh with the # command 'systemctl enable storage-music2.mount'
After the reboot, the mount is broken:
systemctl status storage-Pi.mount returns:
Code
Display More● storage-Pi.mount - test cifs mount script Loaded: loaded (/storage/.config/system.d/storage-Pi.mount; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2018-06-22 13:11:57 CEST; 7 months 14 days ago Where: /storage/Pi What: //192.168.8.4/pi Jun 22 13:11:53 LibreELEC systemd[1]: Mounting test cifs mount script... Jun 22 13:11:57 LibreELEC mount[325]: mount: mounting //192.168.8.4/pi on /storage/Pi failed: Host is down Jun 22 13:11:57 LibreELEC systemd[1]: storage-Pi.mount: Mount process exited, code=exited status=255 Jun 22 13:11:57 LibreELEC systemd[1]: storage-Pi.mount: Failed with result 'exit-code'. Jun 22 13:11:57 LibreELEC systemd[1]: Failed to mount test cifs mount script.
Note the date Fri 2018-06-22 13:11:57 CEST and Host is down (which it is not).
Doing systemctl start storage-Pi.mount makes it work again and systemctl status storage-Pi.mount now returns:
Code● storage-Pi.mount - test cifs mount script Loaded: loaded (/storage/.config/system.d/storage-Pi.mount; enabled; vendor preset: disabled) Active: active (mounted) since Tue 2019-02-05 07:03:48 CET; 2min 33s ago Where: /storage/Pi What: //192.168.8.4/pi CGroup: /system.slice/storage-Pi.mount Feb 05 07:03:48 LibreELEC systemd[1]: Mounting test cifs mount script... Feb 05 07:03:48 LibreELEC systemd[1]: Mounted test cifs mount script.
-
I use my Synology NAS to store recordings etc from Tvheadend in LE. I need the network share to be set up at boot. I've used the instructions at Mounting network shares [LibreELEC.wiki] but it doesn't work.
When I do systemctl status storage-Synology-backup.mount, I get:
Code... Jun 22 13:11:57 LibreELEC mount[323]: mount: mounting //192.168.8.2/backup on /storage/Synology/backup failed: Host is down
First the date (Jun 22) is strange, but more importantly the host (192.168.8.2) is not down.
I think this is a timing error and that the network is not fully up or it might also be that there is a timeout in trying to connect to the server.
When I do systemctl start storage-Synology-backup.mount it works and the share is correctly mounted.
Any ideas?
I used to have the same kind of problem pre LE 9 that I solved using some magic (that I have now forgotten). After the update to LE 9 the problem is back again