unraid 4.5.6

 

A drive failed in my array, following these instructions I've finished the 7th step:

"Tick the "I'm sure" checkbox, and press "Start will bring the array on-line, start Data-Rebuild, and then expand the file system.""

 

Instead of proceeding onto 'hefty disk activity' unraid's status is now "Stopped. New parity disk installed." the drive ball changed to red saying "Start will bring the array on-line and start Parity-Sync." (w/ a checkbox)

 

The failed disk was NOT my parity drive. Is it safe to proceed with 'start'?

 

hmmm I just captured my (huge) syslog and there's lots of errors...how should I proceed?

 

Thanks.

syslog_part1.txt

syslog_part2.txt

According to this, it was disk10 that was replaced:

Nov 22 08:06:08 Tower kernel: md: unRAID driver 0.95.4 installed

Nov 22 08:06:08 Tower kernel: md: import disk0: [8,96] (sdg) WDC WD20EADS-00R WD-WCAVY1847460 offset: 63 size: 1953514552

Nov 22 08:06:08 Tower kernel: md: import disk1: [8,128] (sdi) WDC WD20EADS-00R WD-WCAVY1849757 offset: 63 size: 1953514552

Nov 22 08:06:08 Tower kernel: md: import disk2: [8,112] (sdh) WDC WD20EADS-55R WD-WCAVY1357993 offset: 63 size: 1953514552

Nov 22 08:06:08 Tower kernel: md: import disk3: [8,144] (sdj) WDC WD20EADS-55R WD-WCAVY1358065 offset: 63 size: 1953514552

Nov 22 08:06:08 Tower kernel: md: import disk4: [8,160] (sdk) WDC WD20EADS-00R WD-WCAVY0339491 offset: 63 size: 1953514552

Nov 22 08:06:08 Tower kernel: md: import disk5: [8,176] (sdl) WDC WD20EADS-00R WD-WCAVY0327739 offset: 63 size: 1953514552

Nov 22 08:06:08 Tower kernel: md: import disk6: [8,16] (sdb) WDC WD20EARS-00M WD-WMAZ20386495 offset: 63 size: 1953514552

Nov 22 08:06:08 Tower kernel: md: import disk7: [8,32] (sdc) WDC WD20EARS-00M WD-WMAZ20407802 offset: 63 size: 1953514552

Nov 22 08:06:08 Tower kernel: md: import disk8: [8,64] (sde) WDC WD20EARS-00J WD-WCAYY0246515 offset: 63 size: 1953514552

Nov 22 08:06:08 Tower kernel: md: import disk9: [8,48] (sdd) WDC WD20EARS-00J WD-WCAYY0171110 offset: 63 size: 1953514552

Nov 22 08:06:08 Tower kernel: md: import disk10: [8,80] (sdf) WDC WD20EARS-00M WD-WMAZA0716731 offset: 63 size: 1953514552

Nov 22 08:06:08 Tower kernel: md: disk10 replaced

 

Then, here is where I think you assigned it to the array.  The MBR was written (or rather, attempted to be written. I think it failed)

Nov 22 08:07:45 Tower kernel: ata5: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00

Nov 22 08:07:45 Tower kernel: ata5: status=0x41 { DriveReady Error }

Nov 22 08:07:45 Tower emhttp: ckmbr: read: Input/output error

Nov 22 08:07:45 Tower emhttp: writing mbr on disk 10 (/dev/sdf)

Nov 22 08:07:45 Tower kernel: ata5: error=0x04 { DriveStatusError }

Nov 22 08:07:45 Tower kernel: ata5: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00

Nov 22 08:07:45 Tower kernel: ata5: status=0x41 { DriveReady Error }

Nov 22 08:07:45 Tower kernel: ata5: error=0x04 { DriveStatusError }

Nov 22 08:07:45 Tower kernel: ata5: translated ATA stat/err 0x41/04 to SCSI SK/ASC/ASCQ 0xb/00/00

Nov 22 08:07:45 Tower kernel: ata5: status=0x41 { DriveReady Error }

Nov 22 08:07:45 Tower kernel: ata5: error=0x04 { DriveStatusError }

Nov 22 08:07:45 Tower kernel: sd 1:0:4:0: [sdf] Result: hostbyte=0x00 driverbyte=0x08

Nov 22 08:07:45 Tower kernel: sd 1:0:4:0: [sdf] Sense Key : 0xb [current] [descriptor]

Nov 22 08:07:45 Tower kernel: Descriptor sense data with sense descriptors (in hex):

Nov 22 08:07:45 Tower kernel:        72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00

Nov 22 08:07:45 Tower kernel:        00 00 00 00

Nov 22 08:07:45 Tower kernel: sd 1:0:4:0: [sdf] ASC=0x0 ASCQ=0x0

Nov 22 08:07:45 Tower kernel: sd 1:0:4:0: [sdf] CDB: cdb[0]=0x28: 28 00 00 00 00 00 00 00 20 00

Nov 22 08:07:45 Tower kernel: end_request: I/O error, dev sdf, sector 0

 

To me, it appears as if the replacement drive is not responding.

I'd power down check the cabling to it (most likely to be loose) and power up once more and see if the message changes.

 

Joe L.

Thanks Joe, I appreciate that you're always here to help everyone

 

I played with the cables, no difference. I took the drive out of the cage and connected power/sata directly, no difference. Changed the sata cable & port, no difference.

 

So I took the replacement drive and connected it to my workstation and SMART was reporting one 'pending sector' (C5) I guess that's why unraid reacting strangely

From what I understand I have to read or write to that sector for it to either be reallocated or not and thus be usable in unraid so I'm doing disk checks/benchmarks hoping to fix it.

Just an update, I couldn't get that one sector to reallocate no matter how much I wrote to the disk. I returned it and bought a new one, data rebuild is in progress now!