June update: USB HDD non recognized at boot time

Hi,
after updating OSMC to 2020.06-1 version, my USB HDD is not recognized anymore at boot time; if I disconnect the cable with OSMC running, then it is recognized and works as expected. I’ve never had any issue with my HDD at boot time before June update, so I suspect that something has changed regarding USB timeout.

Any config to check to investigate the problem?

My setup:
Raspberry pi 3 B+
Western Digital Elements 2 TB USB3 hard disk drive directly connected to Rpi
Genuine Rpi Power supply 2.5 A
Logitech KT400 RF keyboard

Here is my logs:

Bye, Kranz.

Hi,

Does the Hard disk drive how its own PSU? If not does connecting to powered USB hub make any difference?

Thanks Tom.

Hi Tom,
thank you for your answer.

My HDD is a 2.5" powered via Rpi USB port and I don’t have a powered USB hub to check if it solves the problem. I have to say that this configuration worked wery well before the June update: every time I made a reboot (or cold boot) the HDD was correctly recognized and available to OSMC and Kodi, so I don’t think it is a power issue.
I suspect the spin time is a bit too long - or OSMC is too fast at boot :slight_smile: so the hard disk doesn’t have the time to be recognized…the strange thing is that I’m experiencing this issue only with June update.

Bye, Kranz

Quite possibly, since you say that it works if you plug it in later.

The log shows that udisks-glue didn’t know what to do with it, which could be due to a slow spin-up time (possibly power-related).

giu 21 19:16:28 osmc udisks-glue[485]: Device /dev/sda1 did not match any rules.

What file system does it contain?

I see that you have an additional package installed called usbmount. This seems to be no longer supported in Debian Stretch and was also failing, this time with a different error:

giu 21 19:16:45 osmc usbmount[746]: no mountpoint found for dev/sda1

This was last available in Debian Jessis, so you should considr removing it.

1 Like

Quite possibly, since you say that it works if you plug it in later.
The log shows that udisks-glue didn’t know what to do with it, which could be due to a slow spin-up time (possibly power-related).
giu 21 19:16:28 osmc udisks-glue[485]: Device /dev/sda1 did not match any rules.
What file system does it contain?

NTFS.

I see that you have an additional package installed called usbmount. This seems to be no longer supported in Debian Stretch and was also failing, this time with a different error:
giu 21 19:16:45 osmc usbmount[746]: no mountpoint found for dev/sda1
This was last available in Debian Jessis, so you should considr removing it.

Yes, usbmount was installed by the Retropie script. It throws out an error, but it’s harmless. BTW I will consider to uninstall it if doesn’t break any Retropie dependency.