Used: unknown (minor revision code 0x011b)ĬHS current addressable sectors: 16514064 Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0 |_ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, $ sudo hdparm -I /dev/sda : Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 480M |_ Port 1: Dev 2, If 0, Class=Mass Storage, Driver=usb-storage, 5000M Hubīus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root $ lsusb -t Please not that I already use quirk trick.īus 002 Device 002: ID 125f:a88a A-DATA Technology Co., Ltd.īus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hubīus 001 Device 002: ID 2109:3431 VIA Labs, Inc. I thought naively that re-power of the USB port is equivalent to re-plugging. instead of buying new SATA to USB or even new SSD first try this trick.īecause I see the only one problem - you must do this re-insertion every power failure.Ģ) Had someone managed to solve the boot problem using this strange feature to re-power the USB ports during the power on process?įor some reason this option is introduced, so there are some efforts and probably some success behind. May be it will be useful for some other people. That is why I have two questions to the community -ġ) there are some reports - like this particular SSD or USB to SSD adapter work, another does not -īut am I the only one using this trick - to connect SSD after the pi is powered? Please also note - I can reconnect reconnect SSD after the boot start (when system is waiting for the root), or just connect the SSD after powering on the pi (in my case the boot partition is at sd card, thanks to this "combined" option), and the sstem will work for weeks without any problem. The boot problem persists even if I have nothing connected to USB3 and USB2 ports accept the SSD drive.Įven network is plugged out during this very basic boot procedure. Sorry if it was not clear from my original post. I had played with this parameter a lot - but no luck. My second idea was to cancel this interruption. ![]() My first idea was to make this time as long as possible. In documentation I found that, on power on, the USB ports power is interrupted for a short time (as I remember, the default value is 1 second). To make SSD visible I have to unplug it and pug it back. Today I "built" custom 5.2V 5A power supply. ![]() There are lot of discussions that the problem might be the limited current of the original raspberry's power supply,īefore, I used official PI4 power supply (5V 3A). It looks like the HUB boots faster than raspberry, so the SSD is ready when it is needed by pi.īut this solution is not elegant (and requires additional elements!) The second scenario is better as it is stable against the power failure/cycling. It means the system will not restart after e.g. The first scenario requires manual insertion of the SSD after the pi is powered on. The HUB must be powered before the raspberry pi. In configuration, root / is mapped to SSD. SSD becomes alive and system works fine.Ģ) Boot from sd card. In configuration, root / is mapped to SSD.Ĭonnect it back. ![]() In both cases the boot partition is on the sd card, but root partition is redirected to ssd.ġ) Boot from sd card. The LED at the SSD becomes active for a short time at the very beginning of the power on,īut after say 1 second the SSD becomes inactive.Īnd the problem is not solved by more powerful power supply.Īfter lot of efforts I can use this SSD for the root / (the boot is still from sd card) The problem is - the SSD does not start on power on. It is a SSD with built in USB 3.1 out.Īccording to the manual, it consumes 900 mA. There are lot of discussions about booting PI4 from SSD,
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |