mgworek Posted January 12, 2011 Share Posted January 12, 2011 First time unraid builder. had it working in a test environment, now wanting to build the real server. Ran the Preclear script on 2 brand new drives and have questions on my results. 1. First drive is a western digital ws20ears with the jumper set. The script runs but gives me this message after. 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: (0x82) Offline data collection activity < was completed without error. --- > Offline data collection status: (0x84) Offline data collection activity > was suspended by an interrupting command from host. 63c63 < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 32 --- > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 35 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 2. drive is a samsung HD204UI with the latest patch installed. I ran the script last friday, been out sick till today so did not get to check it at all until now. The script is still running. It says Post-Read in progress: 70% complete. It has been running 114:35:21. Any thoughts on why it would be taking so long? Like I said before, these are 2 new drives. Took them out of package and put them in my server. Thanks! Quote Link to comment
kbowman Posted January 14, 2011 Share Posted January 14, 2011 I am new to this. How does this drive look. ar_disk-finish[5059]: Vendor Specific SMART Attributes with Thresholds: Jan 14 15:46:45 Tower preclear_disk-finish[5059]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Jan 14 15:46:45 Tower preclear_disk-finish[5059]: 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 Jan 14 15:46:45 Tower preclear_disk-finish[5059]: 3 Spin_Up_Time 0x0027 222 222 021 Pre-fail Always - 3858 Jan 14 15:46:45 Tower preclear_disk-finish[5059]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 24 Jan 14 15:46:45 Tower preclear_disk-finish[5059]: 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 Jan 14 15:46:45 Tower preclear_disk-finish[5059]: 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 Jan 14 15:46:45 Tower preclear_disk-finish[5059]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 44 Jan 14 15:46:45 Tower preclear_disk-finish[5059]: 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Jan 14 15:46:45 Tower preclear_disk-finish[5059]: 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Jan 14 15:46:45 Tower preclear_disk-finish[5059]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 20 Jan 14 15:46:45 Tower preclear_disk-finish[5059]: 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 17 Jan 14 15:46:45 Tower preclear_disk-finish[5059]: 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 75 Jan 14 15:46:45 Tower preclear_disk-finish[5059]: 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 Jan 14 15:46:45 Tower preclear_disk-finish[5059]: 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 Jan 14 15:46:45 Tower preclear_disk-finish[5059]: 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 Jan 14 15:46:45 Tower preclear_disk-finish[5059]: 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 Jan 14 15:46:45 Tower preclear_disk-finish[5059]: 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 Jan 14 15:46:45 Tower preclear_disk-finish[5059]: Jan 14 15:46:45 Tower preclear_disk-finish[5059]: SMART Error Log Version: 1 Jan 14 15:46:45 Tower preclear_disk-finish[5059]: No Errors Logged Jan 14 15:46:45 Tower preclear_disk-finish[5059]: Jan 14 15:46:45 Tower preclear_disk-finish[5059]: SMART Self-test log structure revision number 1 Jan 14 15:46:45 Tower preclear_disk-finish[5059]: No self-tests have been logged. [To run self-tests, use: smartctl -t] Jan 14 15:46:45 Tower preclear_disk-finish[5059]: Jan 14 15:46:45 Tower preclear_disk-finish[5059]: Jan 14 15:46:45 Tower preclear_disk-finish[5059]: SMART Selective self-test log data structure revision number 1 Jan 14 15:46:45 Tower preclear_disk-finish[5059]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Jan 14 15:46:45 Tower preclear_disk-finish[5059]: 1 0 0 Not_testing Jan 14 15:46:45 Tower preclear_disk-finish[5059]: 2 0 0 Not_testing Jan 14 15:46:45 Tower preclear_disk-finish[5059]: 3 0 0 Not_testing Jan 14 15:46:45 Tower preclear_disk-finish[5059]: 4 0 0 Not_testing Jan 14 15:46:45 Tower preclear_disk-finish[5059]: 5 0 0 Not_testing Jan 14 15:46:45 Tower preclear_disk-finish[5059]: Selective self-test flags (0x0): Jan 14 15:46:45 Tower preclear_disk-finish[5059]: After scanning selected spans, do NOT read-scan remainder of disk. Jan 14 15:46:45 Tower preclear_disk-finish[5059]: If Selective self-test is pending on power-up, resume after 0 minute delay. Jan 14 15:46:45 Tower preclear_disk-finish[5059]: Jan 14 15:46:45 Tower preclear_disk-diff[5072]: ============================================================================ Jan 14 15:46:45 Tower preclear_disk-diff[5072]: == Jan 14 15:46:45 Tower preclear_disk-diff[5072]: == Disk /dev/sdb has been successfully precleared Jan 14 15:46:45 Tower preclear_disk-diff[5072]: == Jan 14 15:46:45 Tower preclear_disk-diff[5072]: == Ran 1 preclear-disk cycle Jan 14 15:46:45 Tower preclear_disk-diff[5072]: == Jan 14 15:46:45 Tower preclear_disk-diff[5072]: == Using :Read block size = 8225280 Bytes Jan 14 15:46:45 Tower preclear_disk-diff[5072]: == Last Cycle's Pre Read Time : 6:56:19 (80 MB/s) Jan 14 15:46:45 Tower preclear_disk-diff[5072]: == Last Cycle's Zeroing time : 6:05:43 (91 MB/s) Jan 14 15:46:45 Tower preclear_disk-diff[5072]: == Last Cycle's Post Read Time : 13:09:25 (42 MB/s) Jan 14 15:46:45 Tower preclear_disk-diff[5072]: == Last Cycle's Total Time : 26:12:34 Jan 14 15:46:45 Tower preclear_disk-diff[5072]: == Jan 14 15:46:45 Tower preclear_disk-diff[5072]: == Total Elapsed Time 26:12:34 Jan 14 15:46:45 Tower preclear_disk-diff[5072]: == Jan 14 15:46:45 Tower preclear_disk-diff[5072]: == Disk Start Temperature: 22C Jan 14 15:46:45 Tower preclear_disk-diff[5072]: == Jan 14 15:46:45 Tower preclear_disk-diff[5072]: == Current Disk Temperature: 24C, Jan 14 15:46:45 Tower preclear_disk-diff[5072]: == Jan 14 15:46:45 Tower preclear_disk-diff[5072]: ============================================================================ Jan 14 15:46:45 Tower preclear_disk-diff[5072]: S.M.A.R.T. error count differences detected after pre-clear Jan 14 15:46:45 Tower preclear_disk-diff[5072]: note, some 'raw' values may change, but not be an indication of a problem Jan 14 15:46:45 Tower preclear_disk-diff[5072]: 63c63 Jan 14 15:46:45 Tower preclear_disk-diff[5072]: < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 74 Jan 14 15:46:45 Tower preclear_disk-diff[5072]: --- Jan 14 15:46:45 Tower preclear_disk-diff[5072]: > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 75 Quote Link to comment
kbowman Posted January 14, 2011 Share Posted January 14, 2011 sweet! What should I be looking for Quote Link to comment
kbowman Posted January 15, 2011 Share Posted January 15, 2011 And here is my other log that I would like looked at Jan 14 18:41:09 Tower preclear_disk-finish[12885]: SMART overall-health self-assessment test result: PASSED Jan 14 18:41:09 Tower preclear_disk-finish[12885]: Jan 14 18:41:09 Tower preclear_disk-finish[12885]: General SMART Values: Jan 14 18:41:09 Tower preclear_disk-finish[12885]: Offline data collection status: (0x84)^IOffline data collection activity Jan 14 18:41:09 Tower preclear_disk-finish[12885]: ^I^I^I^I^Iwas suspended by an interrupting command from host. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: ^I^I^I^I^IAuto Offline Data Collection: Enabled. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: Self-test execution status: ( 0)^IThe previous self-test routine completed Jan 14 18:41:09 Tower preclear_disk-finish[12885]: ^I^I^I^I^Iwithout error or no self-test has ever Jan 14 18:41:09 Tower preclear_disk-finish[12885]: ^I^I^I^I^Ibeen run. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: Total time to complete Offline Jan 14 18:41:09 Tower preclear_disk-finish[12885]: data collection: ^I^I (39900) seconds. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: Offline data collection Jan 14 18:41:09 Tower preclear_disk-finish[12885]: capabilities: ^I^I^I (0x7b) SMART execute Offline immediate. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: ^I^I^I^I^IAuto Offline data collection on/off support. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: ^I^I^I^I^ISuspend Offline collection upon new Jan 14 18:41:09 Tower preclear_disk-finish[12885]: ^I^I^I^I^Icommand. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: ^I^I^I^I^IOffline surface scan supported. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: ^I^I^I^I^ISelf-test supported. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: ^I^I^I^I^IConveyance Self-test supported. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: ^I^I^I^I^ISelective Self-test supported. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: SMART capabilities: (0x0003)^ISaves SMART data before entering Jan 14 18:41:09 Tower preclear_disk-finish[12885]: ^I^I^I^I^Ipower-saving mode. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: ^I^I^I^I^ISupports SMART auto save timer. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: Error logging capability: (0x01)^IError logging supported. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: ^I^I^I^I^IGeneral Purpose Logging supported. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: Short self-test routine Jan 14 18:41:09 Tower preclear_disk-finish[12885]: recommended polling time: ^I ( 2) minutes. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: Extended self-test routine Jan 14 18:41:09 Tower preclear_disk-finish[12885]: recommended polling time: ^I ( 255) minutes. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: Conveyance self-test routine Jan 14 18:41:09 Tower preclear_disk-finish[12885]: recommended polling time: ^I ( 5) minutes. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: SCT capabilities: ^I (0x3035)^ISCT Status supported. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: ^I^I^I^I^ISCT Feature Control supported. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: ^I^I^I^I^ISCT Data Table supported. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: Jan 14 18:41:09 Tower preclear_disk-finish[12885]: SMART Attributes Data Structure revision number: 16 Jan 14 18:41:09 Tower preclear_disk-finish[12885]: Vendor Specific SMART Attributes with Thresholds: Jan 14 18:41:09 Tower preclear_disk-finish[12885]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Jan 14 18:41:09 Tower preclear_disk-finish[12885]: 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 Jan 14 18:41:09 Tower preclear_disk-finish[12885]: 3 Spin_Up_Time 0x0027 100 253 021 Pre-fail Always - 0 Jan 14 18:41:09 Tower preclear_disk-finish[12885]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 4 Jan 14 18:41:09 Tower preclear_disk-finish[12885]: 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 Jan 14 18:41:09 Tower preclear_disk-finish[12885]: 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 Jan 14 18:41:09 Tower preclear_disk-finish[12885]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 28 Jan 14 18:41:09 Tower preclear_disk-finish[12885]: 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Jan 14 18:41:09 Tower preclear_disk-finish[12885]: 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Jan 14 18:41:09 Tower preclear_disk-finish[12885]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 3 Jan 14 18:41:09 Tower preclear_disk-finish[12885]: 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 2 Jan 14 18:41:09 Tower preclear_disk-finish[12885]: 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 5 Jan 14 18:41:09 Tower preclear_disk-finish[12885]: 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 Jan 14 18:41:09 Tower preclear_disk-finish[12885]: 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 Jan 14 18:41:09 Tower preclear_disk-finish[12885]: 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 Jan 14 18:41:09 Tower preclear_disk-finish[12885]: 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 Jan 14 18:41:09 Tower preclear_disk-finish[12885]: 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 Jan 14 18:41:09 Tower preclear_disk-finish[12885]: Jan 14 18:41:09 Tower preclear_disk-finish[12885]: SMART Error Log Version: 1 Jan 14 18:41:09 Tower preclear_disk-finish[12885]: No Errors Logged Jan 14 18:41:09 Tower preclear_disk-finish[12885]: Jan 14 18:41:09 Tower preclear_disk-finish[12885]: SMART Self-test log structure revision number 1 Jan 14 18:41:09 Tower preclear_disk-finish[12885]: No self-tests have been logged. [To run self-tests, use: smartctl -t] Jan 14 18:41:09 Tower preclear_disk-finish[12885]: Jan 14 18:41:09 Tower preclear_disk-finish[12885]: Jan 14 18:41:09 Tower preclear_disk-finish[12885]: SMART Selective self-test log data structure revision number 1 Jan 14 18:41:09 Tower preclear_disk-finish[12885]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Jan 14 18:41:09 Tower preclear_disk-finish[12885]: 1 0 0 Not_testing Jan 14 18:41:09 Tower preclear_disk-finish[12885]: 2 0 0 Not_testing Jan 14 18:41:09 Tower preclear_disk-finish[12885]: 3 0 0 Not_testing Jan 14 18:41:09 Tower preclear_disk-finish[12885]: 4 0 0 Not_testing Jan 14 18:41:09 Tower preclear_disk-finish[12885]: 5 0 0 Not_testing Jan 14 18:41:09 Tower preclear_disk-finish[12885]: Selective self-test flags (0x0): Jan 14 18:41:09 Tower preclear_disk-finish[12885]: After scanning selected spans, do NOT read-scan remainder of disk. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: If Selective self-test is pending on power-up, resume after 0 minute delay. Jan 14 18:41:09 Tower preclear_disk-finish[12885]: Jan 14 18:41:09 Tower preclear_disk-diff[12898]: ============================================================================ Jan 14 18:41:09 Tower preclear_disk-diff[12898]: == Jan 14 18:41:09 Tower preclear_disk-diff[12898]: == Disk /dev/sda has been successfully precleared Jan 14 18:41:09 Tower preclear_disk-diff[12898]: == Jan 14 18:41:09 Tower preclear_disk-diff[12898]: == Ran 1 preclear-disk cycle Jan 14 18:41:09 Tower preclear_disk-diff[12898]: == Jan 14 18:41:09 Tower preclear_disk-diff[12898]: == Using :Read block size = 8225280 Bytes Jan 14 18:41:09 Tower preclear_disk-diff[12898]: == Last Cycle's Pre Read Time : 8:18:31 (66 MB/s) Jan 14 18:41:09 Tower preclear_disk-diff[12898]: == Last Cycle's Zeroing time : 6:39:32 (83 MB/s) Jan 14 18:41:09 Tower preclear_disk-diff[12898]: == Last Cycle's Post Read Time : 14:08:46 (39 MB/s) Jan 14 18:41:09 Tower preclear_disk-diff[12898]: == Last Cycle's Total Time : 29:07:55 Jan 14 18:41:09 Tower preclear_disk-diff[12898]: == Jan 14 18:41:09 Tower preclear_disk-diff[12898]: == Total Elapsed Time 29:07:55 Jan 14 18:41:09 Tower preclear_disk-diff[12898]: == Jan 14 18:41:09 Tower preclear_disk-diff[12898]: == Disk Start Temperature: 17C Jan 14 18:41:09 Tower preclear_disk-diff[12898]: == Jan 14 18:41:09 Tower preclear_disk-diff[12898]: == Current Disk Temperature: 24C, Jan 14 18:41:09 Tower preclear_disk-diff[12898]: == Jan 14 18:41:09 Tower preclear_disk-diff[12898]: ============================================================================ Jan 14 18:41:09 Tower preclear_disk-diff[12898]: S.M.A.R.T. error count differences detected after pre-clear Jan 14 18:41:09 Tower preclear_disk-diff[12898]: note, some 'raw' values may change, but not be an indication of a problem Jan 14 18:41:09 Tower preclear_disk-diff[12898]: 19,20c19,20 Jan 14 18:41:09 Tower preclear_disk-diff[12898]: < Offline data collection status: (0x80)^IOffline data collection activity Jan 14 18:41:09 Tower preclear_disk-diff[12898]: < ^I^I^I^I^Iwas never started. Jan 14 18:41:09 Tower preclear_disk-diff[12898]: --- Jan 14 18:41:09 Tower preclear_disk-diff[12898]: > Offline data collection status: (0x84)^IOffline data collection activity Jan 14 18:41:09 Tower preclear_disk-diff[12898]: > ^I^I^I^I^Iwas suspended by an interrupting command from host. Jan 14 18:41:09 Tower preclear_disk-diff[12898]: 54c54 Jan 14 18:41:09 Tower preclear_disk-diff[12898]: < 1 Raw_Read_Error_Rate 0x002f 100 253 051 Pre-fail Always - 0 Jan 14 18:41:09 Tower preclear_disk-diff[12898]: --- Jan 14 18:41:09 Tower preclear_disk-diff[12898]: > 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 Jan 14 18:41:09 Tower preclear_disk-diff[12898]: 58c58 Jan 14 18:41:09 Tower preclear_disk-diff[12898]: < 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 Jan 14 18:41:09 Tower preclear_disk-diff[12898]: --- Jan 14 18:41:09 Tower preclear_disk-diff[12898]: > 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 Jan 14 18:41:09 Tower preclear_disk-diff[12898]: 63c63 Jan 14 18:41:09 Tower preclear_disk-diff[12898]: < 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 4 Jan 14 18:41:09 Tower preclear_disk-diff[12898]: --- Jan 14 18:41:09 Tower preclear_disk-diff[12898]: > 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 5 Jan 14 18:41:09 Tower preclear_disk-diff[12898]: 67c67 Jan 14 18:41:09 Tower preclear_disk-diff[12898]: < 199 UDMA_CRC_Error_Count 0x0032 200 253 000 Old_age Always - 0 Jan 14 18:41:09 Tower preclear_disk-diff[12898]: --- Jan 14 18:41:09 Tower preclear_disk-diff[12898]: > 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 Jan 14 18:41:09 Tower preclear_disk-diff[12898]: ============================================================================ Jan 14 18:41:09 Tower preclear_disk-diff[12898]: Quote Link to comment
Joe L. Posted January 15, 2011 Share Posted January 15, 2011 Are there any sectors pending re-allocation? Are there any sectors already re-allocated? Are there any SMART parameters that are marked as FAILING_NOW? Are there any SMART parameters where the normalized VALUE is nearing the failure THRESHOLD? If you don't know what to look for, this might help. Joe L. Quote Link to comment
kbowman Posted January 15, 2011 Share Posted January 15, 2011 Thank you that does. Did you not see anything wrong with that second drive though. I appreciate your help Quote Link to comment
Joe L. Posted January 15, 2011 Share Posted January 15, 2011 Thank you that does. Did you not see anything wrong with that second drive though. I appreciate your help I guess you just do not want to look for yourself. No, nothing wrong with the second disk at this time. Joe L. Quote Link to comment
kbowman Posted January 15, 2011 Share Posted January 15, 2011 I did. I just wanted to be safe. Sorry Quote Link to comment
chuck23322 Posted January 17, 2011 Share Posted January 17, 2011 Hello. First time post here. Just getting started with unRAID. Ultimately this new system will replace my WHS. While awaiting the flash memory I ordered (waiting to register those for the PRO version), I couldn't wait to build the server and get three of my "laying around" hard drives online... to play with. I downloaded/installed 4.7-beta1 (because I want to avoid the jumper issues when formatting, etc), and installed unMenu, mail, etc. Ran pre_clear on all three of the drives. One of them reports as a "known" issue -- a Seagate 7200.11 (SDA) Model Family: Seagate Barracuda 7200.11 family Device Model: ST3750330AS Serial Number: 5QK0169W Firmware Version: SD04 But when I check Seagate's website, there is nothing for my serial number, nor my firmware. Googling, I've read stories of those who have bricked this drive upgrading the firmware when it was not advised/listed on the Seagate website. Attached is the pre-clear results from Seagate SDA (ST3750330AS), and the Western Digital SDB and SDC (B = WD5000AAKS, C = WD5000AAJS ) I'm not sure how to read these results. I know these were removed from 'active' service awhile back... (being 700, 500 and 500 gb respectively -- they had been upgraded in the WHS server to larger drives. I now have the ability with my new build to use them again...) Some of the results come back as "Pre-fail" or "Old_age", and again, not sure how to interpret this data -- informational? Of concern? Example: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0003 191 167 021 Pre-fail Always - 5433 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 38 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x000e 200 200 051 Old_age Always - 0 So I guess I have three basic questions: 1) If Seagate's website for that drive comes back, by serial number, and doesn't have anything listed for my current firmwared of SD04 -- should I just leave it be? 2) The SMARTS info about "Pre-fail" or "Old_age" -- how should I interpret it? 3) And if anyone sees anything else 'weird' in the pre_clear report, I would be grateful for the education. (Pre_clear results attached) PreClear-SDA.txt PreClear-SDB.txt PreClear-SDC.txt Quote Link to comment
BlackCat Posted January 18, 2011 Share Posted January 18, 2011 I ran preclear 3 times on my Seagate drive (Firmware Version: CC34). I have some Raw_Read_Error_Rate errors. I think the drive is fine because on the second and third preclears the value only changed by 1. I wanted to double check since this will be my parity drive. 1st Preclear: < 1 Raw_Read_Error_Rate 0x000f 100 100 006 Pre-fail Always - 143233 > 1 Raw_Read_Error_Rate 0x000f 118 100 006 Pre-fail Always - 199111887 2nd Preclear: < 1 Raw_Read_Error_Rate 0x000f 118 100 006 Pre-fail Always - 199127430 > 1 Raw_Read_Error_Rate 0x000f 117 100 006 Pre-fail Always - 1596701 3rd Preclear: < 1 Raw_Read_Error_Rate 0x000f 117 100 006 Pre-fail Always - 159764581 > 1 Raw_Read_Error_Rate 0x000f 116 100 006 Pre-fail Always - 115106924 Is this something the firmware upgrade to CC35 would help solve? I have attached the system logs just in-case the drive is not fine or more info is needed. Thanks Seagate-Barracuda_Preclear-Syslogs.zip Quote Link to comment
Joe L. Posted January 18, 2011 Share Posted January 18, 2011 I ran preclear 3 times on my Seagate drive (Firmware Version: CC34). I have some Raw_Read_Error_Rate errors. I think the drive is fine because on the second and third preclears the value only changed by 1. I wanted to double check since this will be my parity drive. 1st Preclear: < 1 Raw_Read_Error_Rate 0x000f 100 100 006 Pre-fail Always - 143233 > 1 Raw_Read_Error_Rate 0x000f 118 100 006 Pre-fail Always - 199111887 2nd Preclear: < 1 Raw_Read_Error_Rate 0x000f 118 100 006 Pre-fail Always - 199127430 > 1 Raw_Read_Error_Rate 0x000f 117 100 006 Pre-fail Always - 1596701 3rd Preclear: < 1 Raw_Read_Error_Rate 0x000f 117 100 006 Pre-fail Always - 159764581 > 1 Raw_Read_Error_Rate 0x000f 116 100 006 Pre-fail Always - 115106924 Is this something the firmware upgrade to CC35 would help solve? I have attached the system logs just in-case the drive is not fine or more info is needed. Thanks Only the manufacturer knows how to interpret the "raw" results for most attributes. Read error rates especially. You and I use the "normalized" values. As long as they are above the affiliated failure threshold, they are fine. The faliure threshold is 006 You started out with a value of 100. It INCREASED from 100 (got better) when the first pre-clear and finished with a value of 118. It has the starting to average downward, now at 116, but still better than the factory initialized value of 100. Remember, it has to drop to 6 before the SMART firmware will consider the drive to have failed. Please download the newer preclear_disk.sh script. (Just posted a few days ago) as it has a much easier output format for less-experienced users such as yourself. Upgrading the disk firmware to fix a bug is usually a good idea. Drive manufacturers rarely issue updates unless their problems are very serious. Joe L. Quote Link to comment
BlackCat Posted January 18, 2011 Share Posted January 18, 2011 I ran preclear 3 times on my Seagate drive (Firmware Version: CC34). I have some Raw_Read_Error_Rate errors. I think the drive is fine because on the second and third preclears the value only changed by 1. I wanted to double check since this will be my parity drive. 1st Preclear: < 1 Raw_Read_Error_Rate 0x000f 100 100 006 Pre-fail Always - 143233 > 1 Raw_Read_Error_Rate 0x000f 118 100 006 Pre-fail Always - 199111887 2nd Preclear: < 1 Raw_Read_Error_Rate 0x000f 118 100 006 Pre-fail Always - 199127430 > 1 Raw_Read_Error_Rate 0x000f 117 100 006 Pre-fail Always - 1596701 3rd Preclear: < 1 Raw_Read_Error_Rate 0x000f 117 100 006 Pre-fail Always - 159764581 > 1 Raw_Read_Error_Rate 0x000f 116 100 006 Pre-fail Always - 115106924 Is this something the firmware upgrade to CC35 would help solve? I have attached the system logs just in-case the drive is not fine or more info is needed. Thanks Only the manufacturer knows how to interpret the "raw" results for most attributes. Read error rates especially. You and I use the "normalized" values. As long as they are above the affiliated failure threshold, they are fine. The faliure threshold is 006 You started out with a value of 100. It INCREASED from 100 (got better) when the first pre-clear and finished with a value of 118. It has the starting to average downward, now at 116, but still better than the factory initialized value of 100. Remember, it has to drop to 6 before the SMART firmware will consider the drive to have failed. Please download the newer preclear_disk.sh script. (Just posted a few days ago) as it has a much easier output format for less-experienced users such as yourself. Upgrading the disk firmware to fix a bug is usually a good idea. Drive manufacturers rarely issue updates unless their problems are very serious. Joe L. Thanks Joe, I'll go ahead and download the new script. Quote Link to comment
jsdds Posted January 25, 2011 Share Posted January 25, 2011 I'm preclearing a 2Tb EARS drive and letting it go through three consecutive cycles. The first cycle took 28 hours, the second 20 hours, and the third cycle seems to be going even quicker. The test is currently in Post-Read going at about 110 MB/s at 10% complete. I don't remember that high a speed for the first two cycles. Disk temp is 23 degrees C. Is it normal for preclear cycles to speed up like they seem to be. Is this a bad sign that parts of the disk have been marked bad by a prior cycle? I guess I'll find out sometime after midnight tonight but I wanted to see what you all thought. Thanks Quote Link to comment
Joe L. Posted January 26, 2011 Share Posted January 26, 2011 The first cycle does a pre-read, a write, and a post read. Subsequent consecutive cycles perform a "write" and a post-read. (They get to skip the pre-read since the post-read of the prior cycle acts as the pre-read for the next "write". ) This feature is new on recent versions of the pre-clear script. It used to always do the pre-read on every cycle when asked to perform multiple cycles and they all took the same time. So... the 8 hours difference is easily explained. It was the initial pre-read on the first cycle. Joe L. Quote Link to comment
jsdds Posted January 26, 2011 Share Posted January 26, 2011 Thanks Joe. I feel a lot less anxious now. jsdds Quote Link to comment
Mntneer Posted January 26, 2011 Share Posted January 26, 2011 Jan 25 04:40:01 Tower syslogd 1.4.1: restart. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Jan 25 06:14:29 Tower preclear_disk-finish[28454]: === START OF INFORMATION SECTION === Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Device Model: WDC WD20EARS-00S8B1 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Serial Number: WD-WCAVY5659496 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Firmware Version: 80.00A80 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: User Capacity: 2,000,398,934,016 bytes Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Device is: Not in smartctl database [for details use: -P showall] Jan 25 06:14:29 Tower preclear_disk-finish[28454]: ATA Version is: 8 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: ATA Standard is: Exact ATA specification draft version not indicated Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Local Time is: Tue Jan 25 06:14:29 2011 EST Jan 25 06:14:29 Tower preclear_disk-finish[28454]: SMART support is: Available - device has SMART capability. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: SMART support is: Enabled Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Jan 25 06:14:29 Tower preclear_disk-finish[28454]: === START OF READ SMART DATA SECTION === Jan 25 06:14:29 Tower preclear_disk-finish[28454]: SMART overall-health self-assessment test result: FAILED! Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Drive failure expected in less than 24 hours. SAVE ALL DATA. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: See vendor-specific Attribute list for failed Attributes. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Jan 25 06:14:29 Tower preclear_disk-finish[28454]: General SMART Values: Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Offline data collection status: (0x80)^IOffline data collection activity Jan 25 06:14:29 Tower preclear_disk-finish[28454]: ^I^I^I^I^Iwas never started. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: ^I^I^I^I^IAuto Offline Data Collection: Enabled. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Self-test execution status: ( 0)^IThe previous self-test routine completed Jan 25 06:14:29 Tower preclear_disk-finish[28454]: ^I^I^I^I^Iwithout error or no self-test has ever Jan 25 06:14:29 Tower preclear_disk-finish[28454]: ^I^I^I^I^Ibeen run. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Total time to complete Offline Jan 25 06:14:29 Tower preclear_disk-finish[28454]: data collection: ^I^I (41880) seconds. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Offline data collection Jan 25 06:14:29 Tower preclear_disk-finish[28454]: capabilities: ^I^I^I (0x7b) SMART execute Offline immediate. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: ^I^I^I^I^IAuto Offline data collection on/off support. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: ^I^I^I^I^ISuspend Offline collection upon new Jan 25 06:14:29 Tower preclear_disk-finish[28454]: ^I^I^I^I^Icommand. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: ^I^I^I^I^IOffline surface scan supported. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: ^I^I^I^I^ISelf-test supported. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: ^I^I^I^I^IConveyance Self-test supported. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: ^I^I^I^I^ISelective Self-test supported. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: SMART capabilities: (0x0003)^ISaves SMART data before entering Jan 25 06:14:29 Tower preclear_disk-finish[28454]: ^I^I^I^I^Ipower-saving mode. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: ^I^I^I^I^ISupports SMART auto save timer. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Error logging capability: (0x01)^IError logging supported. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: ^I^I^I^I^IGeneral Purpose Logging supported. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Short self-test routine Jan 25 06:14:29 Tower preclear_disk-finish[28454]: recommended polling time: ^I ( 2) minutes. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Extended self-test routine Jan 25 06:14:29 Tower preclear_disk-finish[28454]: recommended polling time: ^I ( 255) minutes. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Conveyance self-test routine Jan 25 06:14:29 Tower preclear_disk-finish[28454]: recommended polling time: ^I ( 5) minutes. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: SCT capabilities: ^I (0x3031)^ISCT Status supported. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: ^I^I^I^I^ISCT Feature Control supported. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: ^I^I^I^I^ISCT Data Table supported. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Jan 25 06:14:29 Tower preclear_disk-finish[28454]: SMART Attributes Data Structure revision number: 16 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Vendor Specific SMART Attributes with Thresholds: Jan 25 06:14:29 Tower preclear_disk-finish[28454]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Jan 25 06:14:29 Tower preclear_disk-finish[28454]: 1 Raw_Read_Error_Rate 0x002f 131 111 051 Pre-fail Always - 5388 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: 3 Spin_Up_Time 0x0027 181 154 021 Pre-fail Always - 7925 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 16 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: 5 Reallocated_Sector_Ct 0x0033 050 050 140 Pre-fail Always FAILING_NOW 1195 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 58 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 12 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 8 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 82 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: 196 Reallocated_Event_Count 0x0032 196 196 000 Old_age Always - 4 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 70 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Jan 25 06:14:29 Tower preclear_disk-finish[28454]: SMART Error Log Version: 1 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: No Errors Logged Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Jan 25 06:14:29 Tower preclear_disk-finish[28454]: SMART Self-test log structure revision number 1 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: No self-tests have been logged. [To run self-tests, use: smartctl -t] Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Jan 25 06:14:29 Tower preclear_disk-finish[28454]: SMART Selective self-test log data structure revision number 1 Jan 25 06:14:29 Tower preclear_disk-finish[28454]: SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS Jan 25 06:14:29 Tower preclear_disk-finish[28454]: 1 0 0 Not_testing Jan 25 06:14:29 Tower preclear_disk-finish[28454]: 2 0 0 Not_testing Jan 25 06:14:29 Tower preclear_disk-finish[28454]: 3 0 0 Not_testing Jan 25 06:14:29 Tower preclear_disk-finish[28454]: 4 0 0 Not_testing Jan 25 06:14:29 Tower preclear_disk-finish[28454]: 5 0 0 Not_testing Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Selective self-test flags (0x0): Jan 25 06:14:29 Tower preclear_disk-finish[28454]: After scanning selected spans, do NOT read-scan remainder of disk. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: If Selective self-test is pending on power-up, resume after 0 minute delay. Jan 25 06:14:29 Tower preclear_disk-finish[28454]: Jan 25 06:14:30 Tower preclear_disk-diff[29174]: ============================================================================ Jan 25 06:14:30 Tower preclear_disk-diff[29174]: == Jan 25 06:14:30 Tower preclear_disk-diff[29174]: == Disk /dev/sdb has been successfully precleared Jan 25 06:14:30 Tower preclear_disk-diff[29174]: == with a starting sector of 63 Jan 25 06:14:30 Tower preclear_disk-diff[29174]: == Ran 1 preclear-disk cycle Jan 25 06:14:30 Tower preclear_disk-diff[29174]: == Jan 25 06:14:30 Tower preclear_disk-diff[29174]: == Using :Read block size = 8225280 Bytes Jan 25 06:14:30 Tower preclear_disk-diff[29174]: == Last Cycle's Pre Read Time : 12:35:36 (44 MB/s) Jan 25 06:14:30 Tower preclear_disk-diff[29174]: == Last Cycle's Zeroing time : 16:02:30 (34 MB/s) Jan 25 06:14:30 Tower preclear_disk-diff[29174]: == Last Cycle's Post Read Time : 25:45:09 (21 MB/s) Jan 25 06:14:30 Tower preclear_disk-diff[29174]: == Last Cycle's Total Time : 54:24:22 Jan 25 06:14:30 Tower preclear_disk-diff[29174]: == Jan 25 06:14:30 Tower preclear_disk-diff[29174]: == Total Elapsed Time 54:24:22 Jan 25 06:14:30 Tower preclear_disk-diff[29174]: == Jan 25 06:14:30 Tower preclear_disk-diff[29174]: == Disk Start Temperature: 25C Jan 25 06:14:30 Tower preclear_disk-diff[29174]: == Jan 25 06:14:30 Tower preclear_disk-diff[29174]: == Current Disk Temperature: 26C, Jan 25 06:14:30 Tower preclear_disk-diff[29174]: == Jan 25 06:14:30 Tower preclear_disk-diff[29174]: ============================================================================ Jan 25 06:14:30 Tower preclear_disk-diff[29174]: ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb Jan 25 06:14:30 Tower preclear_disk-diff[29174]: ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Jan 25 06:14:30 Tower preclear_disk-diff[29174]: Raw_Read_Error_Rate = 131 200 51 ok 5388 Jan 25 06:14:30 Tower preclear_disk-diff[29174]: Reallocated_Sector_Ct = 50 200 140 FAILING_NOW 1195 Jan 25 06:14:30 Tower preclear_disk-diff[29174]: Reallocated_Event_Count = 196 200 0 ok 4 Jan 25 06:14:30 Tower preclear_disk-diff[29174]: Jan 25 06:14:30 Tower preclear_disk-diff[29174]: *** Failing SMART Attributes in /tmp/smart_finish_sdb *** Jan 25 06:14:30 Tower preclear_disk-diff[29174]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Jan 25 06:14:30 Tower preclear_disk-diff[29174]: 5 Reallocated_Sector_Ct 0x0033 050 050 140 Pre-fail Always FAILING_NOW 1195 Jan 25 06:14:30 Tower preclear_disk-diff[29174]: Jan 25 06:14:30 Tower preclear_disk-diff[29174]: 0 sectors were pending re-allocation before the start of the preclear. Jan 25 06:14:30 Tower preclear_disk-diff[29174]: 70 sectors are pending re-allocation at the end of the preclear, Jan 25 06:14:30 Tower preclear_disk-diff[29174]: a change of 70 in the number of sectors pending re-allocation. Jan 25 06:14:30 Tower preclear_disk-diff[29174]: 0 sectors had been re-allocated before the start of the preclear. Jan 25 06:14:30 Tower preclear_disk-diff[29174]: 1195 sectors are re-allocated at the end of the preclear, Jan 25 06:14:30 Tower preclear_disk-diff[29174]: a change of 1195 in the number of sectors re-allocated. Jan 25 06:14:30 Tower preclear_disk-diff[29174]: SMART overall-health status = FAILED! Jan 25 06:14:30 Tower preclear_disk-diff[29174]: ============================================================================ Jan 25 06:14:30 Tower preclear_disk-diff[29174]: Jan 25 07:40:35 Tower dhcpcd[1166]: sending DHCP_REQUEST for 192.168.1.113 to 192.168.1.1 Jan 25 07:40:35 Tower dhcpcd[1166]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Jan 25 07:40:35 Tower dhcpcd[1166]: DHCP_ACK received from (192.168.1.1) Jan 25 19:40:35 Tower dhcpcd[1166]: sending DHCP_REQUEST for 192.168.1.113 to 192.168.1.1 Jan 25 19:40:35 Tower dhcpcd[1166]: dhcpIPaddrLeaseTime=86400 in DHCP server response. Jan 25 19:40:35 Tower dhcpcd[1166]: DHCP_ACK received from (192.168.1.1) I precleared 2 of my WD 2TB EARS drives. 1st one precleared with no errors, but the second one reported that it failed SMART after preclearing. In looking at the log, I'm assuming the "Reallocated_Sector_Ct" is not a good sign. I didn't jumper these drives, but failed to use the "-A" when running preclear. Should I try running preclear on this drive again, or just go ahead and plan on RMA'ing it. Also, will it matter if I didn't use the "-A" option and not jumper the drives? Quote Link to comment
Joe L. Posted January 26, 2011 Share Posted January 26, 2011 this says it all: ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 131 200 51 ok 5388 Reallocated_Sector_Ct = 50 200 140 [color=red]FAILING_NOW[/color] [b][color=red]1195[/color][/b] Reallocated_Event_Count = 196 200 0 ok 4 *** Failing SMART Attributes in /tmp/smart_finish_sdb *** ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 5 Reallocated_Sector_Ct 0x0033 [color=red]050[/color] 050 [color=red]140[/color] Pre-fail Always FAILING_NOW 1195 0 sectors were pending re-allocation before the start of the preclear. 70 sectors are pending re-allocation at the end of the preclear, a change of 70 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. 1195 sectors are re-allocated at the end of the preclear, a change of 1195 in the number of sectors re-allocated. [color=red]SMART overall-health status = FAILED![/color] RMA the drive. It has failed the pre-clear. It has major problems in reading the disk. Be very happy you did not install it in your server. The re-allocated sector value of 50 is below the failure-threshold for that parameter of 140. Joe L. Quote Link to comment
Mntneer Posted January 26, 2011 Share Posted January 26, 2011 this says it all: ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 131 200 51 ok 5388 Reallocated_Sector_Ct = 50 200 140 [color=red]FAILING_NOW[/color] [b][color=red]1195[/color][/b] Reallocated_Event_Count = 196 200 0 ok 4 *** Failing SMART Attributes in /tmp/smart_finish_sdb *** ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 5 Reallocated_Sector_Ct 0x0033 [color=red]050[/color] 050 [color=red]140[/color] Pre-fail Always FAILING_NOW 1195 0 sectors were pending re-allocation before the start of the preclear. 70 sectors are pending re-allocation at the end of the preclear, a change of 70 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. 1195 sectors are re-allocated at the end of the preclear, a change of 1195 in the number of sectors re-allocated. [color=red]SMART overall-health status = FAILED![/color] RMA the drive. It has failed the pre-clear. It has major problems in reading the disk. Be very happy you did not install it in your server. The re-allocated sector value of 50 is below the failure-threshold for that parameter of 140. Joe L. Thanks Joe. That's what I thought. That's the 2nd of the 3 drives I got from Newegg I'll have to RMA. The other drive turned out perfect. Should I bother doing another preclear on the good drive, and this time use the "-A" option since I'm not jumpering it? Thanks again. Quote Link to comment
Joe L. Posted January 26, 2011 Share Posted January 26, 2011 The other drive turned out perfect. Should I bother doing another preclear on the good drive, and this time use the "-A" option since I'm not jumpering it? Thanks again. If you pre-cleared it already, and it was not yet assigned to the array, and you pre-cleared it without a jumper, you can use: preclear_disk.sh -C 64 /dev/sdX (where sdX = your disks's device) It will convert the pre-clear signature to use a starting sector of 64. It only takes a few seconds. It will only convert if it is currently "precleared" and you did not change the jumper setting since you cleared it. If not, use the "-A" option and run it through another cycle. Joe L. Quote Link to comment
Mntneer Posted January 26, 2011 Share Posted January 26, 2011 The other drive turned out perfect. Should I bother doing another preclear on the good drive, and this time use the "-A" option since I'm not jumpering it? Thanks again. If you pre-cleared it already, and it was not yet assigned to the array, and you pre-cleared it without a jumper, you can use: preclear_disk.sh -C 64 /dev/sdX (where sdX = your disks's device) It will convert the pre-clear signature to use a starting sector of 64. It only takes a few seconds. It will only convert if it is currently "precleared" and you did not change the jumper setting since you cleared it. If not, use the "-A" option and run it through another cycle. Joe L. Okay. I'll do that. Thanks again for all the help. Quote Link to comment
internetfriend Posted January 26, 2011 Share Posted January 26, 2011 Hi you might remember me from fun posts such as "Why is my 2tb drive reporting as 1tb" and "I had to format this drive in partition magic to get all my space on a new drive wtf" Anyways 2 of my 3 drives have finished a 5 pass preclear, and as far as I see I think I am good. If I didnt have the formatting issue I'd just jam ahead, but thought why not ask. results + smart below: SDC ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VA LUE Seek_Error_Rate = 200 100 0 ok 0 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 176 163 021 Pre-fail Always - 6191 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 20 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 150 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 17 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 11 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 25 194 Temperature_Celsius 0x0022 120 116 000 Old_age Always - 30 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SDD == Disk /dev/sdd has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VA LUE Seek_Error_Rate = 200 100 0 ok 0 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. SMARTT ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 176 166 021 Pre-fail Always - 6158 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 20 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 147 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 17 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 11 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 20 194 Temperature_Celsius 0x0022 119 115 000 Old_age Always - 31 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 So if we're good I am going to replace my parity drive and 1 data drive. Are my next steps to replace parity, rebuild, then replace a data drive, and rebuild one more time? thanks all! Quote Link to comment
Joe L. Posted January 26, 2011 Share Posted January 26, 2011 So if we're good I am going to replace my parity drive and 1 data drive. Are my next steps to replace parity, rebuild, then replace a data drive, and rebuild one more time? thanks all! Looks good. I added two steps to your proposed upgrade procedure. next steps to replace parity, rebuild, perform parity check to ensure written parity is readable then replace a data drive, and rebuild one more time then perform parity check to make sure data drive written is readable/ Quote Link to comment
internetfriend Posted January 26, 2011 Share Posted January 26, 2011 Would you run the check that doesn't correct correct errors, or can I just hit check on the stock UNRAID page? Many thanks as always Joe. Quote Link to comment
Joe L. Posted January 26, 2011 Share Posted January 26, 2011 Would you run the check that doesn't correct correct errors, or can I just hit check on the stock UNRAID page? Many thanks as always Joe. Good question. I'd use the stock one when checking the parity drive and the NOCORRECT one when checking the data drive. (Otherwise, it might use an un-readable data drive to potentially update parity) You could use the NOCORRECT for both, but it does no harm if it fixes parity when checking the quality of the initial load of the parity drive. 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.