September 22, 201015 yr Hi. I Just finished running the preclear script in 2 of my drives and i was wondering if anyone can give me some help in interpretate the syslogs. I read in this post about similar Syslogs and the Raw & UDMA errors and seems to e normal, but i just rather double check before start moving data. Syslogs attached Thanks in advance! Everything looks normal. Enjoy your new drives. Yay...!!!!!!
September 23, 201015 yr drive #4 (a 7200 1.5TB Seagate) has just finished preclearing....from what I gather, it seems ok, but is anyone interested in having a quick look? I hope it's complete, it sort of seems like there's something missing..but I may be wrong. The telnet session reports the drive has cleared. Thanks in advance! Sep 22 14:56:44 Tower kernel: sdd: sdd1 Sep 22 14:58:34 Tower preclear_disk-start[17262]: smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Sep 22 14:58:34 Tower preclear_disk-start[17262]: Home page is http://smartmontools.sourceforge.net/ Sep 22 14:58:34 Tower preclear_disk-start[17262]: Sep 22 14:58:34 Tower preclear_disk-start[17262]: === START OF INFORMATION SECTION === Sep 22 14:58:34 Tower preclear_disk-start[17262]: Device Model: ST31500341AS Sep 22 14:58:34 Tower preclear_disk-start[17262]: Serial Number: 9VS141QF Sep 22 14:58:34 Tower preclear_disk-start[17262]: Firmware Version: CC1H Sep 22 14:58:34 Tower preclear_disk-start[17262]: User Capacity: 1,500,301,910,016 bytes Sep 22 14:58:34 Tower preclear_disk-start[17262]: Device is: Not in smartctl database [for details use: -P showall] Sep 22 14:58:34 Tower preclear_disk-start[17262]: ATA Version is: 8 Sep 22 14:58:34 Tower preclear_disk-start[17262]: ATA Standard is: ATA-8-ACS revision 4 Sep 22 14:58:34 Tower preclear_disk-start[17262]: Local Time is: Wed Sep 22 14:58:34 2010 CEST Sep 22 14:58:34 Tower preclear_disk-start[17262]: SMART support is: Available - device has SMART capability. Sep 22 14:58:34 Tower preclear_disk-start[17262]: SMART support is: Enabled Sep 22 14:58:34 Tower preclear_disk-start[17262]: Sep 22 14:58:34 Tower preclear_disk-start[17262]: === START OF READ SMART DATA SECTION === Sep 22 14:58:34 Tower preclear_disk-start[17262]: SMART overall-health self-assessment test result: PASSED Sep 22 14:58:34 Tower preclear_disk-start[17262]: Sep 22 14:58:34 Tower preclear_disk-start[17262]: General SMART Values: Sep 22 14:58:34 Tower preclear_disk-start[17262]: Offline data collection status: (0x82)^IOffline data collection activity Sep 22 14:58:34 Tower preclear_disk-start[17262]: ^I^I^I^I^Iwas completed without error. Sep 22 14:58:34 Tower preclear_disk-start[17262]: ^I^I^I^I^IAuto Offline Data Collection: Enabled. Sep 22 14:58:34 Tower preclear_disk-start[17262]: Self-test execution status: ( 0)^IThe previous self-test routine completed Sep 22 14:58:34 Tower preclear_disk-start[17262]: ^I^I^I^I^Iwithout error or no self-test has ever Sep 22 14:58:34 Tower preclear_disk-start[17262]: ^I^I^I^I^Ibeen run. Sep 22 14:58:34 Tower preclear_disk-start[17262]: Total time to complete Offline Sep 22 14:58:34 Tower preclear_disk-start[17262]: data collection: ^I^I ( 617) seconds. Sep 22 14:58:34 Tower preclear_disk-start[17262]: Offline data collection Sep 22 14:58:34 Tower preclear_disk-start[17262]: capabilities: ^I^I^I (0x7b) SMART execute Offline immediate. Sep 22 14:58:34 Tower preclear_disk-start[17262]: ^I^I^I^I^IAuto Offline data collection on/off support. Sep 22 14:58:34 Tower preclear_disk-start[17262]: ^I^I^I^I^ISuspend Offline collection upon new Sep 22 14:58:34 Tower preclear_disk-start[17262]: ^I^I^I^I^Icommand. Sep 22 14:58:34 Tower preclear_disk-start[17262]: ^I^I^I^I^IOffline surface scan supported. Sep 22 14:58:34 Tower preclear_disk-start[17262]: ^I^I^I^I^ISelf-test supported. Sep 22 14:58:34 Tower preclear_disk-start[17262]: ^I^I^I^I^IConveyance Self-test supported. Sep 22 14:58:34 Tower preclear_disk-start[17262]: ^I^I^I^I^ISelective Self-test supported. Sep 22 14:58:34 Tower preclear_disk-start[17262]: SMART capabilities: (0x0003)^ISaves SMART data before entering Sep 22 14:58:34 Tower preclear_disk-start[17262]: ^I^I^I^I^Ipower-saving mode. Sep 22 14:58:34 Tower preclear_disk-start[17262]: ^I^I^I^I^ISupports SMART auto save timer. Sep 22 14:58:34 Tower preclear_disk-start[17262]: Error logging capability: (0x01)^IError logging supported. Sep 22 14:58:34 Tower preclear_disk-start[17262]: ^I^I^I^I^IGeneral Purpose Logging supported. Sep 22 14:58:34 Tower preclear_disk-start[17262]: Short self-test routine Sep 22 14:58:34 Tower preclear_disk-start[17262]: recommended polling time: ^I ( 1) minutes. Sep 22 14:58:34 Tower preclear_disk-start[17262]: Extended self-test routine Sep 22 14:58:34 Tower preclear_disk-start[17262]: recommended polling time: ^I ( 255) minutes. Sep 22 14:58:34 Tower preclear_disk-start[17262]: Conveyance self-test routine Sep 22 14:58:34 Tower preclear_disk-start[17262]: recommended polling time: ^I ( 2) minutes. Sep 22 14:58:34 Tower preclear_disk-start[17262]: SCT capabilities: ^I (0x103f)^ISCT Status supported. Sep 22 14:58:34 Tower preclear_disk-start[17262]: ^I^I^I^I^ISCT Feature Control supported. Sep 22 14:58:34 Tower preclear_disk-start[17262]: ^I^I^I^I^ISCT Data Table supported. Sep 22 14:58:34 Tower preclear_disk-start[17262]: Sep 22 14:58:34 Tower preclear_disk-start[17262]: SMART Attributes Data Structure revision number: 10 Sep 22 14:58:34 Tower preclear_disk-start[17262]: Vendor Specific SMART Attributes with Thresholds: Sep 22 14:58:34 Tower preclear_disk-start[17262]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Sep 22 14:58:34 Tower preclear_disk-start[17262]: 1 Raw_Read_Error_Rate 0x000f 114 099 006 Pre-fail Always - 80368931 Sep 22 14:58:34 Tower preclear_disk-start[17262]: 3 Spin_Up_Time 0x0003 096 092 000 Pre-fail Always - 0 Sep 22 14:58:34 Tower preclear_disk-start[17262]: 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 327 Sep 22 14:58:34 Tower preclear_disk-start[17262]: 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 Sep 22 14:58:34 Tower preclear_disk-start[17262]: 7 Seek_Error_Rate 0x000f 064 060 030 Pre-fail Always - 3034086 Sep 22 14:58:34 Tower preclear_disk-start[17262]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 450 Sep 22 14:58:34 Tower preclear_disk-start[17262]: 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 4 Sep 22 14:58:34 Tower preclear_disk-start[17262]: 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 78 Sep 22 14:58:34 Tower preclear_disk-start[17262]: 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 Sep 22 14:58:34 Tower preclear_disk-start[17262]: 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 Sep 22 14:58:34 Tower preclear_disk-start[17262]: 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 Sep 22 14:58:34 Tower preclear_disk-start[17262]: 189 High_Fly_Writes 0x003a 081 081 000 Old_age Always - 19 Sep 22 14:58:34 Tower preclear_disk-start[17262]: 190 Airflow_Temperature_Cel 0x0022 073 052 045 Old_age Always - 27 (Lifetime Min/Max 26/39) Sep 22 14:58:34 Tower preclear_disk-start[17262]: 195 Hardware_ECC_Recovered 0x001a 042 040 000 Old_age Always - 80368931 Sep 22 14:58:34 Tower preclear_disk-start[17262]: 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 Sep 22 14:58:34 Tower preclear_disk-start[17262]: 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 Sep 22 14:58:34 Tower preclear_disk-start[17262]: 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 Sep 22 14:58:34 Tower preclear_disk-start[17262]: 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 268448340902310 Sep 22 14:58:34 Tower preclear_disk-start[17262]: 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 4112256113 Sep 22 14:58:34 Tower preclear_disk-start[17262]: 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 3069564223 Sep 22 14:58:34 Tower preclear_disk-start[17262]: Sep 22 14:58:34 Tower preclear_disk-start[17262]: SMART Error Log Version: 1 Sep 22 14:58:34 Tower preclear_disk-start[17262]: No Errors Logged Sep 22 14:58:34 Tower preclear_disk-start[17262]: Sep 22 14:58:34 Tower preclear_disk-start[17262]: SMART Self-test log structure revision number 1 Sep 22 14:58:34 Tower preclear_disk-start[17262]: No self-tests have been logged. [To run self-tests, use: smartctl -t] Sep 22 14:58:34 Tower preclear_disk-start[17262]: Sep 22 14:58:34 Tower preclear_disk-start[17262]: Sep 22 14:58:34 Tower preclear_disk-start[17262]: SMART Selective self-test log data structure revision number 1 Sep 22 14:58:34 Tower preclear_disk-start[17262]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Sep 22 14:58:34 Tower preclear_disk-start[17262]: 1 0 0 Not_testing Sep 22 14:58:34 Tower preclear_disk-start[17262]: 2 0 0 Not_testing Sep 22 14:58:34 Tower preclear_disk-start[17262]: 3 0 0 Not_testing Sep 22 14:58:34 Tower preclear_disk-start[17262]: 4 0 0 Not_testing Sep 22 14:58:34 Tower preclear_disk-start[17262]: 5 0 0 Not_testing Sep 22 14:58:34 Tower preclear_disk-start[17262]: Selective self-test flags (0x0): Sep 22 14:58:34 Tower preclear_disk-start[17262]: After scanning selected spans, do NOT read-scan remainder of disk. Sep 22 14:58:34 Tower preclear_disk-start[17262]: If Selective self-test is pending on power-up, resume after 0 minute delay. Sep 22 14:58:34 Tower preclear_disk-start[17262]: Sep 22 19:23:42 Tower kernel: md: sync done. time=26980sec rate=72406K/sec Sep 22 19:23:42 Tower kernel: md: recovery thread sync completion status: 0 Sep 22 20:05:35 Tower kernel: mdcmd (4001): spindown 1
September 23, 201015 yr Only the "start" smart report is in the syslog segment you posted. Not the "post" smart report. To see if the drive is really cleared, type: preclear_disk.sh -t /dev/sdX
September 23, 201015 yr strange, why didn't it show? if I run preclear_disk.sh -t /dev/sdd I get "command not found" - is that because I put the server to S3 sleep in the meantime, and that I have to do it all over again, for a third time?
September 23, 201015 yr strange, why didn't it show? if I run preclear_disk.sh -t /dev/sdd I get "command not found" - is that because I put the server to S3 sleep in the meantime, and that I have to do it all over again, for a third time? Probably because you are not in the directory where you downloaded and un-zipped preclear_disk.sh If you log in you'll probably need to change directory first: cd /boot (assuming you put it in the top directory of the flash drive)
September 23, 201015 yr strange...preclear is indeed in /boot. when I run "preclear_disk.sh -t /dev/sdd" via telnet, it just goes down one line, but doesn't give me any information.
September 24, 201015 yr Could someone take a look at my Syslog please. I have 3 different drives running preclear right now. I thought I would look at my syslog, and I see errors at the end for all 3 drives concerning the SMART. I have precleared 8 other drives and never had this show up before. There are also several warnings that I am not sure of. Log is attached Edit: Don't need an answer to the last question about "HDIO_GET_IDENTITY", found that in the UnMenu thread. syslog-2010-09-23.txt
September 25, 201015 yr so, three times is a charm, I guess - it finally completed preclear. It must have stopped for some reason the second time around. Here's the result, I hope it looks good! =========================================================================== = 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: 37C, Elapsed Time: 20:25:14 ============================================================================ == == 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 0x000f 113 099 006 Pre-fail Always - 53148975 --- > 1 Raw_Read_Error_Rate 0x000f 120 099 006 Pre-fail Always - 1920904 58c58 < 7 Seek_Error_Rate 0x000f 065 060 030 Pre-fail Always - 3222666 --- > 7 Seek_Error_Rate 0x000f 065 060 030 Pre-fail Always - 3379418 64,66c64,66 < 189 High_Fly_Writes 0x003a 069 069 000 Old_age Always - 31 < 190 Airflow_Temperature_Cel 0x0022 062 052 045 Old_age Always - 38 (Lifetime Min/Max 19/38) < 195 Hardware_ECC_Recovered 0x001a 056 040 000 Old_age Always --- > 189 High_Fly_Writes 0x003a 059 059 000 Old_age Always - 41 > 190 Airflow_Temperature_Cel 0x0022 063 052 045 Old_age Always - 37 (Lifetime Min/Max 19/40) > 195 Hardware_ECC_Recovered 0x001a 058 040 000 Old_age Always 70,72c70,72 < 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 240032837271999 < 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 2868307976 < 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1510481113 --- > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 38560216383956 > 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1543831579 > 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 187566324
September 25, 201015 yr so, three times is a charm, I guess - it finally completed preclear. It must have stopped for some reason the second time around. Here's the result, I hope it looks good! It does look good. Joe L.
September 25, 201015 yr I just precleared 4 drives and i cant really tell if the results are good or not. So could someone take a look at them, thanks in advance The first drive is a Hitachi Deskstar 7K2000 HDS722020ALA330 Sep 25 07:39:45 Tower preclear_disk-diff[19750]: == Disk /dev/sda has been successfully precleared Sep 25 07:39:45 Tower preclear_disk-diff[19750]: == Sep 25 07:39:45 Tower preclear_disk-diff[19750]: == Ran 1 preclear-disk cycle Sep 25 07:39:45 Tower preclear_disk-diff[19750]: == Sep 25 07:39:45 Tower preclear_disk-diff[19750]: == Using :Read block size = 8225280 Bytes Sep 25 07:39:45 Tower preclear_disk-diff[19750]: == Last Cycle's Pre Read Time : 6:23:14 (86 MB/s) Sep 25 07:39:45 Tower preclear_disk-diff[19750]: == Last Cycle's Zeroing time : 6:16:27 (88 MB/s) Sep 25 07:39:45 Tower preclear_disk-diff[19750]: == Last Cycle's Post Read Time : 14:47:42 (37 MB/s) Sep 25 07:39:45 Tower preclear_disk-diff[19750]: == Last Cycle's Total Time : 27:28:39 Sep 25 07:39:45 Tower preclear_disk-diff[19750]: == Sep 25 07:39:45 Tower preclear_disk-diff[19750]: == Total Elapsed Time 27:28:39 Sep 25 07:39:45 Tower preclear_disk-diff[19750]: == Sep 25 07:39:45 Tower preclear_disk-diff[19750]: == Disk Start Temperature: 36C Sep 25 07:39:45 Tower preclear_disk-diff[19750]: == Sep 25 07:39:45 Tower preclear_disk-diff[19750]: == Current Disk Temperature: -->44<--C, Sep 25 07:39:45 Tower preclear_disk-diff[19750]: == Sep 25 07:39:45 Tower preclear_disk-diff[19750]: ============================================================================ Sep 25 07:39:45 Tower preclear_disk-diff[19750]: S.M.A.R.T. error count differences detected after pre-clear Sep 25 07:39:45 Tower preclear_disk-diff[19750]: note, some 'raw' values may change, but not be an indication of a problem Sep 25 07:39:45 Tower preclear_disk-diff[19750]: 19,20c19,20 Sep 25 07:39:45 Tower preclear_disk-diff[19750]: < Offline data collection status: (0x80)^IOffline data collection activity Sep 25 07:39:45 Tower preclear_disk-diff[19750]: < ^I^I^I^I^Iwas never started. Sep 25 07:39:45 Tower preclear_disk-diff[19750]: --- Sep 25 07:39:45 Tower preclear_disk-diff[19750]: > Offline data collection status: (0x84)^IOffline data collection activity Sep 25 07:39:45 Tower preclear_disk-diff[19750]: > ^I^I^I^I^Iwas suspended by an interrupting command from host. Sep 25 07:39:45 Tower preclear_disk-diff[19750]: ============================================================================ And the other 3 drives are Samsung SpinPoints F3EG Desktop Class HD203WI: Sep 25 11:26:07 Tower preclear_disk-diff[16777]: == Disk /dev/sdb has been successfully precleared Sep 25 11:26:07 Tower preclear_disk-diff[16777]: == Sep 25 11:26:07 Tower preclear_disk-diff[16777]: == Ran 1 preclear-disk cycle Sep 25 11:26:07 Tower preclear_disk-diff[16777]: == Sep 25 11:26:07 Tower preclear_disk-diff[16777]: == Using :Read block size = 8225280 Bytes Sep 25 11:26:07 Tower preclear_disk-diff[16777]: == Last Cycle's Pre Read Time : 7:13:58 (76 MB/s) Sep 25 11:26:07 Tower preclear_disk-diff[16777]: == Last Cycle's Zeroing time : 6:57:14 (79 MB/s) Sep 25 11:26:07 Tower preclear_disk-diff[16777]: == Last Cycle's Post Read Time : 17:01:19 (32 MB/s) Sep 25 11:26:07 Tower preclear_disk-diff[16777]: == Last Cycle's Total Time : 31:13:55 Sep 25 11:26:07 Tower preclear_disk-diff[16777]: == Sep 25 11:26:07 Tower preclear_disk-diff[16777]: == Total Elapsed Time 31:13:55 Sep 25 11:26:07 Tower preclear_disk-diff[16777]: == Sep 25 11:26:07 Tower preclear_disk-diff[16777]: == Disk Start Temperature: 29C Sep 25 11:26:07 Tower preclear_disk-diff[16777]: == Sep 25 11:26:07 Tower preclear_disk-diff[16777]: == Current Disk Temperature: 33C, Sep 25 11:26:07 Tower preclear_disk-diff[16777]: == Sep 25 11:26:07 Tower preclear_disk-diff[16777]: ============================================================================ Sep 25 11:26:07 Tower preclear_disk-diff[16777]: S.M.A.R.T. error count differences detected after pre-clear Sep 25 11:26:07 Tower preclear_disk-diff[16777]: note, some 'raw' values may change, but not be an indication of a problem Sep 25 11:26:07 Tower preclear_disk-diff[16777]: 55c55 Sep 25 11:26:07 Tower preclear_disk-diff[16777]: < 1 Raw_Read_Error_Rate 0x002f 252 252 051 Pre-fail Always - 0 Sep 25 11:26:07 Tower preclear_disk-diff[16777]: --- Sep 25 11:26:07 Tower preclear_disk-diff[16777]: > 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 12 Sep 25 11:26:07 Tower preclear_disk-diff[16777]: 67c67 Sep 25 11:26:07 Tower preclear_disk-diff[16777]: < 195 Hardware_ECC_Recovered 0x003a 252 252 000 Old_age Always Sep 25 11:26:07 Tower preclear_disk-diff[16777]: --- Sep 25 11:26:07 Tower preclear_disk-diff[16777]: > 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always Sep 25 11:26:07 Tower preclear_disk-diff[16777]: 72c72 Sep 25 11:26:07 Tower preclear_disk-diff[16777]: < 200 Multi_Zone_Error_Rate 0x002a 252 252 000 Old_age Always - 0 Sep 25 11:26:07 Tower preclear_disk-diff[16777]: --- Sep 25 11:26:07 Tower preclear_disk-diff[16777]: > 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 0 Sep 25 11:26:07 Tower preclear_disk-diff[16777]: ============================================================================ Sep 25 13:16:05 Tower preclear_disk-diff[25318]: == Disk /dev/sdd has been successfully precleared Sep 25 13:16:05 Tower preclear_disk-diff[25318]: == Sep 25 13:16:05 Tower preclear_disk-diff[25318]: == Ran 1 preclear-disk cycle Sep 25 13:16:05 Tower preclear_disk-diff[25318]: == Sep 25 13:16:05 Tower preclear_disk-diff[25318]: == Using :Read block size = 8225280 Bytes Sep 25 13:16:05 Tower preclear_disk-diff[25318]: == Last Cycle's Pre Read Time : 7:43:19 (71 MB/s) Sep 25 13:16:05 Tower preclear_disk-diff[25318]: == Last Cycle's Zeroing time : 7:24:26 (75 MB/s) Sep 25 13:16:05 Tower preclear_disk-diff[25318]: == Last Cycle's Post Read Time : 17:53:32 (31 MB/s) Sep 25 13:16:05 Tower preclear_disk-diff[25318]: == Last Cycle's Total Time : 33:02:41 Sep 25 13:16:05 Tower preclear_disk-diff[25318]: == Sep 25 13:16:05 Tower preclear_disk-diff[25318]: == Total Elapsed Time 33:02:41 Sep 25 13:16:05 Tower preclear_disk-diff[25318]: == Sep 25 13:16:05 Tower preclear_disk-diff[25318]: == Disk Start Temperature: 28C Sep 25 13:16:05 Tower preclear_disk-diff[25318]: == Sep 25 13:16:05 Tower preclear_disk-diff[25318]: == Current Disk Temperature: 31C, Sep 25 13:16:05 Tower preclear_disk-diff[25318]: == Sep 25 13:16:05 Tower preclear_disk-diff[25318]: ============================================================================ Sep 25 13:16:05 Tower preclear_disk-diff[25318]: S.M.A.R.T. error count differences detected after pre-clear Sep 25 13:16:05 Tower preclear_disk-diff[25318]: note, some 'raw' values may change, but not be an indication of a problem Sep 25 13:16:05 Tower preclear_disk-diff[25318]: 55c55 Sep 25 13:16:05 Tower preclear_disk-diff[25318]: < 1 Raw_Read_Error_Rate 0x002f 252 252 051 Pre-fail Always - 0 Sep 25 13:16:05 Tower preclear_disk-diff[25318]: --- Sep 25 13:16:05 Tower preclear_disk-diff[25318]: > 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 358 Sep 25 13:16:05 Tower preclear_disk-diff[25318]: 65c65 Sep 25 13:16:05 Tower preclear_disk-diff[25318]: < 191 G-Sense_Error_Rate 0x0022 252 252 000 Old_age Always - 0 Sep 25 13:16:05 Tower preclear_disk-diff[25318]: --- Sep 25 13:16:05 Tower preclear_disk-diff[25318]: > 191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 25 Sep 25 13:16:05 Tower preclear_disk-diff[25318]: 67c67 Sep 25 13:16:05 Tower preclear_disk-diff[25318]: < 195 Hardware_ECC_Recovered 0x003a 252 252 000 Old_age Always Sep 25 13:16:05 Tower preclear_disk-diff[25318]: --- Sep 25 13:16:05 Tower preclear_disk-diff[25318]: > 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always Sep 25 13:16:05 Tower preclear_disk-diff[25318]: 72c72 Sep 25 13:16:05 Tower preclear_disk-diff[25318]: < 200 Multi_Zone_Error_Rate 0x002a 252 252 000 Old_age Always - 0 Sep 25 13:16:05 Tower preclear_disk-diff[25318]: --- Sep 25 13:16:05 Tower preclear_disk-diff[25318]: > 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 0 Sep 25 13:16:05 Tower preclear_disk-diff[25318]: ============================================================================ Sep 25 13:32:33 Tower preclear_disk-diff[25905]: == Disk /dev/sdc has been successfully precleared Sep 25 13:32:33 Tower preclear_disk-diff[25905]: == Sep 25 13:32:33 Tower preclear_disk-diff[25905]: == Ran 1 preclear-disk cycle Sep 25 13:32:33 Tower preclear_disk-diff[25905]: == Sep 25 13:32:33 Tower preclear_disk-diff[25905]: == Using :Read block size = 8225280 Bytes Sep 25 13:32:33 Tower preclear_disk-diff[25905]: == Last Cycle's Pre Read Time : 7:48:19 (71 MB/s) Sep 25 13:32:33 Tower preclear_disk-diff[25905]: == Last Cycle's Zeroing time : 7:35:07 (73 MB/s) Sep 25 13:32:33 Tower preclear_disk-diff[25905]: == Last Cycle's Post Read Time : 17:54:57 (31 MB/s) Sep 25 13:32:33 Tower preclear_disk-diff[25905]: == Last Cycle's Total Time : 33:19:49 Sep 25 13:32:33 Tower preclear_disk-diff[25905]: == Sep 25 13:32:33 Tower preclear_disk-diff[25905]: == Total Elapsed Time 33:19:49 Sep 25 13:32:33 Tower preclear_disk-diff[25905]: == Sep 25 13:32:33 Tower preclear_disk-diff[25905]: == Disk Start Temperature: 30C Sep 25 13:32:33 Tower preclear_disk-diff[25905]: == Sep 25 13:32:33 Tower preclear_disk-diff[25905]: == Current Disk Temperature: 36C, Sep 25 13:32:33 Tower preclear_disk-diff[25905]: == Sep 25 13:32:33 Tower preclear_disk-diff[25905]: ============================================================================ Sep 25 13:32:33 Tower preclear_disk-diff[25905]: S.M.A.R.T. error count differences detected after pre-clear Sep 25 13:32:33 Tower preclear_disk-diff[25905]: note, some 'raw' values may change, but not be an indication of a problem Sep 25 13:32:33 Tower preclear_disk-diff[25905]: 55c55 Sep 25 13:32:33 Tower preclear_disk-diff[25905]: < 1 Raw_Read_Error_Rate 0x002f 252 252 051 Pre-fail Always - 0 Sep 25 13:32:33 Tower preclear_disk-diff[25905]: --- Sep 25 13:32:33 Tower preclear_disk-diff[25905]: > 1 Raw_Read_Error_Rate 0x002f 100 100 051 Pre-fail Always - 71 Sep 25 13:32:33 Tower preclear_disk-diff[25905]: 67c67 Sep 25 13:32:33 Tower preclear_disk-diff[25905]: < 195 Hardware_ECC_Recovered 0x003a 252 252 000 Old_age Always Sep 25 13:32:33 Tower preclear_disk-diff[25905]: --- Sep 25 13:32:33 Tower preclear_disk-diff[25905]: > 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always Sep 25 13:32:33 Tower preclear_disk-diff[25905]: 72c72 Sep 25 13:32:33 Tower preclear_disk-diff[25905]: < 200 Multi_Zone_Error_Rate 0x002a 252 252 000 Old_age Always - 0 Sep 25 13:32:33 Tower preclear_disk-diff[25905]: --- Sep 25 13:32:33 Tower preclear_disk-diff[25905]: > 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 1 Sep 25 13:32:33 Tower preclear_disk-diff[25905]: ============================================================================
September 25, 201015 yr I just precleared 4 drives and i cant really tell if the results are good or not. So could someone take a look at them, thanks in advance None of the "normalized values are below their failure thresholds, there are no re-allocated sectors or pending re-allocation. The temperature of 44C of the first drive is a bit high for my comfort. It probably needs more air flow around it. I have four of that same Hitachi drive in one of my servers and they all sit between 27C and 32C.
September 25, 201015 yr The temperature of 44C of the first drive is a bit high for my comfort. It probably needs more air flow around it. I have four of that same Hitachi drive in one of my servers and they all sit between 27C and 32C. Thats good news, the Hitachi drive indeed has bad airflow. It seems the bottom tray is around 5 degrees warmer then the top ones (Zalman 3-in-3 bay) and thats with an empty bay in the middle. But i'll try to play with the fans a little more to make it a little cooler, thanks for the help
September 25, 201015 yr Thats good news, the Hitachi drive indeed has bad airflow. It seems the bottom tray is around 5 degrees warmer then the top ones (Zalman 3-in-3 bay) and thats with an empty bay in the middle. But i'll try to play with the fans a little more to make it a little cooler, thanks for the help If you put something in the empty bay to block the air, similar to how a drive would, that will improve the airflow around the disks.
September 26, 201015 yr Hey! Im back here again because i just finished the Preclear for a new drive and i was hoping to get some help with the syslog. Ilooked for the reallocated sectors and in my knowledge seems to be Ok. Syslog attached if anyone can take a look and give me some advice about the drive. Thx in advance!! syslog_26-9-2010-0200.txt
September 26, 201015 yr Hey! Im back here again because i just finished the Preclear for a new drive and i was hoping to get some help with the syslog. Ilooked for the reallocated sectors and in my knowledge seems to be Ok. Syslog attached if anyone can take a look and give me some advice about the drive. Thx in advance!! Looks good. No re-allocated sectors, or sectors pending re-allocation. No parameters FAILING_NOW, nor any where the current value is nearing the failure-threshold. (You can see several changing from the factory 253 value to the starting value of 200.) You must have very good air flow past that drive, since its temperature only rose from 26C to 28C during the clearing cycle that lasted over 27 hours. Nice.
September 26, 201015 yr I'm currently running my third preclear cycle on a new WD20EARS (about 60% complete on the preread). The raw values for raw read error rate and current pending sectors are increasing. As well you can see a lot of reported read errors in the attached syslog, which I assume is driving the changes in the SMART reported raw values. FYI - the attached syslog only includes the results from the first preclear because there were so many errors that the file size was too large to be attached. I'll attach the results from the 2nd cycle on another post. I guess that's not a good sign either. But the changes are limited to only the raw values and not the normalized values. I'm wondering what the community thinks about the drive so far? Should I consider a RMA for this drive or is it too early to tell? It's not the fact that there are errors being reported that bothers me as much as the fact that they are increasing. Doesn't give me a lot of confidence that the drive will last. syslog-1stcycle.txt
September 26, 201015 yr Hey! Im back here again because i just finished the Preclear for a new drive and i was hoping to get some help with the syslog. Ilooked for the reallocated sectors and in my knowledge seems to be Ok. Syslog attached if anyone can take a look and give me some advice about the drive. Thx in advance!! Looks good. No re-allocated sectors, or sectors pending re-allocation. No parameters FAILING_NOW, nor any where the current value is nearing the failure-threshold. (You can see several changing from the factory 253 value to the starting value of 200.) You must have very good air flow past that drive, since its temperature only rose from 26C to 28C during the clearing cycle that lasted over 27 hours. Nice. Thanks Joe. FYI Im using 2 X 120mm Enermax Fans in the front and 2 X 80 mm Enermax fans in the rear. Both are really quiet, I love them .
September 27, 201015 yr Here is the syslog from the second cycle. I don't like the increasing number of sectors pending re-allocation yet no sectors are re-allocated, indicating the second attempt at writing them to their original sector worked, but then the post-read found more un-readable sectors. I'd first try a different power connection in case it is a noisy power supply, but other than that, I'd consider it a candidate for an RMA if the errors continue. In know it is not the news you wanted to hear, but it is far easier now than after it holds your data and has those same errors. Joe L.
September 27, 201015 yr I'd first try a different power connection in case it is a noisy power supply Do you mean try a different sata power connector on my current power supply or an entirely new power supply?
September 27, 201015 yr Power-Off_Retract_Count is usually the count of how many times the disk heads were retracted in a power loss. Load_Cycle_Count is how many times the disk heads are loaded from their parked position. Both counts incremented by 1. (as if the disk lost power, it retracted the disk heads, then power was restored, and it re-loaded them) I'd look for a loose power connection to the drive. Or, it could be your power supply is not up to the task, or you have a bad splitter, back-plane, card-rack, etc... It is not normal to see those counts increment in a pre-clear cycle. I will check the cables. I'm running a new US budget box build. Is there any reason the 400W power supply is not enough? We have no idea... How many disks do you have attached, how many are "green"? What specific 400 Watt supply? Is it a single 12 Volt rail supply? Joe L. I changed the power cable and this problem went away. Thanks for the help Joe.
September 27, 201015 yr I'd first try a different power connection in case it is a noisy power supply Do you mean try a different sata power connector on my current power supply or an entirely new power supply? You can do either as a test. Some drives perform poorly if attached to a marginal power supply, or if the voltage on the cable is "noisy" I was just trying to let you know it might not be the drive, but what it is attached to. If you are using splitters, try not to. If the power supply is marginal for your use, they perhaps a better one (with a single 12 Volt rail with high current capacity) will help.
September 27, 201015 yr Good point Joe L. I'll try another connector after the third cycle is finished. Although I'm not holding my breath as the power connector that is currently connected to that drive was previously connected to another drive which did not have any SMART problems at all. But I suppose that there is a chance it could be flaky so better safe than sorry. Should I switch the sata cable also? The sata cable I'm using is new so it could be bad as well. Could it cause the types of errors I'm seeing?
September 27, 201015 yr Good point Joe L. I'll try another connector after the third cycle is finished. Although I'm not holding my breath as the power connector that is currently connected to that drive was previously connected to another drive which did not have any SMART problems at all. But I suppose that there is a chance it could be flaky so better safe than sorry. Should I switch the sata cable also? The sata cable I'm using is new so it could be bad as well. Could it cause the types of errors I'm seeing? I don't think the SATA cable could cause the types of errors you are seeing. You would be getting CRC errors, not media errors. Even though it is the same cable as a different drive, it could be that specific drive is more sensitive to noise on the supply voltage. If you transpose two drives, and the problem follows the drive, then it is highly likely you do not want that drive in your array.
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.