Posts by fanformusik

Here you are (password replaced by *****):

LibreELEC:~ # cat /storage/.config/system.d/storage-ProLiant.mount
[Unit]
Description=cifs mount script
Requires=network-online.service
After=network-online.service
Before=kodi.service
[Mount]
What=//192.168.0.10/Media/PVR
Where=/storage/ProLiant
Options=username=Michael,password=*****,rw,vers2.1
Type=cifs
[Install]
WantedBy=multi-user.target
LibreELEC:~ #

I tried manual mounting (password replaced by *****):

LibreELEC:~ # mount -t cifs -o username=Michael,password=*****,vers=2.1 //192.168.0.10/Media/PVR /storage/ProLiant

This works as expected. I can see all my server files in /storage/ProLiant.

Any idea?

UPDATE : I found it

In my mount definition file (see above) the "=" was missing: vers2.1 needs to be vers=2.1

Changed it and the share is mounted.

This parameter is taken from the sample mount definition File in the librelec Wiki.

Not correct?

Mario77 : Thank you for your help! This time, things changed:

dos2unix... did not help.

For curiosity, I checked my config file /storage/.config/system.d/storage-ProLiant.mount . And it had NO credentials info under "options". How can that happen? So, I added the login data manually with nano and rebooted LE. The share would not be mounted again, but this time the error messages are different. See below "...Unknown parameter 'vers2.1'.

Does that give an indication what's wrong?

May 28 21:16:59 LibreELEC systemd[1]: Mounting storage-ProLiant.mount... 
May 28 21:16:59 LibreELEC systemd[1]: Starting nmbd.service... 
May 28 21:16:59 LibreELEC connmand[684]: eth0 {del} route 212.227.81.55 gw 192.168.0.1 scope 0 <UNIVERSE> 
May 28 21:16:59 LibreELEC mount[932]: mount error(22): Invalid argument 
May 28 21:16:59 LibreELEC mount[932]: Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) 
May 28 21:16:59 LibreELEC systemd[1]: storage-ProLiant.mount: Mount process exited, code=exited, status=32/n/a 
May 28 21:16:59 LibreELEC systemd[1]: storage-ProLiant.mount: Failed with result 'exit-code'. 
May 28 21:16:59 LibreELEC kernel: cifs: Unknown parameter 'vers2.1' 
May 28 21:16:59 LibreELEC systemd[1]: Failed to mount storage-ProLiant.mount. 

And here again, the messages

journalctl -xe

May 28 20:46:50 LibreELEC systemd[1]: Mounting storage-ProLiant.mount...
May 28 20:46:50 LibreELEC systemd[1]: Starting nmbd.service...
May 28 20:46:50 LibreELEC mount[924]: username specified with no parameter
May 28 20:46:50 LibreELEC systemd[1]: Started service.tvheadend42.service.
May 28 20:46:50 LibreELEC systemd[1]: Finished wait-time-sync.service.
May 28 20:46:50 LibreELEC systemd[1]: storage-ProLiant.mount: Mount process exited, code=exited, status=1/FAILURE
May 28 20:46:50 LibreELEC systemd[1]: storage-ProLiant.mount: Failed with result 'exit-code'.
May 28 20:46:50 LibreELEC systemd[1]: Failed to mount storage-ProLiant.mount.

Mario77 :

Here are my actual settings (from kodi):
Lowest supported protocol version = SMB2
Highest supported protocol version = SMB3

For testing I changed SMB2 to SMB1, but no success.

Network waiting delay = 10 sec

Messages on LE boot:
Waiting on network to come online...
Failed to mount storage-ProLiant.mount (=the mount def file)

