3.5" WD HDD isn't starting on reboot

I am using a 12V 5A DC power source, and using splitters + a step down converter to power the potato (ubuntu 22, flashed just a few days ago) and a single 4TB SATA hdd. Whenever I reboot, the light on the HDD adapter is showing that there’s power, but I don’t hear the disk spinning (and lsblk doesn’t show the HDD). If I unplug and replug the USB connection, it shows up.

Can you copy and paste your dmesg log into a pastebin?

possibly this line?:
[ 9.858651] usb 1-1.3: USB disconnect, device number 3

Ah, the known issue (mentioned at the end of linked message) with the on-board hub bites another customer.

https://hub.libre.computer/t/how-to-build-an-image-for-any-distribution-for-libre-computer-boards/3804/3?u=mmaney

We plan to fix this by the time we roll out Linux 6.6 soon.

3 Likes

Any update on this? This is recurring issue for me

If you are using Le Potato, use the top port closest to the ethernet. It is not attached to a hub so it does not suffer the reset issue. If it does, it’s a power issue due to your device.

using the top left USB port – also the adapter is powered independently by a 12V 5A adapter – more than enough for one hdd

Please provide your dmesg log or a photo of the screen when the issue occurs.

There are some usb-sata bridges that have broken support for UAS (but they claim to support it, so Linux enables it). The fix is to add a disabling option to the kernel’s boot command line:

usb-storage.quirks=152d:0578:u

The USB ID codes on the right might need adjustment - that was for a common JMicron chip that’s in an enclosure I have. You can find the ID in the output of lsusb (of course the adapter must be attached).

On review, I do see the known issue when onboard-usb-hub (module) is loaded, but that just disconnects the wifi for a moment. What I don’t see any sign of in the dmesg output you pasted was the usb:sata bridge - it’s like it isn’t there during that time. What might be very interesting is a dmesg after the unplug/replug. (just the tail of it with that post-boot activity, mostly). Might be a clue there.