October 19, 201015 yr Author Here's the result of my preclear. Not sure if it's good as I have no idea how to read all this. S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 19,20c19,20 < Offline data collection status: (0x80) Offline data collection activi < was never started. --- > Offline data collection status: (0x84) Offline data collection activi > was suspended by an interrupting comma from host. 54c54 < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 --- > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 58c58 < 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 --- > 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 17 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 18 67c67 < 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 --- > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 ============================================================================ root@Tower:/boot#
October 19, 201015 yr Here's the result of my preclear. Not sure if it's good as I have no idea how to read all this. S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 19,20c19,20 < Offline data collection status: (0x80) Offline data collection activi < was never started. --- > Offline data collection status: (0x84) Offline data collection activi > was suspended by an interrupting comma from host. 54c54 < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 --- > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 58c58 < 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 --- > 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 17 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 18 67c67 < 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 --- > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 ============================================================================ root@Tower:/boot# The "worst" values of 253 are the factory values indicating the drive has never been used. Thos values are changed to either 100 or 200 once the drive gets some use and then those "starting" values go downward from there as errors are detected over the disk's lifetime. Your disk just shows those initial values being set. It is perfectly fine. When the "normalized value" drops below the failure threshold the SMART firmware will consider the disk as failed. Joe L.
October 20, 201015 yr Author Just ran a preclear on an older drive I popped into my array. Got the following back but not sure how to read this. I read the thread on the preclear results but still at a loss to be honest. I'll have to go through some more threads I guess. =========================================================================== = unRAID server Pre-Clear disk /dev/sdh = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 43C, Elapsed Time: 8:17:11 ============================================================================ == == Disk /dev/sdh has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 54c54 < 7 Seek_Error_Rate 0x000f 085 060 030 Pre-fail Always - 337533835 --- > 7 Seek_Error_Rate 0x000f 085 060 030 Pre-fail Always - 340208795 59,60c59,60 < 190 Airflow_Temperature_Cel 0x0022 060 048 045 Old_age Always - 40 (Lifetime Min/Max 34/40) < 195 Hardware_ECC_Recovered 0x001a 065 050 000 Old_age Always --- > 190 Airflow_Temperature_Cel 0x0022 057 048 045 Old_age Always - 43 (Lifetime Min/Max 34/45) > 195 Hardware_ECC_Recovered 0x001a 064 050 000 Old_age Always ============================================================================ root@Tower:/boot#
October 20, 201015 yr Author Also got this result on my other drive S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 58c58 < 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 --- > 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 ============================================================================ root@Tower:/boot#
October 20, 201015 yr Also got this result on my other drive S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 58c58 < 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 --- > 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 ============================================================================ root@Tower:/boot# Neither of your drives have anything abnormal at all. It is just the initial factory value (253) being replaced by an initial value of 100.
October 20, 201015 yr Author Hi Jo, THanks, Is there any way you can give me a brief overview in layman's terms that explains what I need to look for in the Worst Value Threshhold columns? I hate having to always ask. I did read some of the other threads but having a hard time understanding. For ex if I see < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 --- > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 Am I looking where for when the 100 or 200 is lower than the 51?
October 20, 201015 yr I'll take a stab at this. Joe, please correct me if I'm wrong. < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 --- > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 In this case, you will look at the Raw value (0, the value that is generally kicked down to the next line) and compare it with the threshold (51). If the Raw value starts approaching the threshold, then you can start to worry, or at least take precautions with that drive. In this case you are perfectly fine. Also, what size is that first drive? 8 hours seems pretty fast for a preclear, unless it is a smaller drive. 43C is also a bit hot, but not hot enough to worry about. Preclear exercises the drive, so it is normal for a drive to run a bit hotter during it. As long as the drive runs around 40C or cooler during normal operation, there's nothing to worry about.
October 20, 201015 yr The "worst" values of 253 are the factory values indicating the drive has never been used. Those values are changed to either 100 or 200 once the drive gets some use and then those "starting" values go downward from there as errors are detected over the disk's lifetime. Your disk just shows those initial values being set. It is perfectly fine. When the "normalized value" drops below the failure threshold the SMART firmware will consider the disk as failed. Joe L. More references http://smartlinux.sourceforge.net/smart/attributes.php http://www.ariolic.com/activesmart/smart-attributes/ http://www.ntfs.com/disk-monitor-smart-attributes.htm
October 20, 201015 yr Hi Jo, THanks, Is there any way you can give me a brief overview in layman's terms that explains what I need to look for in the Worst Value Threshhold columns? I hate having to always ask. I did read some of the other threads but having a hard time understanding. For ex if I see < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 --- > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 Am I looking where for when the 100 or 200 is lower than the 51? The line with the leading "<" was the smart report before the pre-clear, the line with the leading ">" is the same line after the pre-clear. The current normalized value is 200. The worst value ever is also 200 (in other words, it has not changed from when it was initialized to 200.) The failure threshold is 51. When the current value gets below the failure threshold the manufacturer will consider that parameter to have failed its smart test. > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always The "raw" values at the ends of the lines have little meaning to us except for temperature, re-allocated sectors, sectors-pending-re-allocation, load-cycles. they frequently change and have no effect on the "normalized" value. As an example I can see one of your drives had a lifetime max temperature of 45C and is currently at 43C. That is a bit high for most of us, as we like to keep temperatures below 40C.
Archived
This topic is now archived and is closed to further replies.