I've reused two 500GB old 2.5" drives from taken out from laptops in my unRAID server until I will get second WD RED 4TB (currently using only one as a parity drive).

 

Today, older one of the 500GB was marked with red dot. I've disabled it, checked SMART. Because I did not see any errors, based on recommendations in other topics in the forum, I double check the HDD power supply and replaced SATA cable for a new one.

 

Then I followed the disk replacement procedure (stop array, remove disk, start, stop, add disk and start again) with the same disk, because I believed it was a cabling problem. The drive had started to rebuilt, when I got the write error again.

 

Also I need to mention that I experienced one unclean shutdown today - it can be possible related to HDD fail later.

 

Relevant part from syslog:

May 31 19:58:11 unRAID kernel: ata5.00: qc timeout (cmd 0x47)
May 31 19:58:11 unRAID kernel: ata5.00: READ LOG DMA EXT failed, trying PIO
May 31 19:58:11 unRAID kernel: ata5: failed to read log page 10h (errno=-5)
May 31 19:58:11 unRAID kernel: ata5.00: exception Emask 0x1 SAct 0x400001f8 SErr 0x400001 action 0x6 frozen
May 31 19:58:11 unRAID kernel: ata5.00: irq_stat 0x40000008
May 31 19:58:11 unRAID kernel: ata5: SError: { RecovData Handshk }
May 31 19:58:11 unRAID kernel: ata5.00: failed command: WRITE FPDMA QUEUED
May 31 19:58:11 unRAID kernel: ata5.00: cmd 61/40:18:d0:77:38/05:00:3a:00:00/40 tag 3 ncq dma 688128 out
May 31 19:58:11 unRAID kernel:         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x1 (device error)
May 31 19:58:11 unRAID kernel: ata5.00: status: { DRDY }
May 31 19:58:11 unRAID kernel: ata5.00: failed command: WRITE FPDMA QUEUED
May 31 19:58:11 unRAID kernel: ata5.00: cmd 61/40:20:10:7d:38/05:00:3a:00:00/40 tag 4 ncq dma 688128 out
May 31 19:58:11 unRAID kernel:         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x1 (device error)

...

May 31 19:58:29 unRAID kernel: print_req_error: I/O error, dev sdc, sector 976775080
May 31 19:58:29 unRAID kernel: md: disk1 write error, sector=976775016
May 31 19:58:29 unRAID kernel: md: disk1 write error, sector=976775024
May 31 19:58:29 unRAID kernel: md: disk1 write error, sector=976775032
May 31 19:58:29 unRAID kernel: md: disk1 write error, sector=976775040
May 31 19:58:29 unRAID kernel: md: disk1 write error, sector=976775048
May 31 19:58:29 unRAID kernel: md: disk1 write error, sector=976775056

...

 

I'm also attaching my diagnostic files. (1743 - HDD fail, 2055 - rebuild attempt).

 

Should I replace this drive or is the problem elsewhere?

 

As I currently only experimenting with unRAID setup, I don't have any important data stored on those drives. However, I am curious what to do in such case once I will have my media library and personal data stored there.

 

 

unraid-diagnostics-20200531-2055.zip unraid-diagnostics-20200531-1743.zip

Edited June 1, 20206 yr by dotn
solved

Disk looks healthy but if you already replaced cables there could still be a problem there, make sure you also replaced/swapped the power cable, I would also swap to a different SATA port and try again if the issues continue it's likely the disk.

I replaced power cable and used different SATA port. Data rebuilt end up with the same error. So it has to be faulty disk. Thanks