A few weeks ago I started using unRaid. I was very convinced about the software so I bought an entirely new system and an unRaid plus license.

 

First of all I successfully completed a parity check, afterwards I started copying data.

 

Unfortunately I noticed some handle_stripe errors in syslog since last night.

Should I be worried and start RMA procedures?

 

Attached are the syslogs & smartctl logs for all disks.

 

Thanks alot to anyone who is willing to take a look at it.

 

Also, unmenu reports the following:

Array Status
STARTED, 5 disks in array.    Parity is Valid:.   Last parity check 5 days ago .   Parity updated  3725  times to address sync errors.

Model / Serial No. 			Temp 	Size 		Free 		Reads 		Writes 		Errors
parity 	WDC_WD20EARS-00M_WD-WCAZA1012362 	36°C 	1,953,514,552 	- 		18,012,643 	4,429,302 	0
disk1 	WDC_WD20EARS-00M_WD-WMAZA0938132 	* 	1,953,514,552 	971,474,496 	25,761,032 	2,271,281 	0
disk2 	WDC_WD20EARS-00M_WD-WMAZA0938839 	* 	1,953,514,552 	1,508,516,768 	14,527,128 	1,026,859 	0
disk3 	WDC_WD20EARS-00M_WD-WMAZA0384670 	33°C 	1,953,514,552 	1,552,148,036 	25,654,408 	916,257 	0
disk4 	WDC_WD20EARS-00M_WD-WMAZA0938772 	* 	1,953,514,552 	1,885,845,876 	32,258,194 	214,984 	128   

Syslog+SmartLogs.zip

Disk4, /dev/sdf,  WDC WD20EARS-00M WD-WMAZA0938772

 

It is timing out when queried.

Jan 21 08:09:01 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 21 08:09:01 Tower kernel: ata5.00: failed command: READ DMA EXT
Jan 21 08:09:01 Tower kernel: ata5.00: cmd 25/00:00:77:fe:66/00:04:e7:00:00/e0 tag 0 dma 524288 in
Jan 21 08:09:01 Tower kernel:          res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jan 21 08:09:01 Tower kernel: ata5.00: status: { DRDY }
Jan 21 08:09:01 Tower kernel: ata5: hard resetting link
Jan 21 08:09:02 Tower kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 21 08:09:02 Tower kernel: ata5.00: configured for UDMA/133
Jan 21 08:09:02 Tower kernel: ata5.00: device reported invalid CHS sector 0
Jan 21 08:09:02 Tower kernel: ata5: EH complete
Jan 21 08:09:32 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 21 08:09:32 Tower kernel: ata5.00: failed command: READ DMA EXT
Jan 21 08:09:32 Tower kernel: ata5.00: cmd 25/00:00:77:fe:66/00:04:e7:00:00/e0 tag 0 dma 524288 in
Jan 21 08:09:32 Tower kernel:          res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jan 21 08:09:32 Tower kernel: ata5.00: status: { DRDY }
Jan 21 08:09:32 Tower kernel: ata5: hard resetting link
Jan 21 08:09:33 Tower kernel: ata5: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jan 21 08:09:33 Tower kernel: ata5.00: configured for UDMA/133
Jan 21 08:09:33 Tower kernel: ata5.00: device reported invalid CHS sector 0
Jan 21 08:09:33 Tower kernel: ata5: EH complete
Jan 21 08:10:03 Tower kernel: ata5.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 21 08:10:03 Tower kernel: ata5.00: failed command: READ DMA EXT
Jan 21 08:10:03 Tower kernel: ata5.00: cmd 25/00:00:77:fe:66/00:04:e7:00:00/e0 tag 0 dma 524288 in
Jan 21 08:10:03 Tower kernel:          res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Jan 21 08:10:03 Tower kernel: ata5.00: status: { DRDY }

It does not show anything in its SMART report.  You could try checking the connections to it (both power and data cables)

EARS drives have been seen to mis-report their geometry, especially if the "jumper" setting was changed.  The errors are not normal.  It might be a candidate for an RMA if the cabling is secure and the errors continue.

 

 

I've put on the jumper before installing unRaid, so that couldn't be the problem.

 

I will replace the sata and power cable just to be sure and will keep an eye on the syslog.

 

Thanks Joe!