Posts by mglae

Add touch /storage/.update/.nocompat to the update process (before reboot). Your old kernel is not able to mount recent squashfs images.

Thanks for the log, it helps to avoid the error in the future.

To erase the system disk press <Alt>-<F3> at the installer screen to switch to the debug console and type

dd if=/dev/zero of=/dev/sda bs=1M count=1

Then <Alt>-<F1> and continue to install.

Edit: in the meantime the current release is LibreELEC-Generic.x86_64-10.0.4.tar

After enabling ssh in the LibreELEC Settings Addon the device can be accessed from Windows using e.g. putty or WinSCP.

User name is root default password is libreelec.

The terminal from System Tools is only available on X11 systems, e.g. LE10/Generic or LE11/Generic-legacy.

Starting with Kodi Matrix/LE10 you have to create an Autoexec Service yourself: https://kodi.wiki/view/Autoexec_Service

It is definitely there on the Estuary skin: https://kodi.wiki/view/Settings/Services/Control

chewitt /dev/sda is listed before /dev/sda1 so sda is powered down before sda1 is unmounted.

1. To see logs of autostop.sh and the shutdown process enable Persistent Logging via LibreELEC Settings Addon, reboot, type journalctl -b -1 and scroll almost to the end. journalctl -b -1 -u kodi-autostart may be more selective.
2. Never use a parallel subshell in autostop.sh. It will be killed after a short time period.

Edit: Disks are still mounted during autostop.sh. Powering them off is a bad idea.

Fix is included in nightly 2013010[45]-21c204a

rasser Thanks for heads up, I've corrected my post for the records.

There was just a report with connman's OfflineMode enabled.

Likely the m4 source of LE10 is "too old" for the Ubuntu 22.10 gcc and library headers.

Use an Ubuntu LTS 20.04 Docker container.

For 9.2 even Ubuntu 18.04 may be required.

Quote from rasser

[global]

OfflineMode=true

That's wrong, type once:

connmanctl disable offline

Eight years old but worth a try: https://stackoverflow.com/questions/2516…down-and-reboot

Are there other reports for Python 3.11 too? E.g. with Fedora 37 or Archlinux?

More detailed research in LE requires using a debug image.

Just a few brief thoughts.

Modifying systemd services

Use /storage/.config/system.d to create systemd drop-in directories or your modified service files. Additional units can be created too.

Persistent Logging

Can be enabled via LE Settings Addon's System tab. Use journalctl -b -1 to view last boot. Logs are visible until local file systems are unmounted on shutdown.

Final error messages

Do exist because neither /flash/SYSTEM nor /flash can be cleanly unmounted while still being used.

Shutdown scripts

Due to target dependencies network access is not possible in shutdown.sh. Use autostop.sh

SEGFAULT due to null pointer access in elementtree, no idea about the cause:

Thread 1 (Thread 0x7f1654ff96c0 (LWP 151486)):
#0  0x0000000000000000 in ?? ()
#1  0x00007f169188738e in ?? () from /usr/lib/python3.11/lib-dynload/_elementtree.so
#2  0x00007f16b9a6f781 in ?? () from /usr/lib/libpython3.11.so.1.0
#3  0x00007f16b9a18c1b in _PyObject_MakeTpCall () from /usr/lib/libpython3.11.so.1.0
#4  0x00007f16b99c8c94 in _PyEval_EvalFrameDefault () from /usr/lib/libpython3.11.so.1.0
#5  0x00007f16b9ae72e0 in ?? () from /usr/lib/libpython3.11.so.1.0
#6  0x00007f16b9ae7383 in PyEval_EvalCode () from /usr/lib/libpython3.11.so.1.0
#7  0x00007f16b9b259f3 in ?? () from /usr/lib/libpython3.11.so.1.0
#8  0x00007f16b9b25bf6 in ?? () from /usr/lib/libpython3.11.so.1.0
#9  0x00007f16b9b25cd0 in ?? () from /usr/lib/libpython3.11.so.1.0
#10 0x00007f16b9b28dec in PyRun_FileExFlags () from /usr/lib/libpython3.11.so.1.0
#11 0x0000000000ab8810 in CPythonInvoker::executeScript(_IO_FILE*, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, _object*) ()
#12 0x0000000000acb2f0 in CPythonInvoker::execute(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::vector<std::__cxx11::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> >, std::allocator<std::__cxx11::basic_string<wchar_t, std::char_traits<wchar_t>, std::allocator<wchar_t> > > >&) ()
#13 0x0000000000acbeca in CPythonInvoker::execute(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > > const&) ()
#14 0x00000000015211be in CLanguageInvokerThread::Process() ()
#15 0x0000000000e559a3 in CThread::Action() ()
#16 0x00000000016a2b93 in ?? ()
#17 0x0000000000e53d93 in ?? ()
#18 0x00007f16b6f2a403 in ?? () from /usr/lib/libstdc++.so.6
#19 0x00007f16b70f0460 in ?? () from /usr/lib/libc.so.6
#20 0x00007f16b7169a2c in ?? () from /usr/lib/libc.so.6

Quote from chewitt

Creating /storage/.please_resize_me will result in the current partition being removed and a new one being created on the next boot. This is a destructive action that will nuke the current contents of /storage, so you probably don't want to do that.

The resize file is ignored if there is anything relevant on the partition although the resize operations are not destructive (when the whole process is working correctly).

It only works on a fresh empty image.

Technically you can revert the commits of #7216 and #7072 and build your test image.

A crash log may be more useful for the script developer.