-
Notifications
You must be signed in to change notification settings - Fork 205
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Usb 2.0 vs 3.0 #194
Comments
The bug report is missing full details of the USB device and the symptoms that you are reporting will be specific to that USB device. Please can you also try the latest bootloader beta release |
Yes, sorry!
|
Thanks, that's useful. A link to the retail (e.g. amazon) product is also useful because there are a lot of products which use the same USB SATA adaptor. The latest beta bootloader changes the USB port power initialization which I think should resolve that. It would also be useful to know the board revision (cat /proc/cpuinfo | grep -i revision) |
cat /proc/cpuinfo | grep -i revision
When using the last beta pieeprom-2020-07-31.bin, first reboot (not power on) works (hdd are seen on OMV), second reboot does not work (hdd are missing in OMV), and when rebooting for the third time, the pi gets stuck on "Reached target reboot". |
I've just noticed "Booting from SD card" so not a USB MSD boot thing. The Linux USB stack is separate and PCI is actually reset before Linux starts. However, you could try adding USB_MSD_PWR_OFF_TIME=5000 which will cause the bootloader to turn off the USB port power for long enough that it should look like a power off to the HDD. It might be similar to an issue seen with some wireless keyboards which don't like something about the hardware power reset sequencing. |
Added USB_MSD_PWR_OFF_TIME=5000. |
You could try zero but this is starting to look like a Linux bug unless this is a regression compared to the latest default bootloader (ie latest critical update). Do the drives appear or you hotplug the device after boot? |
No, I have to unplug the power to make them appear again. |
USB2.0 and USB3.0 are independent buses over the same wires, it's possible that it's talking to almost completely separate silicon on the SATA adapter. |
Based on the powering-diagram that @malinduta posted earlier, it makes sense why modifying USB_MSD_PWR_OFF_TIME makes no difference (the HDDs are externally powered, so powering off the USB ports at the Pi-side has no affect). ping @P33M in case he has any ideas about if/how this can be resolved from the Linux-side. |
The bootloader switches off the USB port power to avoid any glitches around reboot. However, from the diagram it looks as though the adapter always provides power. If hotplugging the USB cable from Linux without disconnecting the power cable doesn't work then there's nothing the bootloader can do about this. |
Based on similar issues in this repo (see e.g. #151 #180 #168 ), it sounds like some HDD->USB adaptors have "problems" (this isn't my area of expertise!) if the Pi is rebooted without the power also being removed from the adaptor - I believe that's the entire reason for the |
Yes the problem is that the separate power supply is not really managed by the usb device. That’s not something the usb host can influence. Closing but because if hot plugging the usb in Linux doesn’t work without manually toggling the power supply then there’s nothing we can do about this |
Describe the bug
Have 2xhdd conected to pi 4b.
When the hdds are connected to usb 2.0 everything is working as expected.
When connected to usb 3.0, things are different. On shutdown, the hdds remains ON. On reboot the hdds are not seen, missing from Openmediavault.
Booting from SD card.
To Reproduce
Swap usb 2.0-3.0 and reboot/shutdown.
Expected behaviour
Usb 3.0 as 2.0
Bootloader version and configuration
vcgencmd bootloader_config
vcgencmd bootloader_version
SD card boot (please complete the following information):
The text was updated successfully, but these errors were encountered: