I have a Raspberry PI 4 running with the SATA HAT with a 4 disk (a 2TB) setup.
The Raid is working good, but after a while the kernel throws errors …:
"kernel: md: super_written gets error=-5"
…which leads to a corrupt Raid and a complete rebuild.
PowerSupply is the one which came with the SATA HAT (I guess 60W)
Anyone having similar issues?
Hello, can you post the dmesg
will post it as soon as it fails the next time … usually it takes about 4 - 5 days with heavily loads until the error appears.
here we go:
sudo mdadm --detail /dev/md0
/dev/md0:
Version : 1.2
Raid Level : raid0
Total Devices : 4
Persistence : Superblock is persistent
State : inactive
Working Devices : 4
Name : raspberrypi:0 (local to host raspberrypi)
UUID : 77af0203:0a524086:e6b38f9a:b9ec28f4
Events : 5975
Number Major Minor RaidDevice
- 8 49 - /dev/sdd1
- 8 33 - /dev/sdc1
- 8 17 - /dev/sdb1
- 8 1 - /dev/sda1
dmesg (relevant parts) / if you need the complete dmesg, use the link to pastebin
It suddenly starts to disconnect USB device number 5
[14819.685837] usb 1-1.4.3.3: USB disconnect, device number 5
[14819.998852] usb 1-1.4.3.3: new high-speed USB device number 6 using xhci_hcd
[14820.129551] usb 1-1.4.3.3: New USB device found, idVendor=0451, idProduct=bef3, bcdDevice= 1.00
[14820.129561] usb 1-1.4.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[14820.129569] usb 1-1.4.3.3: Product: XDS110 (03.00.00.15) Embed with CMSIS-DAP
[14820.129576] usb 1-1.4.3.3: Manufacturer: Texas Instruments
[14820.129583] usb 1-1.4.3.3: SerialNumber: L1100FQJ
[14820.136114] cdc_acm 1-1.4.3.3:1.0: ttyACM0: USB ACM device
[14820.237415] cdc_acm 1-1.4.3.3:1.3: ttyACM1: USB ACM device
[14820.239168] hid-generic 0003:0451:BEF3.0002: hiddev96,hidraw0: USB HID v1.11 Device [Texas Instruments XDS110 (03.00.00.15) Embed with CMSIS-DAP] on usb-0000:01:00.0-1.4.3.3/input5
then device number 4 & 6
[35208.921340] usb 1-1.4.3: USB disconnect, device number 4
[35208.921363] usb 1-1.4.3.3: USB disconnect, device number 6
[35209.245316] usb 1-1.4.3: new high-speed USB device number 7 using xhci_hcd
[35209.386604] usb 1-1.4.3: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=77.60
[35209.386615] usb 1-1.4.3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[35209.386623] usb 1-1.4.3: Product: USB2.0 Hub
[35209.387882] hub 1-1.4.3:1.0: USB hub found
[35209.388153] hub 1-1.4.3:1.0: 4 ports detected
[35209.725330] usb 1-1.4.3.3: new high-speed USB device number 8 using xhci_hcd
[35209.875983] usb 1-1.4.3.3: New USB device found, idVendor=0451, idProduct=bef3, bcdDevice= 1.00
[35209.875993] usb 1-1.4.3.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[35209.876001] usb 1-1.4.3.3: Product: XDS110 (03.00.00.15) Embed with CMSIS-DAP
[35209.876008] usb 1-1.4.3.3: Manufacturer: Texas Instruments
[35209.876015] usb 1-1.4.3.3: SerialNumber: L1100FQJ
[35209.882782] cdc_acm 1-1.4.3.3:1.0: ttyACM0: USB ACM device
[35209.984094] cdc_acm 1-1.4.3.3:1.3: ttyACM1: USB ACM device
[35209.985942] hid-generic 0003:0451:BEF3.0003: hiddev96,hidraw0: USB HID v1.11 Device [Texas Instruments XDS110 (03.00.00.15) Embed with CMSIS-DAP] on usb-0000:01:00.0-1.4.3.3/input5
complete on pastebin >> Click me <<
Hi @chdrsto -
I think I have the same issue as you. Check out my syslog below.
Did you find a solution? What’s your setup? Did you disable UAS or do the firmware upgrade?
Jan 21 11:31:31 nastie kernel: [ 539.360782] sda: sda1
Jan 21 11:31:39 nastie kernel: [ 547.260707] sda: sda1
Jan 21 11:31:59 nastie kernel: [ 567.642104] sda: sda1
Jan 21 11:32:02 nastie kernel: [ 570.508842] sda: sda1
Jan 21 11:32:16 nastie kernel: [ 584.259362] sda:
Jan 21 11:32:16 nastie kernel: [ 584.267564] sda:
Jan 21 11:32:19 nastie kernel: [ 586.956767] sda:
Jan 21 11:33:34 nastie kernel: [ 662.251004] sda: sda1
Jan 21 11:33:37 nastie kernel: [ 665.057616] sda: sda1
Jan 21 11:34:09 nastie kernel: [ 697.210012] sda: sda1
Jan 21 11:34:09 nastie kernel: [ 697.217648] sda: sda1
Jan 21 11:34:11 nastie kernel: [ 698.882504] sda: sda1
Jan 21 11:34:14 nastie kernel: [ 702.195019] sda: sda1
Jan 21 11:34:32 nastie kernel: [ 720.134479] sdb: sdb1
Jan 21 11:34:34 nastie kernel: [ 722.517976] sdb: sdb1
Jan 21 11:34:41 nastie kernel: [ 728.927955] sdb: sdb1
Jan 21 11:35:18 nastie kernel: [ 766.360959] sdc: sdc1
Jan 21 11:35:33 nastie kernel: [ 781.518405] sdd: sdd1
Jan 21 11:35:35 nastie kernel: [ 783.299513] sda: sda1
Jan 21 11:35:40 nastie kernel: [ 787.808349] sda: sda1
Jan 21 11:35:42 nastie kernel: [ 790.342196] sdb: sdb1
Jan 21 11:35:44 nastie kernel: [ 792.482067] sdb: sdb1
Jan 21 11:35:45 nastie kernel: [ 793.475912] sdc: sdc1
Jan 21 11:35:48 nastie kernel: [ 796.115809] sdc: sdc1
Jan 21 11:35:49 nastie kernel: [ 797.612291] sdd: sdd1
Jan 21 11:36:14 nastie kernel: [ 821.992856] sdd: sdd1
Jan 21 11:37:21 nastie kernel: [ 889.124444] raid6: neonx8 gen() 4349 MB/s
Jan 21 11:37:21 nastie kernel: [ 889.192440] raid6: neonx8 xor() 3845 MB/s
Jan 21 11:37:21 nastie kernel: [ 889.260429] raid6: neonx4 gen() 5267 MB/s
Jan 21 11:37:21 nastie kernel: [ 889.328443] raid6: neonx4 xor() 4030 MB/s
Jan 21 11:37:21 nastie kernel: [ 889.396443] raid6: neonx2 gen() 4598 MB/s
Jan 21 11:37:21 nastie kernel: [ 889.464421] raid6: neonx2 xor() 3617 MB/s
Jan 21 11:37:21 nastie kernel: [ 889.532430] raid6: neonx1 gen() 3482 MB/s
Jan 21 11:37:21 nastie kernel: [ 889.600426] raid6: neonx1 xor() 2803 MB/s
Jan 21 11:37:21 nastie kernel: [ 889.668429] raid6: int64x8 gen() 3087 MB/s
Jan 21 11:37:22 nastie kernel: [ 889.736430] raid6: int64x8 xor() 1772 MB/s
Jan 21 11:37:22 nastie kernel: [ 889.804448] raid6: int64x4 gen() 3028 MB/s
Jan 21 11:37:22 nastie kernel: [ 889.872431] raid6: int64x4 xor() 1783 MB/s
Jan 21 11:37:22 nastie kernel: [ 889.940452] raid6: int64x2 gen() 2778 MB/s
Jan 21 11:37:22 nastie kernel: [ 890.008429] raid6: int64x2 xor() 1578 MB/s
Jan 21 11:37:22 nastie kernel: [ 890.076435] raid6: int64x1 gen() 2167 MB/s
Jan 21 11:37:22 nastie kernel: [ 890.144433] raid6: int64x1 xor() 1177 MB/s
Jan 21 11:37:22 nastie kernel: [ 890.144440] raid6: using algorithm neonx4 gen() 5267 MB/s
Jan 21 11:37:22 nastie kernel: [ 890.144444] raid6: .... xor() 4030 MB/s, rmw enabled
Jan 21 11:37:22 nastie kernel: [ 890.144448] raid6: using neon recovery algorithm
Jan 21 11:37:22 nastie kernel: [ 890.147239] xor: measuring software checksum speed
Jan 21 11:37:22 nastie kernel: [ 890.148603] 8regs : 7588 MB/sec
Jan 21 11:37:22 nastie kernel: [ 890.149730] 32regs : 8774 MB/sec
Jan 21 11:37:22 nastie kernel: [ 890.151018] arm64_neon : 7669 MB/sec
Jan 21 11:37:22 nastie kernel: [ 890.151022] xor: using function: 32regs (8774 MB/sec)
Jan 21 11:37:22 nastie kernel: [ 890.152357] async_tx: api initialized (async)
Jan 21 11:37:22 nastie kernel: [ 890.169166] md/raid:md0: device sdc1 operational as raid disk 2
Jan 21 11:37:22 nastie kernel: [ 890.169177] md/raid:md0: device sdb1 operational as raid disk 1
Jan 21 11:37:22 nastie kernel: [ 890.169182] md/raid:md0: device sda1 operational as raid disk 0
Jan 21 11:37:22 nastie kernel: [ 890.170843] md/raid:md0: raid level 5 active with 3 out of 4 devices, algorithm 2
Jan 21 11:37:22 nastie kernel: [ 890.170874] md0: Warning: Device sdd1 is misaligned
Jan 21 11:37:22 nastie kernel: [ 890.193366] md0: detected capacity change from 0 to 6000690069504
Jan 21 11:37:22 nastie kernel: [ 890.197206] md: recovery of RAID array md0
Jan 21 11:37:34 nastie systemd[1]: Starting Cleanup of Temporary Directories...
Jan 21 11:37:34 nastie systemd[1]: systemd-tmpfiles-clean.service: Succeeded.
Jan 21 11:37:34 nastie systemd[1]: Finished Cleanup of Temporary Directories.
Jan 21 11:38:31 nastie kernel: [ 959.481481] sd 0:0:0:0: [sda] tag#12 uas_eh_abort_handler 0 uas-tag 4 inflight: IN
Jan 21 11:38:31 nastie kernel: [ 959.481495] sd 0:0:0:0: [sda] tag#12 CDB: opcode=0x28 28 00 00 7c fe 07 00 04 00 00
Jan 21 11:38:31 nastie kernel: [ 959.497486] scsi host0: uas_eh_device_reset_handler start
Jan 21 11:38:31 nastie kernel: [ 959.626199] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Jan 21 11:38:31 nastie kernel: [ 959.646495] usb 2-2: device firmware changed
Jan 21 11:38:31 nastie kernel: [ 959.654695] scsi host0: uas_eh_device_reset_handler FAILED err -19
Jan 21 11:38:31 nastie kernel: [ 959.654710] sd 0:0:0:0: Device offlined - not ready after error recovery
Jan 21 11:38:31 nastie kernel: [ 959.654765] sd 0:0:0:0: [sda] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06 cmd_age=31s
Jan 21 11:38:31 nastie kernel: [ 959.654773] sd 0:0:0:0: [sda] tag#12 CDB: opcode=0x28 28 00 00 7c fe 07 00 04 00 00
Jan 21 11:38:31 nastie kernel: [ 959.654781] blk_update_request: I/O error, dev sda, sector 8191495 op 0x0:(READ) flags 0x0 phys_seg 128 prio class 0
Jan 21 11:38:31 nastie kernel: [ 959.654791] md/raid:md0: read error not correctable (sector 8125960 on sda1).
...
Jan 21 11:38:31 nastie kernel: [ 959.654843] md/raid:md0: read error not correctable (sector 8126032 on sda1).
Jan 21 11:38:31 nastie kernel: [ 959.655016] sd 0:0:0:0: rejecting I/O to offline device
Jan 21 11:38:31 nastie kernel: [ 959.655019] blk_update_request: I/O error, dev sda, sector 8191503 op 0x0:(READ) flags 0x4000 phys_seg 1 prio class 0
...
Jan 21 11:38:31 nastie kernel: [ 959.655080] blk_update_request: I/O error, dev sda, sector 8191551 op 0x0:(READ) flags 0x4000 phys_seg 1 prio class 0
Jan 21 11:38:31 nastie kernel: [ 959.655209] usb 2-2: USB disconnect, device number 2
Jan 21 11:38:31 nastie kernel: [ 959.655423] md: super_written gets error=-5
Jan 21 11:38:31 nastie kernel: [ 959.661537] sd 0:0:0:0: [sda] Synchronizing SCSI cache
Jan 21 11:38:32 nastie kernel: [ 959.733483] sd 0:0:0:1: [sdb] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
Jan 21 11:38:32 nastie kernel: [ 959.733498] sd 0:0:0:1: [sdb] tag#6 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
Jan 21 11:38:32 nastie kernel: [ 959.733514] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 959.733683] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 959.733693] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 959.805481] sd 0:0:0:1: [sdb] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
Jan 21 11:38:32 nastie kernel: [ 959.805493] sd 0:0:0:1: [sdb] tag#6 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
Jan 21 11:38:32 nastie kernel: [ 959.805506] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 959.805659] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 959.881480] sd 0:0:0:1: [sdb] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
Jan 21 11:38:32 nastie kernel: [ 959.881492] sd 0:0:0:1: [sdb] tag#6 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
Jan 21 11:38:32 nastie kernel: [ 959.881504] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 959.881653] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 959.881662] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 959.913493] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=0x00
Jan 21 11:38:32 nastie kernel: [ 959.953485] sd 0:0:0:1: [sdb] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x07 driverbyte=0x00 cmd_age=0s
Jan 21 11:38:32 nastie kernel: [ 959.953496] sd 0:0:0:1: [sdb] tag#5 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
Jan 21 11:38:32 nastie kernel: [ 959.953510] md: super_written gets error=-5
...
Jan 21 11:38:32 nastie kernel: [ 959.954320] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 959.954563] sd 0:0:0:1: [sdb] Synchronizing SCSI cache
Jan 21 11:38:32 nastie kernel: [ 959.955764] md: super_written gets error=-5
...
Jan 21 11:38:32 nastie kernel: [ 960.264179] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 960.265524] sd 0:0:0:1: [sdb] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=0x00
Jan 21 11:38:32 nastie kernel: [ 960.266206] md: super_written gets error=-5
...
Jan 21 11:38:32 nastie kernel: [ 960.526793] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 960.527369] usb 2-2: New USB device found, idVendor=152d, idProduct=0561, bcdDevice=81.36
Jan 21 11:38:32 nastie kernel: [ 960.527375] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Jan 21 11:38:32 nastie kernel: [ 960.527380] usb 2-2: Product: External Disk 3.0
Jan 21 11:38:32 nastie kernel: [ 960.527384] usb 2-2: Manufacturer: JMicron
Jan 21 11:38:32 nastie kernel: [ 960.527388] usb 2-2: SerialNumber: RANDOM__7CDEBB6A0840
Jan 21 11:38:32 nastie kernel: [ 960.528241] md: super_written gets error=-5
...
Jan 21 11:38:32 nastie kernel: [ 960.535054] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 960.535429] scsi host2: uas
Jan 21 11:38:32 nastie kernel: [ 960.536344] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 960.536377] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 960.536397] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 960.536406] scsi 2:0:0:0: Direct-Access JMicron Tech 8136 PQ: 0 ANSI: 6
Jan 21 11:38:32 nastie kernel: [ 960.537723] sd 2:0:0:0: Attached scsi generic sg0 type 0
Jan 21 11:38:32 nastie kernel: [ 960.538744] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 960.538773] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 960.538913] scsi 2:0:0:1: Direct-Access JMicron Tech 8136 PQ: 0 ANSI: 6
Jan 21 11:38:32 nastie kernel: [ 960.539029] sd 2:0:0:0: [sde] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
Jan 21 11:38:32 nastie kernel: [ 960.539294] sd 2:0:0:0: [sde] Write Protect is off
Jan 21 11:38:32 nastie kernel: [ 960.539300] sd 2:0:0:0: [sde] Mode Sense: 67 00 10 08
Jan 21 11:38:32 nastie kernel: [ 960.540103] sd 2:0:0:0: [sde] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jan 21 11:38:32 nastie kernel: [ 960.540234] scsi 2:0:0:1: Attached scsi generic sg1 type 0
Jan 21 11:38:32 nastie kernel: [ 960.540907] sd 2:0:0:0: [sde] Optimal transfer size 33553920 bytes
Jan 21 11:38:32 nastie kernel: [ 960.542251] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 960.542289] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 960.543075] sd 2:0:0:1: [sdf] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
Jan 21 11:38:32 nastie kernel: [ 960.543345] sd 2:0:0:1: [sdf] Write Protect is off
Jan 21 11:38:32 nastie kernel: [ 960.543353] sd 2:0:0:1: [sdf] Mode Sense: 67 00 10 08
Jan 21 11:38:32 nastie kernel: [ 960.543852] sd 2:0:0:1: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jan 21 11:38:32 nastie kernel: [ 960.544235] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 960.544259] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 960.544660] sd 2:0:0:1: [sdf] Optimal transfer size 33553920 bytes
Jan 21 11:38:32 nastie kernel: [ 960.545619] md: super_written gets error=-5
...
Jan 21 11:38:32 nastie kernel: [ 960.561995] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 960.562089] sdf: sdf1
Jan 21 11:38:32 nastie kernel: [ 960.563064] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 960.563105] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 960.564218] sde: sde1
Jan 21 11:38:32 nastie kernel: [ 960.565133] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 960.565147] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 960.566239] sd 2:0:0:1: [sdf] Attached SCSI disk
Jan 21 11:38:32 nastie kernel: [ 960.566493] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 960.566530] md: super_written gets error=-5
Jan 21 11:38:32 nastie kernel: [ 960.567288] sd 2:0:0:0: [sde] Attached SCSI disk
Jan 21 11:38:32 nastie kernel: [ 960.568410] md: super_written gets error=-5
...
Jan 21 11:38:32 nastie kernel: [ 960.660238] md: super_written gets error=-5
Jan 21 11:38:33 nastie kernel: [ 960.699772] md0: detected capacity change from 6000690069504 to 0
Jan 21 11:38:33 nastie kernel: [ 960.699796] md: md0 stopped.
Jan 21 11:38:33 nastie systemd-udevd[4781]: sdb1: Process '/sbin/mdadm -If sdb1 --path platform-fd500000.pcie-pci-0000:01:00.0-usb-0:2:1.0-scsi-0:0:0:1' failed with exit code 1.
Jan 21 11:38:33 nastie mtp-probe: checking bus 2, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2"
Jan 21 11:38:33 nastie mtp-probe: bus: 2, device: 4 was not an MTP device
Jan 21 11:38:33 nastie mtp-probe: checking bus 2, device 4: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2"
Jan 21 11:38:33 nastie mtp-probe: bus: 2, device: 4 was not an MTP deviceI have a Sata Hat system (1.2 hardware) which can experience the same problems, in which the JMicron controller can disconnect from USB, and then reconnect. I have a 3-active, 1-spare raid-5 system, with Seagate 2.5 inch 2TB drives. I run OMV for external service access through Samba.
The V1.2 hat came with the latest firmware already installed. The following syslog entries suggest that this is due to transfer errors causing the system to reset the controller.
I have seen, occasionally under heavy load such a a resync of the array, that a controller will disconnect, dropping its associated drives and then re-appear. At that point the drives on it will be recognized with different device number, which breaks the array, even though the drives on the other controller will reconnect as their previous device ids.
A much more reliable stiumulus (shorter to fail), is to use another drive in an external enclosure, plugged into the USB2.0 connector of the Raspberry Pi 4 and to do an rsync backup of the array to it for another level of protection. This typically will stimulate the problem within 20 to 100+ GBytes.
A clipping of a syslogof system start and recognition follows:
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.478396] usb 2-2: new SuperSpeed Gen 1 USB device number 2 using xhci_hcd
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.517236] usb 2-2: New USB device found, idVendor=152d, idProduct=0561, bcdDevice=81.36
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.517261] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.517279] usb 2-2: Product: External Disk 3.0
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.517296] usb 2-2: Manufacturer: JMicron
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.517314] usb 2-2: SerialNumber: RANDOM__525084014383
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.847854] scsi host0: uas
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.849974] scsi 0:0:0:0: Direct-Access JMicron Tech 8136 PQ: 0 ANSI: 6
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.853331] scsi 0:0:0:1: Direct-Access JMicron Tech 8136 PQ: 0 ANSI: 6
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.853450] sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.853826] sd 0:0:0:0: [sda] Write Protect is off
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.853848] sd 0:0:0:0: [sda] Mode Sense: 67 00 10 08
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.854422] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.855896] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.856832] sd 0:0:0:1: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.857138] sd 0:0:0:1: [sdb] Write Protect is off
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.857160] sd 0:0:0:1: [sdb] Mode Sense: 67 00 10 08
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.857713] sd 0:0:0:1: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.858650] sd 0:0:0:1: [sdb] Optimal transfer size 33553920 bytes
Jan 20 12:45:03 raspberry-NAS mtp-probe: checking bus 2, device 2: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2"
Jan 20 12:45:03 raspberry-NAS mtp-probe: bus: 2, device: 2 was not an MTP device
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.925841] sda: sda1
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.958393] sdb: sdb1
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.960862] sd 0:0:0:0: [sda] Attached SCSI disk
Jan 20 12:45:03 raspberry-NAS kernel: [ 21.962837] sd 0:0:0:1: [sdb] Attached SCSI disk
Jan 20 12:45:03 raspberry-NAS mtp-probe: checking bus 2, device 2: "/sys/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb2/2-2"
Jan 20 12:45:03 raspberry-NAS mtp-probe: bus: 2, device: 2 was not an MTP device
Jan 20 12:45:03 raspberry-NAS kernel: [ 22.063318] sd 0:0:0:0: Attached scsi generic sg0 type 0
Jan 20 12:45:03 raspberry-NAS kernel: [ 22.064136] sd 0:0:0:1: Attached scsi generic sg1 type 0
Jan 20 12:45:04 raspberry-NAS kernel: [ 22.235634] usb 2-1: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
Jan 20 12:45:04 raspberry-NAS kernel: [ 22.266944] usb 2-1: New USB device found, idVendor=152d, idProduct=0561, bcdDevice=81.36
Jan 20 12:45:04 raspberry-NAS kernel: [ 22.266969] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Jan 20 12:45:04 raspberry-NAS kernel: [ 22.266987] usb 2-1: Product: External Disk 3.0
Jan 20 12:45:04 raspberry-NAS kernel: [ 22.267005] usb 2-1: Manufacturer: JMicron
Jan 20 12:45:04 raspberry-NAS kernel: [ 22.267022] usb 2-1: SerialNumber: RANDOM__6BA993A16EF0
Jan 20 12:45:04 raspberry-NAS kernel: [ 23.115893] scsi host1: uas
Jan 20 12:45:04 raspberry-NAS kernel: [ 23.117564] scsi 1:0:0:0: Direct-Access JMicron Tech 8136 PQ: 0 ANSI: 6
Jan 20 12:45:04 raspberry-NAS kernel: [ 23.119471] sd 1:0:0:0: Attached scsi generic sg2 type 0
Jan 20 12:45:04 raspberry-NAS kernel: [ 23.120883] sd 1:0:0:0: [sdc] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
Jan 20 12:45:04 raspberry-NAS kernel: [ 23.121187] sd 1:0:0:0: [sdc] Write Protect is off
Jan 20 12:45:04 raspberry-NAS kernel: [ 23.121209] sd 1:0:0:0: [sdc] Mode Sense: 67 00 10 08
Jan 20 12:45:04 raspberry-NAS kernel: [ 23.121376] scsi 1:0:0:1: Direct-Access JMicron Tech 8136 PQ: 0 ANSI: 6
Jan 20 12:45:04 raspberry-NAS kernel: [ 23.121883] sd 1:0:0:0: [sdc] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jan 20 12:45:04 raspberry-NAS kernel: [ 23.122805] sd 1:0:0:0: [sdc] Optimal transfer size 33553920 bytes
Jan 20 12:45:04 raspberry-NAS kernel: [ 23.123769] sd 1:0:0:1: Attached scsi generic sg3 type 0
Jan 20 12:45:04 raspberry-NAS kernel: [ 23.125347] sd 1:0:0:1: [sdd] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
Jan 20 12:45:05 raspberry-NAS kernel: [ 23.125665] sd 1:0:0:1: [sdd] Write Protect is off
Jan 20 12:45:05 raspberry-NAS kernel: [ 23.125687] sd 1:0:0:1: [sdd] Mode Sense: 67 00 10 08
Jan 20 12:45:05 raspberry-NAS kernel: [ 23.126327] sd 1:0:0:1: [sdd] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jan 20 12:45:05 raspberry-NAS kernel: [ 23.127208] sd 1:0:0:1: [sdd] Optimal transfer size 33553920 bytes
Jan 20 12:48:59 raspberry-NAS kernel: [ 258.068523] md/raid:md0: device sda1 operational as raid disk 0
Jan 20 12:48:59 raspberry-NAS kernel: [ 258.068533] md/raid:md0: device sdc1 operational as raid disk 2
Jan 20 12:48:59 raspberry-NAS kernel: [ 258.068541] md/raid:md0: device sdd1 operational as raid disk 1
Jan 20 12:48:59 raspberry-NAS kernel: [ 258.070885] md/raid:md0: raid level 5 active with 3 out of 3 devices, algorithm 2
Jan 20 12:48:59 raspberry-NAS kernel: [ 258.070919] md0: Warning: Device sda1 is misaligned
Jan 20 12:48:59 raspberry-NAS kernel: [ 258.096731] md0: detected capacity change from 0 to 4000460046336
Jan 20 12:49:00 raspberry-NAS systemd[1]: Started MD array monitor.
The disconnect and reconnect follows (note that syslog shows transfer errors):
Jan 20 13:27:25 raspberry-NAS systemd[1]: Started Session 53 of user pi.
Jan 20 13:28:11 raspberry-NAS kernel: [ 2609.717421] xhci_hcd 0000:01:00.0: ERROR Transfer event for unknown stream ring slot 3 ep 7
Jan 20 13:28:11 raspberry-NAS kernel: [ 2609.717432] xhci_hcd 0000:01:00.0: @000000041ad09be0 00000000 00000000 05000000 03088000
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.900652] sd 1:0:0:1: [sdd] tag#13 uas_eh_abort_handler 0 uas-tag 12 inflight: CMD IN
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.900663] sd 1:0:0:1: [sdd] tag#13 CDB: opcode=0x28 28 00 08 dd ed ff 00 02 00 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.901043] sd 1:0:0:1: [sdd] tag#11 uas_eh_abort_handler 0 uas-tag 8 inflight: CMD IN
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.901050] sd 1:0:0:1: [sdd] tag#11 CDB: opcode=0x28 28 00 08 dd b3 ff 00 02 00 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.901427] sd 1:0:0:1: [sdd] tag#9 uas_eh_abort_handler 0 uas-tag 13 inflight: CMD IN
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.901434] sd 1:0:0:1: [sdd] tag#9 CDB: opcode=0x28 28 00 08 dd ef ff 00 04 00 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.901795] sd 1:0:0:1: [sdd] tag#8 uas_eh_abort_handler 0 uas-tag 11 inflight: CMD OUT
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.901801] sd 1:0:0:1: [sdd] tag#8 CDB: opcode=0x2a 2a 00 79 45 09 4f 00 00 08 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.901914] sd 1:0:0:1: [sdd] tag#7 uas_eh_abort_handler 0 uas-tag 9 inflight: CMD IN
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.901920] sd 1:0:0:1: [sdd] tag#7 CDB: opcode=0x28 28 00 08 dd eb ff 00 02 00 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.901931] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.902189] sd 1:0:0:1: [sdd] tag#6 uas_eh_abort_handler 0 uas-tag 10 inflight: CMD OUT
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.902195] sd 1:0:0:1: [sdd] tag#6 CDB: opcode=0x2a 2a 00 79 45 08 ff 00 00 08 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.902368] sd 1:0:0:1: [sdd] tag#1 uas_eh_abort_handler 0 uas-tag 14 inflight: CMD IN
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.902374] sd 1:0:0:1: [sdd] tag#1 CDB: opcode=0x28 28 00 08 dd f7 ff 00 04 00 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.902383] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.902701] sd 1:0:0:0: [sdc] tag#12 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD OUT
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.902708] sd 1:0:0:0: [sdc] tag#12 CDB: opcode=0x2a 2a 00 7a a5 09 97 00 00 08 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.902773] sd 1:0:0:0: [sdc] tag#10 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD OUT
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.902779] sd 1:0:0:0: [sdc] tag#10 CDB: opcode=0x2a 2a 00 a3 85 08 ff 00 00 08 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.902788] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.902856] sd 1:0:0:0: [sdc] tag#5 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD OUT
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.902862] sd 1:0:0:0: [sdc] tag#5 CDB: opcode=0x2a 2a 00 79 25 08 ff 00 00 08 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.902871] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.902952] sd 1:0:0:0: [sdc] tag#4 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD OUT
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.902958] sd 1:0:0:0: [sdc] tag#4 CDB: opcode=0x2a 2a 00 7c 85 0b cf 00 00 08 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.902967] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.903034] sd 1:0:0:0: [sdc] tag#3 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD OUT
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.903040] sd 1:0:0:0: [sdc] tag#3 CDB: opcode=0x2a 2a 00 79 25 09 9f 00 00 08 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.903049] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.903117] sd 1:0:0:0: [sdc] tag#2 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.903123] sd 1:0:0:0: [sdc] tag#2 CDB: opcode=0x2a 2a 00 7c 85 09 37 00 00 18 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.903132] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.903146] sd 1:0:0:0: [sdc] tag#0 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD OUT
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.903152] sd 1:0:0:0: [sdc] tag#0 CDB: opcode=0x2a 2a 00 7b 65 08 ff 00 00 08 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.903227] xhci_hcd 0000:01:00.0: WARN Set TR Deq Ptr cmd failed due to incorrect slot or ep state.
Jan 20 13:28:41 raspberry-NAS kernel: [ 2639.950740] scsi host1: uas_eh_device_reset_handler start
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.101409] usb 2-1: reset SuperSpeed Gen 1 USB device number 3 using xhci_hcd
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.131729] usb 2-1: device firmware changed
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.136793] scsi host1: uas_eh_device_reset_handler FAILED err -19
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.136805] scsi host1: uas_eh_device_reset_handler FAILED to get lock err -19
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.136818] sd 1:0:0:0: Device offlined - not ready after error recovery
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.136826] sd 1:0:0:0: Device offlined - not ready after error recovery
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.136833] sd 1:0:0:0: Device offlined - not ready after error recovery
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.136840] sd 1:0:0:0: Device offlined - not ready after error recovery
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.136847] sd 1:0:0:0: Device offlined - not ready after error recovery
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.136854] sd 1:0:0:0: Device offlined - not ready after error recovery
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.136861] sd 1:0:0:0: Device offlined - not ready after error recovery
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.136869] sd 1:0:0:1: Device offlined - not ready after error recovery
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.136876] sd 1:0:0:1: Device offlined - not ready after error recovery
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.136884] sd 1:0:0:1: Device offlined - not ready after error recovery
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.136891] sd 1:0:0:1: Device offlined - not ready after error recovery
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.136898] sd 1:0:0:1: Device offlined - not ready after error recovery
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.136905] sd 1:0:0:1: Device offlined - not ready after error recovery
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.136912] sd 1:0:0:1: Device offlined - not ready after error recovery
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.136941] sd 1:0:0:0: [sdc] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06 cmd_age=30s
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.136951] sd 1:0:0:0: [sdc] tag#0 CDB: opcode=0x2a 2a 00 7b 65 08 ff 00 00 08 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.136962] blk_update_request: I/O error, dev sdc, sector 2070219007 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137003] sd 1:0:0:0: [sdc] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06 cmd_age=30s
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137012] sd 1:0:0:0: [sdc] tag#2 CDB: opcode=0x2a 2a 00 7c 85 09 37 00 00 18 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137021] blk_update_request: I/O error, dev sdc, sector 2089093431 op 0x1:(WRITE) flags 0x0 phys_seg 3 prio class 0
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137047] sd 1:0:0:0: [sdc] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06 cmd_age=30s
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137055] sd 1:0:0:0: [sdc] tag#3 CDB: opcode=0x2a 2a 00 79 25 09 9f 00 00 08 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137064] blk_update_request: I/O error, dev sdc, sector 2032470431 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137083] sd 1:0:0:0: [sdc] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06 cmd_age=30s
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137091] sd 1:0:0:0: [sdc] tag#4 CDB: opcode=0x2a 2a 00 7c 85 0b cf 00 00 08 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137100] blk_update_request: I/O error, dev sdc, sector 2089094095 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137118] sd 1:0:0:0: [sdc] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06 cmd_age=30s
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137126] sd 1:0:0:0: [sdc] tag#5 CDB: opcode=0x2a 2a 00 79 25 08 ff 00 00 08 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137134] blk_update_request: I/O error, dev sdc, sector 2032470271 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137152] sd 1:0:0:0: [sdc] tag#10 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06 cmd_age=30s
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137160] sd 1:0:0:0: [sdc] tag#10 CDB: opcode=0x2a 2a 00 a3 85 08 ff 00 00 08 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137169] blk_update_request: I/O error, dev sdc, sector 2743404799 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137186] sd 1:0:0:0: [sdc] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06 cmd_age=30s
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137194] sd 1:0:0:0: [sdc] tag#12 CDB: opcode=0x2a 2a 00 7a a5 09 97 00 00 08 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137203] blk_update_request: I/O error, dev sdc, sector 2057636247 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137222] sd 1:0:0:1: [sdd] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06 cmd_age=30s
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137230] sd 1:0:0:1: [sdd] tag#1 CDB: opcode=0x28 28 00 08 dd f7 ff 00 04 00 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137239] blk_update_request: I/O error, dev sdd, sector 148764671 op 0x0:(READ) flags 0x80700 phys_seg 128 prio class 0
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137265] sd 1:0:0:1: [sdd] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06 cmd_age=30s
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137274] sd 1:0:0:1: [sdd] tag#6 CDB: opcode=0x2a 2a 00 79 45 08 ff 00 00 08 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137282] blk_update_request: I/O error, dev sdd, sector 2034567423 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137301] sd 1:0:0:1: [sdd] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x06 cmd_age=30s
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137308] sd 1:0:0:1: [sdd] tag#7 CDB: opcode=0x28 28 00 08 dd eb ff 00 02 00 00
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137317] blk_update_request: I/O error, dev sdd, sector 148761599 op 0x0:(READ) flags 0x80700 phys_seg 64 prio class 0
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137386] sd 1:0:0:0: rejecting I/O to offline device
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137396] md: super_written gets error=-5
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137404] md/raid:md0: Disk failure on sdc1, disabling device.
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137404] md/raid:md0: Operation continuing on 2 devices.
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137571] sd 1:0:0:1: rejecting I/O to offline device
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137581] md: super_written gets error=-5
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137807] md: super_written gets error=-5
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.137872] usb 2-1: USB disconnect, device number 3
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.143703] md: super_written gets error=-5
Jan 20 13:28:41 raspberry-NAS kernel: [ 2640.151681] sd 1:0:0:0: [sdc] Synchronizing SCSI cache
Jan 20 13:28:42 raspberry-NAS kernel: [ 2640.531158] md/raid:md0: read error not correctable (sector 148700160 on sdd1).
Jan 20 13:28:42 raspberry-NAS kernel: [ 2640.531204] md/raid:md0: read error not correctable (sector 148700168 on sdd1).
Jan 20 13:28:42 raspberry-NAS kernel: [ 2640.531238] md/raid:md0: read error not correctable (sector 148700176 on sdd1).
Jan 20 13:28:42 raspberry-NAS kernel: [ 2640.531272] md/raid:md0: read error not correctable (sector 148700184 on sdd1).
Jan 20 13:28:42 raspberry-NAS kernel: [ 2640.531305] md/raid:md0: read error not correctable (sector 148700192 on sdd1).
Jan 20 13:28:42 raspberry-NAS kernel: [ 2640.531338] md/raid:md0: read error not correctable (sector 148700200 on sdd1).
Jan 20 13:28:42 raspberry-NAS kernel: [ 2640.531370] md/raid:md0: read error not correctable (sector 148700208 on sdd1).
Jan 20 13:28:42 raspberry-NAS kernel: [ 2640.531403] md/raid:md0: read error not correctable (sector 148700216 on sdd1).
Jan 20 13:28:42 raspberry-NAS kernel: [ 2640.531436] md/raid:md0: read error not correctable (sector 148700224 on sdd1).
Jan 20 13:28:42 raspberry-NAS kernel: [ 2640.531468] md/raid:md0: read error not correctable (sector 148700232 on sdd1).
Jan 20 13:28:42 raspberry-NAS kernel: [ 2640.545510] md: super_written gets error=-5
Jan 20 13:28:42 raspberry-NAS kernel: [ 2640.545605] md: super_written gets error=-5
Jan 20 13:28:42 raspberry-NAS kernel: [ 2640.591069] md: super_written gets error=-5
Jan 20 13:28:42 raspberry-NAS kernel: [ 2640.591153] md: super_written gets error=-5
Jan 20 13:28:42 raspberry-NAS kernel: [ 2640.760784] sd 1:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=0x00
Jan 20 13:28:42 raspberry-NAS kernel: [ 2640.907709] sd 1:0:0:1: [sdd] Synchronizing SCSI cache
Jan 20 13:28:42 raspberry-NAS kernel: [ 2640.960907] md: super_written gets error=-5
Jan 20 13:28:42 raspberry-NAS kernel: [ 2641.010951] md: super_written gets error=-5
Jan 20 13:28:42 raspberry-NAS kernel: [ 2641.010971] md: super_written gets error=-5
Jan 20 13:28:42 raspberry-NAS kernel: [ 2641.049313] md: super_written gets error=-5
Jan 20 13:28:42 raspberry-NAS kernel: [ 2641.066228] md: super_written gets error=-5
Jan 20 13:28:42 raspberry-NAS kernel: [ 2641.066260] md: super_written gets error=-5
Jan 20 13:28:42 raspberry-NAS kernel: [ 2641.103986] md: super_written gets error=-5
Jan 20 13:28:42 raspberry-NAS kernel: [ 2641.121564] md: super_written gets error=-5
Jan 20 13:28:42 raspberry-NAS kernel: [ 2641.121597] md: super_written gets error=-5
Jan 20 13:28:42 raspberry-NAS kernel: [ 2641.159085] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.176845] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.176877] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.214321] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.232155] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.232189] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.269881] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.287440] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.287461] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.324975] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.342885] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.342930] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.380302] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.398044] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.398065] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.435574] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.453445] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.453481] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.490905] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.508745] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.508780] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.530720] sd 1:0:0:1: [sdd] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=0x00
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.546234] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.564008] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.564041] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.660828] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.674750] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.674783] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.712189] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.730096] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.730133] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.767554] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.785373] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.785410] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.811008] usb 2-1: new SuperSpeed Gen 1 USB device number 4 using xhci_hcd
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.822961] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.840764] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.840801] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.842384] usb 2-1: New USB device found, idVendor=152d, idProduct=0561, bcdDevice=81.36
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.842401] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.842417] usb 2-1: Product: External Disk 3.0
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.842432] usb 2-1: Manufacturer: JMicron
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.842447] usb 2-1: SerialNumber: RANDOM__43833EEF5DA5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.851866] scsi host3: uas
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.853446] scsi 3:0:0:0: Direct-Access JMicron Tech 8136 PQ: 0 ANSI: 6
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.855144] sd 3:0:0:0: Attached scsi generic sg2 type 0
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.878161] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.895984] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.896021] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.933389] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.951256] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.951314] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2641.988707] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2642.006551] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2642.006609] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2642.044057] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2642.061962] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2642.062003] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2642.099410] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2642.117250] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2642.117288] md: super_written gets error=-5
Jan 20 13:28:43 raspberry-NAS kernel: [ 2642.137783] scsi 3:0:0:1: Direct-Access JMicron Tech 8136 PQ: 0 ANSI: 6
Jan 20 13:28:43 raspberry-NAS kernel: [ 2642.138181] sd 3:0:0:0: [sdf] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
Jan 20 13:28:43 raspberry-NAS kernel: [ 2642.138470] sd 3:0:0:0: [sdf] Write Protect is off
Jan 20 13:28:43 raspberry-NAS kernel: [ 2642.138478] sd 3:0:0:0: [sdf] Mode Sense: 67 00 10 08
Jan 20 13:28:43 raspberry-NAS kernel: [ 2642.139034] sd 3:0:0:0: [sdf] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jan 20 13:28:43 raspberry-NAS kernel: [ 2642.139321] sd 3:0:0:1: Attached scsi generic sg3 type 0
Jan 20 13:28:43 raspberry-NAS kernel: [ 2642.139873] sd 3:0:0:0: [sdf] Optimal transfer size 33553920 bytes
Jan 20 13:28:43 raspberry-NAS kernel: [ 2642.140690] sd 3:0:0:1: [sdg] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
Jan 20 13:28:43 raspberry-NAS kernel: [ 2642.140955] sd 3:0:0:1: [sdg] Write Protect is off
Jan 20 13:28:43 raspberry-NAS kernel: [ 2642.140964] sd 3:0:0:1: [sdg] Mode Sense: 67 00 10 08
Jan 20 13:28:43 raspberry-NAS kernel: [ 2642.141485] sd 3:0:0:1: [sdg] Write cache: enabled, read cache: enabled, supports DPO and FUA
Jan 20 13:28:43 raspberry-NAS kernel: [ 2642.142257] sd 3:0:0:1: [sdg] Optimal transfer size 33553920 bytes
In my case it only occasionally caused a raid resync because the failure removed 2 of the 3 active drives and the array basically could not continue to a failure forcing a resync. But that was more luck than planning.
I have also had periods without any such failures and if the system is essentially idle it does not seem to fail, so heavy activity seems to be a trigger.
@mostarman, @oket
Yes, I was able to overcome the issue by upgrading the firmware (Windows way) and disabling the uas.
Since then, i havent had the issue again (since 9 days now)
Hmm - I tried both and nothing worked. I am still running into the same issue, quite frequently actually, especially when trying to run a RAID.
What / how did you set the uas disablement?
I did it following way:
Step 1)
run:
dmesg | grep "usb 2-1:"
Identify the IdVendor (in my case 152d) and idProduct (in my case 0561):
[ 20.705149] usb 2-1: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 20.746428] usb 2-1: New USB device found, idVendor=152d, idProduct=0561, bcdDevice=81.36
[ 20.746438] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[ 20.746446] usb 2-1: Product: External
[ 20.746453] usb 2-1: Manufacturer: JMicron
[ 20.746460] usb 2-1: SerialNumber: RANDOM__D3A16EF0C17A
[ 20.749472] usb 2-1: UAS is ignored for this device, using usb-storage instead
[ 20.749529] usb 2-1: UAS is ignored for this device, using usb-storage instead
Step 2)
edit
sudo vim cmdline.txt
Step 3)
Add following line (exchange the id with the one you’ve found in dmesg):
usb-storage.quirks=152d:0561:u …
Step 4)
execute (exchange the id with the ones you found in dmesg:
echo options usb-storage quirks=152d:0561:u | sudo tee /etc/modprobe.d/blacklist-uas_152d.conf
Keep in mind, the vendor ID / Product ID will change depending on how you applied the firmware update … in case youve used the Windows variant, you might get the same as I got
@mostarman , @oket
Can you check calling sudo hdparm -I /dev/sda1
@setq, calling the mentioned code is causing the issue again
@oket Thank you for your information. It seems possible to fix it by upgrade the firmware, I will try to find a stable firmware. Or it could reset because it was too hot in heavy load. I’ll take a test.
This is not heat or load related, if I go in the S.M.A.R.T tab on omv, one of the controllers resets (usb 2-2: reset SuperSpeed Gen 1 USB), the drives get other names like SDE and SDF and raid goes to degraded.
I’m quessing omv triggers hdparm to get smart info and that resets one of the controllers.
Even if i don’t go in to smart tab on OMV, after a period the controller still gets a reset and once again same story, might be omv does some checks and uses hdparm which triggers the reset.
This is really bad as it makes the device unusable and it could break the hdds
Anyone found a solution or a workarround, as disabling UAS doesn’t work?