pauls1213

Swapped the motherboard, plugged my flash drive and hard drives to it without issue transferring the Unraid install. I was able to run a rebuild without issue on the drive array. As far as I can see for now, the issue is solved. No more errors in the log, so it's back to business for my Unraid server.

Replaced SATA cables on all drives, ran a rebuild, and the system lost the ethernet so the WebGUI stopped working. Fortunately the terminal on my second monitor input was still working, so I was able to go into the console. when I ran "lsssci", the only item listed was my system flash drive - everything else dropped again. So I think itimpi was correct and there's a common factor here - the motherboard. Going to order a new one compatible with my CPU off Amazon and hopefully, that will get it working and stable again.

Alright well I finished the extended SMART test of the drive that dropped out, and then the second drive it mentioned in the logs as ATA6 (sdg) - as far as I can tell there's no issues that leap out at me from the reports. I think that it's going to be a common issue - bad cables (sata/power loom), bad motherboard, or bad PSU. I've got some replacement SATA cables on their way today, going to reseat everything for drive power, and then try to run a rebuild with the syslog mirrored to flash. tower-sdb-ata1-smart-20240604-0656.zip tower-sdg-ata6-smart-20240603-1930.zip

Some of the issues that I saw while searching for "ata6 unraid" and other errors I was experiencing seemed to point the finger at the power supply as a possible issue. Both the PSU and the motherboard are mid-2018, and have seen years of continuous usage. Wouldn't surprise me if one were starting to fail. From searching on unraid.net, it would seem that the issue points to 1/ bad drive, 2/ bad motherboard or 3/ bad PSU. I've been running the missing disk in emulated mode all evening serving up files without issue, while the extended SMART test runs on the "failed" drive. Obviously my data is unprotected right now running off the parity information, but I'm keeping to tasks that are pretty light duty on disk usage until that extended SMART finishes. I'll post the result in this thread when that completes.

I'm running an extended SMART test on the Disk 4, the disk that started the issue. That will take some time, of course.

