Hi,
I have an external 3tb HDD powered by a psu and connected by a hub to the 4k. Recently, it has started disappearing from the system. The only way to get it to reappear is to pull the power on it. I have checked it with fsck and it is clean and there is no click of death. Any idea what the issue may be and how it could be fixed?
Thanks and happy new year!
To get a better understanding of the problem you are experiencing we need more information from you. The best way to get this information is for you to upload logs that demonstrate your problem. You can learn more about how to submit a useful support request here.
Depending on the used skin you have to set the settings-level to standard or higher, in summary:
enable debug logging at settings->system->logging
reboot the OSMC device twice(!)
reproduce the issue (wait till the hdd disappears)
upload the log set (all configs and logs!) either using the Log Uploader method within the My OSMC menu in the GUI or the ssh method invoking command grab-logs -A
publish the provided URL from the log set upload, here
Thanks for your understanding. We hope that we can help you get up and running again shortly.
OSMC skin screenshot:
Trying to enable logging without overlay using:
<advancedsettings> <loglevel>1</loglevel> </advancedsettings>
but the overlay still persists. How can this be done please?
Did you stopped kodi before making your change?
sudo systemctl stop mediacenter
Rebooted a few times in between. WOuld that not suffice?
It’s not about reboot it’s about making changes to the config file while the mediacenter is not running.
Cheers. Did as you said but still shows overlay 
Provide URL from paste-log .kodi/userdata/advancedsettings.xml
Sorry, you mean you want to see my advancedsettings.xml?
Yes, you can also upload all logs with grab-logs -A
Here we go. Probably a bit random as multiple reboots and debug logging on/off 
https://paste.osmc.tv/ixafedemab
Ok first for your topic of loglevel.
You are missing
<advancedsettings>
and
</advancedsettings>
tags in your .kodi/userdata/advancedsettings.xml
Ahh,got it. The rest of the stuff is library related so is just backeted in but this needs ?
Good to know after using it wrongly all these years! 
This correct then? <advancedsettings> <videolibrary> <allitemsonbottom>false</allitemsonb - Pastebin.com
Nope, closing one should be </advancedsettings>
So, correct your advancedsettings.xml, take another log set (activate logging, 2 x reboot, wait for the hdd to disappear, upload logset and provide the link, here).
btw: Which of the hdds is the one you have issues with?
Jan 03 12:09:47 HTPC kernel: usb 1-2.1: Product: Expansion Desk
Jan 03 12:09:47 HTPC kernel: usb 1-2.1: Manufacturer: Seagate
Jan 03 12:09:47 HTPC kernel: usb 1-2.1: SerialNumber: NA4KQLNL
...
Jan 03 12:09:47 HTPC kernel: usb 1-2.2: Product: Expansion Desk
Jan 03 12:09:47 HTPC kernel: usb 1-2.2: Manufacturer: Seagate
Jan 03 12:09:47 HTPC kernel: usb 1-2.2: SerialNumber: NA4K6BQY
...
Jan 03 12:09:47 HTPC kernel: usb 1-2.3: Product: Iomega
Jan 03 12:09:47 HTPC kernel: usb 1-2.3: Manufacturer: Iomega
Jan 03 12:09:47 HTPC kernel: usb 1-2.3: SerialNumber: FF2000DF000000000000006FD1FFFC
...
Jan 03 12:09:47 HTPC kernel: usb 1-2.4.1: Product: Elements 25A3
Jan 03 12:09:47 HTPC kernel: usb 1-2.4.1: Manufacturer: Western Digital
Jan 03 12:09:47 HTPC kernel: usb 1-2.4.1: SerialNumber: 57583331443439483550544A
Great. That’s got it. Thanks for your help. Will post back when it occurs but its
Jan 03 12:09:47 HTPC kernel: usb 1-2.1: Product: Expansion Desk
Jan 03 12:09:47 HTPC kernel: usb 1-2.1: Manufacturer: Seagate
Jan 03 12:09:47 HTPC kernel: usb 1-2.1: SerialNumber: NA4KQLNL
No full URL given could indicate the logs are too big for upload.
Let’s take a look at the journal first grab-logs -JKD