Sorry, I forgot that we are on x86.
Then the equivalent idea is to install latest Debian (or whatever Linux) Live on USB stick, and try that hdparm version. I recently made a Debian 12 stick to bring my parallel port printer back to life.
I should be able to do that, 
an Ubuntu server distro would be also fine?
If yes I'll give it a try next days, I'm out of home now.
Thanks a lot.
OK. The next thing I would do is installing RPi OS on another microSD, and see whether it works on that OS.
If it does, then our devs can usually implement it on LE (maybe just copying the command to LE already does the trick).
I don't know anything about RPI Os, never used it nor installed.
I wouldn't be able to configure it or to make any test with it, sorry.
Nothing in hd-idle.log?
The log file is not even being created.
I installed hd-idle and set it up in autostart.sh but it does nothing.
I tried to launch it directly from the command line but it has no effect, literally nothing happens.
The command I used is: /storage/.kodi/addons/virtual.system-tools/bin/hd-idle -a sda -i 1200 -l /storage/logs/hd-idle.log
The "-1 1200" parameter should spin down HDD after 20 minutes but it spins down after few minutes as usual and no log file is written.
I read the manual at https://hd-idle.sourceforge.net/ and the command I used should be fine.
Thanks.
These are all internal, not external drives.
Which enclosure are you using? Check with the manufacturer of the enclosure, very often (and in your case very likely) it'll be the USB-SATA controller in the enclosure that's responsible for the spindown.
so long,
Hias
Yes, they're all internal drives.
I use a simple metallic (almost hand made) box to contain HDD and this cable to connect SATA to USB https://shorturl.at/mfLVR.
I use it also to connect HDDs to Windows PC but none of them have spin down problems, I have problem with LibreElec only.
Thanks.
There is an hd-idle command, which is provided by the System Tools add-on:
It also generates a log file, so maybe helpful for further investigations.
Ok, I will give it a try.
Thanks a lot.
Unfortunately no useful BIOS setting for USB power or something of that kind.
BIOS is new (2023) but has few settings for USB.
Check the support pages of your drive manufacturer. eg with external WD drives you have to use WD Drive Utilities on Windows to configure the sleep timer.
I could check support pages yes but I tried with 3 different HDD: WD-RED 12TB, SEAGATE BARRACUDA 8TB, HITACHI DESKTAR 3 TB and all of them have the same "problem": when I pause a movie from LibreElec HDD spins down after few minutes.
Any other helpful hint?
Thanks.
BIOS settings ok, I will give it a try.
Thanks.
The first example should fail because the script is not providing the full path to hdparm and is addressing a partition not a disk.
The second example should fail because the script is providing an incorrect path to hdparm and addressing a partition not a disk.
Even if you corrected to /dev/sda as per my previous suggestion, you're still going to fail on the first points above.
The correct path is /usr/sbin/hdparm not /usr/bin/hdparm
I beg your pardon but it was my typo, the path I used is /usr/sbin/hdparm.
Anyway I think the problem is not there.
I wrote before:
I noted one thing, if I launch the command "hdparm -S 0 /dev/sda" from an SSH shell, HDD spins UP and "Setting StandBy to 0 (off)" appears on console but after few minutes HDD spins down again.
It seems hdparm can't manage HDD power management even when launched directly through shell
Hi and thanks for your reply.
So in general it's not a bug, but a feature.
I can in general agree with you but the fact that HDD spins down after 2-3 minutes as soon as I pause a movie it's not a feature but an annoyance, at least for me. It would be different if HDD would stop after say 10 or more minutes.
The above facts result in the conclusion that your HDD firmware does the energy management, not LE.
- The HDD firmware spins down whenever idle in mounted mode.
- The HDD firmware takes hdparm as an abstract task, and spins up without further command interpretation.
I would not be so sure of that. If it's the firmware that spins down the HDD, why that firmware does not spin HDD down when LibreElec is off?
Then I don't event think it's not a HDD type matter because I tried with 3 different HDD (and one of them is very very old): the behavouir is the same for all.
Anyway, if hdparm does not seem to be working, what else I can do to control my HDD power management with LibreElec?
Thanks a lot, Michele.
Not working, modified script in "hdparm -S 0 /dev/sda", rebooted and after few minutes HDD spins down.
I noted one thing, if I launch the command "hdparm -S 0 /dev/sda" from an SSH shell HDD spins UP and "Setting StanBy to 0 (off)" appears on console but after few minutes HDD spins down again.
I really don't undestand what's going on. This is the third HDD I try and with all of them I have the same result. This must something inside LibreElec or its operative system.
Any other idea?
I'll give it a try late in the evening.
The thing that looks stange to me is the fact that if I lunch the command "hdparm -S 0 /dev/sda2" from an SSH shell when the HDD is sleeping then it start to spin up immediately.
Thanks a lot for your advice.
Hi.
I'm using version 13 night builds on my GMKtec G3 Plus (version 12 doesn's work on my box).
I have an USB hard drive connected via USB and have no problem in general but when I pause a movie or anything I'm watching for just few minutes, HDD spins down.
I tried to use hdparm in autostart.sh with this command: "hdparm -S 0 /dev/sda2" and also "/usr/bin/hdparm -S /dev/sda2" but with no luck: if I pause my watching, HDD spins down, always.
If I open a shell (ssh) and run the command "hdparm -S 0 /dev/sda2" when HDD is down then it resumes so, I guess, the command is correct but when inserted in autostart.sh it doesn't work.
If I shutdown LibreElec keeping HDD on it never spins down so I guess it's LibreElec that somehow spins HDD down in some way.
What am I doing wrong? Is there anything else I can do to avoid the spinning down of my HDD after few minutes?
Thanks a lot,
Michele.
Hi Chewitt.
Today I encontered the same problem: wifi didn't connect and I had to restart system 2 times.
Here's the log, hoping you'll find sometighin useful:
Thanks,
Michele.
Here I am.
Today the box had a strange behavior, I turned it up and it took several minutes (say 4 at least) before connecting to wifi, I took the log.
Then I reboot it three times and it connected to wifi in few seconds, all the times.
Hope you cand find the reason of this stange behavior in the log:
Thanks,
Michele.
Thanks a lot.
I'll implement those commands ASAP then post in pastebin. In my system autostart.sh is in /storage/.config: is it the good place?
"lspci -nnk | paste"
Sorry for the mistyping...
No errors reported in the log so I'd assume rtw89 is working to the best of its abilities. The one thing to check is setting the Wireless regulatory domain in the LE settings so the radio properties are aligned to the domain set in your router. Sometimes (but not always) the router advertises it and the driver auto-adjusts to match, but I don't see that in the system log, so either the driver doesn't support that kernel capability yet or the router doesn't advertise.
The log has been taken when the wireless connection was successful. When connection is not up I can't "paste" the log. Is there any way to view (and then copy) the log when connection is not successful? Maybe it would be more useful to see the log when connection can't be established.
Sorry but what is the "Wireless regulatory domain" and where can I find it in LE settings?
Thanks a lot.
Sorry for the late.
Here's the link from the first command: https://paste.libreelec.tv/golden-kitten.log
The command "pspci -nnk | paste" generates a "-sh: pspci: not found" error.
I hope it can be useful.
Hi, I recently bought the GMKtec G3 Plus box with the new Intel N150. I had to install version 13 nigthly builds because version 12 stable and nightly builds didn't boot.
I'm very satisified with this box, it manages 4k high res video and audio with no problem. At home it's connected to my oled TV and soundbar through E-ARC.
The "problem" I'd like to bring to your attention is the fact that sometimes the box doesn't connect to saved wi-fi. Sometimes it simply doesn't show any active connections (in Libreelec plugin), other times it shows some networks but not the one I want it to connect to. I tried to disable an re-enable Wi-fi networks (in Libreelec plugin) but it does not help. The only way to make it connect to the saved network is to reboot the box one, twice and sometimes more.
I tried to make it operate in different wi-fi networks that uses different devices and tecnology (wi-fi 4, 5 and 6) but the problem persists.
The box uses the Realtek 8852BE wi-fi chip and as much as I know, Libreelec should have the correct driver to operate with it (please confirm).
I searched the forum and didn't find any relevant thread.
Could it be a driver problem?
Any help will be highly appreciated.
Thanks a lot.
Cheers,
Michele.
