D5-300C single-mode offline after heavy write

[roffdog]

Howdy,

I am using D5-300C on Linux in single-mode with the intention of using zfs and btrfs with software RAID as needed for individual pools.

I am able to read from my drives fine now that they're in the array. However when I write to it I get UAS errors:

Code: Select all

[Fri Apr  7 19:53:53 2023] sd 8:0:0:0: [sdb] tag#6 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN 
[Fri Apr  7 19:53:53 2023] sd 8:0:0:0: [sdb] tag#6 CDB: Read(16) 88 00 00 00 00 01 72 3d f4 d8 00 00 04 00 00 00
[Fri Apr  7 19:53:53 2023] scsi host10: uas_eh_device_reset_handler start
[Fri Apr  7 19:53:53 2023] scsi host8: uas_eh_device_reset_handler start
[Fri Apr  7 19:53:53 2023] hub 2-4:1.0: hub_ext_port_status failed (err = -71)
[Fri Apr  7 19:53:53 2023] usb 2-4-port3: cannot reset (err = -71)
[Fri Apr  7 19:53:53 2023] usb 2-4-port3: cannot reset (err = -71)
[Fri Apr  7 19:53:53 2023] usb 2-4-port3: cannot reset (err = -71)
[Fri Apr  7 19:53:53 2023] usb 2-4-port3: cannot reset (err = -71)
[Fri Apr  7 19:53:53 2023] usb 2-4-port3: cannot reset (err = -71)
[Fri Apr  7 19:53:53 2023] usb 2-4-port3: Cannot enable. Maybe the USB cable is bad?

I found this and tried disabling UAS on the devices. There was some improvement - I was able to write about 7GB to a pool until it conked out again:

Code: Select all

[Fri Apr  7 20:27:15 2023] usb 2-4.4: reset SuperSpeed USB device number 6 using xhci_hcd
[Fri Apr  7 20:27:15 2023] hub 2-4:1.0: hub_ext_port_status failed (err = -71)
[Fri Apr  7 20:27:15 2023] usb 2-4-port1: cannot reset (err = -71)
[Fri Apr  7 20:27:15 2023] usb 2-4-port1: cannot reset (err = -71)
[Fri Apr  7 20:27:15 2023] usb 2-4-port1: cannot reset (err = -71)
[Fri Apr  7 20:27:15 2023] usb 2-4-port1: cannot reset (err = -71)
[Fri Apr  7 20:27:15 2023] usb 2-4-port1: cannot reset (err = -71)
[Fri Apr  7 20:27:15 2023] usb 2-4-port1: Cannot enable. Maybe the USB cable is bad?
[Fri Apr  7 20:27:15 2023] usb 2-4-port1: cannot disable (err = -71)
[Fri Apr  7 20:27:15 2023] hub 2-4:1.0: hub_ext_port_status failed (err = -71)
[Fri Apr  7 20:27:15 2023] usb 2-4-port1: cannot reset (err = -71)
[Fri Apr  7 20:27:15 2023] usb 2-4-port1: cannot reset (err = -71)
[Fri Apr  7 20:27:15 2023] usb 2-4-port1: cannot reset (err = -71)
[Fri Apr  7 20:27:15 2023] usb 2-4-port1: cannot reset (err = -71)
[Fri Apr  7 20:27:15 2023] usb 2-4-port1: cannot reset (err = -71)
[Fri Apr  7 20:27:15 2023] usb 2-4-port1: Cannot enable. Maybe the USB cable is bad?

