So, long story short, I have a ROCK 5B with a 4TB NVMe SSD from Crucial and currently a 1TB SSD from Crucial as well attached via USB. When I attach the SSD using a USB3.0 Cable the drive tends to reset rather frequently(every couple hours) and sometimes fails to the point of the whole drive being removed from the kernels space. Its not like this drive is pulling major load, it should at no point have to do any continuous reads(full read load for longer than 1 minute) but is rather used as a media storage for a jellyfin server. I noticed that when I attach the drive to the system using a usb 2.0 cable it works flawlessly(no errors or resets for over a week).
Now, I have a second drive, thats an intenso SSD with 2TB that I would like to add to the system. Same game here, the drive works for a short time, eventually starts resetting, and will then at some point just drop out until physically disconnected and reconnected. However the Case for this drive uses USBA-A cables, and I just dont happen to have a non-USB3 cable lying around. I’m fairly certain the only reason that the first drive works with a 2.0 cable is power, as in requests from the drive are delivered at full speed and that peaks power for a short time, thus causing the device to reset, so limiting the speed of the drive down to USB-2.0 might be a workable solution.
I have also tried attaching both drives to the USB2 Ports on the rock5, but regardless of the cable they both start resetting during use. I suppose the usb2 port by design only delivers the 500mA its supposed to whereas the 3.0 ports have a higher limit regardless of whether they are being used in 2.0 or 3.0 mode.
Is there any way to force devices attached to usb3 to be used in usb2 mode?