Decided to upgrade a few drives in the array.  Against my better judgement I installed a drive without preclearing.  After 36 hours of data rebuilding it failed and is red balled with 288 errors.  I have 2 other drives that are in the 2nd run of preclearing on another box.  Would my best course of action to be to power down the array and replace disk2 with an identical precleared drive?

 

Unraid 4.5.4

Parity = ST31000528AS

disk1 = ST31000528AS

disk2 = ST31000528AS (replaced 500gig Seagate)

disk3 = WDC_WD5000AAKS-0

disk4 = WDC_WD5000AAKS-0

disk5 = WDC_WD5000AAKS-0

disk6 = WDC_WD5000AAKS-0

disk7 = WDC_WD5000AAKS-0

 

Nov 11 13:06:41 Tower kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov 11 13:06:41 Tower kernel: ata2.00: irq_stat 0x40000001

Nov 11 13:06:41 Tower kernel: ata2.00: failed command: WRITE DMA EXT

Nov 11 13:06:41 Tower kernel: ata2.00: cmd 35/00:a8:ef:21:93/00:03:56:00:00/e0 tag 0 dma 479232 out

Nov 11 13:06:41 Tower kernel:          res 71/04:04:91:00:32/00:00:00:00:00/e0 Emask 0x1 (device error)

Nov 11 13:06:41 Tower kernel: ata2.00: status: { DRDY DF ERR }

Nov 11 13:06:41 Tower kernel: ata2.00: error: { ABRT }

Nov 11 13:06:46 Tower kernel: ata2.00: qc timeout (cmd 0xec)

Nov 11 13:06:46 Tower kernel: ata2.00: failed to IDENTIFY (I/O error, err_mask=0x5)

Nov 11 13:06:46 Tower kernel: ata2.00: revalidation failed (errno=-5)

Nov 11 13:06:46 Tower kernel: ata2: hard resetting link

Nov 11 13:06:47 Tower kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Nov 11 13:06:47 Tower kernel: ata2.00: both IDENTIFYs aborted, assuming NODEV

Nov 11 13:06:47 Tower kernel: ata2.00: revalidation failed (errno=-2)

Nov 11 13:06:52 Tower kernel: ata2: hard resetting link

Nov 11 13:06:52 Tower kernel: ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)

Nov 11 13:06:52 Tower kernel: ata2.00: both IDENTIFYs aborted, assuming NODEV

Nov 11 13:06:52 Tower kernel: ata2.00: revalidation failed (errno=-2)

Nov 11 13:06:52 Tower kernel: ata2.00: disabled

Nov 11 13:06:52 Tower kernel: ata2: EH complete

Nov 11 13:06:52 Tower kernel: sd 2:0:0:0: [sdb] Unhandled error code

Nov 11 13:06:52 Tower kernel: sd 2:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00

Nov 11 13:06:52 Tower kernel: sd 2:0:0:0: [sdb] CDB: cdb[0]=0x2a: 2a 00 56 93 21 ef 00 03 a8 00

Nov 11 13:06:52 Tower kernel: end_request: I/O error, dev sdb, sector 1452483055

Nov 11 13:06:52 Tower kernel: sd 2:0:0:0: [sdb] Unhandled error code

Nov 11 13:06:52 Tower kernel: sd 2:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00

Nov 11 13:06:52 Tower kernel: sd 2:0:0:0: [sdb] CDB: cdb[0]=0x2a: 2a 00 56 93 25 97 00 01 78 00

Nov 11 13:06:52 Tower kernel: end_request: I/O error, dev sdb, sector 1452483991

Nov 11 13:06:52 Tower kernel: sd 2:0:0:0: [sdb] Unhandled error code

Nov 11 13:06:52 Tower kernel: sd 2:0:0:0: [sdb] Result: hostbyte=0x04 driverbyte=0x00

Nov 11 13:06:52 Tower kernel: sd 2:0:0:0: [sdb] CDB: cdb[0]=0x2a: 2a 00 56 93 27 0f 00 03 e0 00

Nov 11 13:06:52 Tower kernel: end_request: I/O error, dev sdb, sector 1452484367

Nov 11 13:06:52 Tower kernel: md: disk2 write error

Nov 11 13:06:52 Tower kernel: handle_stripe write error: 1452482992/2, count: 1

Nov 11 13:06:52 Tower kernel: md: disk2 write error

<small snip>

Nov 11 13:06:52 Tower kernel: handle_stripe write error: 1452485232/2, count: 1

Nov 11 13:06:52 Tower kernel: md: disk2 write error

Nov 11 13:06:52 Tower kernel: handle_stripe write error: 1452485240/2, count: 1

Nov 11 13:06:52 Tower kernel: md: disk2 write error

Nov 11 13:06:52 Tower kernel: handle_stripe write error: 1452485248/2, count: 1

Nov 11 13:06:52 Tower kernel: md: disk2 write error

Nov 11 13:06:52 Tower kernel: handle_stripe write error: 1452485256/2, count: 1

Nov 11 13:06:52 Tower kernel: md: disk2 write error

Nov 11 13:06:52 Tower kernel: handle_stripe write error: 1452485264/2, count: 1

Nov 11 13:06:52 Tower kernel: md: disk2 write error

Nov 11 13:06:52 Tower kernel: handle_stripe write error: 1452485272/2, count: 1

Nov 11 13:06:52 Tower kernel: md: disk2 write error

Nov 11 13:06:52 Tower kernel: handle_stripe write error: 1452485280/2, count: 1

Nov 11 13:06:52 Tower kernel: md: disk2 write error

Nov 11 13:06:52 Tower kernel: handle_stripe write error: 1452485288/2, count: 1

Nov 11 13:06:52 Tower kernel: md: md_do_sync: got signal, exit...

Nov 11 13:06:53 Tower kernel: md: recovery thread sync completion status: -4

Nov 11 13:06:53 Tower kernel: md: recovery thread woken up ...

Nov 11 13:06:53 Tower kernel: md: recovery thread has nothing to resync

Nov 11 13:42:05 Tower emhttp: disk_temperature: ioctl (smart_enable): Input/output error

could be anything, including a loose cable to the drive.

 

POwer down, try re-seating the cable, then go from there.

(You can replace the drive, of course, if you have a spare)

Double checked all cabling prior to powering it up first time.  (been burned before!).

 

I will replace drive with a known good precleared drive.

 

I will run your fancy preclear on the questionable drive.

 

Sound like a plan?

 

 

Double checked all cabling prior to powering it up first time.  (been burned before!).

 

I will replace drive with a known good precleared drive.

 

I will run your fancy preclear on the questionable drive.

 

Sound like a plan?

 

 

To start, Just get a smart report on the questionable drive.

Smartctl couldn't find the drive.  So I stopped the array and rebooted.  Drive is now MIA (UnRAID shows it as "Not Installed").  I will verify connections when I get home, but I think that sucker is dead!

Smartctl couldn't find the drive.  So I stopped the array and rebooted.  Drive is now MIA (UnRAID shows it as "Not Installed").  I will verify connections when I get home, but I think that sucker is dead!

Sounds like it.  But re-seat the connections when you have it powered down anyways.

Got it spun up in another box.  BIOS reports smart failure immediately.  This sucker is going back.

 

Thanks from the community Joe.