Have UnRaid 6.2.14 running with 1 Parity and 5 Disk Array. The build is around 5 years old, never had any issues. 

 

Just now tried copying a 100GB file over network to UnRaid and noticed it got stuck at 10%.

 

Checked the logs and saw Warnings and Errors, could someone please help me make sense of these and what steps I should take to resolve (Diagnostics are attached below).

 

Greatly appreciate your help!

 

Feb 21 23:11:44 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x40c0000f SErr 0x0 action 0x6 frozen
Feb 21 23:11:44 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED
Feb 21 23:11:44 Tower kernel: ata3.00: cmd 60/10:00:20:9e:48/01:00:bc:00:00/40 tag 0 ncq dma 139264 in
Feb 21 23:11:44 Tower kernel:         res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Feb 21 23:11:44 Tower kernel: ata3.00: status: { DRDY }
Feb 21 23:11:44 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED
Feb 21 23:11:44 Tower kernel: ata3.00: cmd 60/40:08:30:9f:48/05:00:bc:00:00/40 tag 1 ncq dma 688128 in
Feb 21 23:11:44 Tower kernel:         res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Feb 21 23:11:44 Tower kernel: ata3.00: status: { DRDY }
Feb 21 23:11:44 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED
Feb 21 23:11:44 Tower kernel: ata3.00: cmd 60/40:10:70:a4:48/05:00:bc:00:00/40 tag 2 ncq dma 688128 in
Feb 21 23:11:44 Tower kernel:         res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Feb 21 23:11:44 Tower kernel: ata3.00: status: { DRDY }
Feb 21 23:11:44 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED
Feb 21 23:11:44 Tower kernel: ata3.00: cmd 60/40:18:b0:a9:48/05:00:bc:00:00/40 tag 3 ncq dma 688128 in
Feb 21 23:11:44 Tower kernel:         res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Feb 21 23:11:44 Tower kernel: ata3.00: status: { DRDY }
Feb 21 23:11:44 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED
Feb 21 23:11:44 Tower kernel: ata3.00: cmd 60/40:b0:70:92:48/05:00:bc:00:00/40 tag 22 ncq dma 688128 in
Feb 21 23:11:44 Tower kernel:         res 40/00:01:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Feb 21 23:11:44 Tower kernel: ata3.00: status: { DRDY }
Feb 21 23:11:44 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED
Feb 21 23:11:44 Tower kernel: ata3.00: cmd 60/40:b8:b0:97:48/05:00:bc:00:00/40 tag 23 ncq dma 688128 in
Feb 21 23:11:44 Tower kernel:         res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Feb 21 23:11:44 Tower kernel: ata3.00: status: { DRDY }
Feb 21 23:11:44 Tower kernel: ata3.00: failed command: READ FPDMA QUEUED
Feb 21 23:11:44 Tower kernel: ata3.00: cmd 60/30:f0:f0:9c:48/01:00:bc:00:00/40 tag 30 ncq dma 155648 in
Feb 21 23:11:44 Tower kernel:         res 40/00:00:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout)
Feb 21 23:11:44 Tower kernel: ata3.00: status: { DRDY }
Feb 21 23:11:44 Tower kernel: ata3: hard resetting link
Feb 21 23:11:47 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 21 23:11:52 Tower kernel: ata3.00: qc timeout after 5000 msecs (cmd 0xec)
Feb 21 23:11:52 Tower kernel: ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
Feb 21 23:11:52 Tower kernel: ata3.00: revalidation failed (errno=-5)
Feb 21 23:11:52 Tower kernel: ata3: hard resetting link
Feb 21 23:11:52 Tower kernel: ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 21 23:11:52 Tower kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT2._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-332)
Feb 21 23:11:52 Tower kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT2._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Feb 21 23:11:52 Tower kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.PRT2._GTF.DSSP], AE_NOT_FOUND (20220331/psargs-332)
Feb 21 23:11:52 Tower kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.PRT2._GTF due to previous error (AE_NOT_FOUND) (20220331/psparse-529)
Feb 21 23:11:52 Tower kernel: ata3.00: configured for UDMA/133
Feb 21 23:11:52 Tower kernel: ata3: EH complete

 

tower-diagnostics-20250221-2329.zip

Edited February 22, 20251 yr by AVP

Check/replace cables for disk2 and retest, both power and SATA.

On 2/22/2025 at 2:47 AM, JorgeB said:

Check/replace cables for disk2 and retest, both power and SATA.

Thank you. Will give that a try.