I'm testing Unraid for almost a month now (4 days left in trial). I've created array of 2 disks (one of them is parity). And every few days array is broken because of write errors on one of the disks.

 

I've replaced both SATA cables, I did full SMART test - no errors. What else should I try? Thanks

 

Part of the log file...

 

Feb  8 02:32:05 Unraid kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Feb  8 02:32:05 Unraid kernel: ata1.00: failed command: FLUSH CACHE EXT
Feb  8 02:32:05 Unraid kernel: ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 2
Feb  8 02:32:05 Unraid kernel: ata1.00: status: { DRDY }
Feb  8 02:32:05 Unraid kernel: ata1: hard resetting link
Feb  8 02:32:10 Unraid kernel: ata1: link is slow to respond, please be patient (ready=0)
Feb  8 02:32:15 Unraid kernel: ata1: COMRESET failed (errno=-16)
Feb  8 02:32:15 Unraid kernel: ata1: hard resetting link
Feb  8 02:32:20 Unraid kernel: ata1: link is slow to respond, please be patient (ready=0)
Feb  8 02:32:25 Unraid kernel: ata1: COMRESET failed (errno=-16)
Feb  8 02:32:25 Unraid kernel: ata1: hard resetting link
Feb  8 02:32:30 Unraid kernel: ata1: link is slow to respond, please be patient (ready=0)
Feb  8 02:33:00 Unraid kernel: ata1: COMRESET failed (errno=-16)
Feb  8 02:33:00 Unraid kernel: ata1: limiting SATA link speed to 3.0 Gbps
Feb  8 02:33:00 Unraid kernel: ata1: hard resetting link
Feb  8 02:33:05 Unraid kernel: ata1: COMRESET failed (errno=-16)
Feb  8 02:33:05 Unraid kernel: ata1: reset failed, giving up
Feb  8 02:33:05 Unraid kernel: ata1.00: disable device
Feb  8 02:33:05 Unraid kernel: ata1: EH complete
Feb  8 02:33:05 Unraid kernel: sd 1:0:0:0: [sdb] tag#16 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=117s
Feb  8 02:33:05 Unraid kernel: sd 1:0:0:0: [sdb] tag#16 CDB: opcode=0x8a 8a 00 00 00 00 01 84 ea 05 78 00 00 00 08 00 00
Feb  8 02:33:05 Unraid kernel: I/O error, dev sdb, sector 6524896632 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2
Feb  8 02:33:05 Unraid kernel: sd 1:0:0:0: [sdb] tag#17 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
Feb  8 02:33:05 Unraid kernel: sd 1:0:0:0: [sdb] tag#17 CDB: opcode=0x8a 8a 00 00 00 00 01 84 ea 05 98 00 00 00 10 00 00
Feb  8 02:33:05 Unraid kernel: I/O error, dev sdb, sector 6524896664 op 0x1:(WRITE) flags 0x0 phys_seg 2 prio class 2
Feb  8 02:33:05 Unraid kernel: sd 1:0:0:0: [sdb] tag#27 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
Feb  8 02:33:05 Unraid kernel: sd 1:0:0:0: [sdb] tag#27 CDB: opcode=0x8a 8a 00 00 00 00 01 84 ea 05 b0 00 00 00 08 00 00
Feb  8 02:33:05 Unraid kernel: I/O error, dev sdb, sector 6524896688 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 2
Feb  8 02:33:05 Unraid kernel: sd 1:0:0:0: [sdb] tag#19 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=0s
Feb  8 02:33:05 Unraid kernel: sd 1:0:0:0: [sdb] tag#19 CDB: opcode=0x8a 8a 00 00 00 00 03 80 00 00 88 00 00 00 20 00 00
Feb  8 02:33:05 Unraid kernel: I/O error, dev sdb, sector 15032385672 op 0x1:(WRITE) flags 0x0 phys_seg 4 prio class 2
Feb  8 02:33:05 Unraid kernel: sd 1:0:0:0: [sdb] tag#20 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=DRIVER_OK cmd_age=122s
Feb  8 02:33:05 Unraid kernel: sd 1:0:0:0: [sdb] tag#20 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
Feb  8 02:33:05 Unraid kernel: I/O error, dev sdb, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 2

Attach Diagnostics to your NEXT post in this thread 

@trurlThis one?

 

I've downloaded the syslog after I've found that array is broken, then I've rebooted the server and attached diagnostics.

unraid-syslog-20240208-1223.zip unraid-diagnostics-20240208-1338.zip

Parity disk is not connected. Check cables and connections, including power and splitters.

I haven't touched the cables. I just turned off and on the server and the parity disk is back online and now I'm doing the raid check.

 

I will replace the PSU, disks are directly powered from PSU. Or maybe I will use the power from motherboard. 

 

Thank you for the suggestions.