Joe L. Posted November 10, 2010 Share Posted November 10, 2010 I just precleared a new drive. Can anyone take a look at this please? Seems to be normal to me but i just want to make sure before add the disk to the array. Syslog Attached. Thanks in advance!! Looks real good. Quote Link to comment
joshpond Posted November 11, 2010 Share Posted November 11, 2010 hi all, Just a quick question with a drive I've just finished preclearing. I've precleared a few other disks that all came back looking fin from what I can tell but this one was different. It's telling me a SMART command failed. What does all this mean? thanks Josh =========================================================================== = 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: 29C, Elapsed Time: 21:06:48 ============================================================================ == == 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 18,28c18,97 < Error SMART Status command failed < Please get assistance from http://smartmontools.sourceforge.net/ < Register values returned from SMART Status command are: < ST =0x40 < ERR=0x00 < NS =0x0c < SC =0x80 < CL =0x7a < CH =0xa8 < SEL=0x40 < A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. --- > === START OF READ SMART DATA SECTION === > SMART overall-health self-assessment test result: PASSED > > General SMART Values: > Offline data collection status: (0x00) Offline data collection activity > was never started. > Auto Offline Data Collection: Disabled. > Self-test execution status: ( 0) The previous self-test routine completed > without error or no self-test has ever > been run. > Total time to complete Offline > data collection: (19176) seconds. > Offline data collection > capabilities: (0x7b) SMART execute Offline immediate. > Auto Offline data collection on/off support. > Suspend Offline collection upon new > command. > Offline surface scan supported. > Self-test supported. > Conveyance Self-test supported. > Selective Self-test supported. > SMART capabilities: (0x0003) Saves SMART data before entering > power-saving mode. > Supports SMART auto save timer. > Error logging capability: (0x01) Error logging supported. > General Purpose Logging supported. > Short self-test routine > recommended polling time: ( 2) minutes. > Extended self-test routine > recommended polling time: ( 255) minutes. > Conveyance self-test routine > recommended polling time: ( 33) minutes. > SCT capabilities: (0x003f) SCT Status supported. > SCT Feature Control supported. > SCT Data Table supported. > > 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 0x000f 100 100 051 Pre-fail Always - 0 > 3 Spin_Up_Time 0x0007 063 063 011 Pre-fail Always - 11790 > 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 32 > 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 > 7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0 > 8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 0 > 10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0 > 11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 0 > 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 32 > 13 Read_Soft_Error_Rate 0x000e 100 100 000 Old_age Always - 0 > 183 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 > 184 Unknown_Attribute 0x0033 100 100 000 Pre-fail Always - 0 > 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 > 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 > 190 Airflow_Temperature_Cel 0x0022 071 067 000 Old_age Always - 29 (Lifetime Min/Max 28/33) > 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always > 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 > 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 > 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 > 199 UDMA_CRC_Error_Count 0x003e 253 253 000 Old_age Always - 0 > 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0 > 201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always - 0 > > SMART Error Log Version: 1 > No Errors Logged > > SMART Self-test log structure revision number 1 > No self-tests have been logged. [To run self-tests, use: smartctl -t] > > > SMART Selective self-test log data structure revision number 1 > SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS > 1 0 0 Not_testing > 2 0 0 Not_testing > 3 0 0 Not_testing > 4 0 0 Not_testing > 5 0 0 Not_testing > Selective self-test flags (0x0): > After scanning selected spans, do NOT read-scan remainder of disk. > If Selective self-test is pending on power-up, resume after 0 minute delay. > ============================================================================ root@Tower:/boot/preclear_disk# Quote Link to comment
JustinAiken Posted November 11, 2010 Share Posted November 11, 2010 ============================================================================ == == 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 19,20c19,20 < Offline data collection status: (0x80) Offline data collection activity < was never started. --- > Offline data collection status: (0x84) Offline data collection activity > was suspended by an interrupting command 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 - 24 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 25 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 ============================================================================ Quote Link to comment
Joe L. Posted November 11, 2010 Share Posted November 11, 2010 hi all, Just a quick question with a drive I've just finished preclearing. I've precleared a few other disks that all came back looking fin from what I can tell but this one was different. It's telling me a SMART command failed. What does all this mean? Your guess is as good as mine. It seems to indicate the first smart test failed. Perhaps SMART reporting was not enabled on the drive, or it was not initialized as expected.... Or it could be one that SMART is unable to address in some conditions. I'd try a quick test with preclear_disk.sh -t /dev/sdh command to be sure the pre-clear actually completed. Quote Link to comment
Dephcon Posted November 12, 2010 Share Posted November 12, 2010 Hello! This is my first pre-clear ever so i was just wondering if i need to be concerned or re-run it or whatever. ============================================================================ 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 - 18 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 19 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 ============================================================================ Thanks! Quote Link to comment
dgaschk Posted November 12, 2010 Share Posted November 12, 2010 Looks good. Doesn't get much better than that. Quote Link to comment
Dephcon Posted November 12, 2010 Share Posted November 12, 2010 I dont suppose there's an explanation somewhere about what all the numbers mean? Quote Link to comment
Joe L. Posted November 12, 2010 Share Posted November 12, 2010 I dont suppose there's an explanation somewhere about what all the numbers mean? Look here: http://en.wikipedia.org/wiki/S.M.A.R.T. Quote Link to comment
dgaschk Posted November 12, 2010 Share Posted November 12, 2010 Column headers are: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Look at the "VALUE WORST THRESH" values. As long as VALUE is above THRESH your OK. Quote Link to comment
Dephcon Posted November 12, 2010 Share Posted November 12, 2010 Column headers are: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Look at the "VALUE WORST THRESH" values. As long as VALUE is above THRESH your OK. Most helpful. Thank you. I'm going to add the headers to the script output. Quote Link to comment
jdmcrae Posted November 13, 2010 Share Posted November 13, 2010 Just spent the past week preclearing six 2TB drives. Not sure if the results are good or not, but one of the drives took forever to finish.....about 3-4 time longer than the others. Do my results look ok? Thanks, jeff preclear.results.txt Quote Link to comment
eroz Posted November 13, 2010 Share Posted November 13, 2010 Just spent the past week preclearing six 2TB drives. Not sure if the results are good or not, but one of the drives took forever to finish.....about 3-4 time longer than the others. Do my results look ok? Thanks, jeff I noticed they are all EARS drives. Did you place the jumper on pins 7 & 8? Should normally take about 30-40 hours to preclear a 2TB drive. Were all 6 drives pre-clearing at the same time? Quote Link to comment
jdmcrae Posted November 13, 2010 Share Posted November 13, 2010 I noticed they are all EARS drives. Did you place the jumper on pins 7 & 8? Should normally take about 30-40 hours to preclear a 2TB drive. Were all 6 drives pre-clearing at the same time? Yes, all drives have jumpers on pins 7 & 8. I started 4 drives preclearing at same time including the slow one (sdb). After the first two completed, I started up the next two. Never had more than 4 running at same time. Drive sdd was precleared twice because I forgot to save the results the first time. Quote Link to comment
jdmcrae Posted November 13, 2010 Share Posted November 13, 2010 I ran the disk speed test and all drives except sdb were above 100 MB/s. Drive sdb was 25 MB/s...ran the test again and it was 1.24 MB/s! I decided to switch this drive to a slot where one of the higher performing drives was and also replaced the jumper and it gave 90 MB/s and the drive that I moved into sdb old slot was still pretty high at 107 MB/s. Strange...still not sure if it's safe to build the array?? Perhaps the problem was a bad connection with the jumper?? Despite the speed anomalies, do my preclear results look ok? I built the 15 Drive Budget Box listed here http://lime-technology.com/forum/index.php?topic=7998.0 my latest speed test results are below... /dev/sdb: Timing cached reads: 3556 MB in 2.00 seconds = 1778.70 MB/sec Timing buffered disk reads: 324 MB in 3.01 seconds = 107.66 MB/sec /dev/sdc: Timing cached reads: 3572 MB in 2.00 seconds = 1786.67 MB/sec Timing buffered disk reads: 326 MB in 3.00 seconds = 108.61 MB/sec /dev/sdd: Timing cached reads: 3558 MB in 2.00 seconds = 1779.21 MB/sec Timing buffered disk reads: 318 MB in 3.02 seconds = 105.31 MB/sec /dev/sde: Timing cached reads: 3326 MB in 2.00 seconds = 1662.72 MB/sec Timing buffered disk reads: 272 MB in 3.01 seconds = 90.43 MB/sec /dev/sdf: Timing cached reads: 3552 MB in 2.00 seconds = 1775.83 MB/sec Timing buffered disk reads: 354 MB in 3.02 seconds = 117.39 MB/sec /dev/sdg: Timing cached reads: 3564 MB in 2.00 seconds = 1782.33 MB/sec Timing buffered disk reads: 340 MB in 3.00 seconds = 113.26 MB/sec Quote Link to comment
nukhem Posted November 14, 2010 Share Posted November 14, 2010 Please have a look to my results, does the drive have any problems? =========================================================================== = unRAID server Pre-Clear disk /dev/sdb = 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: 35C, Elapsed Time: 3:03:09 ============================================================================ == == Disk /dev/sdb 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 56c56 < 7 Seek_Error_Rate 0x000f 082 060 030 Pre-fail Always - 183202342 --- > 7 Seek_Error_Rate 0x000f 082 060 030 Pre-fail Always - 184053388 61c61 < 190 Airflow_Temperature_Cel 0x0022 068 034 045 Old_age Always In_ the_past 32 (Lifetime Min/Max 28/33) --- > 190 Airflow_Temperature_Cel 0x0022 065 034 045 Old_age Always In_ the_past 35 (Lifetime Min/Max 28/40) 63,64c63,64 < 193 Load_Cycle_Count 0x0032 004 004 000 Old_age Always - 192505 < 195 Hardware_ECC_Recovered 0x001a 062 045 000 Old_age Always --- > 193 Load_Cycle_Count 0x0032 004 004 000 Old_age Always - 192507 > 195 Hardware_ECC_Recovered 0x001a 057 045 000 Old_age Always ============================================================================ Quote Link to comment
Joe L. Posted November 14, 2010 Share Posted November 14, 2010 Please have a look to my results, does the drive have any problems? No. But is this a small drive? (3 hours is a very short time, I'm suspicious unless the disk is a small one) Quote Link to comment
Lleot Posted November 14, 2010 Share Posted November 14, 2010 Not really sure what do do next, do I have a useless/almost dead drive here? Nov 12 18:53:57 Tower preclear_disk-start[4573]: smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Nov 12 18:53:57 Tower preclear_disk-start[4573]: Home page is http://smartmontools.sourceforge.net/ Nov 12 18:53:57 Tower preclear_disk-start[4573]: Nov 12 18:53:57 Tower preclear_disk-start[4573]: === START OF INFORMATION SECTION === Nov 12 18:53:57 Tower preclear_disk-start[4573]: Device Model: SAMSUNG HD154UI Nov 12 18:53:57 Tower preclear_disk-start[4573]: Serial Number: S1XWJ1KZ309758 Nov 12 18:53:57 Tower preclear_disk-start[4573]: Firmware Version: 1AG01118 Nov 12 18:53:57 Tower preclear_disk-start[4573]: User Capacity: 1,500,301,910,016 bytes Nov 12 18:53:57 Tower preclear_disk-start[4573]: Device is: In smartctl database [for details use: -P show] Nov 12 18:53:57 Tower preclear_disk-start[4573]: ATA Version is: 8 Nov 12 18:53:57 Tower preclear_disk-start[4573]: ATA Standard is: ATA-8-ACS revision 3b Nov 12 18:53:57 Tower preclear_disk-start[4573]: Local Time is: Fri Nov 12 18:53:57 2010 GMT Nov 12 18:53:57 Tower preclear_disk-start[4573]: Nov 12 18:53:57 Tower preclear_disk-start[4573]: Nov 12 18:53:57 Tower preclear_disk-start[4573]: SMART Attributes Data Structure revision number: 16 Nov 12 18:53:57 Tower preclear_disk-start[4573]: Vendor Specific SMART Attributes with Thresholds: Nov 12 18:53:57 Tower preclear_disk-start[4573]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Nov 12 18:53:57 Tower preclear_disk-start[4573]: 1 Raw_Read_Error_Rate 0x000f 099 081 051 Pre-fail Always - 463 Nov 12 18:53:57 Tower preclear_disk-start[4573]: 3 Spin_Up_Time 0x0007 064 064 011 Pre-fail Always - 11610 Nov 12 18:53:57 Tower preclear_disk-start[4573]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 120 Nov 12 18:53:57 Tower preclear_disk-start[4573]: 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 Nov 12 18:53:57 Tower preclear_disk-start[4573]: 7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0 Nov 12 18:53:57 Tower preclear_disk-start[4573]: 8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 0 Nov 12 18:53:57 Tower preclear_disk-start[4573]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 1912 Nov 12 18:53:57 Tower preclear_disk-start[4573]: 10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0 Nov 12 18:53:57 Tower preclear_disk-start[4573]: 11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 0 Nov 12 18:53:57 Tower preclear_disk-start[4573]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 120 Nov 12 18:53:57 Tower preclear_disk-start[4573]: 13 Read_Soft_Error_Rate 0x000e 099 082 000 Old_age Always - 439 Nov 12 18:53:57 Tower preclear_disk-start[4573]: 183 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 Nov 12 18:53:57 Tower preclear_disk-start[4573]: 184 Unknown_Attribute 0x0033 100 100 000 Pre-fail Always - 0 Nov 12 18:53:57 Tower preclear_disk-start[4573]: 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 712 Nov 12 18:53:57 Tower preclear_disk-start[4573]: 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 Nov 12 18:53:57 Tower preclear_disk-start[4573]: 190 Airflow_Temperature_Cel 0x0022 073 066 000 Old_age Always - 27 (Lifetime Min/Max 26/27) Nov 12 18:53:57 Tower preclear_disk-start[4573]: 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 2587 Nov 12 18:53:57 Tower preclear_disk-start[4573]: 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 Nov 12 18:53:57 Tower preclear_disk-start[4573]: 197 Current_Pending_Sector 0x0012 099 099 000 Old_age Always - 38 Nov 12 18:53:57 Tower preclear_disk-start[4573]: 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 Nov 12 18:53:57 Tower preclear_disk-start[4573]: 199 UDMA_CRC_Error_Count 0x003e 253 253 000 Old_age Always - 0 Nov 12 18:53:57 Tower preclear_disk-start[4573]: 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0 Nov 12 18:53:57 Tower preclear_disk-start[4573]: 201 Soft_Read_Error_Rate 0x000a 253 253 000 Old_age Always - 0 Nov 12 18:53:57 Tower preclear_disk-start[4573]: Nov 12 18:53:57 Tower preclear_disk-start[4573]: SMART Error Log Version: 1 Nov 12 18:53:57 Tower preclear_disk-start[4573]: No Errors Logged Nov 12 18:53:57 Tower preclear_disk-start[4573]: Nov 12 18:53:57 Tower preclear_disk-start[4573]: SMART Self-test log structure revision number 1 Nov 12 18:53:57 Tower preclear_disk-start[4573]: No self-tests have been logged. [To run self-tests, use: smartctl -t] Nov 12 18:53:57 Tower preclear_disk-start[4573]: Nov 12 18:53:57 Tower preclear_disk-start[4573]: Nov 12 18:53:57 Tower preclear_disk-start[4573]: SMART Selective self-test log data structure revision number 1 Nov 12 18:53:57 Tower preclear_disk-start[4573]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Nov 12 18:53:57 Tower preclear_disk-start[4573]: 1 0 0 Not_testing Nov 12 18:53:57 Tower preclear_disk-start[4573]: 2 0 0 Not_testing Nov 12 18:53:57 Tower preclear_disk-start[4573]: 3 0 0 Not_testing Nov 12 18:53:57 Tower preclear_disk-start[4573]: 4 0 0 Not_testing Nov 12 18:53:57 Tower preclear_disk-start[4573]: 5 0 0 Not_testing Nov 12 18:53:57 Tower preclear_disk-start[4573]: Selective self-test flags (0x0): Nov 12 18:53:57 Tower preclear_disk-start[4573]: After scanning selected spans, do NOT read-scan remainder of disk. Nov 12 18:53:57 Tower preclear_disk-start[4573]: If Selective self-test is pending on power-up, resume after 0 minute delay. Nov 12 18:53:57 Tower preclear_disk-start[4573]: Nov 13 21:19:05 Tower preclear_disk-finish[9680]: smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Nov 13 21:19:05 Tower preclear_disk-finish[9680]: Home page is http://smartmontools.sourceforge.net/ Nov 13 21:19:05 Tower preclear_disk-finish[9680]: Nov 13 21:19:05 Tower preclear_disk-finish[9680]: === START OF INFORMATION SECTION === Nov 13 21:19:05 Tower preclear_disk-finish[9680]: Device Model: SAMSUNG HD154UI Nov 13 21:19:05 Tower preclear_disk-finish[9680]: Serial Number: S1XWJ1KZ309758 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: Firmware Version: 1AG01118 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: User Capacity: 1,500,301,910,016 bytes Nov 13 21:19:05 Tower preclear_disk-finish[9680]: Device is: In smartctl database [for details use: -P show] Nov 13 21:19:05 Tower preclear_disk-finish[9680]: ATA Version is: 8 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: ATA Standard is: ATA-8-ACS revision 3b Nov 13 21:19:05 Tower preclear_disk-finish[9680]: Local Time is: Sat Nov 13 21:19:05 2010 GMT Nov 13 21:19:05 Tower preclear_disk-finish[9680]: Nov 13 21:19:05 Tower preclear_disk-finish[9680]: ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. Nov 13 21:19:05 Tower preclear_disk-finish[9680]: Nov 13 21:19:05 Tower preclear_disk-finish[9680]: SMART support is: Available - device has SMART capability. Nov 13 21:19:05 Tower preclear_disk-finish[9680]: SMART support is: Enabled Nov 13 21:19:05 Tower preclear_disk-finish[9680]: Nov 13 21:19:05 Tower preclear_disk-finish[9680]: === START OF READ SMART DATA SECTION === Nov 13 21:19:05 Tower preclear_disk-finish[9680]: SMART overall-health self-assessment test result: PASSED Nov 13 21:19:05 Tower preclear_disk-finish[9680]: See vendor-specific Attribute list for marginal Attributes. Nov 13 21:19:05 Tower preclear_disk-finish[9680]: Nov 13 21:19:05 Tower preclear_disk-finish[9680]: SMART Attributes Data Structure revision number: 16 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: Vendor Specific SMART Attributes with Thresholds: Nov 13 21:19:05 Tower preclear_disk-finish[9680]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 1 Raw_Read_Error_Rate 0x000f 099 003 051 Pre-fail Always In_the_past 3138 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 3 Spin_Up_Time 0x0007 064 064 011 Pre-fail Always - 11610 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 120 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 5 Reallocated_Sector_Ct 0x0033 099 099 010 Pre-fail Always - 44 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 0 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 1938 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 0 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 120 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 13 Read_Soft_Error_Rate 0x000e 099 003 000 Old_age Always - 3052 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 183 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 184 Unknown_Attribute 0x0033 100 100 000 Pre-fail Always - 0 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 6705 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 190 Airflow_Temperature_Cel 0x0022 069 066 000 Old_age Always - 31 (Lifetime Min/Max 26/33) Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 821135454 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 196 Reallocated_Event_Count 0x0032 099 099 000 Old_age Always - 44 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 197 Current_Pending_Sector 0x0012 096 096 000 Old_age Always - 149 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 199 UDMA_CRC_Error_Count 0x003e 253 253 000 Old_age Always - 0 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 201 Soft_Read_Error_Rate 0x000a 100 048 000 Old_age Always - 0 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: Nov 13 21:19:05 Tower preclear_disk-finish[9680]: SMART Error Log Version: 1 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: No Errors Logged Nov 13 21:19:05 Tower preclear_disk-finish[9680]: Nov 13 21:19:05 Tower preclear_disk-finish[9680]: SMART Self-test log structure revision number 1 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: No self-tests have been logged. [To run self-tests, use: smartctl -t] Nov 13 21:19:05 Tower preclear_disk-finish[9680]: Nov 13 21:19:05 Tower preclear_disk-finish[9680]: Nov 13 21:19:05 Tower preclear_disk-finish[9680]: SMART Selective self-test log data structure revision number 1 Nov 13 21:19:05 Tower preclear_disk-finish[9680]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 1 0 0 Not_testing Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 2 0 0 Not_testing Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 3 0 0 Not_testing Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 4 0 0 Not_testing Nov 13 21:19:05 Tower preclear_disk-finish[9680]: 5 0 0 Not_testing Nov 13 21:19:05 Tower preclear_disk-finish[9680]: Selective self-test flags (0x0): Nov 13 21:19:05 Tower preclear_disk-finish[9680]: After scanning selected spans, do NOT read-scan remainder of disk. Nov 13 21:19:05 Tower preclear_disk-finish[9680]: If Selective self-test is pending on power-up, resume after 0 minute delay. Nov 13 21:19:05 Tower preclear_disk-finish[9680]: Nov 13 21:19:05 Tower preclear_disk-diff[9693]: ============================================================================ Nov 13 21:19:05 Tower preclear_disk-diff[9693]: == Nov 13 21:19:05 Tower preclear_disk-diff[9693]: == Disk /dev/sdb has been successfully precleared Nov 13 21:19:05 Tower preclear_disk-diff[9693]: == Nov 13 21:19:05 Tower preclear_disk-diff[9693]: == Ran 1 preclear-disk cycle Nov 13 21:19:05 Tower preclear_disk-diff[9693]: == Nov 13 21:19:05 Tower preclear_disk-diff[9693]: == Using :Read block size = 8225280 Bytes Nov 13 21:19:05 Tower preclear_disk-diff[9693]: == Last Cycle's Pre Read Time : 5:31:21 (75 MB/s) Nov 13 21:19:05 Tower preclear_disk-diff[9693]: == Last Cycle's Zeroing time : 4:50:54 (85 MB/s) Nov 13 21:19:05 Tower preclear_disk-diff[9693]: == Last Cycle's Post Read Time : 16:01:50 (25 MB/s) Nov 13 21:19:05 Tower preclear_disk-diff[9693]: == Last Cycle's Total Time : 26:25:08 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: == Nov 13 21:19:05 Tower preclear_disk-diff[9693]: == Total Elapsed Time 26:25:08 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: == Nov 13 21:19:05 Tower preclear_disk-diff[9693]: == Disk Start Temperature: 27C Nov 13 21:19:05 Tower preclear_disk-diff[9693]: == Nov 13 21:19:05 Tower preclear_disk-diff[9693]: == Current Disk Temperature: 31C, Nov 13 21:19:05 Tower preclear_disk-diff[9693]: == Nov 13 21:19:05 Tower preclear_disk-diff[9693]: ============================================================================ Nov 13 21:19:05 Tower preclear_disk-diff[9693]: S.M.A.R.T. error count differences detected after pre-clear Nov 13 21:19:05 Tower preclear_disk-diff[9693]: note, some 'raw' values may change, but not be an indication of a problem Nov 13 21:19:05 Tower preclear_disk-diff[9693]: 19a20 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: > See vendor-specific Attribute list for marginal Attributes. Nov 13 21:19:05 Tower preclear_disk-diff[9693]: 57c58 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: < 1 Raw_Read_Error_Rate 0x000f 099 081 051 Pre-fail Always - 463 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: --- Nov 13 21:19:05 Tower preclear_disk-diff[9693]: > 1 Raw_Read_Error_Rate 0x000f 099 003 051 Pre-fail Always In_the_past 3138 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: 60c61 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: < 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: --- Nov 13 21:19:05 Tower preclear_disk-diff[9693]: > 5 Reallocated_Sector_Ct 0x0033 099 099 010 Pre-fail Always - 44 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: 66c67 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: < 13 Read_Soft_Error_Rate 0x000e 099 082 000 Old_age Always - 439 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: --- Nov 13 21:19:05 Tower preclear_disk-diff[9693]: > 13 Read_Soft_Error_Rate 0x000e 099 003 000 Old_age Always - 3052 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: 69c70 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: < 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 712 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: --- Nov 13 21:19:05 Tower preclear_disk-diff[9693]: > 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 6705 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: 71c72 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: < 190 Airflow_Temperature_Cel 0x0022 073 066 000 Old_age Always - 27 (Lifetime Min/Max 26/27) Nov 13 21:19:05 Tower preclear_disk-diff[9693]: --- Nov 13 21:19:05 Tower preclear_disk-diff[9693]: > 190 Airflow_Temperature_Cel 0x0022 069 066 000 Old_age Always - 31 (Lifetime Min/Max 26/33) Nov 13 21:19:05 Tower preclear_disk-diff[9693]: 73,74c74,75 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: < 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: < 197 Current_Pending_Sector 0x0012 099 099 000 Old_age Always - 38 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: --- Nov 13 21:19:05 Tower preclear_disk-diff[9693]: > 196 Reallocated_Event_Count 0x0032 099 099 000 Old_age Always - 44 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: > 197 Current_Pending_Sector 0x0012 096 096 000 Old_age Always - 149 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: 78c79 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: < 201 Soft_Read_Error_Rate 0x000a 253 253 000 Old_age Always - 0 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: --- Nov 13 21:19:05 Tower preclear_disk-diff[9693]: > 201 Soft_Read_Error_Rate 0x000a 100 048 000 Old_age Always - 0 Nov 13 21:19:05 Tower preclear_disk-diff[9693]: ============================================================================ Quote Link to comment
SSD Posted November 15, 2010 Share Posted November 15, 2010 Not really sure what do do next, do I have a useless/almost dead drive here? Was this a brand new drive when you started? There were 38 pending sectors when the preclear began. A pending sector basically means that the drive thinks it is a bad sector but has not been able to reallocate it yet. After there preclear, you have 44 reallocated sectors (this means that the drive has marked them as bad and "mapped" spare sectors to replace them). This is a good thing, as if effectively repairs those bad sectors. But you also have 149 pending sectors. There are also 44 reallocated events (representing the 44 reallocated sectors). This is a pretty bad condition. You could run another preclear cycle on the drive. If the drive is good, you'd expect that the 149 pending sectors would get reallocated (leaving 193 reallocated sectors, and no pending sectors). If that happened, and the count didn't increase under stress, the drive would be ok. But the odds are way against that happening. When this many sectors are being reallocated it is normally downhill. Long story short - you don't want to trust your data to this drive. RMA it. Quote Link to comment
Joe L. Posted November 15, 2010 Share Posted November 15, 2010 Not really sure what do do next, do I have a useless/almost dead drive here? When I see a disk with a lot of sectors pending re-allocation after a pre-clear it indicates the sectors were un-readable in the post-clear read. (If identified in the pre-read, they should have been re-allocated when written with zeros) The other possibility is a poorly regulated power supply, causing read errors. Or, drive electronics sensitive to noise on the power supply lines. Right now, I see a drive with a fair number of re-allocated sectors (44 ) and a lot more pending re-allocation ( 149 ) I'd run another pre-clear cycle, and if the numbers continue to increment, RMA the drive. Quote Link to comment
Lleot Posted November 17, 2010 Share Posted November 17, 2010 Thanks a lot for the prompt help guys, I've done another pre clear on the drive and it doesn't look good. However SMART still says the drive has passed so can I still RMA it? preclear_results.txt Quote Link to comment
Joe L. Posted November 17, 2010 Share Posted November 17, 2010 Thanks a lot for the prompt help guys, I've done another pre clear on the drive and it doesn't look good. I agree, it does not look good. However SMART still says the drive has passed so can I still RMA it? Yes, you can still RMA it. (and you should RMA it... it is returning many un-readable sector errors. It does not look like they'll get better with time) Joe L. Quote Link to comment
fishface Posted November 19, 2010 Share Posted November 19, 2010 After my disastrous start using WD15EARS drives, used with XP, no jumper and ran WDAlign, I now have 2 new WD20EARS drives, so just to check I'm on track with things I have posted the preclear results for 1 drive. Conditions. 1) The drive is new from WD 2) Has not been used in any system other than unRAID and preclear.sh 3) I soon as I unpacked it I placed the jumper across pins 7 & 8 4) I then ran preclear.sh smart_finish3419_results_wd20ears_1.txt preclear_results_wd20ears_1.txt Quote Link to comment
Joe L. Posted November 19, 2010 Share Posted November 19, 2010 After my disastrous start using WD15EARS drives, used with XP, no jumper and ran WDAlign, I now have 2 new WD20EARS drives, so just to check I'm on track with things I have posted the preclear results for 1 drive. Conditions. 1) The drive is new from WD 2) Has not been used in any system other than unRAID and preclear.sh 3) I soon as I unpacked it I placed the jumper across pins 7 & 8 4) I then ran preclear.sh Looks perfect. Quote Link to comment
fishface Posted November 19, 2010 Share Posted November 19, 2010 Thanks Joe...looks like I'm good to go... :) 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.