Interestingly, from within kodi I can access the server without problems, but during LE startup mounting a network share to a local folder fails (I need this for TV recording, TVheadend can't write to network).

Reddirt :

I am NOT using any Windows PCs in my setup (see above: My server runs openmediavault, i.e. Linux based). The issue startet after I updated LE11 to LE12, and there was no other change. So, I think it must be related to that somehow.

Hello Mario77,

Quote from Mario77

Check kodi settings services smb client minimum 1,maximum 3,

The issue is not related to kodi. The mount error occurs on booting LE (error message: network FAILED), before kodi is started.

Quote

Make sure folder on your PC is shared.

I use a dedicated server that runs openmediavault. The server is fine, and all data can be acessed without problem.
With LE11, I had no problems connecting.

Quote

Check mount file for any errors from editing on windows

I did not edit the mount file, and it worked before with LE11.

Any other idea?

A few days ago I started the upgrade LE11 -> LE12. Everything went fine - but LE12 won't mount my samba share any more. I get this error message:

journalctl -xe
.....
May 27 17:52:50 LibreELEC systemd[1]: Mounting storage-ProLiant.mount...
May 27 17:52:50 LibreELEC mount[1958]: username specified with no parameter
May 27 17:52:50 LibreELEC systemd[1]: storage-ProLiant.mount: Mount process exited, code=exited, status=1/FAILURE
May 27 17:52:50 LibreELEC systemd[1]: storage-ProLiant.mount: Failed with result 'exit-code'.
May 27 17:52:50 LibreELEC systemd[1]: Failed to mount storage-ProLiant.mount.
.....

I double checked my mount definition file (storage-ProLiant.mount) but it is completely unchanged, and contains full username and password.
I disabled the "old" mountpoint, rebooted LE and enabled the mountpoint again: Still no connection to the share.

For info, here's my mount def file (credentials replaced by ****)

[Unit]
Description=cifs mount script
Requires=network-online.service
After=network-online.service
Before=kodi.service
[Mount]
What=//192.168.0.10/Media/PVR
Where=/storage/ProLiant
Options=username=******,password=***********,rw,vers=2.1
Type=cifs
[Install]
WantedBy=multi-user.target

Did I make a mistake? How can I reconnect my Network share?

Since shortly, presumably after an automatic update, TVheadend 10.0.0.126 was installed. This lead to complete failure of TV+PVR services.

Addons.log has this error message:

###############################################################################
# ... output of cat /storage/.kodi/userdata/addon_data/service.tvheadend42/service.log
# LibreELEC release: Generic.x86_64-10.0.2
#
################################################################################
/storage/.kodi/addons/service.tvheadend42/bin/tvheadend: error while loading shared libraries: libx265.so.199: cannot open shared object file: No such file or directory 

It seems that a file is missing (or was deleted during the update process).

After a downgrade to TVheadend 10.0.0.125 everything worked fine again.

Hello,

after 2 months, there were no more sound issues. My problem has been fixed by getedid.

Thanks!

Hello,

after installation of getedid HDMI sound seems to work fine after resume from standby. I will observe this in the future, but i looks as if it cured my problem.

mglae: Thank you very much!

Quote from mglae

Try getedid.

Thank you. I installed getedid using the provided script and all went fine.

It will take a few days to find out if this cleaned up my problem.

Hello all,

although quite old, this issue is still present on my system (config+specs see below). The problem occurs sporadically and none of the proposed actions seemed to work. So I decided to re-open the discussion and ask for help again.

Interestingly, I never can re-activate HDMI sound by simply going to ->System->Settings->Audio (as proposed here and in other posts). The only way is to cold reboot LibreElec, after which everything works fine.

Also, when putting LibreElec into standby manually (via its On/Off menu), HDMI sound is usually fine after resume, but If I let LibreElec go to standby automatically (e.g. after completing a PVR recording), almost ervery time it wakes up with no sound. The only difference I see is that the connected units (Receiver, Projector) are active during manual shutdown, but inactive during PVR operation (manual shutdown).

Is there ayone out there who can help?

Thank you very much in advance!

-----------------

HTPC System setup:

CableTV--->(DVB Stick)---USB--->(INTEL NUC)---HDMI--->(Receiver)---HDMI--->(Projector)

(DVB Stick): Hauppauge win-TV Dual HD

(INTEL NUC): DN2820FYKH , LibreELEC 9.2.2 + Tvh 4.2.8-36 + addon v9.2.0.121

(Receiver) : Pioneer VSX S520D

(Projector): EH-TW6700W

Hello Nicolas,

just to let you know: There was no more Freeze since I made the Fresh install last Thursday (I only backed up + reinstalled Tvh settings).

It seems that my System suffered from "leftovers", so I will install the "profile cleaner" as you advised.

Once again, thank you very much!

Michael

Hello,

thank you, Nicolas.

Quote from Nicolas

Mediathekview 062 is still in your logs and Returns Errors.

Oh, that is strange…

I will do a complete reinstall then. Something for the upcoming Holidays....

Quote from Nicolas

Thumbnail cleanup

What is that? And how is it done?

Thanks and best regards
Michael

Hello,

I'm back, sooner than expected: Last night I saw one more Freeze, i.e. the Actions above didn't help. Logfiles are attached.

It went the typical way: I cold booted my System, then navigated to the Live TV tab, then pressed OK, then the System stalled.
Since my HTPC is connected to LAN, I tried to Access it (while stalled) from a remote Computer:
- the System was accessible via LAN, and I was able to retrieve the error logfiles (attached)
- Tvheadend addon's configuration page was reachable too and seemed to be functional

From the above I assume that Libreelec's GUI crashes.

How should I go on to find the Problem? Any Ideas?

Thank you very much!

Hello Nicolas,

sorry for not posting anything over last weekend…

I deinstalled mediaview and replaced it by two different addons (ARD Mediathek and ZDF Mediathek, from official libreelec repositories). Now I will watch if my System gets more stable. This should take a few days.

I will keep you informed.

Hello Nicolas,

thank you very much.

Quote from Nicolas

German TV you should use a refresh rate of 50hz

Yes, this is what I use. (->third post pof mine)

Quote from Nicolas

But as you say the Problems came Up recently i would guess on RAM.

I have seen those freezes sporadically all the time. But recently they become more frequent. (->first post)

I am not sure if that the problem results from a bad RAM. If so, the whole System would be much more unstable and fail in random situations. Here, the failure ONLY occurs when trying to activate Live TV.

Quote from Nicolas

If you Set a 5 Second wait for the tvh

I will try this, but I doubt it will help. For testing, I configured my System not to go to Live TV after boot, which introduces sort of a "Manual delay", as Live Tv has to be activated manually. This did not improve anything. (->first post)

Last night, I had another Freeze after applying all above Actions. The log files are attached.

Can something be found in the data?