June 22, 201610 yr It looks like my parity disk is having issues. This thing has been running unattended so long, I think I've just about forgotten what little I knew! Anyway, would like some advice before doing anything. Unraid 5.0, syslog and smart report attached. Thanks! Well it says the files are greater than 192KB and won't take them. Not sure how as the file sizes are 66KB, 32KB and 5KB. Anyway, try here: https://1drv.ms/f/s!AgqKPKE94KRrhb0rOM51uX98VY4Xgg
June 22, 201610 yr Resolving a Pending Sector The wiki is talking about a data drive but the parity drive can be dealt with in the same way, either replace or rebuild to the same drive.
June 23, 201610 yr Author So, I need to run a preclear? Does the array need to be shut down? Or does the parity disk need to be unassigned? Or can I just run it? Thanks. Sorry for the questions, just kind of scary when my data is in peril!
June 23, 201610 yr Author Never mind, I've comprehended what I was reading a little better now. I'm doing the second option under re-enable drive. It is building parity now, should be finished by morning. Thanks again!
June 23, 201610 yr You should get another SMART after and hopefully the pending will be gone, possibly changed to reallocated, which is OK as long as it isn't increasing fast.
June 23, 201610 yr Personally though, I would replace any drive with pending / reallocated sector asap.
June 23, 201610 yr Personally though, I would replace any drive with pending / reallocated sector asap. If pending goes to zero and the reallocated count is small and not increasing then its probably OK just to keep an eye on it. Reallocating is a normal function for drives.
June 24, 201610 yr Author That took a while, but it's finished rebuilding and checking parity with 0 errors. Here is smart report now: SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: 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 - 0 3 Spin_Up_Time 0x0027 177 169 021 Pre-fail Always - 8141 4 Start_Stop_Count 0x0032 094 094 000 Old_age Always - 6608 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 070 070 000 Old_age Always - 22161 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 - 13 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 11 193 Load_Cycle_Count 0x0032 179 179 000 Old_age Always - 64660 194 Temperature_Celsius 0x0022 126 119 000 Old_age Always - 26 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 3 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 Pending is now 3 instead of 5 and reallocated is still 0. Does that mean if it tries to read from one of those 3 sectors it will fail again? Why wouldn't it reallocate them? I checked and it's under warranty until October. Is this sufficient issue to return? If not, what do I need to watch for?
June 24, 201610 yr An increasing number of pending is not a good thing. Personally I would use the warranty. I have utilised warranty in the past with just 1 pending sector so I'm sure 5 is 5 times more valid.
Archived
This topic is now archived and is closed to further replies.