March 13, 201115 yr I see this in syslog. Nothing eventful before or after except spindowns. What should I do? Replace the drive? Backup data? Syslog Mar 12 21:34:01 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 12 21:34:01 Tower kernel: ata4.00: irq_stat 0x40000001 Mar 12 21:34:01 Tower kernel: ata4.00: failed command: READ DMA EXT Mar 12 21:34:01 Tower kernel: ata4.00: cmd 25/00:08:8f:00:a8/00:00:ab:00:00/e0 tag 0 dma 4096 in Mar 12 21:34:01 Tower kernel: res 51/40:00:8f:00:a8/00:00:ab:00:00/e0 Emask 0x9 (media error) Mar 12 21:34:01 Tower kernel: ata4.00: status: { DRDY ERR } Mar 12 21:34:01 Tower kernel: ata4.00: error: { UNC } Mar 12 21:34:01 Tower kernel: ata4.00: configured for UDMA/133 Mar 12 21:34:01 Tower kernel: ata4: EH complete Mar 12 21:34:04 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Mar 12 21:34:04 Tower kernel: ata4.00: irq_stat 0x40000001 Mar 12 21:34:04 Tower kernel: ata4.00: failed command: READ DMA EXT Mar 12 21:34:04 Tower kernel: ata4.00: cmd 25/00:08:8f:00:a8/00:00:ab:00:00/e0 tag 0 dma 4096 in Mar 12 21:34:04 Tower kernel: res 51/40:00:8f:00:a8/00:00:ab:00:00/e0 Emask 0x9 (media error) Mar 12 21:34:04 Tower kernel: ata4.00: status: { DRDY ERR } Mar 12 21:34:04 Tower kernel: ata4.00: error: { UNC } Mar 12 21:34:04 Tower kernel: ata4.00: configured for UDMA/133 Mar 12 21:34:04 Tower kernel: ata4: EH complete Smart report ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 47 3 Spin_Up_Time 0x0027 199 180 021 Pre-fail Always - 5050 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 803 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 091 091 000 Old_age Always - 6597 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 95 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 31 193 Load_Cycle_Count 0x0032 195 195 000 Old_age Always - 163 194 Temperature_Celsius 0x0022 122 115 000 Old_age Always - 28 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 199 199 000 Old_age Always - 369 198 Offline_Uncorrectable 0x0030 200 199 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 190 000 Old_age Offline - 6 If they are pending how to get them remapped? Do I attempt this? Parity check was done nine days ago. http://lime-technology.com/forum/index.php?topic=4068.msg91731#msg91731 [Edit] just noticed this procedure is for parity only. This drive is disk1. Is there a way to force these sectors to be remapped? PB [sOLVED] New drive precleared, and disk1 rebuilt
March 14, 201115 yr I see this in syslog. Nothing eventful before or after except spindowns. What should I do? Replace the drive? Probably Backup data?If you have space capacity elsewhere, yes. The only way those sectors will get re-mapped is if they are written. You can possibly Stop the array un-assign the bad drive start the array with it un-assigned stop the array once more re-assign the bad drive. Start the array once more. unRAID will re-construct the contents onto itself, hopefully the drive will have enough spare sectors to re-allocate those pending re-allocation. (Most drives have several thousand spare sectors) Bad news is, you probably need a new drive. Odds are you will constantly see more and more un-readable sectors. Joe L.
March 14, 201115 yr Author Thanks Joe. I've got one on order. Rebuilding the existing one as I reply. It got me thinking, I have one slot left. Should it hold a warm spare not assigned to the array ready to replace a drive? How many really do this? Or is it just about having all the available drives for data?
March 14, 201115 yr Thanks Joe. I've got one on order. Rebuilding the existing one as I reply. It got me thinking, I have one slot left. Should it hold a warm spare not assigned to the array ready to replace a drive? How many really do this? Or is it just about having all the available drives for data? Many use the "warm spare" as their cache drive. If you don't need to use all the disks it is an alternative.
March 14, 201115 yr Author Rebuild finished. What happened? Current_Pending_Sector went to 0 (expected). I thought the Reallocated_Event_Count or Reallocated_Sector_Ct would increase. What happened to the Multi_Zone_Error_Rate it went from 6 to 0 ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 47 3 Spin_Up_Time 0x0027 199 180 021 Pre-fail Always - 5041 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 806 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 091 091 000 Old_age Always - 6612 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 96 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 31 193 Load_Cycle_Count 0x0032 195 195 000 Old_age Always - 165 194 Temperature_Celsius 0x0022 124 115 000 Old_age Always - 26 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 199 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 199 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 190 000 Old_age Offline - 0 PB
March 14, 201115 yr Rebuild finished. What happened? Current_Pending_Sector went to 0 (expected). I thought the Reallocated_Event_Count or Reallocated_Sector_Ct would increase. What happened to the Multi_Zone_Error_Rate it went from 6 to 0 ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 47 3 Spin_Up_Time 0x0027 199 180 021 Pre-fail Always - 5041 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 806 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 091 091 000 Old_age Always - 6612 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 96 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 31 193 Load_Cycle_Count 0x0032 195 195 000 Old_age Always - 165 194 Temperature_Celsius 0x0022 124 115 000 Old_age Always - 26 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 199 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 199 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 190 000 Old_age Offline - 0 PB Are you sure it is the same drive?
March 14, 201115 yr Author Are you sure it is the same drive? Yes, it's the only drive I have with Raw_Read_Error_Rate = 47. Even MyMain no longer has it flagged. All drives looks good except this Raw_Read_Error_Rate and the udma_crc_error_count on another drive you helped me through about two weeks ago by rerouting the cable away from the power.
March 14, 201115 yr That has happened (pending sectors just clear) before but I don't recall any reports with that many bad sectors. I suppose the problem could go away if the drive was having trouble reading for some reason (cabling or power supply) and then the problem was fixed. I would keep a close eye on that drive for a while before fully trusting it. Peter
March 15, 201115 yr Author Well, while at work I had another failure in syslog. I'm glad a new drive will arrive tomorrow. I won't go into details, the failure was against "ata4", looking through the syslog ata4 is the following drive: Mar 14 05:54:54 Tower kernel: ata4.00: ATA-8: WDC WD15EARS-00Z5B1, 80.00A80, max UDMA/133 Majority of my drives are this model. My question is... Is ata4 and host4 the same? This is the only drive by SN with SMART failures on. Mar 14 05:54:54 Tower emhttp: pci-0000:00:11.0-scsi-1:0:0:0 host4 (sde) WDC_WD15EARS-00Z5B1_WD-WMAVU3009283 I just want to check with the members I am interpreting this correct. PB
March 16, 201115 yr Mar 14 05:54:54 Tower emhttp: pci-0000:00:11.0-scsi-0:0:0:0 host3 (sdd) WDC_WD20EARS-00MVWB0_WD-WCAZA1209586 Mar 14 05:54:54 Tower emhttp: pci-0000:00:11.0-scsi-1:0:0:0 host4 (sde) WDC_WD15EARS-00Z5B1_WD-WMAVU3009283 Mar 14 05:54:54 Tower emhttp: pci-0000:00:11.0-scsi-2:0:0:0 host5 (sdf) WDC_WD15EARS-00Z5B1_WD-WMAVU1454433 Mar 14 05:54:54 Tower emhttp: pci-0000:00:11.0-scsi-3:0:0:0 host6 (sdg) WDC_WD15EARS-00Z5B1_WD-WMAVU1266799 Mar 14 05:54:54 Tower emhttp: pci-0000:00:11.0-scsi-4:0:0:0 host7 (sdh) WDC_WD10EARS-00Y5B1_WD-WCAV55278988 Mar 14 05:54:54 Tower emhttp: pci-0000:00:11.0-scsi-5:0:0:0 host8 (sdi) WDC_WD15EARS-00Z5B1_WD-WMAVU3255402 Mar 14 05:54:54 Tower emhttp: pci-0000:02:00.0-scsi-0:0:0:0 host1 (sda) WDC_WD10EARS-00Y5B1_WD-WCAV56078708 Mar 14 05:54:54 Tower emhttp: pci-0000:02:00.0-scsi-1:0:0:0 host2 (sdb) WDC_WD20EARS-22MVWB0_WD-WCAZA3835619 Mar 14 05:54:54 Tower emhttp: shcmd (2): modprobe -rw md-mod 2>&1 | logger Mar 14 05:54:54 Tower emhttp: shcmd (3): modprobe md-mod super=/boot/config/super.dat slots=8,48,8,64,8,80,8,96,8,112,8,128,8,16,8,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0 2>&1 | logger Mar 14 05:54:54 Tower kernel: xor: automatically using best checksumming function: pIII_sse Mar 14 05:54:54 Tower kernel: pIII_sse : 11035.200 MB/sec Mar 14 05:54:54 Tower kernel: xor: using function: pIII_sse (11035.200 MB/sec) Mar 14 05:54:54 Tower kernel: md: unRAID driver 1.1.0 installed Mar 14 05:54:54 Tower kernel: md: import disk0: [8,48] (sdd) WDC WD20EARS-00M WD-WCAZA1209586 offset: 63 size: 1953514552 Mar 14 05:54:54 Tower kernel: md: import disk1: [8,64] (sde) WDC WD15EARS-00Z WD-WMAVU3009283 offset: 63 size: 1465138552 Mar 14 05:54:54 Tower kernel: md: import disk2: [8,80] (sdf) WDC WD15EARS-00Z WD-WMAVU1454433 offset: 63 size: 1465138552 Mar 14 05:54:54 Tower kernel: md: import disk3: [8,96] (sdg) WDC WD15EARS-00Z WD-WMAVU1266799 offset: 63 size: 1465138552 Mar 14 05:54:54 Tower kernel: md: import disk4: [8,112] (sdh) WDC WD10EARS-00Y WD-WCAV55278988 offset: 63 size: 976762552 Mar 14 05:54:54 Tower kernel: md: import disk5: [8,128] (sdi) WDC WD15EARS-00Z WD-WMAVU3255402 offset: 63 size: 1465138552 Mar 14 05:54:54 Tower kernel: md: import disk6: [8,16] (sdb) WDC WD20EARS-22M WD-WCAZA3835619 offset: 63 size: 1953514552 Mar 14 05:54:54 Tower emhttp: Spinning up all drives... host4 is disk1. disk4 is host7. The ata and host numbers are unimportant. The sdX and disk numbers are needed for unRAID configuration and potential maintenance.
March 16, 201115 yr Author Sorry for not being clear. Since my syslog failure was against ata4 Mar 12 21:34:01 Tower kernel: [b]ata4[/b].00: error: { UNC } I was inquiring the relationship with host4 and ata4 since lines with ata4 have no reference to drive id (s/n), it references the model and I have a few of these models in my system. Only a host4 line reference the sdx and s/n. Just trying to understand the association between ata4 and host4. Basically, if I see an ata# error how do I trace it to the s/n or sdx? Is is via host#? Thanks in advance for the help and education, I'm a newbe wanting to learn. PB "Give a man a fish and you feed him for a day. Teach a man to fish and you feed him for a lifetime."
March 16, 201115 yr I was inquiring the relationship with host4 and ata4 since lines with ata4 have no reference to drive id (s/n), it references the model and I have a few of these models in my system. Yes. Both host4 and ata4 reference the same disk. It is also the same as 'sde'.
Archived
This topic is now archived and is closed to further replies.