Posts by Grimson

LibreELEC

Quote from nickr

Refresh hasn't worked for me.

Clear/Empty the browser cache.

What IP and netmask has your PI, what IP and netmask have the other devices in the network.

Is your wireless connection setup as a guest network, or do you have AP isolation activated.

Workgroup has no effect on SSH or pings. You need to provide detailed information about your network setup to diagnose this.

Quote from macmpi

It does not seem a generic (all platform) Kodi bug: would the issue lie on LibreELEC remit?

Read the posts I linked above. It's (at least) reported on Android, Windows, IOs and OpenELEC, what makes you think it's LibreELEC only?

Just download the .tar file and extract it.

Skin settings won't save
skin settings not saving
Skin settings not being retained profile to profile in Jarvis
Jarvis Skin Settings

It seems to be a Kodi issue in itself, so read the above threads and see if they contain anything that might help.

You're not supposed to edit the sources in the build directory. You rather should create patch files, look at the differen packages to see how they work. This way the buildsystem detects changes and rebuilds the needed parts by itself.

Quote from fTdOmen

By using the bios boot tool, I am completely bypassing auto mounting.

Nope, mounting is done by the Linux kernel and has nothing to do with the bios tool. The tool just chooses the initial boot device.

Quote from fTdOmen

Is this an issue specifically due to how similar OE and LE are? As I've never encountered an issue like this when creating Windows & SteamOS drives.

Yes, because both use similar partition labels/device names while other distributions use unique UUIDs.

Quote from fTdOmen

I get that best practice would be to remove the SSD drive before installing LibreElec on the usb key, but I'm still rather surprised that I'm coming up with this error message.

It's not only best practice but actually required in your case. Because otherwise you have two system and storage partitions each, and they get mixed up in the mounting process causing random issues like the one you are reporting.

Quote from David1977

I edited my posting already

Yeah, I know I still like to point out/document such pitfalls. Nothing personal.

Quote from David1977

Good points!!!

This:

"2. The process running the shutdown.sh, is killed before the script is completely executed."

could be tested if you let the fuckme.sh write something to a file.

fuckme.sh:

Bash

#!/bin/sh
echo `date` > /storage/test.txt

or, if `date` doesn't work in sh:

Bash

#!/bin/sh
echo "This script runs" > /storage/test.txt

and then check if something is written to test.txt

Display More

That test won't be conclusive, because opening a SSH connection with public key authorization takes quite a bit longer than writing a few bytes of text onto the sdcard/ssd, and it takes even longer when the SSH daemon on the NAS performs DNS lookups for connecting clients. That's why I asked whether the logs from the NAS are showing incomplete/failed connection attempts.

Edit, in reference to my earlier post here change your script this way, and we also want stderr logged too:

#!/bin/sh
/bin/ping -c4 192.168.178.43 1> /storage/test.txt 2>&1

Two possible reasons, though I don't have tested them so far:

1. The network connection could be shutdown before the shutdown.sh is called.
2. The process running the shutdown.sh, is killed before the script is completely executed.

Is there anything in the logs from the NAS? Does it show an SSH connection attempt?
Try to ping the NAS from your custom script and log the output to a file, this should show whether the network is still up or not.

Open the script, find this line:

grep OpenELEC /etc/os-release >/dev/null && DDTIME=5 || DDTIME=6

change "OpenELEC" to "LibreELEC" and give it a try.

Make sure you saved the samba config file as "samba.conf" and not "samba.conf.sample" in the "configfiles" share. It then should be enough to deactivate and reactivate samba, but a complete reboot of the LE device can't hurt eighter.

Thank you!

Some general informations about shell scripts.

You should never trust that environment variables like "path" are correctly set, always use the full path to a binary, so for example:

ssh do_stuff

is bad.

/usr/bin/ssh do_stuff

is the correct way.

You seem to be using public key authentification for the connection to your NAS. If yes the above also applies for the certificates, so better specify them with the "-i" parameter, see ssh.

When you enter the LibreELEC forum there are speech bubbles in front of every sub forum showing wheter it contains new posts or not. Currently the color difference between those two versions is quite minimal and on a bright monitor you can barely see it. So I would like to suggest to change the color of one of them.

Maybe change the one that signals new posts into a green/brown combination, fitting the LE logo.