I have another 4B system running from a 480GB SSD with a 2.4A PSU, and it's also on 24/7 as a small server. I even tested that 4B system with dual SSD, which worked fine for me as well (to run dual SSD they need to be power efficient models). The SSD is powered directly from the Pi4's USB 3.0 port (using the official Raspberry Pi Foundation USB-C power supply). I have an OG Pi 4B v1.1 running from a 256GB SATA-III SSD with an ASM1153E based USB 3.0 adapter cable that runs 24/7 and has been doing so since shortly after I got it back when the 4B first launched (initially with /boot on SD card and the the main OS on SSD, but since USB booting was in beta the OS has been running entirely from the SSD). I ran 3B models from SSD for years before the Pi4 came out (even on USB 2.0 an SSD is faster than a micro-SD card). I have been running Pi computers from inexpensive SATA based SSD models with USB adapter cables for years. Not only will you gain nothing in performance, you are likely to have power problems (as you have discovered). Pi computers don't support anything faster than USB 3.0, so using a power hungry NVMe based drive is pointless. Everything works except for the USB port - drives keep disappearing, does not matter which technologyĮverything works except for the USB port - drives keep disappearing, does not matter which technologyĪctually, it does matter. I did eliminate the possibility of OS issues by using Raspbian 32 bit and Ubuntu 64 bit both in the SD card and on a USB key. If you are running an old kernel or haven't updated your OS, this could be the problem. Are you running the most up to date version of Raspberry Pi OS? There was at one point an error in how Linux allocated DMA buffers for USB on the Pi 4B that caused random disconnects. On the other hand, there's also not much that can go wrong. With a single-board computer, not much can be fixed if things go wrong. The main thing I learned was that random crashes make any computer no matter how expensive seem like junk. I finally tracked the problem to the networking cards in those machines-same manufacturer, specifications and model number as the others but a newer revision. One year I struggled with four dual-socket servers that were all randomly crashing. If that does not work I will give up and go back to a dependable laptop repurposed as a server, at least it works. I am going to make a last ditch effort of returning the board to Canakit with the assumption that it is actually a hardware failure. usb 1-1.2-port3: unable to enumerate USB deviceĪfter amassing a bunch of usb hubs and SSD drives in this quest, my conclusion is that the Raspberry Pi4 is firmly in the category of a toy, undeserving of being elevated to the status of a home nextcloud server since it cannot handle a USB drive. usb 1-1.2.3: new high-speed USB device number 112 using xhci_hcd usb 1-1.2.3: device descriptor read/64, error -71 usb 1-1.2.3: new high-speed USB device number 111 using xhci_hcd Speed Attribute ID: 0 10Gb/s Symmetric TX SuperSpeedPlusĬan't get debug descriptor: Resource temporarily unavailableĬode: Select all usb 1-1.2-port3: attempt power cycle Speed Attribute ID: 0 10Gb/s Symmetric RX SuperSpeedPlus Lowest fully-functional device speed is Full Speed (12Mbps) IdProduct 0x9210 RTL9210 M.2 NVME AdapterīESL Link Power Management (LPM) Supportedĭevice can operate at Full Speed (12Mbps)ĭevice can operate at High Speed (480Mbps) IdVendor 0x0bda Realtek Semiconductor Corp. I tried combinations found via google search - autosuspend, use_both_schemes to no availĬode: Select all Bus 001 Device 097: ID 0bda:9210 Realtek Semiconductor Corp. usb 1-1.4: device not accepting address 3, error -71 usb 1-1.4: Device not responding to setup address. usb 1-1.4: reset high-speed USB device number 3 using xhci_hcd usb-storage 1-1.4:1.0: USB Mass Storage device detected usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-1.4: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=20.01 Usb 1-1.4: new high-speed USB device number 3 using xhci_hcd
0 Comments
Leave a Reply. |