Good day, I'm having an issue that cropped up suddenly this morning running a monthly parity check on my disks. The system hard froze about 30-40% of the way through, had to do a hard reset, and then my Disk 4 was errored out. I'm not sure why it happened, so I tried to rebuild the array by removing and then adding the Disk 4 back into the Array to rebuild it. However, it will go for about 1-3 TB of rebuild before it locks up the system again. I ran one test in MemTest86+, no errors. I have the System Idle configured to typical to avoid any issues with Ryzen Gen 2. I set the Syslog to write to the system flash drive so I could get an understanding of what is causing the issue, and it does seem to be disk related. However, some of the other threads I've seen on these errors suggest that it could be: 1/ bad disk 2/ bad cable 3/ bad power supply. To quote some of the log file where the error starts occurring in the last example: Jun 2 15:28:33 Tower kernel: ata6.00: exception Emask 0x0 SAct 0xbff8ffff SErr 0x0 action 0x6 frozen Jun 2 15:28:33 Tower kernel: ata6.00: failed command: READ FPDMA QUEUED Jun 2 15:28:33 Tower kernel: ata6.00: cmd 60/98:00:08:e8:d2/00:00:74:00:00/40 tag 0 ncq dma 77824 in Jun 2 15:28:33 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 2 15:28:33 Tower kernel: ata6.00: status: { DRDY } Jun 2 15:28:33 Tower kernel: ata6.00: failed command: READ FPDMA QUEUED Jun 2 15:28:33 Tower kernel: ata6.00: cmd 60/60:08:a0:e8:d2/01:00:74:00:00/40 tag 1 ncq dma 180224 in Jun 2 15:28:33 Tower kernel: res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 2 15:28:33 Tower kernel: ata6.00: status: { DRDY } Jun 2 15:28:33 Tower kernel: ata6.00: failed command: READ FPDMA QUEUED Jun 2 15:28:33 Tower kernel: ata6.00: cmd 60/f8:10:00:ea:d2/00:00:74:00:00/40 tag 2 ncq dma 126976 in Jun 2 15:28:33 Tower kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 2 15:28:33 Tower kernel: ata6.00: status: { DRDY } Jun 2 15:28:33 Tower kernel: ata6.00: failed command: READ FPDMA QUEUED Jun 2 15:28:33 Tower kernel: ata6.00: cmd 60/00:18:f8:ea:d2/01:00:74:00:00/40 tag 3 ncq dma 131072 in Jun 2 15:28:33 Tower kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 2 15:28:33 Tower kernel: ata6.00: status: { DRDY } Jun 2 15:28:33 Tower kernel: ata6.00: failed command: READ FPDMA QUEUED Jun 2 15:28:33 Tower kernel: ata6.00: cmd 60/98:20:f8:eb:d2/00:00:74:00:00/40 tag 4 ncq dma 77824 in Jun 2 15:28:33 Tower kernel: res 40/00:01:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) This continues for several minutes until it reaches this point: Jun 2 15:28:33 Tower kernel: ata6: hard resetting link Jun 2 15:28:34 Tower kernel: pcieport 0000:00:01.3: AER: Uncorrected (Fatal) error message received from 0000:00:00.0 Jun 2 15:28:34 Tower kernel: pcieport 0000:00:01.3: PCIe Bus Error: severity=Uncorrected (Fatal), type=Transaction Layer, (Receiver ID) Jun 2 15:28:34 Tower kernel: pcieport 0000:00:01.3: device [1022:1453] error status/mask=00040000/04400000 Jun 2 15:28:34 Tower kernel: pcieport 0000:00:01.3: [18] MalfTLP (First) Jun 2 15:28:34 Tower kernel: pcieport 0000:00:01.3: AER: TLP Header: 60000000 010100ff 00000001 04b80440 Jun 2 15:28:34 Tower kernel: xhci_hcd 0000:01:00.0: AER: can't recover (no error_detected callback) Jun 2 15:28:34 Tower kernel: ahci 0000:01:00.1: AER: can't recover (no error_detected callback) Jun 2 15:28:34 Tower kernel: xhci_hcd 0000:04:00.0: AER: can't recover (no error_detected callback) Jun 2 15:28:34 Tower kernel: igb 0000:06:00.0 eth0: PCIe link lost Jun 2 15:28:34 Tower kernel: bond0: (slave eth0): link status definitely down, disabling slave Jun 2 15:28:34 Tower kernel: device eth0 left promiscuous mode Jun 2 15:28:34 Tower kernel: bond0: now running without any active interface! Jun 2 15:28:35 Tower kernel: sched: RT throttling activated Jun 2 15:28:35 Tower dhcpcd[1505]: br0: carrier lost Jun 2 15:28:35 Tower kernel: pcieport 0000:02:09.0: Unable to change power state from D3hot to D0, device inaccessible Jun 2 15:28:35 Tower kernel: br0: port 1(bond0) entered disabled state Jun 2 15:28:35 Tower kernel: pcieport 0000:02:06.0: Unable to change power state from D3hot to D0, device inaccessible Jun 2 15:28:35 Tower kernel: pcieport 0000:02:00.0: Unable to change power state from D3hot to D0, device inaccessible Jun 2 15:28:35 Tower avahi-daemon[9787]: Withdrawing address record for 192.168.0.31 on br0. Jun 2 15:28:35 Tower avahi-daemon[9787]: Leaving mDNS multicast group on interface br0.IPv4 with address 192.168.0.31. Jun 2 15:28:35 Tower avahi-daemon[9787]: Interface br0.IPv4 no longer relevant for mDNS. Jun 2 15:28:35 Tower dhcpcd[1505]: br0: deleting route to 192.168.0.0/24 Jun 2 15:28:35 Tower dhcpcd[1505]: br0: deleting default route via 192.168.0.1 Jun 2 15:28:35 Tower dnsmasq[28449]: no servers found in /etc/resolv.conf, will retry Jun 2 15:28:35 Tower kernel: pcieport 0000:00:01.3: AER: Root Port link has been reset (0) Jun 2 15:28:35 Tower kernel: pcieport 0000:00:01.3: AER: device recovery failed Jun 2 15:28:35 Tower kernel: ata6: failed to resume link (SControl FFFFFFFF) Jun 2 15:28:35 Tower kernel: ata6: SATA link down (SStatus FFFFFFFF SControl FFFFFFFF) Jun 2 15:28:37 Tower ntpd[1677]: Deleting interface #1 br0, 192.168.0.31#123, interface stats: received=282, sent=282, dropped=0, active_time=4593 secs Jun 2 15:28:37 Tower ntpd[1677]: 216.239.35.12 local addr 192.168.0.31 -> <null> Jun 2 15:28:37 Tower ntpd[1677]: 216.239.35.8 local addr 192.168.0.31 -> <null> Jun 2 15:28:37 Tower ntpd[1677]: 216.239.35.4 local addr 192.168.0.31 -> <null> Jun 2 15:28:37 Tower ntpd[1677]: 216.239.35.0 local addr 192.168.0.31 -> <null> Jun 2 15:28:40 Tower kernel: ata6: hard resetting link Jun 2 15:28:40 Tower kernel: ahci 0000:01:00.1: AHCI controller unavailable! Jun 2 15:28:41 Tower kernel: ata6: failed to resume link (SControl FFFFFFFF) Jun 2 15:28:41 Tower kernel: ata6: SATA link down (SStatus FFFFFFFF SControl FFFFFFFF) Jun 2 15:28:41 Tower kernel: ata6: limiting SATA link speed to <unknown> Jun 2 15:28:47 Tower kernel: ata6: hard resetting link Jun 2 15:28:47 Tower kernel: ahci 0000:01:00.1: AHCI controller unavailable! Jun 2 15:28:48 Tower kernel: ata6: failed to resume link (SControl FFFFFFFF) Jun 2 15:28:48 Tower kernel: ata6: SATA link down (SStatus FFFFFFFF SControl FFFFFFFF) Jun 2 15:28:48 Tower kernel: ata6.00: disable device Jun 2 15:28:48 Tower kernel: ahci 0000:01:00.1: AHCI controller unavailable! Jun 2 15:28:48 Tower kernel: sd 6:0:0:0: [sdg] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=44s Jun 2 15:28:48 Tower kernel: sd 6:0:0:0: [sdg] tag#0 Sense Key : 0x2 [current] Jun 2 15:28:48 Tower kernel: sd 6:0:0:0: [sdg] tag#0 ASC=0x4 ASCQ=0x21 Jun 2 15:28:48 Tower kernel: sd 6:0:0:0: [sdg] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 74 d2 e8 08 00 00 00 98 00 00 Jun 2 15:28:48 Tower kernel: I/O error, dev sdg, sector 1959979016 op 0x0:(READ) flags 0x0 phys_seg 19 prio class 2 Jun 2 15:28:48 Tower kernel: md: disk1 read error, sector=1959978952 Jun 2 15:28:48 Tower kernel: md: disk1 read error, sector=1959978960 Jun 2 15:28:48 Tower kernel: md: disk1 read error, sector=1959978968 Jun 2 15:28:48 Tower kernel: md: disk1 read error, sector=1959978976 Jun 2 15:28:48 Tower kernel: md: disk1 read error, sector=1959978984 Jun 2 15:28:48 Tower kernel: md: disk1 read error, sector=1959978992 Jun 2 15:28:48 Tower kernel: md: disk1 read error, sector=1959979000 Jun 2 15:28:48 Tower kernel: md: disk1 read error, sector=1959979008 Jun 2 15:28:48 Tower kernel: md: disk1 read error, sector=1959979016 Jun 2 15:28:48 Tower kernel: md: disk1 read error, sector=1959979024 Jun 2 15:28:48 Tower kernel: md: disk1 read error, sector=1959979032 Jun 2 15:28:48 Tower kernel: md: disk1 read error, sector=1959979040 Jun 2 15:28:48 Tower kernel: md: disk1 read error, sector=1959979048 Jun 2 15:28:48 Tower kernel: md: disk1 read error, sector=1959979056 Jun 2 15:28:48 Tower kernel: md: disk1 read error, sector=1959979064 Jun 2 15:28:48 Tower kernel: md: disk1 read error, sector=1959979072 Jun 2 15:28:48 Tower kernel: md: disk1 read error, sector=1959979080 Jun 2 15:28:48 Tower kernel: md: disk1 read error, sector=1959979088 Jun 2 15:28:48 Tower kernel: md: disk1 read error, sector=1959979096 Jun 2 15:28:48 Tower kernel: sd 6:0:0:0: [sdg] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=44s Jun 2 15:28:48 Tower kernel: sd 6:0:0:0: [sdg] tag#1 Sense Key : 0x2 [current] Jun 2 15:28:48 Tower kernel: sd 6:0:0:0: [sdg] tag#1 ASC=0x4 ASCQ=0x21 Jun 2 15:28:48 Tower kernel: sd 6:0:0:0: [sdg] tag#1 CDB: opcode=0x88 88 00 00 00 00 00 74 d2 e8 a0 00 00 01 60 00 00 Jun 2 15:28:48 Tower kernel: I/O error, dev sdg, sector 1959979168 op 0x0:(READ) flags 0x0 phys_seg 44 prio class 2 This then continues onwards with Disk1 read error sector=nnnnnnnnn etc until this starts to happen: Jun 2 15:28:48 Tower kernel: sd 6:0:0:0: [sdg] Synchronizing SCSI cache Jun 2 15:28:48 Tower kernel: sd 6:0:0:0: [sdg] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK Jun 2 15:29:11 Tower kernel: ata4.00: exception Emask 0x52 SAct 0x7f02ffff SErr 0xffffffff action 0xe frozen Jun 2 15:29:11 Tower kernel: ata4: SError: { RecovData RecovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch } Jun 2 15:29:11 Tower kernel: ata4.00: failed command: WRITE FPDMA QUEUED Jun 2 15:29:11 Tower kernel: ata4.00: cmd 61/20:00:a0:cc:04/00:00:00:00:00/40 tag 0 ncq dma 16384 out Jun 2 15:29:11 Tower kernel: res 40/00:00:01:01:80/00:00:00:00:00/00 Emask 0x56 (ATA bus error) This repeats for a while until it starts to give the same ataN error for more disks Jun 2 15:29:17 Tower kernel: ahci 0000:01:00.1: AHCI controller unavailable! Jun 2 15:29:18 Tower kernel: ata5.00: exception Emask 0x52 SAct 0xfe00 SErr 0xffffffff action 0xe frozen Jun 2 15:29:18 Tower kernel: ata5: SError: { RecovData RecovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch } Jun 2 15:29:18 Tower kernel: ata5.00: failed command: READ FPDMA QUEUED Jun 2 15:29:18 Tower kernel: ata5.00: cmd 60/40:48:c0:fa:d2/05:00:74:00:00/40 tag 9 ncq dma 688128 in Jun 2 15:29:18 Tower kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x56 (ATA bus error) Jun 2 15:29:18 Tower kernel: ata5.00: status: { DRDY } Jun 2 15:29:18 Tower kernel: ata5: hard resetting link Jun 2 15:29:18 Tower kernel: ahci 0000:01:00.1: AHCI controller unavailable! Jun 2 15:29:18 Tower kernel: ata3.00: exception Emask 0x52 SAct 0x70f0 SErr 0xffffffff action 0xe frozen Jun 2 15:29:18 Tower kernel: ata3: SError: { RecovData RecovComm UnrecovData Persist Proto HostInt PHYRdyChg PHYInt CommWake 10B8B Dispar BadCRC Handshk LinkSeq TrStaTrns UnrecFIS DevExch } Jun 2 15:29:18 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED Jun 2 15:29:18 Tower kernel: ata3.00: cmd 60/40:20:c0:fa:d2/05:00:74:00:00/40 tag 4 ncq dma 688128 in Jun 2 15:29:18 Tower kernel: res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x56 (ATA bus error) Jun 2 15:29:18 Tower kernel: ata3.00: status: { DRDY } It gets to this place, and then starts to throw disk read errors on 0, 4, then adds 2, 1, 3 as well un 2 15:29:40 Tower kernel: I/O error, dev sde, sector 315200 op 0x1:(WRITE) flags 0x1800 phys_seg 4 prio class 2 Jun 2 15:29:40 Tower kernel: BTRFS error (device sde1): bdev /dev/sde1 errs: wr 10, rd 0, flush 0, corrupt 0, gen 0 Jun 2 15:29:40 Tower kernel: ata4: EH complete Jun 2 15:29:40 Tower kernel: ata4.00: detaching (SCSI 4:0:0:0) Jun 2 15:29:40 Tower kernel: BTRFS: error (device sde1) in btrfs_commit_transaction:2494: errno=-5 IO failure (Error while writing out transaction) Jun 2 15:29:40 Tower kernel: BTRFS info (device sde1: state E): forced readonly Jun 2 15:29:40 Tower kernel: BTRFS warning (device sde1: state E): Skipping commit of aborted transaction. Jun 2 15:29:40 Tower kernel: BTRFS: error (device sde1: state EA) in cleanup_transaction:1992: errno=-5 IO failure Jun 2 15:29:40 Tower kernel: sd 4:0:0:0: [sde] Synchronizing SCSI cache Jun 2 15:29:40 Tower kernel: sd 4:0:0:0: [sde] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK Jun 2 15:29:40 Tower kernel: ata2: failed to resume link (SControl FFFFFFFF) Jun 2 15:29:40 Tower kernel: ata2: SATA link down (SStatus FFFFFFFF SControl FFFFFFFF) Jun 2 15:29:40 Tower kernel: ata2: limiting SATA link speed to <unknown> Jun 2 15:29:45 Tower kernel: ata2: hard resetting link Jun 2 15:29:45 Tower kernel: ahci 0000:01:00.1: AHCI controller unavailable! Jun 2 15:29:45 Tower kernel: ata3: failed to resume link (SControl FFFFFFFF) Jun 2 15:29:45 Tower kernel: ata3: SATA link down (SStatus FFFFFFFF SControl FFFFFFFF) Jun 2 15:29:45 Tower kernel: ata3: limiting SATA link speed to <unknown> Jun 2 15:29:51 Tower kernel: ata3: hard resetting link Jun 2 15:29:51 Tower kernel: ahci 0000:01:00.1: AHCI controller unavailable! Jun 2 15:29:51 Tower kernel: ata5: failed to resume link (SControl FFFFFFFF) Jun 2 15:29:51 Tower kernel: ata5: SATA link down (SStatus FFFFFFFF SControl FFFFFFFF) Jun 2 15:29:51 Tower kernel: ata5: limiting SATA link speed to <unknown> Jun 2 15:29:52 Tower kernel: loop: Write error at byte offset 16150528, length 4096. Jun 2 15:29:52 Tower kernel: loop: Write error at byte offset 16154624, length 4096. Jun 2 15:29:52 Tower kernel: blk_print_req_error: 26 callbacks suppressed Jun 2 15:29:52 Tower kernel: I/O error, dev loop2, sector 31544 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Jun 2 15:29:52 Tower kernel: btrfs_dev_stat_inc_and_print: 14 callbacks suppressed Jun 2 15:29:52 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0 Jun 2 15:29:52 Tower kernel: I/O error, dev loop2, sector 31552 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 2 Jun 2 15:29:52 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 2, rd 0, flush 0, corrupt 0, gen 0 Jun 2 15:29:56 Tower kernel: ata5: hard resetting link Jun 2 15:29:56 Tower kernel: ahci 0000:01:00.1: AHCI controller unavailable! Jun 2 15:29:57 Tower kernel: loop: Write error at byte offset 16150528, length 4096. Jun 2 15:29:57 Tower kernel: I/O error, dev loop2, sector 31544 op 0x1:(WRITE) flags 0x100000 phys_seg 2 prio class 2 Jun 2 15:29:57 Tower kernel: BTRFS error (device loop2): bdev /dev/loop2 errs: wr 3, rd 0, flush 0, corrupt 0, gen 0 Jun 2 15:29:57 Tower kernel: ata2: failed to resume link (SControl FFFFFFFF) Jun 2 15:29:57 Tower kernel: ata2: SATA link down (SStatus FFFFFFFF SControl FFFFFFFF) Jun 2 15:29:57 Tower kernel: ata2.00: disable device Jun 2 15:29:57 Tower kernel: ahci 0000:01:00.1: AHCI controller unavailable! Jun 2 15:29:57 Tower kernel: ata3: failed to resume link (SControl FFFFFFFF) Jun 2 15:29:57 Tower kernel: ata3: SATA link down (SStatus FFFFFFFF SControl FFFFFFFF) Jun 2 15:29:57 Tower kernel: ata3.00: disable device Jun 2 15:29:57 Tower kernel: scsi_io_completion_action: 14 callbacks suppressed Jun 2 15:29:57 Tower kernel: sd 2:0:0:0: [sdc] tag#12 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=69s Jun 2 15:29:57 Tower kernel: sd 2:0:0:0: [sdc] tag#12 Sense Key : 0x5 [current] Jun 2 15:29:57 Tower kernel: sd 2:0:0:0: [sdc] tag#12 ASC=0x21 ASCQ=0x4 Jun 2 15:29:57 Tower kernel: sd 2:0:0:0: [sdc] tag#12 CDB: opcode=0x88 88 00 00 00 00 00 74 d2 fa c0 00 00 05 40 00 00 Jun 2 15:29:57 Tower kernel: I/O error, dev sdc, sector 1959983808 op 0x0:(READ) flags 0x0 phys_seg 168 prio class 2 Jun 2 15:29:57 Tower kernel: ahci 0000:01:00.1: AHCI controller unavailable! Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983744 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983752 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983760 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983768 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983776 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983784 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983792 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983800 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983808 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983816 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983824 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983832 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983840 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983848 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983856 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983864 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983872 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983880 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983888 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983896 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983904 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983912 Jun 2 15:29:57 Tower kernel: sd 3:0:0:0: [sdd] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=69s Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983920 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983928 Jun 2 15:29:57 Tower kernel: sd 3:0:0:0: [sdd] tag#4 Sense Key : 0x5 [current] Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983936 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983944 Jun 2 15:29:57 Tower kernel: sd 3:0:0:0: [sdd] tag#4 ASC=0x21 ASCQ=0x4 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983952 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983960 Jun 2 15:29:57 Tower kernel: sd 3:0:0:0: [sdd] tag#4 CDB: opcode=0x88 88 00 00 00 00 00 74 d2 fa c0 00 00 05 40 00 00 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983968 Jun 2 15:29:57 Tower kernel: I/O error, dev sdd, sector 1959983808 op 0x0:(READ) flags 0x0 phys_seg 168 prio class 2 Jun 2 15:29:57 Tower kernel: md: disk0 read error, sector=1959983976 Any ideas of what I can do with this to solve it? tower-diagnostics-20240602-1650.zip