LibreElec on Wyse 5010 does not properly shut down

Skeeve · December 24, 2022 at 4:24 PM

I installed LibreElec 10.0.2 (previously 9.something) on my Wyse 5010 Thin Client.

Everything seems to work okay except for the shutdown. The system does not power off.

It hangs with:

Code

(LibreELEC (official): 10.0.2
242.7689931 [12531: Failed to unmount /flash: Device or resource busy
[ 242.7713681 systemd-shutdownt11: Failed to finalize file systems, loop devices, ignoring.
242.9591521 reboot: Power down

I tried journalctl -f via ssh but it doesn't give me a clue what's going wrong. Can anybody please give me some guidance?

journalctl output

Code

-- Journal begins at Sat 2022-12-24 16:13:57 UTC. --
Dec 24 16:14:11 KodiWyse kernel: snd_hda_intel 0000:00:01.1: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj.
Dec 24 16:14:12 KodiWyse kodi.sh[1145]: libva info: VA-API version 1.11.0
Dec 24 16:14:12 KodiWyse kodi.sh[1145]: libva info: Trying to open /usr/lib/dri/r600_drv_video.so
Dec 24 16:14:12 KodiWyse kodi.sh[1145]: libva info: Found init function __vaDriverInit_1_11
Dec 24 16:14:12 KodiWyse kodi.sh[1145]: libva info: va_openDriver() returns 0
Dec 24 16:14:30 KodiWyse systemd[1]: systemd-hostnamed.service: Succeeded.
Dec 24 16:16:16 KodiWyse connmand[330]: eth0 {del} route 82.165.8.211 gw 192.168.192.168 scope 0 <UNIVERSE>
Dec 24 16:16:17 KodiWyse connmand[330]: eth0 {add} route 82.165.8.211 gw 192.168.192.168 scope 0 <UNIVERSE>
Dec 24 16:16:25 KodiWyse connmand[330]: eth0 {del} route 82.165.8.211 gw 192.168.192.168 scope 0 <UNIVERSE>
Dec 24 16:17:25 KodiWyse sshd[1195]: Accepted publickey for root from 192.168.192.20 port 54359 ssh2: RSA SHA256:BVwzxOq1/0xWmkucmaDi9a2Xpmq7FyecMMo6+FXkjF4
Dec 24 16:17:50 KodiWyse systemd-logind[317]: System is powering down.
Dec 24 16:17:50 KodiWyse systemd[1]: Removed slice system-modprobe.slice.
Dec 24 16:17:50 KodiWyse systemd[1]: Stopped target Kodi Mediacenter Interface.
Dec 24 16:17:50 KodiWyse systemd[1]: Stopped target RPC Port Mapper.
Dec 24 16:17:50 KodiWyse systemd[1]: Stopped target Sound Card.
Dec 24 16:17:50 KodiWyse systemd[1]: Stopped target System Time Synchronized.
Dec 24 16:17:50 KodiWyse systemd[1]: Stopped target System Time Set.
Dec 24 16:17:50 KodiWyse systemd[1]: Stopped target Timers.
Dec 24 16:17:50 KodiWyse systemd[1]: systemd-tmpfiles-clean.timer: Succeeded.
Dec 24 16:17:50 KodiWyse systemd[1]: Stopped Daily Cleanup of Temporary Directories.
Dec 24 16:17:50 KodiWyse systemd[1]: Starting Save random entropy at shutdown...
Dec 24 16:17:50 KodiWyse systemd[1]: cpufreq.service: Succeeded.
Dec 24 16:17:50 KodiWyse systemd[1]: Stopped Set CPU frequency governor and its tunables.
Dec 24 16:17:50 KodiWyse systemd[1]: Stopping Kodi Media Center...
Dec 24 16:17:50 KodiWyse systemd[1]: ledfix.service: Succeeded.
Dec 24 16:17:50 KodiWyse systemd[1]: Stopped LEDfix Service.
Dec 24 16:17:50 KodiWyse systemd[1]: Stopping RPC Bind...
Dec 24 16:17:50 KodiWyse systemd[1]: Stopping Udevil mount service...
Dec 24 16:17:50 KodiWyse systemd[1]: wait-time-sync.service: Succeeded.
Dec 24 16:17:50 KodiWyse systemd[1]: Stopped Wait for Kernel Time Synchronisation.
Dec 24 16:17:50 KodiWyse systemd[1]: xorg-configure@radeon.service: Succeeded.
Dec 24 16:17:50 KodiWyse systemd[1]: Stopped configure Xorg Server for radeon.
Dec 24 16:17:50 KodiWyse systemd[1]: Removed slice system-xorg\x2dconfigure.slice.
Dec 24 16:17:50 KodiWyse systemd[1]: var-media-PHOTOTANK.mount: Succeeded.
Dec 24 16:17:50 KodiWyse systemd[1]: Unmounted /var/media/PHOTOTANK.
Dec 24 16:17:50 KodiWyse add-random-at-shutdown[1206]: 4+0 records in
Dec 24 16:17:50 KodiWyse add-random-at-shutdown[1206]: 4+0 records out
Dec 24 16:17:50 KodiWyse systemd[1]: rpcbind.service: Succeeded.
Dec 24 16:17:50 KodiWyse udevil[1205]: udevil: success running umount as current user
Dec 24 16:17:50 KodiWyse systemd[1]: Stopped RPC Bind.
Dec 24 16:17:50 KodiWyse add-random-at-shutdown[1206]: 2048 bytes (2.0KB) copied, 0.000479 seconds, 4.1MB/s
Dec 24 16:17:50 KodiWyse systemd[1]: Finished Save random entropy at shutdown.
Dec 24 16:17:50 KodiWyse systemd[1]: udevil-mount@-dev-sdb1.service: Succeeded.
Dec 24 16:17:50 KodiWyse systemd[1]: Stopped Udevil mount service.
Dec 24 16:17:50 KodiWyse systemd[1]: Removed slice system-udevil\x2dmount.slice.
Dec 24 16:17:53 KodiWyse systemd[1]: kodi.service: Succeeded.
Dec 24 16:17:53 KodiWyse systemd[1]: Stopped Kodi Media Center.
Dec 24 16:17:53 KodiWyse systemd[1]: intel-fullrange.service: Succeeded.
Dec 24 16:17:53 KodiWyse systemd[1]: Stopped intel switch to full range.
Dec 24 16:17:53 KodiWyse systemd[1]: Stopping Kodi user autostart script...
Dec 24 16:17:53 KodiWyse systemd[1]: kodi-cleanlogs.service: Succeeded.
Dec 24 16:17:53 KodiWyse systemd[1]: Stopped Kodi clean debug logs.
Dec 24 16:17:53 KodiWyse systemd[1]: Starting Kodi poweroff script...
Dec 24 16:17:53 KodiWyse systemd[1]: kodi-autostart.service: Succeeded.
Dec 24 16:17:53 KodiWyse systemd[1]: Stopped Kodi user autostart script.
Dec 24 16:17:53 KodiWyse systemd[1]: Stopped target Graphical Interface.
Dec 24 16:17:53 KodiWyse systemd[1]: Stopping Fluxbox Window Manager...
Dec 24 16:17:53 KodiWyse sh[1230]: /bin/sh: can't open '/storage/.config/shutdown.sh': No such file or directory
Dec 24 16:17:53 KodiWyse systemd[1]: Finished Kodi poweroff script.
Dec 24 16:17:53 KodiWyse systemd[1]: windowmanager.service: Succeeded.
Dec 24 16:17:53 KodiWyse systemd[1]: Stopped Fluxbox Window Manager.
Dec 24 16:17:53 KodiWyse systemd[1]: Stopping Xorg Server...
Dec 24 16:17:53 KodiWyse xorg-launch[1109]: (II) Server terminated successfully (0). Closing log file.
Connection to kodiwyse closed by remote host.
Connection to kodiwyse closed.

Display More

**Da Flex** · December 25, 2022 at 5:21 PM

Probably broken customization since the update. /storage/.config/shutdown.sh doesn't exist by default, but you call it somewhere:

Code

Dec 24 16:17:53 KodiWyse sh[1230]: /bin/sh: can't open '/storage/.config/shutdown.sh': No such file or directory

Find the reason of shutdown.sh.

Skeeve · December 27, 2022 at 10:23 PM

I do not call it. It's a vanilla generic installation I have here.

As far as I understood on other pages, the /storage/.config/shutdown.sh is called by default by the shutdown process, so this error / warning should be expected.

My assumption is: The wyse needs some special shutdown no one knows about So there is no machine-specific shutdown procedure in LibreElec's kernel. I also assume that it's safe, but yet annoying, to power it down manually when the "Power Down" message appears.

**Da Flex** · December 27, 2022 at 11:23 PM

I see. The message only appears after an incomplete shutdown, so I never had this.

Please provide a full debug log.

How to post a log (wiki)

1. Enable debugging in Settings>System Settings>Logging
2. Restart Kodi
3. Replicate the problem
4. Generate a log URL (do not post/upload logs to the forum)

use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

**Da Flex** · December 28, 2022 at 8:49 PM

What was the issue?

**chewitt** · December 29, 2022 at 8:18 AM

Quote from Skeeve

My assumption is: The wyse needs some special shutdown no one knows about So there is no machine-specific shutdown procedure in LibreElec's kernel. I also assume that it's safe, but yet annoying, to power it down manually when the "Power Down" message appears.

I found a couple of other references, but no solution:

201965 – Power off / Shutdown hangs after echoing "Reboot: Power down" on DELL / WYSE Thin Client - AMD G-T56N

GitHub - sanrab/Dell-Wyse-Thin-Client-Dx0D-5010: Linux install on Dell Wyse Thin Client Dx0D/5010

Linux install on Dell Wyse Thin Client Dx0D/5010. Contribute to sanrab/Dell-Wyse-Thin-Client-Dx0D-5010 development by creating an account on GitHub.

github.com

I'd start with ensuring the device has the latest/last available BIOS/firmware update installed, and seeing what if-anything can be configured in the BIOS for the device with respect to power states.

These devices do claim to support SUSE Linux (SLES 12) so any attempt to triage the process might require comparisons with that OS to see what state certain registers or things are being set to (or not) and upstream linux. How to diagnose power-state issues are way beyond my sphere of knowledge though. I did attempt to Google ACPI and references to Wyse but drew blanks. NB: Userspace shutdown scripts are not the problem or solution here. The issue (and any resolution) will be in lower-level code.

Skeeve · December 30, 2022 at 8:43 AM

I haven't had the time yet to debug - sorry.

Skeeve · January 2, 2023 at 3:24 PM

Quote from Da Flex

I see. The message only appears after an incomplete shutdown, so I never had this.
Please provide a full debug log.

How to post a log (wiki)

1. Enable debugging in Settings>System Settings>Logging
2. Restart Kodi
3. Replicate the problem
4. Generate a log URL (do not post/upload logs to the forum)

use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link

The logging does not work. You see… I think you'd need the power-off logs which seem to be lost when powering on again.

But you may give it a try: https://ix.io/4kb7

I tried to run the two log file commands manually and then shutting down. So additionally you might see something in these two logs:
http://ix.io/4kbb

http://ix.io/4kbc

**chewitt** · January 3, 2023 at 8:45 AM

Quote from chewitt

NB: Userspace shutdown scripts are not the problem or solution here. The issue (and any resolution) will be in lower-level code.

^ I'll quote myself again.

Skeeve · January 4, 2023 at 9:16 AM

FYI: OpenSuse does not power off the system as well.

**chewitt** · January 4, 2023 at 10:26 AM

You probably need to test the specific (not Open) SUSE images provided for these devices as those are more likely to have some tweaked power management code. If not, you're needing to read up on ACPI debugging and/or sending emails to the Linux kernel mailing list asking for help on how to debug it. Understanding power states is one of those less-easily understood bit of the kernel .. I don't have any docs I can point you to.

Behoston · April 4, 2023 at 5:54 PM

I have same issue on Mint xfce and lubuntu on my DX0D 5010 with 16GB flash without wifi card.

I've installed thinOS and SUSE (from dell, if someone is interested how to do that, I can post detailed instructions), both can shutdown device with no problem. I also tried Damn Small Linux and it also works fine (at least once). Both (SUSE and DSM) works on very very old kernels like 2.x. However today linux with such an old kernel is almost unusable. So it is not about "tweaks" it is more about some bug in new kernel version (maybe 4.20) or maybe related to some issue with amdgpu drivers - I'm not sure, I have no knowledge how to proceed with further debug. Best solution I already have is to install smart plug and cut the power off about 5 minutes after scheduling shutdown - it is ugly as hell, disable option to use WOL and consume electricity 24/7, but it does the job.

This is caused probably by race condition somewhere in cpufreq. You can read more here:

- https://bugzilla.kernel.org/show_bug.cgi?id=201965

- https://bugzilla.kernel.org/show_bug.cgi?id=199349

- https://lkml.org/lkml/2018/11/13/857

Behoston · April 17, 2023 at 1:36 PM Best Answer

I found the solution:
Add noefi to

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noefi" <-here

in /etc/default/grub

Then run sudo update-grub and restart. Now you can power off

hemant_5400z · August 22, 2023 at 10:59 AM

Hi,

Just to chip in had the same issue with libreelec - Nexus on Dell Wyse 5010.

Using General MAD_X64 build you will need to follow these steps (worked for me):

1.mount -o remount,rw /flash

2.vi /flash/syslinux.cfg

add noefi to the line and save

Code

APPEND boot=UUID=1106-4449 disk=UUID=25c49e90-d6b6-4486-8c2c-12f15a6bef65 noefi quiet

3.vi /flash/EFI/BOOT/grub.cfg

add noefi to the line and save

Code

APPEND boot=UUID=1106-4449 disk=UUID=25c49e90-d6b6-4486-8c2c-12f15a6bef65 noefi quiet

reboot, after that shutdown work properly and the blue power bottom properly goes off.

Cheers,

Hemant