page3 Posted October 3, 2012 Share Posted October 3, 2012 I'd say the disk is bad... I think 9168 is the highest number of re-allocated sectors I've ever seen on a disk without it being marked as failed. I'd strongly advise not using it in the unRAID array. 5 Reallocated_Sector_Ct 0x0033 087 087 036 Pre-fail Always - 9168 Thanks- thought that looked a bit high for "passed"! I'll ring up for a DOA return tomorrow (7pm here) as the drive is only two days old. Appreciate the help. Quote Link to comment
servion Posted October 3, 2012 Share Posted October 3, 2012 Well, it looks like I may have been looking at the wrong column in this email result... looks like the reallocated sectors are 0? But, there are s few things that are flagged as near_thresh in the difference report. If I look at the pre and post preclear difference log (for example, Spin_Retry_Count ), there is no difference in the individual pre and post tables ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 116 117 6 ok 108888045 Spin_Retry_Count = 100 100 97 near_thresh 9 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 65 67 45 near_thresh 35 Temperature_Celsius = 35 33 0 ok 35 Hardware_ECC_Recovered = 60 54 0 ok 108888045 No SMART attributes are FAILING_NOW The full log is attached to my original post a few posts up, can someone please shed some light on this for me? Thanks! Quote Link to comment
Joe L. Posted October 3, 2012 Share Posted October 3, 2012 I've got an older 750GB barracuda 7200 drive that I went through hell with in the past.... when the whole click of death thing was happening to all the seagate drives. First one crashed after a month, second one after a week, this is the 3rd... it started occasionally clicking after a week or so, so I decided to basically stop using it as opposed to continual RMAs. Fast forward to now ~4 years later... the drive has a 5-year warranty and still has some covered time left, and now I want to see if I can either start using it in the array, or RMA it and hopefully get a good working replacement this time. On windows, I use their SeaTools tool (which they imply is required to show errors to RMA it). Well, all the SeaTools tests (short, long, smart) pass... but using other smart tools, they show issues (100 reallocated sectors). I figured I'd put it into my unraid box and preclear it to see if it can finally kill it... well, it seems to not be getting worse, and I haven't noticed clicking for a while... but I'm hesitant to use it seeing as I remember it scaring me in the past. Can someone look over my preclear results email (which includes the pre and post 3-cycle SMART results)? If either you think its OK to use in the array, or if there's something I can point out when trying to RMA, please let me know! Thanks! Nothing at all wrong with the drive. Joe L. Quote Link to comment
Andrewch Posted October 9, 2012 Share Posted October 9, 2012 Hi everyone, I'm setting up a new system and haven't used the preclear before. I ran 1 cycle and have no idea how to interpret the results. I have a 3tb seagate (sda) and a 3tb WD Green (sdb). They both seem to have big differences. Do you see anything wrong? MB: Asrock B75 Pro3 M, G540, 4gb Patriot Sig Thanks preclear_results.txt Quote Link to comment
Joe L. Posted October 9, 2012 Share Posted October 9, 2012 Hi everyone, I'm setting up a new system and haven't used the preclear before. I ran 1 cycle and have no idea how to interpret the results. I have a 3tb seagate (sda) and a 3tb WD Green (sdb). They both seem to have big differences. Basically, you are looking for no sectors pending re-allocation at the end of the process, and few, if any sectors that have been re-allocated. Also, you are looking for no other parameters where the normalized value has reached its affiliated failure threshold. (Those would be showing FAILING_NOW on their report line) Do you see anything wrong?no Quote Link to comment
Andrewch Posted October 9, 2012 Share Posted October 9, 2012 Thanks so much Joe. Quote Link to comment
ssean Posted October 12, 2012 Share Posted October 12, 2012 Hey guys. I'm new to Unraid and just got my first build completed! I just finished pre-clearing two disks, and I'm somewhat confused by the results. Any help would be appreciated. Disk 1 Disk: /dev/sdc smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-9YN166 Serial Number: S1F0MGNE Firmware Version: CC4C User Capacity: 3,000,592,982,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Fri Oct 12 09:11:52 2012 Local time zone must be set--see zic m SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 575) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 115 100 006 Pre-fail Always - 89809424 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 12 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 517852 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 29 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 12 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 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 073 068 045 Old_age Always - 27 (Min/Max 26/32) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 11 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 24 194 Temperature_Celsius 0x0022 027 040 000 Old_age Always - 27 (0 21 0 0) 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 - 7713761263646 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 30954640505378 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 9464704004932 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. Disk 2 Disk: /dev/sda smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-9YN166 Serial Number: S1F0F0F2 Firmware Version: CC4C User Capacity: 3,000,592,982,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Fri Oct 12 09:35:01 2012 Local time zone must be set--see zic m SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: ( 575) seconds. Offline data collection capabilities: (0x73) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. No Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x3085) SCT Status supported. SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 114 099 006 Pre-fail Always - 72042400 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 12 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 520604 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 30 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 12 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 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 072 068 045 Old_age Always - 28 (Min/Max 27/32) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 11 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 24 194 Temperature_Celsius 0x0022 028 040 000 Old_age Always - 28 (0 21 0 0) 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 - 138611479543838 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 31306800037301 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 9067692847828 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. Quote Link to comment
Joe L. Posted October 12, 2012 Share Posted October 12, 2012 I have no idea why you are including the "diff" for our analysis. There is a report that summarizes the effect of the preclear. It shows how many sectors were pending re-allocation and already re-allocated both before and after the preclear. It also shows those attributes that are failing, or near their failing threshold. Basically, if it does not show re-allocated sectors, and no sectors are pending re-allocation,and there are no attributes failing_now, and the post-read was successful, the disk should be fine. The reports from the preclear are in /boot/preclear_reports. You can look there to see the results. (not in the syslog) Joe L. Quote Link to comment
ssean Posted October 12, 2012 Share Posted October 12, 2012 Sorry Joe. Take a look now. (I didnt realize there was a specific preclear report) Thanks for clearing that up! Quote Link to comment
page3 Posted October 15, 2012 Share Posted October 15, 2012 A quick update - a few weeks ago Joe very kindly helped diagnosing a faulty HDD I had just purchased. The replacement drive has finally turned up, and precleared without any errors. Quote Link to comment
mr-hexen Posted October 16, 2012 Share Posted October 16, 2012 preclearing 30EZRX getting these errors in syslog: Cycle #1 Oct 13 11:22:29 Tower login[6536]: ROOT LOGIN on '/dev/pts/0' from '192.168.1.124' (Logins) Oct 13 11:25:00 Tower kernel: sdg: unknown partition table (Drive related) Oct 13 11:25:28 Tower sSMTP[7924]: Sent mail for root@localhost (221 out.teksavvy.com) uid=0 username=root outbytes=697 Oct 13 11:48:52 Tower kernel: mdcmd (19): spindown 0 (Routine) Oct 13 11:48:52 Tower kernel: mdcmd (20): spindown 1 (Routine) Oct 13 11:48:53 Tower kernel: mdcmd (21): spindown 2 (Routine) Oct 13 11:48:53 Tower kernel: mdcmd (22): spindown 3 (Routine) Oct 13 13:21:32 Tower sSMTP[6021]: Sent mail for root@localhost (221 out.teksavvy.com) uid=0 username=root outbytes=861 Oct 13 15:20:12 Tower sSMTP[30192]: Sent mail for root@localhost (221 out.teksavvy.com) uid=0 username=root outbytes=863 Oct 13 17:36:32 Tower sSMTP[22578]: Sent mail for root@localhost (221 out.teksavvy.com) uid=0 username=root outbytes=866 Oct 13 19:40:25 Tower in.telnetd[14533]: connect from 192.168.1.124 (192.168.1.124) (Routine) Oct 13 19:40:28 Tower login[14534]: ROOT LOGIN on '/dev/pts/0' from '192.168.1.124' (Logins) Oct 13 19:51:39 Tower kernel: mdcmd (23): spindown 3 (Routine) Oct 13 20:27:10 Tower kernel: mdcmd (24): spindown 1 (Routine) Oct 13 20:35:09 Tower sSMTP[22783]: Sent mail for root@localhost (221 out.teksavvy.com) uid=0 username=root outbytes=774 Oct 13 20:35:20 Tower sSMTP[22850]: Sent mail for root@localhost (221 out.teksavvy.com) uid=0 username=root outbytes=583 Oct 13 22:46:59 Tower sSMTP[10966]: Sent mail for root@localhost (221 out.teksavvy.com) uid=0 username=root outbytes=798 Oct 13 22:48:10 Tower apcupsd[2919]: Power failure. (Minor Issues) Oct 13 22:48:11 Tower apcupsd[2919]: Power is back. UPS running on mains. (Minor Issues) Oct 14 01:05:33 Tower sSMTP[4397]: Sent mail for root@localhost (221 out.teksavvy.com) uid=0 username=root outbytes=800 Oct 14 03:40:01 Tower logger: mover started Oct 14 03:40:01 Tower logger: skipping */ Oct 14 03:40:01 Tower logger: mover finished Oct 14 03:53:32 Tower kernel: mdcmd (25): spindown 3 (Routine) Oct 14 03:59:27 Tower sSMTP[29824]: Sent mail for root@localhost (221 out.teksavvy.com) uid=0 username=root outbytes=801 Oct 14 04:16:04 Tower kernel: mdcmd (26): spindown 0 (Routine) Oct 14 04:16:04 Tower kernel: mdcmd (27): spindown 1 (Routine) Oct 14 05:38:55 Tower kernel: ata7.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) Oct 14 05:38:55 Tower kernel: ata7.00: failed command: SMART (Minor Issues) Oct 14 05:38:55 Tower kernel: ata7.00: cmd b0/d0:01:00:4f:c2/00:00:00:00:00/00 tag 0 pio 512 in (Drive related) Oct 14 05:38:55 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Oct 14 05:38:55 Tower kernel: ata7.00: status: { DRDY } (Drive related) Oct 14 05:38:55 Tower kernel: ata7: hard resetting link (Minor Issues) Oct 14 05:39:05 Tower kernel: ata7: softreset failed (device not ready) (Minor Issues) Oct 14 05:39:05 Tower kernel: ata7: hard resetting link (Minor Issues) Oct 14 05:39:09 Tower kernel: ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 300) (Drive related) Oct 14 05:39:09 Tower kernel: ata7.00: configured for UDMA/133 (Drive related) Oct 14 05:39:09 Tower kernel: ata7: EH complete (Drive related) Oct 14 06:49:49 Tower kernel: ata7.00: exception Emask 0x0 SAct 0x7c000000 SErr 0x0 action 0x6 frozen (Errors) Oct 14 06:49:49 Tower kernel: ata7.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Oct 14 06:49:49 Tower kernel: ata7.00: cmd 61/00:d0:c8:81:b0/04:00:49:01:00/40 tag 26 ncq 524288 out (Drive related) Oct 14 06:49:49 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Oct 14 06:49:49 Tower kernel: ata7.00: status: { DRDY } (Drive related) Oct 14 06:49:49 Tower kernel: ata7.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Oct 14 06:49:49 Tower kernel: ata7.00: cmd 61/00:d8:c8:85:b0/04:00:49:01:00/40 tag 27 ncq 524288 out (Drive related) Oct 14 06:49:49 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Oct 14 06:49:49 Tower kernel: ata7.00: status: { DRDY } (Drive related) Oct 14 06:49:49 Tower kernel: ata7.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Oct 14 06:49:49 Tower kernel: ata7.00: cmd 61/00:e0:c8:89:b0/04:00:49:01:00/40 tag 28 ncq 524288 out (Drive related) Oct 14 06:49:49 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Oct 14 06:49:49 Tower kernel: ata7.00: status: { DRDY } (Drive related) Oct 14 06:49:49 Tower kernel: ata7.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Oct 14 06:49:49 Tower kernel: ata7.00: cmd 61/00:e8:c8:8d:b0/04:00:49:01:00/40 tag 29 ncq 524288 out (Drive related) Oct 14 06:49:49 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Oct 14 06:49:49 Tower kernel: ata7.00: status: { DRDY } (Drive related) Oct 14 06:49:49 Tower kernel: ata7.00: failed command: WRITE FPDMA QUEUED (Minor Issues) Oct 14 06:49:49 Tower kernel: ata7.00: cmd 61/00:f0:c8:91:b0/04:00:49:01:00/40 tag 30 ncq 524288 out (Drive related) Oct 14 06:49:49 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) Oct 14 06:49:49 Tower kernel: ata7.00: status: { DRDY } (Drive related) Oct 14 06:49:49 Tower kernel: ata7: hard resetting link (Minor Issues) Oct 14 06:49:51 Tower kernel: ata7: SATA link up 1.5 Gbps (SStatus 113 SControl 300) (Drive related) Oct 14 06:49:51 Tower kernel: ata7.00: configured for UDMA/133 (Drive related) Oct 14 06:49:51 Tower kernel: ata7.00: device reported invalid CHS sector 0 (Drive related) Oct 14 06:49:51 Tower last message repeated 4 times Oct 14 06:49:51 Tower kernel: ata7: EH complete (Drive related) Oct 14 07:48:34 Tower sSMTP[30788]: Sent mail for root@localhost (221 out.teksavvy.com) uid=0 username=root outbytes=670 Oct 14 07:49:15 Tower kernel: sdg: sdg1 (Drive related) Quote Link to comment
mr-hexen Posted October 16, 2012 Share Posted October 16, 2012 Cycle #2: attached cycle2.txt Quote Link to comment
mr-hexen Posted October 16, 2012 Share Posted October 16, 2012 after cycle #1 no sectors pending or re-allocated but raw read err rate went from 0 to 24. cycle 2 not complete. Quote Link to comment
mr-hexen Posted October 17, 2012 Share Posted October 17, 2012 cycle #2 completed with no changes to sectors or pending sectors. raw read error rate changed from 24 to 108. i put the drive in a different hot swap bay to eliminate cable/port/dock as the cause and started cycle #3. Quote Link to comment
Joe L. Posted October 17, 2012 Share Posted October 17, 2012 cycle #2 completed with no changes to sectors or pending sectors. raw read error rate changed from 24 to 108. i put the drive in a different hot swap bay to eliminate cable/port/dock as the cause and started cycle #3. ALL drives have raw read errors. Every one... some report them, some just retry. You can ignore the "raw" read-errors parameter UNLESS the normalized value reaches the affiliated failure threshold. Quote Link to comment
mr-hexen Posted October 17, 2012 Share Posted October 17, 2012 thanks Joe. What about the syslog errors during clearing? Quote Link to comment
ldrax Posted October 29, 2012 Share Posted October 29, 2012 I'm doing an initial preclear for my 3TB Seagate drive, the following is the result if the first cycle, should I be concerned with the 'near threshold' statuses? == ST3000DM001-9YN166 Z1F12YES == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 ============================================================================ ** 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 = 115 117 6 ok 98467112 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 57 64 45 near_thresh 43 Temperature_Celsius = 43 36 0 ok 43 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 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. a side note, I simultaneously precleared this disk with two other drives (2TB Hitachi and WD Green), surprisingly the preclear for this disk finished earlier! Quote Link to comment
Joe L. Posted October 29, 2012 Share Posted October 29, 2012 I'm doing an initial preclear for my 3TB Seagate drive, the following is the result if the first cycle, should I be concerned with the 'near threshold' statuses?No, for those parameters the manufacturer simply has set the failure threshold high. (only a few failures to spin up in a timely manner would cause the drive to fail SMART tests) The "normalized" values are still at their starting values from the factory and the raw value has no errors. a side note, I simultaneously precleared this disk with two other drives (2TB Hitachi and WD Green), surprisingly the preclear for this disk finished earlier! Some disks are faster, others slower... (same for disk controller ports) Quote Link to comment
ldrax Posted October 29, 2012 Share Posted October 29, 2012 No, for those parameters the manufacturer simply has set the failure threshold high. (only a few failures to spin up in a timely manner would cause the drive to fail SMART tests) The "normalized" values are still at their starting values from the factory and the raw value has no errors. Some disks are faster, others slower... (same for disk controller ports) Thanks Joe! Also, I suppose there's no difference if I do one cycle at a time and repeat three times, rather than 3 cycles in one go? Quote Link to comment
Joe L. Posted October 29, 2012 Share Posted October 29, 2012 No, for those parameters the manufacturer simply has set the failure threshold high. (only a few failures to spin up in a timely manner would cause the drive to fail SMART tests) The "normalized" values are still at their starting values from the factory and the raw value has no errors. Some disks are faster, others slower... (same for disk controller ports) Thanks Joe! Also, I suppose there's no difference if I do one cycle at a time and repeat three times, rather than 3 cycles in one go? three at once is quicker, since the post-read phase of the first acts as the pre-read phase of the second, and the post-read phase of the second acts as the pre-read phase of the third. You save two "read" phases, so probably 6 to 8 hours or more with large disks is saved. Quote Link to comment
mmgarci30 Posted November 2, 2012 Share Posted November 2, 2012 Hi mates, I've just received 2 new WD30EFRX (3Tb RED Edition) one of them I forgot to preclear ir so no data. But This is the results. ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sdb = cycle 1 of 1, partition start on sector 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 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 31C, Elapsed Time: 35:22:10 ========================================================================1.13 == WDC WD30EFRX-68AX9N0 WD-WMC1T0667118 == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 119 120 0 ok 31 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 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. The box is a HP Microserver NL36, 8GB of ram, the bios is flashed to the last revision that allows a few more options in the shouthbridge. All ports in ACHI mode full speed. The disk I,m preclearing is in one of the disk slots through the minisas cable. UnRaid 5.0-beta14 It looks strange, in the preclear and postclear phases it begans a 145mb/s pretty good speed, but after a few minutes the speeds progresively slow down till 45mb/s where booth read phases are around 60% it speed up again to 120 / 125 mb/s and then progresively slow down again till finish. All the time there is no body accessing de array and the IO wait in a top command grows till 85%. When I've precleared mi WD20EARX 10 months ago I don't think they took so long ... Has somebody reported that slows down? I will update the pendrive, take a look to the bios and make a new test. Thanks. Quote Link to comment
whipdancer Posted November 3, 2012 Share Posted November 3, 2012 Based on what I've read in this thread (and these boards), I think theses drives should be ok. Any feedback? I did run badblocks prior to running preclear 3 cycles (both drives): ========================================================================1.13 == invoked as: ./preclear_disk.sh -M 3 -c 3 /dev/sdd == Hitachi HDT721010SLA360 STF604MR20HZ0P == Disk /dev/sdd has been successfully precleared == with a starting sector of 64 == Ran 3 cycles == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 3:24:52 (81 MB/s) == Last Cycle's Zeroing time : 3:06:57 (89 MB/s) == Last Cycle's Post Read Time : 8:11:33 (33 MB/s) == Last Cycle's Total Time : 11:19:38 == == Total Elapsed Time 37:32:40 == == Disk Start Temperature: 37C == == Current Disk Temperature: 38C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 157 162 0 ok 38 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 5 sectors had been re-allocated before the start of the preclear. 5 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ ========================================================================1.13 == invoked as: ./preclear_disk.sh -M 3 -c 3 /dev/sdk == Hitachi HDT721010SLA360 STF607MH32SY3K == Disk /dev/sdk has been successfully precleared == with a starting sector of 64 == Ran 3 cycles == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 3:28:25 (79 MB/s) == Last Cycle's Zeroing time : 3:10:20 (87 MB/s) == Last Cycle's Post Read Time : 8:15:26 (33 MB/s) == Last Cycle's Total Time : 11:26:53 == == Total Elapsed Time 38:07:19 == == Disk Start Temperature: 34C == == Current Disk Temperature: 35C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdk /tmp/smart_finish_sdk ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 171 176 0 ok 35 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 1 sector had been re-allocated before the start of the preclear. 1 sector is re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ Thanks, ~Whip Quote Link to comment
ldrax Posted November 3, 2012 Share Posted November 3, 2012 after 97 hours of 3 cycles of preclearing a 3TB drive, this is the result. There were 65535 sectors pending re-allocation for the whole time, and no sectors had been reallocated at any cycle. I guess I need to run another cycle or two, but wondering if the result will still be the same. ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Seek_Error_Rate = 100 200 0 ok 0 Power_On_Hours = 89 90 0 ok 8064 Temperature_Celsius = 111 121 0 ok 41 No SMART attributes are FAILING_NOW 65535 sectors were pending re-allocation before the start of the preclear. 65535 sectors were pending re-allocation after pre-read in cycle 1 of 3. 65535 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 65535 sectors were pending re-allocation after post-read in cycle 1 of 3. 65535 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 65535 sectors were pending re-allocation after post-read in cycle 2 of 3. 65535 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 65535 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. ============================================================================ Quote Link to comment
gmcc Posted November 3, 2012 Share Posted November 3, 2012 These numbers seem very high, should I be concerned? ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 119 115 6 ok 223319186 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 65 67 45 In_the_past 35 Temperature_Celsius = 35 33 0 ok 35 Hardware_ECC_Recovered = 34 19 0 ok 133354662892690 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 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 0x000f 115 099 006 Pre-fail Always - 93331008 3 Spin_Up_Time 0x0003 091 087 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 096 020 Old_age Always - 85 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 074 060 030 Pre-fail Always - 27171043 9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1021 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 25 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 066 000 Old_age Always - 12331039263543 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 067 040 045 Old_age Always In_the_past 33 (14 151 33 30) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 8 193 Load_Cycle_Count 0x0032 097 097 000 Old_age Always - 7082 194 Temperature_Celsius 0x0022 033 060 000 Old_age Always - 33 (0 22 0 0) 195 Hardware_ECC_Recovered 0x001a 019 007 000 Old_age Always - 239947031256640 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 - 268478405673922 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 1077738321 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 1621575892 Quote Link to comment
Evin Posted November 11, 2012 Share Posted November 11, 2012 Hi! My drives just have finished the first preclear-round and I have to admit that I have no idea if everything went ok... https://dl.dropbox.com/u/3485341/temp/preclear_results.txt Right now, the preclear-script is doing it's magic again. In which case the drives should be considered as unsafe to proceed? PS: Wow, It's been 2 years since registering and actually start building a server... 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.