Could this also be due to my old Panasonic plasma?
I don't think so. It's more likely your soundbar changes the HDMI mode somehow. To rule out this, try a config.txt containing your preferred HDMI mode. Example config.txt:
hdmi_force_hotplug=1
hdmi_ignore_edid=0xa5000080
hdmi_group=1
hdmi_mode=4If you upgrade to LE 10, those settings have to be transformed to a different syntax at cmdline.txt.
That was it, man. So try hdparm to spin-down (hopefully), and then use shutdown or reboot. Different sound?
Yes, a voltage issue is unlikely.
I remember some kind of a spin-down command on Linux, but I'm not sure whether it works with SATA drives. Does someone know that command?
To be honest: I have no clue what happens inside an HDD during reboot. Best solution is replacing by an SSD.
ok, i'm not sure if I'm able to follow, but let's give it a try. what's your theory and how to measure it?
Theory: HDD loses power supply on reboot for a very short time, which causes a HDD reboot and a strange noise.
Measurement to proof that theory: Find the power supply pins of the HDD by having a look at the data sheet. Remove some isolation of the connecting cable to get measure points at those power supply pins. Then connect a voltage measure instrument, and check the needle while rebooting. If the needle moves down, the theory has been proofed.
toml Do you have basic electronic skills? If yes, you could test my power-off theory by measuring. Debug logging is usually a good idea, but I don't think we get info about internal HDD state during reboot time.
chewitt Thanks. I'm still thinking the Seagate drive get's a short power-off, but now I have no clue how to fix that.
when I do this with HC4, there is this LE shutdown sequence, drive spins down, then suddenly spins up and then the power is cut or HC4 reboots and that's when that squeak sound appear.
The USB drive probably just get a short power-off, which creates the sound. Attach an external power supply. I don't think you can avoid that short power-off by software.
I don't think you'll get dev support for this, because it's a rare issue, and you didn't named your NAS. We are usually pretty precise on this forum.
Search for an option to program a short suspend time from another OS (look at the Seagate download page). A suspend mode can stop rotation (spin-down), and no proper heads parking will be necessary.
When I use static IP, I try change address many times. I even try’s address from another subnet. All those address does not match DHCP pool. I try use DHCP. Nothing works. Thanks to “twinpeaksr”, only “connman” helps me to resolve this issue.
Can you provide a link to a kodi.log please? I'm using 9.2.8 on RPi, and it works fine there. Our dev's have tested latest 10.0, and they had no issue. Have you done a fresh install of 10.0, as mentioned in the release notes?
Maybe a parse error. Try this keyboard.xml instead of your keymap.xml:
<keymap>
<global>
<keyboard>
<r>XBMC.ReloadSkin()</r>
<one>XBMC.CleanLibrary(video)</one>
<two>XBMC.UpdateLibrary(video)</two>
<three>RunScript(script.trakt,action=sync,silent=False)</three>
<five>XBMC.ReloadSkin()</five>
<nine>XBMC.CleanLibrary(music)</nine>
<f8>RestartApp</f8>
<s>SendClick(8)</s>
<key id="50">contextmenu</key>
</keyboard>
</global>
</keymap>People do not want wires running around their homes.
Depends on the home. I have wired connection to my RPi (12m cable), and I like it. Check that option.
RubberFistFight Now you can be sure that we'll solve the problem. 
no idea how to login via ssh?
This will become a long thread.
After switching on your LE box, login to your router menu (by another PC, not your LE box), and find the IP number of your LE box.
Open a terminal on your PC, and execute ssh root@<LE'S_IP_NUMBER>. Example: ssh [email protected]
After that, type the password, which is libreelec by default.
Then you're hopefully logged in, and you can run the pastekodi command.
PS: At the end, type exit to leave the SSH session.
Anewmission Play DSD from an USB stick, and provide a log (#25).
The problem has been analyzed, and it seems like it only appears when a static IP has been selected, which is already in use. So it's probably a network issue, not a bug.
When getting the auto-connect issue, login to your router, and have a look at the used IP's. If you did the LE setup for static IP usage, but the desired IP is already in use, auto-connect can't work by design.
jim_p Debugging WiFi issues is pain in the ass. Just give away one of your working adapters. It makes some people happy, and saves you a lot of time - sounds like a good deal to me. 
I don't know. It's the right time to provide a kodi.log:
