jbuszkie Posted December 2, 2010 Author Share Posted December 2, 2010 Ok.. I'll try the reseat and switch the cables around... The drives are being cleared in a separate machine. so it's not my main UnRaid machine. Interestingly.. Even on this separate machine I'm seeing much slower reads on the post read. I still am baffled by this. I'm getting about 40MB/s calculated while the test says 84MB/s Post Read in progress on /dev/sda: 75% complete. ( 1,501,936,128,000 of 2,000,398,934,016 bytes read )at 84.3 MB/s Disk Temperature: 35C, Using Block size of 8,225,280 Bytes Next report at 100% Calculated Read Speed: 40 MB/s Elapsed Time of current cycle: 10:15:27 Total Elapsed time: 22:31:51 All three remaining drives exhibit this... The pre-read and the zeroing all were fast... Pre Read finished on /dev/sdc ( 2,000,388,096,000 of 2,000,398,934,016 bytes read) Pre Read Elapsed Time: 6:15:27 Total Elapsed Time: 6:15:32 Disk Temperature: -->41<--C, Using Block size of 8,225,280 Bytes Calculated Read Speed - 88 MB/s Zeroing Disk /dev/sdc Done. Zeroing Elapsed Time: 5:55:17 Total Elapsed Time: 12:10:52 Disk Temperature: -->42<--C, Calculated Write Speed: 93 MB/s Quote Link to comment
monza Posted December 2, 2010 Share Posted December 2, 2010 Just wanted someone to quickly check my preclear results from a WD EARS drive (with jumper over 7 & 8 ) looks ok to me (this is my first time using pre-clear)... but if anyone can see anything strange then please let me know. I did notice this (see attached log): Nov 28 18:14:28 Tower kernel: end_request: I/O error, dev sdg, sector 2563489960 Nov 28 18:14:28 Tower kernel: Buffer I/O error on device sdg, logical block 320436245 This is the summary: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: smartctl version 5.38 [i486-slackware-linux-gnu] Copyright (C) 2002-8 Bruce Allen Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Home page is http://smartmontools.sourceforge.net/ Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: === START OF INFORMATION SECTION === Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Device Model: WDC WD20EARS-00MVWB0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Serial Number: WD-WMAZA1634XXX Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Firmware Version: 51.0AB51 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: User Capacity: 2,000,398,934,016 bytes Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Device is: Not in smartctl database [for details use: -P showall] Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ATA Version is: 8 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ATA Standard is: Exact ATA specification draft version not indicated Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Local Time is: Mon Nov 29 23:05:05 2010 GMT Nov 29 23:05:05 Tower preclear_disk-finish[7312]: SMART support is: Available - device has SMART capability. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: SMART support is: Enabled Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: === START OF READ SMART DATA SECTION === Nov 29 23:05:05 Tower preclear_disk-finish[7312]: SMART overall-health self-assessment test result: PASSED Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: General SMART Values: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Offline data collection status: (0x84)^IOffline data collection activity Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^Iwas suspended by an interrupting command from host. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^IAuto Offline Data Collection: Enabled. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Self-test execution status: ( 0)^IThe previous self-test routine completed Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^Iwithout error or no self-test has ever Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^Ibeen run. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Total time to complete Offline Nov 29 23:05:05 Tower preclear_disk-finish[7312]: data collection: ^I^I (37500) seconds. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Offline data collection Nov 29 23:05:05 Tower preclear_disk-finish[7312]: capabilities: ^I^I^I (0x7b) SMART execute Offline immediate. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^IAuto Offline data collection on/off support. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^ISuspend Offline collection upon new Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^Icommand. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^IOffline surface scan supported. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^ISelf-test supported. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^IConveyance Self-test supported. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^ISelective Self-test supported. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: SMART capabilities: (0x0003)^ISaves SMART data before entering Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^Ipower-saving mode. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^ISupports SMART auto save timer. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Error logging capability: (0x01)^IError logging supported. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^IGeneral Purpose Logging supported. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Short self-test routine Nov 29 23:05:05 Tower preclear_disk-finish[7312]: recommended polling time: ^I ( 2) minutes. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Extended self-test routine Nov 29 23:05:05 Tower preclear_disk-finish[7312]: recommended polling time: ^I ( 255) minutes. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Conveyance self-test routine Nov 29 23:05:05 Tower preclear_disk-finish[7312]: recommended polling time: ^I ( 5) minutes. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: SCT capabilities: ^I (0x3035)^ISCT Status supported. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^ISCT Feature Control supported. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ^I^I^I^I^ISCT Data Table supported. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: SMART Attributes Data Structure revision number: 16 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Vendor Specific SMART Attributes with Thresholds: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 3 Spin_Up_Time 0x0027 253 253 021 Pre-fail Always - 1125 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 10 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 33 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 8 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 7 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 15 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: SMART Error Log Version: 1 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: No Errors Logged Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: SMART Self-test log structure revision number 1 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: No self-tests have been logged. [To run self-tests, use: smartctl -t] Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Nov 29 23:05:05 Tower preclear_disk-finish[7312]: SMART Selective self-test log data structure revision number 1 Nov 29 23:05:05 Tower preclear_disk-finish[7312]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 1 0 0 Not_testing Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 2 0 0 Not_testing Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 3 0 0 Not_testing Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 4 0 0 Not_testing Nov 29 23:05:05 Tower preclear_disk-finish[7312]: 5 0 0 Not_testing Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Selective self-test flags (0x0): Nov 29 23:05:05 Tower preclear_disk-finish[7312]: After scanning selected spans, do NOT read-scan remainder of disk. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: If Selective self-test is pending on power-up, resume after 0 minute delay. Nov 29 23:05:05 Tower preclear_disk-finish[7312]: Nov 29 23:05:05 Tower preclear_disk-diff[7325]: ============================================================================ Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Disk /dev/sdg has been successfully precleared Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Ran 1 preclear-disk cycle Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Using :Read block size = 8225280 Bytes Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Last Cycle's Pre Read Time : 8:10:46 (67 MB/s) Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Last Cycle's Zeroing time : 9:17:46 (59 MB/s) Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Last Cycle's Post Read Time : 16:21:09 (33 MB/s) Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Last Cycle's Total Time : 33:50:49 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Total Elapsed Time 33:50:49 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Disk Start Temperature: 15C Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Current Disk Temperature: 21C, Nov 29 23:05:05 Tower preclear_disk-diff[7325]: == Nov 29 23:05:05 Tower preclear_disk-diff[7325]: ============================================================================ Nov 29 23:05:05 Tower preclear_disk-diff[7325]: S.M.A.R.T. error count differences detected after pre-clear Nov 29 23:05:05 Tower preclear_disk-diff[7325]: note, some 'raw' values may change, but not be an indication of a problem Nov 29 23:05:05 Tower preclear_disk-diff[7325]: 19,20c19,20 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: < Offline data collection status: (0x80)^IOffline data collection activity Nov 29 23:05:05 Tower preclear_disk-diff[7325]: < ^I^I^I^I^Iwas never started. Nov 29 23:05:05 Tower preclear_disk-diff[7325]: --- Nov 29 23:05:05 Tower preclear_disk-diff[7325]: > Offline data collection status: (0x84)^IOffline data collection activity Nov 29 23:05:05 Tower preclear_disk-diff[7325]: > ^I^I^I^I^Iwas suspended by an interrupting command from host. Nov 29 23:05:05 Tower preclear_disk-diff[7325]: 54c54 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: --- Nov 29 23:05:05 Tower preclear_disk-diff[7325]: > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: 58c58 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: < 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: --- Nov 29 23:05:05 Tower preclear_disk-diff[7325]: > 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: 63c63 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 8 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: --- Nov 29 23:05:05 Tower preclear_disk-diff[7325]: > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 15 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: 67c67 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: < 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: --- Nov 29 23:05:05 Tower preclear_disk-diff[7325]: > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 Nov 29 23:05:05 Tower preclear_disk-diff[7325]: ============================================================================ Nov 29 23:05:05 Tower preclear_disk-diff[7325]: excerpt from full log is attached. thanks PreClear_Excerpt_from_syslog.txt Quote Link to comment
wreck Posted December 3, 2010 Share Posted December 3, 2010 Quick check on my results before I add the drive to the array. 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 100 100 006 Pre-fail Always - 124774 --- > 1 Raw_Read_Error_Rate 0x000f 119 099 006 Pre-fail Always - 215099399 58c58 < 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 111 --- > 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 479189 66,67c66,67 < 190 Airflow_Temperature_Cel 0x0022 075 073 045 Old_age Always - 25 (Lifetime Min/Max 21/25) < 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always --- > 190 Airflow_Temperature_Cel 0x0022 077 073 045 Old_age Always - 23 (Lifetime Min/Max 21/27) > 195 Hardware_ECC_Recovered 0x001a 047 041 000 Old_age Always 71,73c71,73 < 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 103835129348108 < 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 0 < 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 97912 --- > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 48546015346729 > 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 833009932 > 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 2000042141 ============================================================================ Smart report: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 119 099 006 Pre-fail Always - 215142716 3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 7 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 479582 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 35 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 7 183 Unknown_Attribute 0x0032 098 098 000 Old_age Always - 2 184 Unknown_Attribute 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 078 073 045 Old_age Always - 22 (Lifetime Min/Max 21/27) 194 Temperature_Celsius 0x0022 022 040 000 Old_age Always - 22 (0 19 0 0) 195 Hardware_ECC_Recovered 0x001a 046 041 000 Old_age Always - 215142716 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 160597417132074 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 833009932 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 161212931 1 and 7 look a little off to me, but I'm not sure if its cause for concern. Thanks in advance. Quote Link to comment
Joe L. Posted December 3, 2010 Share Posted December 3, 2010 You've apparently not seen any of the posts on how to interpret the results. The "raw" column values have meaning only to the manufacturer in most cases. For attribute 1 the normalized value is nowhere near the failure threshold. For attribute 7 the normalized value is still set at its starting point from the factory with a new value of 253. Look at the value for "head flying hours" as an example of a value that has no meaning to us. Even if measured in billionths of a second the raw values would make no sense. (certainly the flying hours would not decrease, and the raw value has decreased) Your disk looks fine. There are no re-allocated sectors or sectors pending re-allocation. Quote Link to comment
wreck Posted December 3, 2010 Share Posted December 3, 2010 Thank you very much Joe L. Good to know everything looks fine. Quote Link to comment
fonzie Posted December 3, 2010 Share Posted December 3, 2010 I just finished preclearing my Black Friday drive Seagate 2TB model: ST32000542AS updated to CC35 firmware I'm still not certain which part of the results should be looked at so I posted an excerpt of what looked to be important. I also am attaching the full results in case I left something out. Please let me know if all is well. Dec 2 23:15:40 media preclear_disk-diff[10348]: == Disk /dev/sdb has been successfully precleared Dec 2 23:15:40 media preclear_disk-diff[10348]: == Dec 2 23:15:40 media preclear_disk-diff[10348]: == Ran 1 preclear-disk cycle Dec 2 23:15:40 media preclear_disk-diff[10348]: == Dec 2 23:15:40 media preclear_disk-diff[10348]: == Using :Read block size = 8225280 Bytes Dec 2 23:15:40 media preclear_disk-diff[10348]: == Last Cycle's Pre Read Time : 6:54:17 (80 MB/s) Dec 2 23:15:40 media preclear_disk-diff[10348]: == Last Cycle's Zeroing time : 6:58:08 (79 MB/s) Dec 2 23:15:40 media preclear_disk-diff[10348]: == Last Cycle's Post Read Time : 14:31:47 (38 MB/s) Dec 2 23:15:40 media preclear_disk-diff[10348]: == Last Cycle's Total Time : 28:25:16 Dec 2 23:15:40 media preclear_disk-diff[10348]: == Dec 2 23:15:40 media preclear_disk-diff[10348]: == Total Elapsed Time 28:25:16 Dec 2 23:15:40 media preclear_disk-diff[10348]: == Dec 2 23:15:40 media preclear_disk-diff[10348]: == Disk Start Temperature: 27C Dec 2 23:15:40 media preclear_disk-diff[10348]: == Dec 2 23:15:40 media preclear_disk-diff[10348]: == Current Disk Temperature: 29C, Dec 2 23:15:40 media preclear_disk-diff[10348]: == Dec 2 23:15:40 media preclear_disk-diff[10348]: ============================================================================ Dec 2 23:15:40 media preclear_disk-diff[10348]: S.M.A.R.T. error count differences detected after pre-clear Dec 2 23:15:40 media preclear_disk-diff[10348]: note, some 'raw' values may change, but not be an indication of a problem Dec 2 23:15:40 media preclear_disk-diff[10348]: 54c54 Dec 2 23:15:40 media preclear_disk-diff[10348]: < 1 Raw_Read_Error_Rate 0x000f 100 100 006 Pre-fail Always - 9935 Dec 2 23:15:40 media preclear_disk-diff[10348]: --- Dec 2 23:15:40 media preclear_disk-diff[10348]: > 1 Raw_Read_Error_Rate 0x000f 119 100 006 Pre-fail Always - 211695025 Dec 2 23:15:40 media preclear_disk-diff[10348]: 58c58 Dec 2 23:15:40 media preclear_disk-diff[10348]: < 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 21 Dec 2 23:15:40 media preclear_disk-diff[10348]: --- Dec 2 23:15:40 media preclear_disk-diff[10348]: > 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 457994 Dec 2 23:15:40 media preclear_disk-diff[10348]: 64c64 Dec 2 23:15:40 media preclear_disk-diff[10348]: < 188 Unknown_Attribute 0x0032 100 253 000 Old_age Always - 0 Dec 2 23:15:40 media preclear_disk-diff[10348]: --- Dec 2 23:15:40 media preclear_disk-diff[10348]: > 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 Dec 2 23:15:40 media preclear_disk-diff[10348]: 66,67c66,67 Dec 2 23:15:40 media preclear_disk-diff[10348]: < 190 Airflow_Temperature_Cel 0x0022 073 071 045 Old_age Always - 27 (Lifetime Min/Max 26/27) Dec 2 23:15:40 media preclear_disk-diff[10348]: < 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always Dec 2 23:15:40 media preclear_disk-diff[10348]: --- Dec 2 23:15:40 media preclear_disk-diff[10348]: > 190 Airflow_Temperature_Cel 0x0022 071 069 045 Old_age Always - 29 (Lifetime Min/Max 26/31) Dec 2 23:15:40 media preclear_disk-diff[10348]: > 195 Hardware_ECC_Recovered 0x001a 051 047 000 Old_age Always Dec 2 23:15:40 media preclear_disk-diff[10348]: 70,73c70,73 Dec 2 23:15:40 media preclear_disk-diff[10348]: < 199 UDMA_CRC_Error_Count 0x003e 200 253 000 Old_age Always - 0 Dec 2 23:15:40 media preclear_disk-diff[10348]: < 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 89073326751757 Dec 2 23:15:40 media preclear_disk-diff[10348]: < 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 0 Dec 2 23:15:40 media preclear_disk-diff[10348]: < 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 923 Dec 2 23:15:40 media preclear_disk-diff[10348]: --- Dec 2 23:15:40 media preclear_disk-diff[10348]: > 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 Dec 2 23:15:40 media preclear_disk-diff[10348]: > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 169973330739242 Dec 2 23:15:40 media preclear_disk-diff[10348]: > 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 878605953 Dec 2 23:15:40 media preclear_disk-diff[10348]: > 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 3328787425 Dec 2 23:15:40 media preclear_disk-diff[10348]: ============================================================================ Dec 2 23:15:40 media preclear_disk-diff[10348]: Seagate_Results.txt Quote Link to comment
jbuszkie Posted December 3, 2010 Author Share Posted December 3, 2010 Joe, I'm trying to preclear 4 2T samsung drives. 3 are chugging along but one failed right after zeroing. I grabbed the first smart report as the drive, now, is un responsive. There are some errors reported. I'll try power cycling once the other drives finish (about 2 hours or so) and see if the drive comes back.. and grab another SMART report... but my guess is this drive might be a dud! Do you concur? I'm guessing it could just as easily be a loose/bad cable to the drive. But do not touch them now... Only do that after stopping the array cleanly and then powering down. (It could be either the power or data cable, or, if in a drive tray, it might not be seated well in the connectors.) Joe L. Crud! The last drive, after power cycling, passed the preclear test.. but there are some more errors. My guess is I should RMA this drive. There are 28 ATA Errors. There were 15 before the 2nd preclear attempt. Here is an excerpt. Full smart report attached. 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 0x002f 100 100 051 Pre-fail Always - 0 2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0 3 Spin_Up_Time 0x0023 067 066 025 Pre-fail Always - 10113 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 4 5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0 8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0 10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 252 252 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 4 181 Unknown_Attribute 0x0022 252 252 000 Old_age Always - 0 191 G-Sense_Error_Rate 0x0022 252 252 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0 195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always 196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 252 252 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0036 100 100 000 Old_age Always - 31 200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 0 223 Load_Retry_Count 0x0032 252 252 000 Old_age Always - 0 225 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 4 SMART Error Log Version: 1 ATA Error Count: 28 (device log contains only the most recent five errors) <-------------------------------------- CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 28 occurred at disk power-on lifetime: 50 hours (2 days + 2 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 84 51 00 00 4f c2 00 Error: ABRT What do you think? I moved the drive to a different cable and power cord for the 2nd pre-clear try.. So it's not a cabling issue.. Thanks, Jim smart_start3805.txt smart_start3805.txt Quote Link to comment
JackBauer Posted December 4, 2010 Share Posted December 4, 2010 I'm going to start reading through the 30 pages of comments here trying to understand my results. While doing so, in case someone wants to review the differences in my two new seagate 5900 Black Friday drives, I would be happy to listen. (Both were upgraded to CE35 firmware prior to being installed in the unraid server) Thanks folks sda: Dec 5 04:02:13 Tower preclear_disk-diff[5090]: S.M.A.R.T. error count differences detected after pre-clear Dec 5 04:02:13 Tower preclear_disk-diff[5090]: note, some 'raw' values may change, but not be an indication of a problem Dec 5 04:02:13 Tower preclear_disk-diff[5090]: 54c54 Dec 5 04:02:13 Tower preclear_disk-diff[5090]: < 1 Raw_Read_Error_Rate 0x000f 100 100 006 Pre-fail Always - 56892 Dec 5 04:02:13 Tower preclear_disk-diff[5090]: --- Dec 5 04:02:13 Tower preclear_disk-diff[5090]: > 1 Raw_Read_Error_Rate 0x000f 116 099 006 Pre-fail Always - 223497429 Dec 5 04:02:13 Tower preclear_disk-diff[5090]: 58c58 Dec 5 04:02:13 Tower preclear_disk-diff[5090]: < 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 148 Dec 5 04:02:13 Tower preclear_disk-diff[5090]: --- Dec 5 04:02:13 Tower preclear_disk-diff[5090]: > 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 192141 Dec 5 04:02:13 Tower preclear_disk-diff[5090]: 64c64 Dec 5 04:02:13 Tower preclear_disk-diff[5090]: < 188 Command_Timeout 0x0032 100 253 000 Old_age Always - 0 Dec 5 04:02:13 Tower preclear_disk-diff[5090]: --- Dec 5 04:02:13 Tower preclear_disk-diff[5090]: > 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 Dec 5 04:02:13 Tower preclear_disk-diff[5090]: 66,67c66,67 Dec 5 04:02:13 Tower preclear_disk-diff[5090]: < 190 Airflow_Temperature_Cel 0x0022 070 068 045 Old_age Always - 30 (Lifetime Min/Max 28/30) Dec 5 04:02:13 Tower preclear_disk-diff[5090]: < 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always Dec 5 04:02:13 Tower preclear_disk-diff[5090]: --- Dec 5 04:02:13 Tower preclear_disk-diff[5090]: > 190 Airflow_Temperature_Cel 0x0022 067 064 045 Old_age Always - 33 (Lifetime Min/Max 28/36) Dec 5 04:02:13 Tower preclear_disk-diff[5090]: > 195 Hardware_ECC_Recovered 0x001a 048 039 000 Old_age Always Dec 5 04:02:13 Tower preclear_disk-diff[5090]: 70,73c70,73 Dec 5 04:02:13 Tower preclear_disk-diff[5090]: < 199 UDMA_CRC_Error_Count 0x003e 200 253 000 Old_age Always - 0 Dec 5 04:02:13 Tower preclear_disk-diff[5090]: < 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 3998614552630 Dec 5 04:02:13 Tower preclear_disk-diff[5090]: < 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 8 Dec 5 04:02:13 Tower preclear_disk-diff[5090]: < 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 14705 Dec 5 04:02:13 Tower preclear_disk-diff[5090]: --- Dec 5 04:02:13 Tower preclear_disk-diff[5090]: > 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 Dec 5 04:02:13 Tower preclear_disk-diff[5090]: > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 164535902142547 Dec 5 04:02:13 Tower preclear_disk-diff[5090]: > 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 3906080672 Dec 5 04:02:13 Tower preclear_disk-diff[5090]: > 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3669296420 sdb: Dec 5 03:40:01 Tower preclear_disk-diff[4172]: S.M.A.R.T. error count differences detected after pre-clear Dec 5 03:40:01 Tower preclear_disk-diff[4172]: note, some 'raw' values may change, but not be an indication of a problem Dec 5 03:40:01 Tower preclear_disk-diff[4172]: 54c54 Dec 5 03:40:01 Tower preclear_disk-diff[4172]: < 1 Raw_Read_Error_Rate 0x000f 100 100 006 Pre-fail Always - 59966 Dec 5 03:40:01 Tower preclear_disk-diff[4172]: --- Dec 5 03:40:01 Tower preclear_disk-diff[4172]: > 1 Raw_Read_Error_Rate 0x000f 120 099 006 Pre-fail Always - 242755498 Dec 5 03:40:01 Tower preclear_disk-diff[4172]: 58c58 Dec 5 03:40:01 Tower preclear_disk-diff[4172]: < 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 147 Dec 5 03:40:01 Tower preclear_disk-diff[4172]: --- Dec 5 03:40:01 Tower preclear_disk-diff[4172]: > 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 187276 Dec 5 03:40:01 Tower preclear_disk-diff[4172]: 64c64 Dec 5 03:40:01 Tower preclear_disk-diff[4172]: < 188 Command_Timeout 0x0032 100 253 000 Old_age Always - 0 Dec 5 03:40:01 Tower preclear_disk-diff[4172]: --- Dec 5 03:40:01 Tower preclear_disk-diff[4172]: > 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 Dec 5 03:40:01 Tower preclear_disk-diff[4172]: 66,67c66,67 Dec 5 03:40:01 Tower preclear_disk-diff[4172]: < 190 Airflow_Temperature_Cel 0x0022 070 069 045 Old_age Always - 30 (Lifetime Min/Max 28/30) Dec 5 03:40:01 Tower preclear_disk-diff[4172]: < 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always Dec 5 03:40:01 Tower preclear_disk-diff[4172]: --- Dec 5 03:40:01 Tower preclear_disk-diff[4172]: > 190 Airflow_Temperature_Cel 0x0022 067 064 045 Old_age Always - 33 (Lifetime Min/Max 28/36) Dec 5 03:40:01 Tower preclear_disk-diff[4172]: > 195 Hardware_ECC_Recovered 0x001a 053 040 000 Old_age Always Dec 5 03:40:01 Tower preclear_disk-diff[4172]: 70,73c70,73 Dec 5 03:40:01 Tower preclear_disk-diff[4172]: < 199 UDMA_CRC_Error_Count 0x003e 200 253 000 Old_age Always - 0 Dec 5 03:40:01 Tower preclear_disk-diff[4172]: < 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 79701708111925 Dec 5 03:40:01 Tower preclear_disk-diff[4172]: < 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 8 Dec 5 03:40:01 Tower preclear_disk-diff[4172]: < 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 14999 Dec 5 03:40:01 Tower preclear_disk-diff[4172]: --- Dec 5 03:40:01 Tower preclear_disk-diff[4172]: > 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 Dec 5 03:40:01 Tower preclear_disk-diff[4172]: > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 125340030599250 Dec 5 03:40:01 Tower preclear_disk-diff[4172]: > 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 3906116822 Dec 5 03:40:01 Tower preclear_disk-diff[4172]: > 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 3713874269 Quote Link to comment
mlounsbury Posted December 5, 2010 Share Posted December 5, 2010 So I got my server built on Thursday and started the preclear on both of my drives. Here are the diff results on each drive. They look good to me, although sda has a weird error: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. I did a search on the forum but didn't see anything specific to this message. Here's the rest. sda: root@Lounsbury-unRAID:/tmp# diff smart_start1376 smart_finish1376 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 - 26 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 27 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 sdb: sdb root@Lounsbury-unRAID:/boot# diff smart_start8573 smart_finish8573 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 - 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 Also I've got these errors in the syslog after sdb finished. Everything from the SMART report looks good, so I'm not sure what happened here. Dec 3 16:30:56 Lounsbury-unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen (Errors) Dec 3 16:30:56 Lounsbury-unRAID kernel: ata2.00: failed command: READ FPDMA QUEUED (Minor Issues) Dec 3 16:30:56 Lounsbury-unRAID kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:30:56 Lounsbury-unRAID kernel: ata2.00: failed command: READ FPDMA QUEUED (Minor Issues) Dec 3 16:30:56 Lounsbury-unRAID kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:30:56 Lounsbury-unRAID kernel: ata2: hard resetting link (Minor Issues) Dec 3 16:31:27 Lounsbury-unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen (Errors) Dec 3 16:31:27 Lounsbury-unRAID kernel: ata2.00: failed command: READ FPDMA QUEUED (Minor Issues) Dec 3 16:31:27 Lounsbury-unRAID kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:31:27 Lounsbury-unRAID kernel: ata2.00: failed command: READ FPDMA QUEUED (Minor Issues) Dec 3 16:31:27 Lounsbury-unRAID kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:31:27 Lounsbury-unRAID kernel: ata2: hard resetting link (Minor Issues) Dec 3 16:31:58 Lounsbury-unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen (Errors) Dec 3 16:31:58 Lounsbury-unRAID kernel: ata2.00: failed command: READ FPDMA QUEUED (Minor Issues) Dec 3 16:31:58 Lounsbury-unRAID kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:31:58 Lounsbury-unRAID kernel: ata2.00: failed command: READ FPDMA QUEUED (Minor Issues) Dec 3 16:31:58 Lounsbury-unRAID kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:31:58 Lounsbury-unRAID kernel: ata2: hard resetting link (Minor Issues) Dec 3 16:32:29 Lounsbury-unRAID kernel: ata2.00: NCQ disabled due to excessive errors (Errors) Dec 3 16:32:29 Lounsbury-unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen (Errors) Dec 3 16:32:29 Lounsbury-unRAID kernel: ata2.00: failed command: READ FPDMA QUEUED (Minor Issues) Dec 3 16:32:29 Lounsbury-unRAID kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:32:29 Lounsbury-unRAID kernel: ata2.00: failed command: READ FPDMA QUEUED (Minor Issues) Dec 3 16:32:29 Lounsbury-unRAID kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:32:29 Lounsbury-unRAID kernel: ata2: hard resetting link (Minor Issues) Dec 3 16:33:00 Lounsbury-unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Dec 3 16:33:00 Lounsbury-unRAID kernel: ata2.00: failed command: READ DMA EXT (Minor Issues) Dec 3 16:33:00 Lounsbury-unRAID kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:33:00 Lounsbury-unRAID kernel: ata2: hard resetting link (Minor Issues) Dec 3 16:33:31 Lounsbury-unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Dec 3 16:33:31 Lounsbury-unRAID kernel: ata2.00: failed command: READ DMA EXT (Minor Issues) Dec 3 16:33:31 Lounsbury-unRAID kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:33:31 Lounsbury-unRAID kernel: ata2: hard resetting link (Minor Issues) Dec 3 16:33:32 Lounsbury-unRAID kernel: end_request: I/O error, dev sdb, sector 3876852784 (Errors) Dec 3 16:33:32 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606598 (Errors) Dec 3 16:33:32 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606599 (Errors) Dec 3 16:33:32 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606600 (Errors) Dec 3 16:33:32 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606601 (Errors) Dec 3 16:33:32 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606602 (Errors) Dec 3 16:33:32 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606603 (Errors) Dec 3 16:33:32 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606604 (Errors) Dec 3 16:33:32 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606605 (Errors) Dec 3 16:33:32 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606606 (Errors) Dec 3 16:33:32 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606607 (Errors) Dec 3 16:34:02 Lounsbury-unRAID kernel: ata2.00: limiting speed to UDMA/100:PIO4 (Minor Issues) Dec 3 16:34:02 Lounsbury-unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Dec 3 16:34:02 Lounsbury-unRAID kernel: ata2.00: failed command: READ DMA EXT (Minor Issues) Dec 3 16:34:02 Lounsbury-unRAID kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:34:02 Lounsbury-unRAID kernel: ata2: hard resetting link (Minor Issues) Dec 3 16:34:33 Lounsbury-unRAID kernel: ata2.00: limiting speed to UDMA/33:PIO4 (Minor Issues) Dec 3 16:34:33 Lounsbury-unRAID kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Dec 3 16:34:33 Lounsbury-unRAID kernel: ata2.00: failed command: READ DMA EXT (Minor Issues) Dec 3 16:34:33 Lounsbury-unRAID kernel: res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Dec 3 16:34:33 Lounsbury-unRAID kernel: ata2: hard resetting link (Minor Issues) Dec 3 16:34:34 Lounsbury-unRAID kernel: end_request: I/O error, dev sdb, sector 3876852528 (Errors) Dec 3 16:34:34 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606566 (Errors) Dec 3 16:34:34 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606567 (Errors) Dec 3 16:34:34 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606568 (Errors) Dec 3 16:34:34 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606569 (Errors) Dec 3 16:34:34 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606570 (Errors) Dec 3 16:34:34 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606571 (Errors) Dec 3 16:34:34 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606572 (Errors) Dec 3 16:34:34 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606573 (Errors) Dec 3 16:34:34 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606574 (Errors) Dec 3 16:34:34 Lounsbury-unRAID kernel: Buffer I/O error on device sdb, logical block 484606575 (Errors) Attached are the SMART start and finish logs. Can anyone provide any feedback? Thanks in advance! smart_start1376.txt smart_finish1376.txt smart_start8573.txt smart_finish8573.txt Quote Link to comment
screwonbudnik20 Posted December 5, 2010 Share Posted December 5, 2010 Here are my results sorry about the dual post. 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 100 100 006 Pre-fail Always - 16748 --- > 1 Raw_Read_Error_Rate 0x000f 119 100 006 Pre-fail Always - 217296903 58c58 < 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 20 --- > 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 249367 64c64 < 188 Unknown_Attribute 0x0032 100 253 000 Old_age Always - 0 --- > 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 66,67c66,67 < 190 Airflow_Temperature_Cel 0x0022 079 073 045 Old_age Always - 21 (Lifetime Min/Max 20/21) < 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always --- > 190 Airflow_Temperature_Cel 0x0022 077 073 045 Old_age Always - 23 (Lifetime Min/Max 20/25) > 195 Hardware_ECC_Recovered 0x001a 050 045 000 Old_age Always 70,73c70,73 < 199 UDMA_CRC_Error_Count 0x003e 200 253 000 Old_age Always - 0 < 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 241424406675462 < 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 0 < 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 1380 --- > 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 > 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 241952687652903 > 241 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 4185498537 > 242 Unknown_Attribute 0x0000 100 253 000 Old_age Offline - 547116347 Quote Link to comment
crumshizzle Posted December 6, 2010 Share Posted December 6, 2010 I just purchased 2x WD20EARS drives from Amazon. When I received them, I immediately jumpered 7-8 prior to installing into my unRaid. I tried putting 1 drive in as my new parity drive, replacing a 500GB that I previously had in there as parity. Everything seemed to boot ok and unRaid recognized it, but when it did the re-build of the parity after hitting Start, that's when I seem to be having problems. It was poking along at something ridiculous like 20k/sec and would have taken 3 months (this is probably an exaggeration) to complete. When checking the syslog, I'm getting absurd amounts of this message: Dec 5 15:36:14 media kernel: ata3: drained 32768 bytes to clear DRQ. Dec 5 15:36:14 media kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Dec 5 15:36:14 media kernel: ata3.00: failed command: READ DMA Dec 5 15:36:14 media kernel: ata3.00: cmd c8/00:80:60:68:37/00:00:00:00:00/e0 tag 0 dma 65536 in Dec 5 15:36:14 media kernel: res ff/ff:ff:ff:ff:ff/ff:ff:ff:ff:ff/ff Emask 0x2 (HSM violation) Dec 5 15:36:14 media kernel: ata3.00: status: { Busy } Dec 5 15:36:14 media kernel: ata3.00: error: { ICRC UNC IDNF ABRT } Dec 5 15:36:14 media kernel: ata3: hard resetting link Dec 5 15:36:14 media kernel: ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Dec 5 15:36:14 media kernel: ata3.00: configured for UDMA/33 Dec 5 15:36:14 media kernel: ata3: EH complete This repeats a billion times with a few of these thrown in randomly: Dec 5 15:43:11 media kernel: Buffer I/O error on device sdc, logical block 531648 Dec 5 15:43:11 media kernel: Buffer I/O error on device sdc, logical block 531649 Dec 5 15:43:11 media kernel: Buffer I/O error on device sdc, logical block 531650 Dec 5 15:43:11 media kernel: Buffer I/O error on device sdc, logical block 531651 Dec 5 15:43:11 media kernel: Buffer I/O error on device sdc, logical block 531652 Dec 5 15:43:11 media kernel: Buffer I/O error on device sdc, logical block 531653 Dec 5 15:43:11 media kernel: Buffer I/O error on device sdc, logical block 531654 Dec 5 15:43:11 media kernel: Buffer I/O error on device sdc, logical block 531655 Dec 5 15:43:11 media kernel: Buffer I/O error on device sdc, logical block 531656 Dec 5 15:43:11 media kernel: Buffer I/O error on device sdc, logical block 531657 I canceled the parity, un-assigned the drive in Settings, then ran a preclear (preclear_disk.sh /dev/sdc) on it to test the drive. I'm seeing it take insane amounts of time during the pre-read. I let it run for 36 hours and it ended up getting to 1%, completing around 30gb out of 2tb. I ended up canceling the pre-clear and trying my second drive. Same exact thing on both. I've attached the SMART log that was run prior to the pre-read. It isn't reporting any re-allocated sectors, so I'm not really sure what is going on. From what I've read, the pre-read shouldn't be taking 36 hours to reach 1%. I never ran these drives un-jumpered. They were immediately jumpered out of the box (thanks to reading these forums), then installed into my unRaid. My hardware specs on the system: AMD 2800+ Gigabyte GA-7N400 1.5gb DDR2 RAM 2x 2-port PCI SATA card - different brands. I can't really see what the exact model they are, as they're currently installed. I don't think it's a bad cable/card, as my previous parity drive ran just fine on the same port, but who knows. Can anyone shed some light on what may be happening? I'm thinking I received a set of bad drives, but since I didn't see any re-allocated sectors on the SMART report, I'm not really sure. Thanks in advance for any help! smart_start1528.txt Quote Link to comment
SSD Posted December 6, 2010 Share Posted December 6, 2010 Smart report looks fine. Suggest you post the full syslog for one of the Linux experts to look at. First thought is a cabling problem. Quote Link to comment
crumshizzle Posted December 7, 2010 Share Posted December 7, 2010 Smart report looks fine. Suggest you post the full syslog for one of the Linux experts to look at. First thought is a cabling problem. Attached is a syslog I just collected. I swapped SATA cables as well and am still seeing the same errors. syslog.txt Quote Link to comment
BlackCat Posted December 7, 2010 Share Posted December 7, 2010 Hello, I just ran pre-clear on my first disk. I'm attaching the syslog, I think I have all the correct info in there. I think it looks fine to me, am I correct? Also, should I run pre-clear anymore on this disk? Obviously the day is off by one and the time is wrong because I didn't think to set it in the settings menu, will this affect anything now that I have fixed it? Syslog-Disk1_Preclear-12-07-2010.txt Quote Link to comment
Joe L. Posted December 8, 2010 Share Posted December 8, 2010 Hello, I just ran pre-clear on my first disk. I'm attaching the syslog, I think I have all the correct info in there. I think it looks fine to me, am I correct? Also, should I run pre-clear anymore on this disk? Obviously the day is off by one and the time is wrong because I didn't think to set it in the settings menu, will this affect anything now that I have fixed it? looks fine to me too. The time will not affect the pre-clear. Quote Link to comment
BlackCat Posted December 8, 2010 Share Posted December 8, 2010 Hello, I just ran pre-clear on my first disk. I'm attaching the syslog, I think I have all the correct info in there. I think it looks fine to me, am I correct? Also, should I run pre-clear anymore on this disk? Obviously the day is off by one and the time is wrong because I didn't think to set it in the settings menu, will this affect anything now that I have fixed it? looks fine to me too. The time will not affect the pre-clear. Joe I read earlier in the post that you recommend running a few pre-clear cycles to verify everything is fine. How many cycles do you suggest for a drive that takes 36 hrs to complete? Quote Link to comment
Joe L. Posted December 8, 2010 Share Posted December 8, 2010 Hello, I just ran pre-clear on my first disk. I'm attaching the syslog, I think I have all the correct info in there. I think it looks fine to me, am I correct? Also, should I run pre-clear anymore on this disk? Obviously the day is off by one and the time is wrong because I didn't think to set it in the settings menu, will this affect anything now that I have fixed it? looks fine to me too. The time will not affect the pre-clear. Joe I read earlier in the post that you recommend running a few pre-clear cycles to verify everything is fine. How many cycles do you suggest for a drive that takes 36 hrs to complete? One is probably enough... if you have the time and don't need it immediately, let it run again. Many manufacturers like to burn-in electronics for 48 hours... you've come pretty close to that. Quote Link to comment
BlackCat Posted December 8, 2010 Share Posted December 8, 2010 One is probably enough... if you have the time and don't need it immediately, let it run again. Many manufacturers like to burn-in electronics for 48 hours... you've come pretty close to that. Ok sounds good, I'll run it once more. Better safe than sorry. Once this has finished for the second time, I will be able to populate it while I pre-clear my other drives? I'm pretty sure I read that at the beginning but wanted to make sure. Quote Link to comment
Joe L. Posted December 8, 2010 Share Posted December 8, 2010 One is probably enough... if you have the time and don't need it immediately, let it run again. Many manufacturers like to burn-in electronics for 48 hours... you've come pretty close to that. Ok sounds good, I'll run it once more. Better safe than sorry. Once this has finished for the second time, I will be able to populate it while I pre-clear my other drives? I'm pretty sure I read that at the beginning but wanted to make sure. Yes you can add it to your array and start using it. While the array is online you can pre-clear any drive not assigned to the array. Quote Link to comment
BlackCat Posted December 8, 2010 Share Posted December 8, 2010 Yes you can add it to your array and start using it. While the array is online you can pre-clear any drive not assigned to the array. Thanks Quote Link to comment
Tom899 Posted December 8, 2010 Share Posted December 8, 2010 Hello, I started preclearing my six disks about nine hours ago. This is my 1TB disk. Is step #4 it shows partitions 2,3 & 4. Is this normal for a new drive? I thought it should have one partition. The other disks did not get this far yet because they are 2TB. I'm using unmenu and screen through a putty telnet sesion. It shows it is doing a Post-Read now. Thanks, Tom = unRAID server Pre-Clear disk /dev/sdf = 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 = Post-Read in progress: 30% complete. ( 305,980,416,000 of 1,000,204,886,016 bytes read ) 91.3 MB/s Disk Temperature: 40C, Elapsed Time: 9:09:32 Quote Link to comment
jbuszkie Posted December 8, 2010 Author Share Posted December 8, 2010 If you look back at a couple of other people's posts, you can see this is normal. Joe will have to explain why.... but it's in other's results as well.. Jim Quote Link to comment
Tom899 Posted December 8, 2010 Share Posted December 8, 2010 If you look back at a couple of other people's posts, you can see this is normal. Joe will have to explain why.... but it's in other's results as well.. Jim Ok, thanks Jim Quote Link to comment
Joe L. Posted December 8, 2010 Share Posted December 8, 2010 If you look back at a couple of other people's posts, you can see this is normal. Joe will have to explain why.... but it's in other's results as well.. Jim Ok, thanks Jim A master boot record has positions in it for 4 partitions. unRAID uses only 1. The bytes describing the other possible three must be cleared in case they once held old partitioning information. as described this message is informational and completely normal. Quote Link to comment
Tom899 Posted December 8, 2010 Share Posted December 8, 2010 If you look back at a couple of other people's posts, you can see this is normal. Joe will have to explain why.... but it's in other's results as well.. Jim Ok, thanks Jim A master boot record has positions in it for 4 partitions. unRAID uses only 1. The bytes describing the other possible three must be cleared in case they once held old partitioning information. as described this message is informational and completely normal. Thanks Joe, My disks are about 16 hours into preclear and 12% into Post-Read. 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.