CupCak3 Posted October 18, 2010 Share Posted October 18, 2010 I've ran 4 preclears on my new Samsung 2TB F3 HD203WI. No problems except for the following errors: Oct 8 12:28:03 Tower preclear_disk-start[4799]: 1 Raw_Read_Error_Rate 0x002f 252 252 051 Pre-fail Always - 0 Oct 10 07:21:47 Tower preclear_disk-start[5998]: 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 38 Oct 12 00:20:50 Tower preclear_disk-start[30688]: 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 64 Oct 13 08:42:33 Tower preclear_disk-finish[4552]: 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 94 Oct 15 05:30:19 Tower preclear_disk-finish[14054]: 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 121 Oct 8 12:28:03 Tower preclear_disk-start[4799]: 200 Multi_Zone_Error_Rate 0x002a 252 252 000 Old_age Always - 0 Oct 10 07:21:47 Tower preclear_disk-start[5998]: 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 3 Oct 12 00:20:50 Tower preclear_disk-start[30688]: 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 4 Oct 13 08:42:33 Tower preclear_disk-finish[4552]: 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 4 Oct 15 05:30:19 Tower preclear_disk-finish[14054]: 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 5 Is it OK for me to use this drive? I'm very much concerned with the always rising Raw_Read_Error_Rate numbers. Thanks! Anyone, please? Thanks! Quote Link to comment
Joe L. Posted October 18, 2010 Share Posted October 18, 2010 All drives have raw read errors. some report them, some do not. The "normalized" value is 100, unchanged from its initialized value from the factory. The failure threshold is 51. You are in fine shape. Quote Link to comment
slarco Posted October 20, 2010 Share Posted October 20, 2010 I have one more syslog if anyone can take a look at this. I did check it for reallocated sectors and pending sectors. Seems fine to me but I been here for a short time. Thanks! syslog20-10-2010-0730.txt Quote Link to comment
Rajahal Posted October 20, 2010 Share Posted October 20, 2010 Joe: I've been wondering, is it possible to slightly modify the preclear script so that it spits out these SMART before/after comparisons with line headers above each line? For example, I think that this is easier to read: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_ FAILED RAW_VALUE < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 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 - 0 than this: < 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 Also, perhaps there's a way to color code the important stuff to make it even easier? I expect this would have to be an unMenu-only type of function. For example: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_ FAILED RAW_VALUE < 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 While you are at it, why not throw in some logic that highlights potential problems: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_ FAILED RAW_VALUE < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 62 --- > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 75 Finally, maybe the output could just get rid of all the stuff that we really don't care about, such as the Flags, normalized values, etc. Possibly some of this is useful to you and other SMART experts, but it seems to me that we could get by with just: ATTRIBUTE_NAME THRESH RAW_VALUE Raw_Read_Error_Rate 051 62 That is of course much easier to read, but maybe it omits some important values, I don't know. Let me know when you've finished all that Quote Link to comment
Joe L. Posted October 20, 2010 Share Posted October 20, 2010 Joe: I've been wondering, is it possible to slightly modify the preclear script <snip> Let me know when you've finished all that I started on it quite a long time ago... Just never got too far. Perhaps you can finish it for me... I wrote the comments already... just need to fill in the code: analyze_for_errors() { err="" if [ "$2" = "" ] then sm_err=`analyze_smart $1` else pre_err=`analyze_smart $2` post_err=`analyze_smart $1` sm_err="$pre_err $post_err" fi echo -e "$sm_err" } analyze_smart() { # First, check overall health err="" overall_state=`grep 'SMART overall-health self-assessment test result:' $1 | cut -d":" -f2` if [ "$overall_state" != "PASSED" ] then err="$err SMART overall-health status = $overall_state\n" fi # next, check for individual attributes that have failed. failed_attributes=`grep 'FAILING_NOW' $1` if [ "$failed_attributes" != "" ] then err="$err\n *** Failing Attributes *** \n$failed_attributes\n" fi # next, look for sectors pending re-allocation # look for re-allocated sectors # look for any attribute within 25% of its threshold for failure. echo -e "$err\n" } Quote Link to comment
slarco Posted October 20, 2010 Share Posted October 20, 2010 I have one more syslog if anyone can take a look at this. I did check it for reallocated sectors and pending sectors. Seems fine to me but I been here for a short time. Thanks! Hoe is good because im already moving data Quote Link to comment
Joe L. Posted October 20, 2010 Share Posted October 20, 2010 I have one more syslog if anyone can take a look at this. I did check it for reallocated sectors and pending sectors. Seems fine to me but I been here for a short time. Thanks! Hoe is good because im already moving data It is fine. The only counter that incremented was the "load-cycle" counter. And if it had NOT incremented there would have been a HUGE issue, because it would then indicate the disk heads did not move from their parked position. Enjoy your new drive. for now, at least, it is working well. (good cooling... the temp did not change from 29C at its start. You must have good fans) 04:16 Tower preclear_disk-diff[32619]: ============================================================================ Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Disk /dev/sdc has been successfully precleared Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Ran 1 preclear-disk cycle Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Using :Read block size = 8225280 Bytes Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Last Cycle's Pre Read Time : 7:34:51 (73 MB/s) Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Last Cycle's Zeroing time : 7:18:06 (76 MB/s) Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Last Cycle's Post Read Time : 14:48:50 (37 MB/s) Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Last Cycle's Total Time : 29:42:54 Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Total Elapsed Time 29:42:54 Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Disk Start Temperature: 29C Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Current Disk Temperature: 29C, Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Oct 21 04:04:16 Tower preclear_disk-diff[32619]: ============================================================================ Oct 21 04:04:16 Tower preclear_disk-diff[32619]: S.M.A.R.T. error count differences detected after pre-clear Oct 21 04:04:16 Tower preclear_disk-diff[32619]: note, some 'raw' values may change, but not be an indication of a problem Oct 21 04:04:16 Tower preclear_disk-diff[32619]: 63c63 Oct 21 04:04:16 Tower preclear_disk-diff[32619]: < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 76 Oct 21 04:04:16 Tower preclear_disk-diff[32619]: --- Oct 21 04:04:16 Tower preclear_disk-diff[32619]: > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 77 Oct 21 04:04:16 Tower preclear_disk-diff[32619]: ============================================================================ Oct 21 04:04:16 Tower preclear_disk-diff[32619]: Quote Link to comment
slarco Posted October 20, 2010 Share Posted October 20, 2010 I have one more syslog if anyone can take a look at this. I did check it for reallocated sectors and pending sectors. Seems fine to me but I been here for a short time. Thanks! Hoe is good because im already moving data It is fine. The only counter that incremented was the "load-cycle" counter. And if it had NOT incremented there would have been a HUGE issue, because it would then indicate the disk heads did not move from their parked position. Enjoy your new drive. for now, at least, it is working well. (good cooling... the temp did not change from 29C at its start. You must have good fans) 04:16 Tower preclear_disk-diff[32619]: ============================================================================ Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Disk /dev/sdc has been successfully precleared Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Ran 1 preclear-disk cycle Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Using :Read block size = 8225280 Bytes Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Last Cycle's Pre Read Time : 7:34:51 (73 MB/s) Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Last Cycle's Zeroing time : 7:18:06 (76 MB/s) Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Last Cycle's Post Read Time : 14:48:50 (37 MB/s) Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Last Cycle's Total Time : 29:42:54 Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Total Elapsed Time 29:42:54 Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Disk Start Temperature: 29C Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Current Disk Temperature: 29C, Oct 21 04:04:16 Tower preclear_disk-diff[32619]: == Oct 21 04:04:16 Tower preclear_disk-diff[32619]: ============================================================================ Oct 21 04:04:16 Tower preclear_disk-diff[32619]: S.M.A.R.T. error count differences detected after pre-clear Oct 21 04:04:16 Tower preclear_disk-diff[32619]: note, some 'raw' values may change, but not be an indication of a problem Oct 21 04:04:16 Tower preclear_disk-diff[32619]: 63c63 Oct 21 04:04:16 Tower preclear_disk-diff[32619]: < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 76 Oct 21 04:04:16 Tower preclear_disk-diff[32619]: --- Oct 21 04:04:16 Tower preclear_disk-diff[32619]: > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 77 Oct 21 04:04:16 Tower preclear_disk-diff[32619]: ============================================================================ Oct 21 04:04:16 Tower preclear_disk-diff[32619]: Thanks Joe for taking the time to review the Logs. I have 2 Enermax 120mm + 2 Enermax 80mm fans Quote Link to comment
Joe L. Posted October 20, 2010 Share Posted October 20, 2010 That might explain why they stayed cool. Quote Link to comment
Rajahal Posted October 20, 2010 Share Posted October 20, 2010 code that I don't understand I would love to Joe, but I'm no programmer. I studied a bit of VB.net back in college for a psych class, but that's about the extent of my knowledge. I don't even know what language that is. How about just the first part about adding the headers in between each line, or just immediately before the SMART output? One of my main issues in analyzing SMART outputs is that I forget which number is the threshold, raw value, etc. Quote Link to comment
joeyke87 Posted October 21, 2010 Share Posted October 21, 2010 Finally, my first disk is done pre-clearing. Are my results any good? Can someone please look at the syslog. I have no idea whether it's good or bad. Sorry still learning... syslog-2010-29-11-disk4.txt syslog-2010-01-12-disk5.txt Quote Link to comment
mcdonagg Posted October 21, 2010 Share Posted October 21, 2010 Just finished me very long preclear of a 2tb Green EADS WD. I did 3 others befor this and they only took half the time, so I think something is up. Disk Temperature: 33C, Elapsed Time: 54:49:44 ============================================================================ == == Disk /dev/sdc1 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 < 1 Raw_Read_Error_Rate 0x002f 169 162 051 Pre-fail Always - 113260 --- > 1 Raw_Read_Error_Rate 0x002f 142 136 051 Pre-fail Always - 246824 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 65c65 < 197 Current_Pending_Sector 0x0032 200 196 000 Old_age Always - 161 --- > 197 Current_Pending_Sector 0x0032 200 196 000 Old_age Always - 15 ============================================================================ Quote Link to comment
Joe L. Posted October 21, 2010 Share Posted October 21, 2010 < 197 Current_Pending_Sector 0x0032 200 196 000 Old_age Always - 161 --- > 197 Current_Pending_Sector 0x0032 200 196 000 Old_age Always - 15 ============================================================================ Those last two line indicate there is an issue. Although the number if pending sectors is not high, there should not be any after writing the drive with zeros... That indicates that 15 were detected in the post-read phase. since we do not see any that were re-allocated, it appears as if they were re-written in place on their original sectors. I'd try one more pre-clear cycle, and if it does not progress at a normal speed, or has any re-allocated sectors or sectors pending re-allocation, RMA the drive. Quote Link to comment
SomeWhatLost Posted October 21, 2010 Share Posted October 21, 2010 while I am waiting fot my 1T & 2T drives to finish, I figured I would ask about the results of one of my 500G drives... anyway, one of my 500G drives finished and just said it was finished... I am guessing that is good... the other 500G drive pooped out 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 53c53 < 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 65536 --- > 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 0 62,63c62,63 < 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 1104 < 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 1104 --- > 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 1105 > 193 Load_Cycle_Count 0x0012 100 100 000 Old_age Always - 1105 ============================================================================ I am guessing most of that stuff is a non-issue... but I am confused about: < 1 Raw_Read_Error_Rate 0x000b 100 100 016 Pre-fail Always - 65536 whats a <1 raw read error rate? and why so many? technically I have a 3rd 500G that wont preclear... but I think I figured that one out all on my own... I am guessing the sata cable actually needs to be plugged in for preclear to work... of course that's just a wild guess... wonder why I left the cable just hanging there, off to the side... I am sure I had a good reason... I think... Quote Link to comment
mbryanr Posted October 21, 2010 Share Posted October 21, 2010 Finally, my first disk is done pre-clearing. Are my results any good? Can someone please look at the syslog. I have no idea whether it's good or bad. Sorry still learning... Joe can confirm, but it looks good. Here are (2) quick starter instructions for interpreting results http://lime-technology.com/forum/index.php?topic=2817.msg53337#msg53337 http://lime-technology.com/forum/index.php?topic=8278.msg81032#msg81032 @somewhatlost That value is a RAW value, which change frequently and are used by manufacturers. Each Attribute has a six-byte raw value (RAW_VALUE) and a one-byte normalized value (VALUE)... The format of the raw data is vendor-specific and not specified by any standard. To track disk reliability, the disk's firmware converts the raw value to a normalized value ranging from 1 to 253. If this normalized value is less than or equal to the threshold (THRESH), the Attribute is said to have failed, as indicated in the WHEN_FAILED column. The column is empty because none of these Attributes has failed. The lowest (WORST) normalized value also is shown; it is the smallest value attained since SMART was enabled on the disk. The TYPE of the Attribute indicates if Attribute failure means the device has reached the end of its design life (Old_age) or it's an impending disk failure (Pre-fail). For example, disk spin-up time (ID #3) is a prefailure Attribute. If this (or any other prefail Attribute) fails, disk failure is predicted in less than 24 hours. Reference http://xpt.sourceforge.net/techdocs/nix/disk/general/disk18-DiskTestHealthMonitoring/ar01s06.html Quote Link to comment
Joe L. Posted October 22, 2010 Share Posted October 22, 2010 All drives have raw read errors, some report them, some do not. The number you see has meaning only to the manufacturer. For that attribute you can only look at the "nomalized" value of 100. It is un-changed from its initial value of 100, and nowhere near the failure threshold of 16. If is good that your disk head loaded once. I am a tiny bit confused by the "Power-Off-Retract-Count" since I really did not expect the disk to be powered off. You might double-check your power connections. Joe L. Quote Link to comment
joeyke87 Posted October 22, 2010 Share Posted October 22, 2010 Just finished my second disk: Oct 22 13:31:27 Tower preclear_disk-diff[6462]: S.M.A.R.T. error count differences detected after pre-clear Oct 22 13:31:27 Tower preclear_disk-diff[6462]: note, some 'raw' values may change, but not be an indication of a problem Oct 22 13:31:27 Tower preclear_disk-diff[6462]: 54c54 Oct 22 13:31:27 Tower preclear_disk-diff[6462]: < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 Oct 22 13:31:27 Tower preclear_disk-diff[6462]: --- Oct 22 13:31:27 Tower preclear_disk-diff[6462]: > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 Oct 22 13:31:27 Tower preclear_disk-diff[6462]: 63c63 Oct 22 13:31:27 Tower preclear_disk-diff[6462]: < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 8 Oct 22 13:31:27 Tower preclear_disk-diff[6462]: --- Oct 22 13:31:27 Tower preclear_disk-diff[6462]: > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 12 Oct 22 13:31:27 Tower preclear_disk-diff[6462]: 67c67 Oct 22 13:31:27 Tower preclear_disk-diff[6462]: < 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 Oct 22 13:31:27 Tower preclear_disk-diff[6462]: --- Oct 22 13:31:27 Tower preclear_disk-diff[6462]: > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 After reading the links provided i'm guessing this is good right? But if the 100 current value would go below 051 it's an rma? I hope someone can clear this out for me so that i don't have to ask this anymore. Quote Link to comment
Joe L. Posted October 22, 2010 Share Posted October 22, 2010 Just finished my second disk: Oct 22 13:31:27 Tower preclear_disk-diff[6462]: S.M.A.R.T. error count differences detected after pre-clear Oct 22 13:31:27 Tower preclear_disk-diff[6462]: note, some 'raw' values may change, but not be an indication of a problem Oct 22 13:31:27 Tower preclear_disk-diff[6462]: 54c54 Oct 22 13:31:27 Tower preclear_disk-diff[6462]: < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 Oct 22 13:31:27 Tower preclear_disk-diff[6462]: --- Oct 22 13:31:27 Tower preclear_disk-diff[6462]: > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 Oct 22 13:31:27 Tower preclear_disk-diff[6462]: 63c63 Oct 22 13:31:27 Tower preclear_disk-diff[6462]: < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 8 Oct 22 13:31:27 Tower preclear_disk-diff[6462]: --- Oct 22 13:31:27 Tower preclear_disk-diff[6462]: > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 12 Oct 22 13:31:27 Tower preclear_disk-diff[6462]: 67c67 Oct 22 13:31:27 Tower preclear_disk-diff[6462]: < 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 Oct 22 13:31:27 Tower preclear_disk-diff[6462]: --- Oct 22 13:31:27 Tower preclear_disk-diff[6462]: > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 After reading the links provided i'm guessing this is good right? But if the 100 current value would go below 051 it's an rma? I hope someone can clear this out for me so that i don't have to ask this anymore. Correct except that your "current" values for all those you included are 200. (The line with a leading "<" is from the smart report prior to the pe-clear, the lines with the leading ">" are from the smart report after the pre-clear. The 100 (or 200) values are initial values set by the manufacturer. In many cases, they start at the factory with a value of 253 and change to either 100 or 200 as soon as the drive is put into service by an end-user. The value then adjusts itself over the lifetime of the drive based on its internal performance. You are correct in that any parameter where the "current" value goes below the threshold will be considered as failed. Joe L. Quote Link to comment
mbryanr Posted October 22, 2010 Share Posted October 22, 2010 Joe, I noticed the Load Cycle Count increase <pre-->post>. It got me thinking about the WD high LCC issue. I found a decent summary in the Syno forum (I have a 210j), but nothing yet in the unRAID wiki. Is it something that should be notated or a non-issue? http://lime-technology.com/forum/index.php?topic=5086.msg53803#msg53803 http://forum.synology.com/enu/viewtopic.php?f=124&t=11682#p49067 Quote Link to comment
actionfreak Posted October 23, 2010 Share Posted October 23, 2010 I just pre-cleared three WD20EARS drives and as far as I can tell everything looks OK except the increment in Load_Cycle_Count. From a previous post, this may be a hardware problem? All three of these drives are in the first row of a new Norco 4220 build. =========================================================================== = unRAID server Pre-Clear disk /dev/sdc = 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: 33C, Elapsed Time: 27:35:02 ============================================================================ == == Disk /dev/sdc 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 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 - 9 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 10 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# =========================================================================== = unRAID server Pre-Clear disk /dev/sdd = 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: 33C, Elapsed Time: 33:08:43 ============================================================================ == == Disk /dev/sdd 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 < 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 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 8 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 9 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# =========================================================================== = unRAID server Pre-Clear disk /dev/sde = 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: 33C, Elapsed Time: 32:59:13 ============================================================================ == == Disk /dev/sde 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 < 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 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 8 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 9 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# Quote Link to comment
actionfreak Posted October 23, 2010 Share Posted October 23, 2010 Regarding my above post. I read the thread again and it looks like that is normal. Quote Link to comment
Joe L. Posted October 23, 2010 Share Posted October 23, 2010 Regarding my above post. I read the thread again and it looks like that is normal. Correct. If the heads did not load it would be a bad thing indeed. Joe L. Quote Link to comment
hunter69 Posted October 24, 2010 Share Posted October 24, 2010 Sorry for the Double post (picked the wrong thread the first post) Here are the results from a drive I had in my whs. I was thinking I could use it as a cache disk. I am rather new at reading results. Should I use this drive as a cache drive? ============================================================================ Oct 24 02:36:35 Tower preclear_disk-diff[14738]: S.M.A.R.T. error count differences detected after pre-clear Oct 24 02:36:35 Tower preclear_disk-diff[14738]: note, some 'raw' values may change, but not be an indication of a problem Oct 24 02:36:35 Tower preclear_disk-diff[14738]: 54c54 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: < 1 Raw_Read_Error_Rate 0x000f 101 099 006 Pre-fail Always - 3525934 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: --- Oct 24 02:36:35 Tower preclear_disk-diff[14738]: > 1 Raw_Read_Error_Rate 0x000f 118 099 006 Pre-fail Always - 171199195 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: 58c58 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: < 7 Seek_Error_Rate 0x000f 078 060 030 Pre-fail Always - 76815635 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: --- Oct 24 02:36:35 Tower preclear_disk-diff[14738]: > 7 Seek_Error_Rate 0x000f 078 060 030 Pre-fail Always - 76912546 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: 64,66c64,66 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: < 189 High_Fly_Writes 0x003a 039 039 000 Old_age Always - 61 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: < 190 Airflow_Temperature_Cel 0x0022 072 055 045 Old_age Always - 28 (Lifetime Min/Max 23/28) Oct 24 02:36:35 Tower preclear_disk-diff[14738]: < 195 Hardware_ECC_Recovered 0x001a 029 025 000 Old_age Always Oct 24 02:36:35 Tower preclear_disk-diff[14738]: --- Oct 24 02:36:35 Tower preclear_disk-diff[14738]: > 189 High_Fly_Writes 0x003a 031 031 000 Old_age Always - 69 Oct 24 02:36:35 Tower preclear_disk-diff[14738]: > 190 Airflow_Temperature_Cel 0x0022 069 055 045 Old_age Always - 31 (Lifetime Min/Max 23/34) Oct 24 02:36:35 Tower preclear_disk-diff[14738]: > 195 Hardware_ECC_Recovered 0x001a 055 025 000 Old_age Always Oct 24 02:36:35 Tower preclear_disk-diff[14738]: Quote Link to comment
eroz Posted October 24, 2010 Share Posted October 24, 2010 Not sure what to make of it. I don't see anything jumping out. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Home page is http://smartmontools.sourceforge.net/ Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Oct 24 18:25:46 Tower preclear_disk-finish[22267]: === START OF INFORMATION SECTION === Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Device Model: SAMSUNG HD103SJ Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Serial Number: S246JD2Z915204 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Firmware Version: 1AJ10001 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: User Capacity: 1,000,204,886,016 bytes Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Device is: In smartctl database [for details use: -P show] Oct 24 18:25:46 Tower preclear_disk-finish[22267]: ATA Version is: 8 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: ATA Standard is: Not recognized. Minor revision code: 0x28 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Local Time is: Sun Oct 24 18:25:45 2010 CDT Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Oct 24 18:25:46 Tower preclear_disk-finish[22267]: ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Oct 24 18:25:46 Tower preclear_disk-finish[22267]: SMART support is: Available - device has SMART capability. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: SMART support is: Enabled Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Oct 24 18:25:46 Tower preclear_disk-finish[22267]: === START OF READ SMART DATA SECTION === Oct 24 18:25:46 Tower preclear_disk-finish[22267]: SMART overall-health self-assessment test result: PASSED Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Oct 24 18:25:46 Tower preclear_disk-finish[22267]: General SMART Values: Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Offline data collection status: (0x00)^IOffline data collection activity Oct 24 18:25:46 Tower preclear_disk-finish[22267]: ^I^I^I^I^Iwas never started. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: ^I^I^I^I^IAuto Offline Data Collection: Disabled. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Self-test execution status: ( 0)^IThe previous self-test routine completed Oct 24 18:25:46 Tower preclear_disk-finish[22267]: ^I^I^I^I^Iwithout error or no self-test has ever Oct 24 18:25:46 Tower preclear_disk-finish[22267]: ^I^I^I^I^Ibeen run. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Total time to complete Offline Oct 24 18:25:46 Tower preclear_disk-finish[22267]: data collection: ^I^I (9240) seconds. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Offline data collection Oct 24 18:25:46 Tower preclear_disk-finish[22267]: capabilities: ^I^I^I (0x5b) SMART execute Offline immediate. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: ^I^I^I^I^IAuto Offline data collection on/off support. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: ^I^I^I^I^ISuspend Offline collection upon new Oct 24 18:25:46 Tower preclear_disk-finish[22267]: ^I^I^I^I^Icommand. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: ^I^I^I^I^IOffline surface scan supported. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: ^I^I^I^I^ISelf-test supported. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: ^I^I^I^I^INo Conveyance Self-test supported. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: ^I^I^I^I^ISelective Self-test supported. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: SMART capabilities: (0x0003)^ISaves SMART data before entering Oct 24 18:25:46 Tower preclear_disk-finish[22267]: ^I^I^I^I^Ipower-saving mode. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: ^I^I^I^I^ISupports SMART auto save timer. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Error logging capability: (0x01)^IError logging supported. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: ^I^I^I^I^IGeneral Purpose Logging supported. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Short self-test routine Oct 24 18:25:46 Tower preclear_disk-finish[22267]: recommended polling time: ^I ( 2) minutes. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Extended self-test routine Oct 24 18:25:46 Tower preclear_disk-finish[22267]: recommended polling time: ^I ( 154) minutes. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: SCT capabilities: ^I (0x003f)^ISCT Status supported. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: ^I^I^I^I^ISCT Feature Control supported. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: ^I^I^I^I^ISCT Data Table supported. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Oct 24 18:25:46 Tower preclear_disk-finish[22267]: SMART Attributes Data Structure revision number: 16 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Vendor Specific SMART Attributes with Thresholds: Oct 24 18:25:46 Tower preclear_disk-finish[22267]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 14 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 3 Spin_Up_Time 0x0023 070 070 025 Pre-fail Always - 9128 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 5 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 26 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 5 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 191 G-Sense_Error_Rate 0x0022 252 252 000 Old_age Always - 0 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 70 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 5 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Oct 24 18:25:46 Tower preclear_disk-finish[22267]: SMART Error Log Version: 1 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: No Errors Logged Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Oct 24 18:25:46 Tower preclear_disk-finish[22267]: SMART Self-test log structure revision number 1 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: No self-tests have been logged. [To run self-tests, use: smartctl -t] Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Oct 24 18:25:46 Tower preclear_disk-finish[22267]: SMART Selective Self-Test Log Data Structure Revision Number (0) should be 1 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: SMART Selective self-test log data structure revision number 0 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Warning: ATA Specification requires selective self-test log data structure revision number = 1 Oct 24 18:25:46 Tower preclear_disk-finish[22267]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 1 0 0 Completed [00% left] (0-65535) Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 2 0 0 Not_testing Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 3 0 0 Not_testing Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 4 0 0 Not_testing Oct 24 18:25:46 Tower preclear_disk-finish[22267]: 5 0 0 Not_testing Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Selective self-test flags (0x0): Oct 24 18:25:46 Tower preclear_disk-finish[22267]: After scanning selected spans, do NOT read-scan remainder of disk. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: If Selective self-test is pending on power-up, resume after 0 minute delay. Oct 24 18:25:46 Tower preclear_disk-finish[22267]: Oct 24 18:25:46 Tower preclear_disk-diff[22280]: ============================================================================ Oct 24 18:25:46 Tower preclear_disk-diff[22280]: == Oct 24 18:25:46 Tower preclear_disk-diff[22280]: == Disk /dev/sdb has been successfully precleared Oct 24 18:25:46 Tower preclear_disk-diff[22280]: == Oct 24 18:25:46 Tower preclear_disk-diff[22280]: == Ran 1 preclear-disk cycle Oct 24 18:25:46 Tower preclear_disk-diff[22280]: == Oct 24 18:25:46 Tower preclear_disk-diff[22280]: == Using :Read block size = 8225280 Bytes Oct 24 18:25:46 Tower preclear_disk-diff[22280]: == Last Cycle's Pre Read Time : 2:54:55 (95 MB/s) Oct 24 18:25:46 Tower preclear_disk-diff[22280]: == Last Cycle's Zeroing time : 2:35:50 (106 MB/s) Oct 24 18:25:46 Tower preclear_disk-diff[22280]: == Last Cycle's Post Read Time : 6:22:19 (43 MB/s) Oct 24 18:25:46 Tower preclear_disk-diff[22280]: == Last Cycle's Total Time : 11:54:21 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: == Oct 24 18:25:46 Tower preclear_disk-diff[22280]: == Total Elapsed Time 11:54:21 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: == Oct 24 18:25:46 Tower preclear_disk-diff[22280]: == Disk Start Temperature: 26C Oct 24 18:25:46 Tower preclear_disk-diff[22280]: == Oct 24 18:25:46 Tower preclear_disk-diff[22280]: == Current Disk Temperature: 29C, Oct 24 18:25:46 Tower preclear_disk-diff[22280]: == Oct 24 18:25:46 Tower preclear_disk-diff[22280]: ============================================================================ Oct 24 18:25:46 Tower preclear_disk-diff[22280]: S.M.A.R.T. error count differences detected after pre-clear Oct 24 18:25:46 Tower preclear_disk-diff[22280]: note, some 'raw' values may change, but not be an indication of a problem Oct 24 18:25:46 Tower preclear_disk-diff[22280]: 18,28c18,95 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: < Error SMART Status command failed Oct 24 18:25:46 Tower preclear_disk-diff[22280]: < Please get assistance from http://smartmontools.sourceforge.net/ Oct 24 18:25:46 Tower preclear_disk-diff[22280]: < Register values returned from SMART Status command are: Oct 24 18:25:46 Tower preclear_disk-diff[22280]: < ST =0x40 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: < ERR=0x00 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: < NS =0x0c Oct 24 18:25:46 Tower preclear_disk-diff[22280]: < SC =0xa0 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: < CL =0x6d Oct 24 18:25:46 Tower preclear_disk-diff[22280]: < CH =0x70 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: < SEL=0x40 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: < A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: --- Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > === START OF READ SMART DATA SECTION === Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > SMART overall-health self-assessment test result: PASSED Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > General SMART Values: Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > Offline data collection status: (0x00)^IOffline data collection activity Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > ^I^I^I^I^Iwas never started. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > ^I^I^I^I^IAuto Offline Data Collection: Disabled. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > Self-test execution status: ( 0)^IThe previous self-test routine completed Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > ^I^I^I^I^Iwithout error or no self-test has ever Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > ^I^I^I^I^Ibeen run. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > Total time to complete Offline Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > data collection: ^I^I (9240) seconds. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > Offline data collection Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > capabilities: ^I^I^I (0x5b) SMART execute Offline immediate. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > ^I^I^I^I^IAuto Offline data collection on/off support. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > ^I^I^I^I^ISuspend Offline collection upon new Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > ^I^I^I^I^Icommand. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > ^I^I^I^I^IOffline surface scan supported. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > ^I^I^I^I^ISelf-test supported. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > ^I^I^I^I^INo Conveyance Self-test supported. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > ^I^I^I^I^ISelective Self-test supported. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > SMART capabilities: (0x0003)^ISaves SMART data before entering Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > ^I^I^I^I^Ipower-saving mode. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > ^I^I^I^I^ISupports SMART auto save timer. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > Error logging capability: (0x01)^IError logging supported. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > ^I^I^I^I^IGeneral Purpose Logging supported. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > Short self-test routine Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > recommended polling time: ^I ( 2) minutes. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > Extended self-test routine Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > recommended polling time: ^I ( 154) minutes. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > SCT capabilities: ^I (0x003f)^ISCT Status supported. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > ^I^I^I^I^ISCT Feature Control supported. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > ^I^I^I^I^ISCT Data Table supported. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > SMART Attributes Data Structure revision number: 16 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > Vendor Specific SMART Attributes with Thresholds: Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 14 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 3 Spin_Up_Time 0x0023 070 070 025 Pre-fail Always - 9128 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 5 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 5 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 191 G-Sense_Error_Rate 0x0022 252 252 000 Old_age Always - 0 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 70 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 5 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > SMART Error Log Version: 1 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > No Errors Logged Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > SMART Self-test log structure revision number 1 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > No self-tests have been logged. [To run self-tests, use: smartctl -t] Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > SMART Selective Self-Test Log Data Structure Revision Number (0) should be 1 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > SMART Selective self-test log data structure revision number 0 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > Warning: ATA Specification requires selective self-test log data structure revision number = 1 Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 1 0 0 Completed [00% left] (0-65535) Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 2 0 0 Not_testing Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 3 0 0 Not_testing Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 4 0 0 Not_testing Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > 5 0 0 Not_testing Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > Selective self-test flags (0x0): Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > After scanning selected spans, do NOT read-scan remainder of disk. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > If Selective self-test is pending on power-up, resume after 0 minute delay. Oct 24 18:25:46 Tower preclear_disk-diff[22280]: > Oct 24 18:25:46 Tower preclear_disk-diff[22280]: ============================================================================ Oct 24 18:25:46 Tower preclear_disk-diff[22280]: Quote Link to comment
Seven Posted October 29, 2010 Share Posted October 29, 2010 Looks like preclear failed on a brand new disk I purchased to keep on hand as a spare drive. I've attached all of the logfiles and output I could find.... I did not find a smart_finish report in the /tmp directory. This is a new WD20EARS drive from Newegg and I did install a jumper over pins 7/8 before attaching to my server. Any thoughts or suggestions would be appreciated. Thanks! Logs.zip Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.