Hey,

 

Had some rain/lightning last night and the surge protector triggered and turned off my unraid machine.  On reboot it went through its parity check and found 18 erros, but am also seeing some error entries in syslog, so can someone more experienced tell me what it means exactly.

 

Also, smart report shows the following:

 

Disk 3

» current_pending_sector=2

» multi_zone_error_rate=484

 

Disk 6

» load_cycle_count=158590

» multi_zone_error_rate=3

 

Disk 8

» load_cycle_count=158213

» multi_zone_error_rate=1

 

Syslog attached, using version 4.7.

 

Thanks for your help.

 

Take Care

syslog-2012-05-22.txt

ata1 seems to have a SATA cable problem.

 

May 22 10:12:24 Tower kernel: ata12.00: ATA-8: WDC WD15EADS-00S2B0, 04.05G04, max UDMA/133
May 22 10:12:24 Tower kernel: ata12.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA

May 22 10:19:26 Tower kernel: ata1: exception Emask 0x10 SAct 0x0 SErr 0x180000 action 0x6 frozen
May 22 10:19:26 Tower kernel: ata1: edma_err_cause=00000020 pp_flags=00000000, SError=00180000
May 22 10:19:26 Tower kernel: ata1: SError: { 10B8B Dispar }

Hey,

 

Thanks for the reply, your first except shows ata12, not ata1 (or is that ata1 2.00)?

 

I will replace the cable and see if it fixes the issue, but how can I tell which drive ata1 is?  Does ata1 = sda?  Is there an easy way to find the disk which relates to ata1?

 

Thanks

You're right. Here is the correct reference

 May 22 10:12:24 Tower kernel: ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
May 22 10:12:24 Tower kernel: ata1.00: ATA-8: WDC WD15EADS-00S2B0, 04.05G04, max UDMA/133
May 22 10:12:24 Tower kernel: ata1.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32)

 

It could be sda. Syslogs indicate no direct mapping from ataX to sdY. Post SMART reports.

Smart reports for all drives attached.

 

Thanks

smart.txt

The SMART report shows nothing wrong with either EADS drive. Check the connections.

Hey,

 

Well I changed my sata cable and even the port but the log still shows those errors. 

 

Ran a parity check and it completed fine with it finding 1 error.  I can access all files/folders fine on disk8 (which seems to be ata4 now in syslog).

 

The disks are connected through a 5-in-3 enclosure, so maybe the connector for the enclosure is the culprit but I didn't have a chance to test with it directly connected to the mobo/pcie card, will try that next and see.

 

Syslog attached.

 

Take Care

syslog-2012-05-23.zip

Hey,

 

Well I guess it wasn't a bad or loose cable as I replaced the drive and the errors went away.

 

Thanks for the help.

 

Take Care