Quantcast
Channel: Raspberry Pi Forums
Viewing all articles
Browse latest Browse all 8051

Troubleshooting • Re: Rasberry pi4 with nvme enclosuer boot problems

$
0
0
Were you trying to use markdown to format your post? The forum doesn't support that. Use bbcode and/or the tag insert menu at the top of the post edit window.

Thank you, it's crystal clear right now. Would you be so kind and clarify the nvme in an enclosure problem. I read few of your post regarding nvme and rasberrypi.

1/ i am aware the limitation of 1.2 a /5v which is 6W power for ALL port combined together

That 1.2A limit requires a good quality, well regulated 3A PSU into your 4B. If you have less, you'll get less.
2/ nvme enclosure i don't know the power consumption but it's ugreene (RTL910B) based enclosure i think it's not power hungry.

```
=== START OF INFORMATION SECTION ===
Model Number: INTEL SSDPEKNW512G8L
Serial Number: BTNH93310F9Y512A
Firmware Version: L02C
PCI Vendor/Subsystem ID: 0x8086
IEEE OUI Identifier: 0x5cd2e4
Controller ID: 1
NVMe Version: 1.3
Number of Namespaces: 1
Namespace 1 Size/Capacity: 512 110 190 592 [512 GB]
Namespace 1 Formatted LBA Size: 512
Namespace 1 IEEE EUI-64: 5cd2e4 3891c09b51
Local Time is: Sat Aug 30 17:40:24 2025 CEST
Firmware Updates (0x14): 2 Slots, no Reset required
Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x0f): S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size: 32 Pages
Warning Comp. Temp. Threshold: 77 Celsius
Critical Comp. Temp. Threshold: 80 Celsius

Supported Power States
St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat
0 + 3.50W - - 0 0 0 0 0 0
```
My disk shows 3.5W max power consumption (hope it's calculated for 5v)

Doesn't matter what voltage it was calculated at. For DC Watts = Amps x Volts. So 3.5W at 5V is 0.7A or 700mA
3. I have good quality USB-C cables
4. The exposure and nvme disk connected to windows usb 3.0 port give me over 800Mb/s read speed.

Windows has different drivers to Linux. Some UAS chipsets will work just fine on Windows but fail or be buggy on Linux. I'm not aware of a definitive list of them.
5. i upgrade firmawre for the enclosure to 1.34.xxxx the newest i could find for RTL, used config provided for this enclosure:

Can't comment on that.
to sum it up i don't think it's a power lack problem the enclosure is detected as USB 2.0 not 3.0

I wouldn't entirely rule it out. Lower speed can mean less power used.
```
2.885110] hub 1-1:1.0: USB hub found
[ 3.179883] usb 1-1.1: new high-speed USB device number 3 using xhci_hcd
[ 3.282772] usb 1-1.1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=22.1d
[ 3.291888] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.299940] usb 1-1.1: Product: Ugreen Storage Device
[ 3.305732] usb 1-1.1: Manufacturer: Ugreen
[ 3.310643] usb 1-1.1: SerialNumber: 0129380003DD
[ 3.349865] usb-storage 1-1.1:1.0: USB Mass Storage device detected
[ 3.357125] usb-storage 1-1.1:1.0: Quirks match for vid 0bda pid 9210: 800000
```
using usb-storage not usg i tried to play with osme quirks for the devies but i gave up. Not sure what is causing the problem btw. i own also a USB 3.1 external powered HUB and it's also detected as USB 2.0 HUB.

Sorry, I have no idea what's going on there.
i addes also more debug options to usb
pi@raspberrypi:~ $ cat /boot/cmdline.txt
console=serial0,115200 console=tty1 root=PARTUUID=96fdc4f9-e9a4-488a-a229-cd34535164f2 rootfstype=ext4 rootwait rootdelay=10 xhci_pci.debug=5 usb-storage.debug=1 usb-storage.quirks=0bda:9210:u

but nothing important showed up in the logs - thought there will be sth about negotiating the superspeed connection and faling back to usb2.0 but there is nothing about it.

```
0.840496] usbcore: registered new interface driver lan78xx
[ 0.840545] usbcore: registered new interface driver smsc95xx
[ 0.841824] xhci_hcd 0000:01:00.0: enabling device (0000 -> 0002)
[ 0.841935] xhci_hcd 0000:01:00.0: xHCI Host Controller
[ 0.841966] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
[ 0.843064] xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0300240000000890
[ 0.844370] xhci_hcd 0000:01:00.0: xHCI Host Controller
[ 0.845071] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[ 0.845777] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
2.636495] mmc0: SDHCI controller on fe340000.mmc [fe340000.mmc] using ADMA
[ 2.719884] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[ 2.862505] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21
[ 2.871435] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 2.879324] usb 1-1: Product: USB2.0 Hub
[ 2.885110] hub 1-1:1.0: USB hub found
[ 2.889813] hub 1-1:1.0: 4 ports detected
[ 3.179883] usb 1-1.1: new high-speed USB device number 3 using xhci_hcd
[ 3.282772] usb 1-1.1: New USB device found, idVendor=0bda, idProduct=9210, bcdDevice=22.1d
[ 3.291888] usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 3.299940] usb 1-1.1: Product: Ugreen Storage Device
[ 3.305732] usb 1-1.1: Manufacturer: Ugreen
[ 3.310643] usb 1-1.1: SerialNumber: 0129380003DD
[ 3.349865] usb-storage 1-1.1:1.0: USB Mass Storage device detected
[ 3.357125] usb-storage 1-1.1:1.0: Quirks match for vid 0bda pid 9210: 800000
```

Sorry, but I'm not sure what else to suggest. Are any USB3 devices correctly detected in a USB 3 (blue) host port on the 4B?

Statistics: Posted by thagrol — Sat Aug 30, 2025 5:42 pm



Viewing all articles
Browse latest Browse all 8051

Trending Articles