I am using Kodi 21.3 + OSMC 2025.11-1 on a Raspberry pi 4, which I recently upgraded from a pi 3. The problem I am encountering is that the USB drive that contains my media files sometimes is not mounted. It happens about 2 times out of 3, and in that case I have to reboot. After a couple of reboots, everything works fine.
Here is the log of one of the times the USB disk was not available: paste.kodi.tv/noxumokatu.kodi
I read about power source issues, but I guess the symptom would be more akin to intermittent unmounting, whether in my case it either works on boot or it doesn’t.
Is the log I posted not complete? I could not find a specific OSMC log, only the Kodi one.
The USB drive is USB powered, no independent power supply.
Full disclosure, I was sent here from the KODI forum; someone over there suggested mounting the drive using fstab. Six or seven reboots later…the drive seems to be mounted correctly!
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
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.
That doesn’t look healthy. I did not find any under-voltage or relevant power/current messages … but this still can be a big issue with your configuration:
You have connected a Logitech Z205 speaker system to a USB port of the Pi. I only found a few specification information about this device but some states it has up to 6 Watt RMS.
The Raspberry Pi 4 model B can offer in sum only 1.2 A on the USB ports and it seems obvious to me that powering this combination of speaker system and HDD or SSD is problematic, or at least running on the edge, on a Raspberry Pi.
If you disconnect the Logitech speaker, the mass storage device always is recognized? Try 10 power-on scenes without the Logitech, so you know that this is the right path to follow.
But…no. I unplugged the speaker, removed the fstab mounting, rebooted just once, and the USB disk was not detected. Then I plugged the speaker back, uncommented the fstab line, rebooted 4 times and the USB drive is always there.
So I guess problem solved for me, but I still do not know the deeper meaning of it not always being detected without fstab. I don’t know if this has a wider interest for the OSMC community…
Mmhh, looking at your fstab entry (thanks for pointing to it) this doesn’t seem to be unique: You’re using the UUID of the whole disk but it contains more than 1 partition.
In the fstab file, you should use the key PARTUUID instead of UUID key to uniquely identify the correct partition. I also wouldn’t recommend using the /media folder for custom mounts instead of /mnt, as this interferes with the udisks-glue process, which automatically mounts mass storage devices under /media. However, changing the directory name in fstab would automatically cause all paths in the media database to point to the void unless path substitution is used (thx @darwindesign for this nice article).
The cleanest method, however, would be to completely rebuild the media database with the new source (/mnt mount point).
I’m running the current release OSMC 2025.5 on a raspberry pi4. It has connected some devices by USB, especially a Samsung T5 SSD. Pi’s power supply should be good enough:-) During boot I encounter exactly the same error messages:
systemd-udevd[277]: sda: Process ‘udisks-part-id /dev/sda’ terminated by signal BUS.
systemd-udevd[277]: sda: Failed to wait for spawned command ‘udisks-part-id /dev/sda’: Input/output error
systemd-udevd[277]: sda: /usr/lib/udev/rules.d/80-udisks.rules:84 Failed to execute ‘udisks-part-id /dev/sda’, ignoring: Input/output error
systemd-udevd[267]: event0: Process ‘/usr/bin/evrepeat -d 750 -p 80 /dev/input/event0’ failed with exit code 1.
systemd-udevd[270]: event1: Process ‘/usr/bin/evrepeat -d 750 -p 80 /dev/input/event1’ failed with exit code 1.
…
systemd-udevd[296]: event2: Process ‘/usr/bin/evrepeat -d 750 -p 80 /dev/input/event2’ failed with exit code 1.
systemd-udevd[271]: sda1: Process ‘udisks-part-id /dev/sda1’ terminated by signal BUS.
systemd-udevd[271]: sda1: Failed to wait for spawned command ‘udisks-part-id /dev/sda1’: Input/output error
systemd-udevd[271]: sda1: /usr/lib/udev/rules.d/80-udisks.rules:84 Failed to execute ‘udisks-part-id /dev/sda1’, ignoring: Input/output error
systemd-udevd[271]: sda1: Process ‘udisks-part-id /dev/sda1’ terminated by signal BUS.
systemd-udevd[271]: sda1: Failed to wait for spawned command ‘udisks-part-id /dev/sda1’: Input/output error
systemd-udevd[271]: sda1: /usr/lib/udev/rules.d/80-udisks.rules:84 Failed to execute ‘udisks-part-id /dev/sda1’, ignoring: Input/output error
But the SSD is correctly mounted by its UUID-entry within /etc/fstab - i.e. no problem.
I assume that the tool /usr/lib/udev/udisks-part-id might cause the problem. Calling it standalone does create the bus exception
using device_file=/dev/sda syspath=/sys/devices/platform/scb/fd500000.pcie/pci00
00:00/0000:00:00.0/0000:01:00.0/usb2/2-2/2-2:1.0/host0/target0:0:0/0:0:0:0/block
/sda, offset=0 ao=0 and number=0 for /dev/sda
Entering MS-DOS parser (offset=0, size=1000204886016)
MSDOS_MAGIC found
Bus-Zugriffsfehler
The SSD uses one ext4 partition covering the whole SSD.
W.r.t. UUID vs. PARTUUID: That shouldn’t matter at all. E.g. my freshly installed tumbleweed linux does all its automatic generated fstab entries using UUIDs.
That is true, but the command udisks-part-id fails reproducible, even when called manually during runtime of osmc. Thus I’m quite sure that that tool has a bug. BTW, meanwhile it has been replaced by udisks2, thus I can’t test it on my other linux systems because it’s no longer available at all.
OT: Regarding USB power support, I have just recently tried to use a cheap powered USB3 hub (brand Acer) for my SAT receiver with USB2 ports. Sadly it does NOT provide (enough) power to the connected SSD - checked with USB cable with a led display showing only 1W power resp. less. Reading behind the lines of its spec I do assume that the external power supply ONLY powers the hub itself, but NOT the connected devices.
Addendum: I’ve just ordered an USB2 power blocker & USB power meter. Using the power blocker I can avoid to power USB devices by the host. Thus I could prove that the external power supply of my USB3 hub does indeed power the connected SSD (contrary to my statement above). And the power meter reports good values for voltage (slightly above 5V), current (below 0.5A), and power.
Difficult to answer - yes, it did mount, but with exactly the same error message as without USB hub. Please keep in mind that my experience is with a SAT receiver, NOT with OSMC. Sadly it’s too much effort for me to do similar tests with OSMC. I do not expect more information - my USB meter does NOT provide USB3.
Regarding my Samsung T5 1TB drive connected to my raspberry pi 4. Here I’m confident wrt power demands. It should use at most 0.8A from spec.
