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
RPI5: usb x-x: cmd cmplt err -71 Error with different USB Disks #6055
Comments
Can't 'help' with your |
I have similar problems since switching from the Raspberry Pi 4 to the Raspberry Pi 5. I use two stacked 4-Port USB 3.1 Hubs with PPPS (Per-Port Power Switching) functionality. Sometimes errors occurs when I want to mount the partition after turning the USB port on:
This probem already occured on my Raspberry Pi 4. I thought, maybe it happens if the drive isn't ready when the mount happens. A second mount was successful. Still so is now. Raspberry Pi 4:
Raspberry Pi 5:
Like mentioned, a second mount is still successful, so that's not the big problem for me. I also get a lot of
|
I'm getting the same issue here
Orico M.2 nvme SSD - usb 3 adapter Rpi5 8gb |
Describe the bug
After as short time (20-60 minutes) USB-disks (a Seagate HDD and a JMicron SSD) run into errors and disconnect.
First entry in journalctl is:
Mar 20 15:11:18 server kernel: usb 4-1: cmd cmplt err -71
more detail later in the Log-section
Steps to reproduce the behaviour
I don't know if I/O is relevant. So I just ran the following
fio
command in a loop:fio --name=random-write --ioengine=posixaio --rw=randwrite --bs=4k --size=1g --numjobs=10 --runtime=60 --time_based --end_fsync=1
After, at most 60 minutes, the error occurs.
Device (s)
Raspberry Pi 5
System
Logs
(only information for Seagate HDD)
Additional context
I'm using the official Pi5 27W PSU (Barcode: 5 056561 803416)
It seems that adding
usb-storage.quirks=152d:0579:u
to/boot/firmware/cmdline.txt
prevent this error from occuring but disk performance decreases significantly!From [w=33.0k IOPS] to [w=6912 IOPS]
if this realy prevents the issue from occuring I can report after some hours/days.
The text was updated successfully, but these errors were encountered: