July 22, 201312 yr I'm not sure how to read SMART, so I figured I'd ask the genius-bar! ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 107 118 6 ok 13092800 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 63 63 45 near_thresh 37 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. Once I know what to watch out for, I'll be good!
July 23, 201312 yr Doesn't look bad, but what you're looking for is values that are dropping (getting worse). In your case, the raw read error rate dropped from 118 to 107. Not likely a problem ... but I'd run another pre-clear cycle and see if this line shows up again with yet-another drop. If not, all is well. If so, you may want to see if the 3rd time's the charm
July 23, 201312 yr Author Doesn't look bad, but what you're looking for is values that are dropping (getting worse). In your case, the raw read error rate dropped from 118 to 107. Not likely a problem ... but I'd run another pre-clear cycle and see if this line shows up again with yet-another drop. If not, all is well. If so, you may want to see if the 3rd time's the charm Should have mentioned, this drive reported errors during initial sync...is it time to return it to the store and get another?
July 23, 201312 yr Yes, I'd return it. I'm probably a bit paranoid, but when I get a new drive, I do ALL of the following: (a) Run Data Lifeguard's Quick Test. (b) Run Data Lifeguard's Extended Test (many hours) © Do a full zero of the drive using Data Lifeguard's Write Zeroes function (d) Repeat (a) and (b) (e) Run the UnRAID Pre-Clear script for two passes If I get ANY errors at any point in that regimen, I RMA the drive for a new one !! This can be a bit hectic when I buy multiple drives at once -- I'll often have 2 or 3 computers doing drive tests for several days
July 23, 201312 yr Author I had setup the drivers and when it was doing the parity (i had no setup reisferfs yet, since i had not done the preclearing) but it had 73 errors under devices. Here is a dump of smartctl amid the current test (second run) - seems Raw_Read_error_rate went back up, was at 107 now at 111?? This is a new drive too. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 111 100 006 Pre-fail Always - 35641088 3 Spin_Up_Time 0x0003 097 097 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 5 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 284605 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 440 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 5 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 062 061 045 Old_age Always - 38 (Min/Max 28/39) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 5 193 Load_Cycle_Count 0x0032 097 097 000 Old_age Always - 7773 194 Temperature_Celsius 0x0022 038 040 000 Old_age Always - 38 (0 25 0 0) 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 57363583205518 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 5860781983 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 24984500065 I'm running checks of the other drives. lol should just use SSDs:))
July 23, 201312 yr That is a perfectly healthy drive. ALL disks have raw read errors. Every one of them. (Just some disks do not report them) As long as the normalized value (107 - and now 111 ) is ABOVE the affiliaated failure threshold of "6" the disk is working as designed. In your case, the raw read error rate improved. (It started out at a nominal value of "100" from the factory, so you are actually doing a bit better than the normal starting value.) Enjoy your new disk.
July 23, 201312 yr Joe => How did going from 118 to 107 represent an "improvement" ?? You indicated it went from 100 to 107, which would in fact be an improvement, but the SMART report shows "old value" 118, "new value" 107. I'm sure I'm just misreading it, but if that's the case what does the "old value" column represent?
July 23, 201312 yr Joe => How did going from 118 to 107 represent an "improvement" ?? You indicated it went from 100 to 107, which would in fact be an improvement, but the SMART report shows "old value" 118, "new value" 107. I'm sure I'm just misreading it, but if that's the case what does the "old value" column represent? I was quoting from this lineHere is a dump of smartctl amid the current test (second run) - seems Raw_Read_error_rate went back up, was at 107 now at 111?? The "Old" value in the preclear report shows the value at the start of the preclear process. (from the first smart report taken) The "New" is at the end of the preclear process. I've just combined the two smart reports and list those where the normalized value changed. Joe L.
Archived
This topic is now archived and is closed to further replies.