I did also try plugging it into a USB 2.0 port (obviously this wouldn't work but it was worth testing...). Two of the disks didn't show up, but I did my test and was able to copy a test file to one of the pools, albeit slowly.

Code: Select all

# time dd if=/dev/urandom of=/moviestv/bigfile bs=1M count=10000

10000+0 records in
10000+0 records out
10485760000 bytes (10 GB, 9.8 GiB) copied, 403.002 s, 26.0 MB/s

real    8m42.202s
user    0m0.015s
sys     1m14.738s

My kernel:

Code: Select all

# uname -a
Linux myhost 6.1.0-7-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.20-1 (2023-03-19) x86_64 GNU/Linux

Are there any known problems with the D5-300C on Linux, newer kernels etc.? Any ideas on what to try next?

[roffdog]

Strangely I tried plugging it into my front panel USB 3.0 port and it's now working reliably

Code: Select all

# time dd if=/dev/urandom of=/moviestv/bigfile bs=1M count=10000
10000+0 records in
10000+0 records out
10485760000 bytes (10 GB, 9.8 GiB) copied, 42.709 s, 246 MB/s

real    0m42.718s
user    0m0.006s
sys     0m23.269s

[roffdog]

Bugger, that was not it. Tried again with a proper data copy (what I was trying to do) and got the same errors as above.

With UAS:

Code: Select all

[Sat Apr  8 15:00:57 2023] sd 8:0:0:0: [sdb] tag#12 CDB: Read(16) 88 00 00 00 00 01 4a 7a ce e8 00 00 02 00 00 00
[Sat Apr  8 15:00:57 2023] sd 8:0:0:0: [sdb] tag#11 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN 
[Sat Apr  8 15:00:57 2023] sd 8:0:0:0: [sdb] tag#11 CDB: Read(16) 88 00 00 00 00 03 62 15 93 f8 00 00 04 00 00 00
[Sat Apr  8 15:00:57 2023] hub 2-2:1.0: hub_ext_port_status failed (err = -71)
[Sat Apr  8 15:00:57 2023] sd 8:0:0:0: [sdb] tag#8 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN 
[Sat Apr  8 15:00:57 2023] sd 8:0:0:0: [sdb] tag#8 CDB: Read(16) 88 00 00 00 00 03 62 15 97 f8 00 00 04 00 00 00
[Sat Apr  8 15:00:57 2023] sd 8:0:0:0: [sdb] tag#3 uas_eh_abort_handler 0 uas-tag 10 inflight: CMD IN 
[Sat Apr  8 15:00:57 2023] sd 8:0:0:0: [sdb] tag#3 CDB: Read(16) 88 00 00 00 00 00 44 8b 8b 30 00 00 01 00 00 00
[Sat Apr  8 15:00:57 2023] sd 8:0:0:0: [sdb] tag#0 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD IN 
[Sat Apr  8 15:00:57 2023] sd 8:0:0:0: [sdb] tag#0 CDB: Read(16) 88 00 00 00 00 01 4a 7a d1 e8 00 00 01 00 00 00
[Sat Apr  8 15:00:57 2023] usb 2-2-port3: cannot reset (err = -71)
<snip>
[Sat Apr  8 15:00:57 2023] usb 2-2-port3: Cannot enable. Maybe the USB cable is bad?
<snip>
[Sat Apr  8 15:00:57 2023] scsi host10: uas_eh_device_reset_handler FAILED err -19
[Sat Apr  8 15:00:57 2023] sd 10:0:0:0: Device offlined - not ready after error recovery

Without UAS:

Code: Select all

[Sat Apr  8 15:12:19 2023] hub 2-2:1.0: hub_ext_port_status failed (err = -71)
[Sat Apr  8 15:12:19 2023] usb 2-2-port1: cannot reset (err = -71)
<snip>
[Sat Apr  8 15:12:20 2023] usb 2-2-port1: Cannot enable. Maybe the USB cable is bad?
[Sat Apr  8 15:12:20 2023] usb 2-2-port1: cannot disable (err = -71)

[roffdog]

I wonder if this post is the same issue, after all I am trying to copy between disks on the DAS array.

[TMRyan]

The D5-300C supports RAID for HDD1/2, while HDD3/4/5 can only be used by a single disk.
Since you created the RAID through a third party, I cannot confirm whether it is the third-party compatible external hard drive box that created the RAID or other reasons.
It is recommended that you try to relieve RAID mode and try again.

[roffdog]

Hi Ryan,

I already had it switched to single mode when I first opened it. Basically I want to use it as a simple JBOD and nothing else. With RAID mode already disabled on the device, how should I proceed?

I did also notice the temps were quite hot on the drives when I pulled them out. I was only 25 degrees celsius today but can get over 35-40 in summer which concerns me if they were getting that hot in mild conditions.

[TMLyy]

{L_BUTTON_AT}roffdog

We recommend that you relieve the third-party RAID mode and use it normally.
The operating temperature of the hard disk is 35-40°C, which is very normal.
For the temperature range of the hard disk, you can look at the working parameters of the hard disk.

[e6SBylizVXn4]

This worked for me when seeing the same types of error messages: viewtopic.php?f=67&t=5830&sid=da6d3e2f8 ... 96082cb754

I think these devices need a good powered usb port, I solved my problems with a powered usb c hub in between my pc and the device

Worked for me, stable after two weeks with strenuous testing (full scrubs and large copies with large and small files)