axeman Posted February 18, 2013 Share Posted February 18, 2013 Nothing too bad, other than the second drive looks like it has been bounced a bit at some point in its past: G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 3 thanks for doing what you do Joe! Still waiting on the WD's to finish. I'll post those too. Again - I appreciate you going through these for me. I'm thinking of keeping 1 of the WDs as a warm spare ... keep it pre-cleared, and attached, but not in array until either I run out of space or one of my other drives fail. I saw that idea floated around somewhere, I can't take the credit for it. Quote Link to comment
JustinChase Posted February 19, 2013 Share Posted February 19, 2013 We'll see what the disk looks like after the preclear. It shows 0 sectors re-allocated. (That is good, as it indicates the disk has been able to write successfully to the original sector.) It shows 6 sectors pending re-allocation. (This is bad, as it indicates they were identified in the most recent pass of the badblocks program...) It shows 150 reallocation events, which again indicates a constant trickle of sectors that are unreadable, but can be written in place. (the original "writes" to those blocks were marginal) Now, this can all be explained by either a defective disk drive, OR a drive that is sensitive to power supply noise or low voltages. (as when supplied on either a marginal supply, or connected through a number of high-resistance connectors/splitters, or sharing a power supply rail with a lot of other drives) In other words, if you can, try a different power connection. Did I ask you yet? What specific make/model power supply are you using? And what mix of disks are you powering? Joe L. sadly, still sectors need to be re-allocated = unRAID server Pre-Clear disk /dev/sdk = cycle 1 of 1, partition start on sector 64 = = 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: 27C, Elapsed Time: 10:22:09 ======================================================================== == SAMSUNG HD103UJ S13PJDWS337885 == Disk /dev/sdk has been successfully precleared == with a starting sector of 64 ======================================================================== ** Changed attributes in files: /tmp/smart_start_sdk /tmp/smart_finish_sdk ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 100 99 51 ok 179 Read_Soft_Error_Rate = 100 99 0 ok 177 Airflow_Temperature_Cel = 73 75 0 ok 27 Temperature_Celsius = 73 75 0 ok 27 No SMART attributes are FAILING_NOW 6 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 10 sectors are pending re-allocation at the end of the preclear, a change of 4 in the number of sectors pending re-allocation. 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. I guess I'm gonna just have to order a new drive. Quote Link to comment
Joe L. Posted February 19, 2013 Share Posted February 19, 2013 I guess I'm gonna just have to order a new drive. That is what I'd do. Quote Link to comment
axeman Posted February 19, 2013 Share Posted February 19, 2013 damnit - the slow read keeps coming back from time to time. syslog attached... sorry it's a 7zip, renamed to .zip syslog-2013-02-18_2.zip Quote Link to comment
Joe L. Posted February 19, 2013 Share Posted February 19, 2013 damnit - the slow read keeps coming back from time to time. syslog attached... sorry it's a 7zip, renamed to .zip I would guess you are maxing out your BR10i. Quote Link to comment
axeman Posted February 19, 2013 Share Posted February 19, 2013 damnit - the slow read keeps coming back from time to time. syslog attached... sorry it's a 7zip, renamed to .zip I would guess you are maxing out your BR10i. yeah - i'm thinking that... surprised, but i guess that's the roll of the dice. I wonder if the whole array not assigned thing is causing issues also.. Quote Link to comment
JustinChase Posted February 19, 2013 Share Posted February 19, 2013 I guess I'm gonna just have to order a new drive. That is what I'd do. Well, I don't generally like the idea of using adaptors or splitters for powering the drives, and the SATA cables on my current power supply only have 3 SATA connectors on each cable, but I have 4 drives in each rack, so it's a bit convoluted to connect power to all the drives as it sits; so... I bought a new 650W modular supply with 2 cables with 4 SATA connectors each, and am ordering a third cable with 4 connectors, which will allow me to connect all 12 drives directly to the PS without any adaptors. It will also provide more power, which I doubt I need, but it was the only PS that had the cabling that I needed at the best price, and it's GOLD certified, so it should be more efficient. Once I get the new PS, I'll replace the old one, and get all the drives connected and see if that helps my issues. I doubt this will resolve everything, but it will eliminate the PS as a potential source of the problem, and will make future usage easier for me also. I'm running a preclear on the 3TB drive now, and hope that this time it finishes without problem, since I REALLY need to get some files moved to make space on the existing drives soon. Quote Link to comment
axeman Posted February 19, 2013 Share Posted February 19, 2013 Okay - one more 2TB drive finished its 3rd cycle... can someone look to see if there's anything to be worried about? I see high temp, but otherwise OK? wd_sdc.txt Quote Link to comment
Helmonder Posted February 20, 2013 Share Posted February 20, 2013 I started preclearing a new 4TB Hitachi drive yesterday, I do not do this weekly so I would like to verify: I am at 36% of phase 1 at the moment and this has taken a little over 26 hours... Sounds a bit long not ? Specific command: preclear_disk.sh -w 65536 -r 65536 -b 200 -c 3 /dev/sdc First time I use the commands Joe provided to reduce effect on memory, can it be that those same paramters make the process longer like this ? Speed is like 50 to 60 MB/s Quote Link to comment
trurl Posted February 20, 2013 Share Posted February 20, 2013 I started preclearing a new 4TB Hitachi drive yesterday, I do not do this weekly so I would like to verify: I am at 36% of phase 1 at the moment and this has taken a little over 26 hours... Sounds a bit long not ? Specific command: preclear_disk.sh -w 65536 -r 65536 -b 200 -c 3 /dev/sdc First time I use the commands Joe provided to reduce effect on memory, can it be that those same paramters make the process longer like this ? Speed is like 50 to 60 MB/s Go back to page 73 of this thread for more discussion of these parameters. I was trying to do 3TB. Increased -b parameter is what you need. Quote Link to comment
Helmonder Posted February 20, 2013 Share Posted February 20, 2013 I started preclearing a new 4TB Hitachi drive yesterday, I do not do this weekly so I would like to verify: I am at 36% of phase 1 at the moment and this has taken a little over 26 hours... Sounds a bit long not ? Specific command: preclear_disk.sh -w 65536 -r 65536 -b 200 -c 3 /dev/sdc First time I use the commands Joe provided to reduce effect on memory, can it be that those same paramters make the process longer like this ? Speed is like 50 to 60 MB/s Go back to page 73 of this thread for more discussion of these parameters. I was trying to do 3TB. Increased -b parameter is what you need. Did that but did not find anything concerning a -b parameter... Since there does appear to be a relation with these parameters (I conclude this from your reply) I will take my chances and do the preclear without the extra parameters, if only to see if that makes the difference.. Quote Link to comment
trurl Posted February 20, 2013 Share Posted February 20, 2013 I started preclearing a new 4TB Hitachi drive yesterday, I do not do this weekly so I would like to verify: I am at 36% of phase 1 at the moment and this has taken a little over 26 hours... Sounds a bit long not ? Specific command: preclear_disk.sh -w 65536 -r 65536 -b 200 -c 3 /dev/sdc First time I use the commands Joe provided to reduce effect on memory, can it be that those same paramters make the process longer like this ? Speed is like 50 to 60 MB/s Go back to page 73 of this thread for more discussion of these parameters. I was trying to do 3TB. Increased -b parameter is what you need. Did that but did not find anything concerning a -b parameter... Since there does appear to be a relation with these parameters (I conclude this from your reply) I will take my chances and do the preclear without the extra parameters, if only to see if that makes the difference.. Sorry, wrong thread. Try this instead. When I tried it on 3TB with the defaults (no parameters) I ran out of memory. The originally suggested -b 200 parameter was too conservative and caused it to be very slow. -b 256000 was suggested and I stopped mine during post-read and restarted it like this. Quote Link to comment
Joe L. Posted February 20, 2013 Share Posted February 20, 2013 I started preclearing a new 4TB Hitachi drive yesterday, I do not do this weekly so I would like to verify: I am at 36% of phase 1 at the moment and this has taken a little over 26 hours... Sounds a bit long not ? Specific command: preclear_disk.sh -w 65536 -r 65536 -b 200 -c 3 /dev/sdc First time I use the commands Joe provided to reduce effect on memory, can it be that those same paramters make the process longer like this ? Speed is like 50 to 60 MB/s Go back to page 73 of this thread for more discussion of these parameters. I was trying to do 3TB. Increased -b parameter is what you need. Did that but did not find anything concerning a -b parameter... Since there does appear to be a relation with these parameters (I conclude this from your reply) I will take my chances and do the preclear without the extra parameters, if only to see if that makes the difference.. Sorry, wrong thread. Try this instead. When I tried it on 3TB with the defaults (no parameters) I ran out of memory. The originally suggested -b 200 parameter was too conservative and caused it to be very slow. -b 256000 was suggested and I stopped mine during post-read and restarted it like this. I have no experience with 3TB drives, nor with your disk controllers (whatever they might be, odds are they are not the same as my older motherboard's) Smaller blocks sizes will slow things down some, as more calls to read the disk must occur. If you are getting 50MB/s, then it will take 20 seconds per GB to read the disk. You have 4000 GB to read ( 4000 * 20 = 80,000 seconds = 22.22 hours ) At 26 hours, I'd say something is slowing you down... (buss bandwidth, or disk controller bandwidth) or there are errors showing in your syslog and the disk controller keeps re-setting the disk in an attempt to keep going. Most people get around 100MB/s on the outer cylinders of a disk and 50 to 60 MB/s on the inner cylinders. Joe L. Quote Link to comment
Helmonder Posted February 20, 2013 Share Posted February 20, 2013 I restarted without the parameters and am at 100+ again .. Quote Link to comment
JustinChase Posted February 21, 2013 Share Posted February 21, 2013 I just finished the preclear on the 3TB drive (not the 1TB drive we had been discussing recently). here is the original/first preclear of this drive, which was done simultaneously with the 1TB drive, and with SABnzbd downloading all at the same time... ========================================================================1.13 == invoked as: ./preclear_disk.sh /dev/sde == WL3000GSA6472C WOL240243956 == Disk /dev/sde has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 8:27:08 (98 MB/s) == Last Cycle's Zeroing time : 7:13:44 (115 MB/s) == Last Cycle's Post Read Time : 19:00:23 (43 MB/s) == Last Cycle's Total Time : 34:42:14 == == Total Elapsed Time 34:42:14 == == Disk Start Temperature: 31C == == Current Disk Temperature: 30C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE End-to-End_Error = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 70 69 0 ok 30 Temperature_Celsius = 120 119 0 ok 30 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. 6 sectors are pending re-allocation at the end of the preclear, a change of 6 in the number of sectors pending re-allocation. 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. ============================================================================ This is the report for the preclear that just finished... ======================================================================== 1.14 = unRAID server Pre-Clear disk /dev/sde = 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: 30C, Elapsed Time: 34:47:40 ======================================================================== == WL3000GSA6472C WOL240243956 == Disk /dev/sde has been successfully precleared == with a starting sector of 1 ======================================================================== ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE End-to-End_Error = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 70 72 0 ok 30 Temperature_Celsius = 120 122 0 ok 30 No SMART attributes are FAILING_NOW 6 sectors were pending re-allocation before the start of the preclear. 6 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, a change of -6 in the number of sectors pending re-allocation. 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. It looks like this drive is okay, and can be put into production. Is that an accurate assessment? You suggested earlier that it might be power supply issue causing the issues with the preclear of the 1TB drive, which might have also been the cause of the re-allocated sectors of this drive, I suppose. I'm betting you're going to suggest that I do one more preclear to confirm that there are no issues one more time, but I'm out of space, and don't want to wait another 35 hours to put this disk to use, unless you really think it's necessary. Is it? Quote Link to comment
Joe L. Posted February 21, 2013 Share Posted February 21, 2013 If you need to use it, go ahead, but keep an eye on it. Joe L. Quote Link to comment
JustinChase Posted February 21, 2013 Share Posted February 21, 2013 cool. Thanks again Joe for all your help! Quote Link to comment
blueink Posted February 21, 2013 Share Posted February 21, 2013 Hi, I just precleared my first hard drive and I think everything looks good, but can I get a confirmation? Thank you! ========================================================================1.13 == invoked as: ./preclear_disk.sh -A /dev/sdb == ST4000DX000-1CL160 Z1Z03FXA == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 10:09:50 (109 MB/s) == Last Cycle's Zeroing time : 9:18:16 (119 MB/s) == Last Cycle's Post Read Time : 23:43:48 (46 MB/s) == Last Cycle's Total Time : 43:12:54 == == Total Elapsed Time 43:12:54 == == Disk Start Temperature: 30C == == Current Disk Temperature: 30C, == ============================================================================ ** 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 94589052 Seek_Error_Rate = 72 66 30 ok 17337159 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 70 70 45 near_thresh 30 Hardware_ECC_Recovered = 34 33 0 ok 94589052 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. ============================================================================ ============================================================================ == == S.M.A.R.T Initial Report for /dev/sdb == Disk: /dev/sdb 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: ST4000DX000-1CL160 Serial Number: Z1Z03FXA Firmware Version: CC44 User Capacity: 4,000,787,030,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: Tue Feb 19 10:02:41 2013 PST 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)^IOffline data collection activity ^I^I^I^I^Iwas never started. ^I^I^I^I^IAuto Offline Data Collection: Disabled. Self-test execution status: ( 0)^IThe previous self-test routine completed ^I^I^I^I^Iwithout error or no self-test has ever ^I^I^I^I^Ibeen run. Total time to complete Offline data collection: ^I^I ( 97) seconds. Offline data collection capabilities: ^I^I^I (0x73) SMART execute Offline immediate. ^I^I^I^I^IAuto Offline data collection on/off support. ^I^I^I^I^ISuspend Offline collection upon new ^I^I^I^I^Icommand. ^I^I^I^I^INo Offline surface scan supported. ^I^I^I^I^ISelf-test supported. ^I^I^I^I^IConveyance Self-test supported. ^I^I^I^I^ISelective Self-test supported. SMART capabilities: (0x0003)^ISaves SMART data before entering ^I^I^I^I^Ipower-saving mode. ^I^I^I^I^ISupports SMART auto save timer. Error logging capability: (0x01)^IError logging supported. ^I^I^I^I^IGeneral Purpose Logging supported. Short self-test routine recommended polling time: ^I ( 1) minutes. Extended self-test routine recommended polling time: ^I ( 255) minutes. Conveyance self-test routine recommended polling time: ^I ( 2) minutes. SCT capabilities: ^I (0x50bf)^ISCT Status supported. ^I^I^I^I^ISCT Error Recovery Control supported. ^I^I^I^I^ISCT Feature Control supported. ^I^I^I^I^ISCT Data Table 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 117 100 006 Pre-fail Always - 158814065 3 Spin_Up_Time 0x0003 092 091 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 16 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 066 060 030 Pre-fail Always - 4185556 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 13 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 16 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 070 061 045 Old_age Always - 30 (Min/Max 29/33) 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 - 21 194 Temperature_Celsius 0x0022 030 040 000 Old_age Always - 30 (0 21 0 0) 195 Hardware_ECC_Recovered 0x001a 033 015 000 Old_age Always - 158814065 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 - 109238198206477 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2007430296 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 8206098229 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. == ============================================================================ ============================================================================ == == S.M.A.R.T Final Report for /dev/sdb == Disk: /dev/sdb 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: ST4000DX000-1CL160 Serial Number: Z1Z03FXA Firmware Version: CC44 User Capacity: 4,000,787,030,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: Thu Feb 21 05:15:35 2013 PST 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)^IOffline data collection activity ^I^I^I^I^Iwas never started. ^I^I^I^I^IAuto Offline Data Collection: Disabled. Self-test execution status: ( 0)^IThe previous self-test routine completed ^I^I^I^I^Iwithout error or no self-test has ever ^I^I^I^I^Ibeen run. Total time to complete Offline data collection: ^I^I ( 97) seconds. Offline data collection capabilities: ^I^I^I (0x73) SMART execute Offline immediate. ^I^I^I^I^IAuto Offline data collection on/off support. ^I^I^I^I^ISuspend Offline collection upon new ^I^I^I^I^Icommand. ^I^I^I^I^INo Offline surface scan supported. ^I^I^I^I^ISelf-test supported. ^I^I^I^I^IConveyance Self-test supported. ^I^I^I^I^ISelective Self-test supported. SMART capabilities: (0x0003)^ISaves SMART data before entering ^I^I^I^I^Ipower-saving mode. ^I^I^I^I^ISupports SMART auto save timer. Error logging capability: (0x01)^IError logging supported. ^I^I^I^I^IGeneral Purpose Logging supported. Short self-test routine recommended polling time: ^I ( 1) minutes. Extended self-test routine recommended polling time: ^I ( 255) minutes. Conveyance self-test routine recommended polling time: ^I ( 2) minutes. SCT capabilities: ^I (0x50bf)^ISCT Status supported. ^I^I^I^I^ISCT Error Recovery Control supported. ^I^I^I^I^ISCT Feature Control supported. ^I^I^I^I^ISCT Data Table 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 - 94589052 3 Spin_Up_Time 0x0003 092 091 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 16 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 072 060 030 Pre-fail Always - 17337159 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 56 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 16 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 070 061 045 Old_age Always - 30 (Min/Max 29/33) 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 - 21 194 Temperature_Celsius 0x0022 030 040 000 Old_age Always - 30 (0 21 0 0) 195 Hardware_ECC_Recovered 0x001a 034 015 000 Old_age Always - 94589052 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 - 126014340464696 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 9821467512 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 32052284577 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
RobJ Posted February 21, 2013 Share Posted February 21, 2013 Hi, I just precleared my first hard drive and I think everything looks good, but can I get a confirmation? Thank you! Looks great! Quote Link to comment
Just Me Posted February 22, 2013 Share Posted February 22, 2013 Hey! Even though I've already pre-cleared some hard drives, I have a question about this result. ========================================================================1.13 == invoked as: ./preclear_disk.sh -A /dev/sde == ST3000DM001-1CH166 W1FXXXXX == Disk /dev/sde has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:07:26 (136 MB/s) == Last Cycle's Zeroing time : 5:12:21 (160 MB/s) == Last Cycle's Post Read Time : 17:24:20 (47 MB/s) == Last Cycle's Total Time : 28:45:12 == == Total Elapsed Time 28:45:12 == == Disk Start Temperature: 26C == == Current Disk Temperature: 27C, == ============================================================================ ** 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 = 112 102 6 ok 45647152 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 99 99 99 FAILING_NOW 1 Airflow_Temperature_Cel = 72 74 45 ok 28 Temperature_Celsius = 28 26 0 ok 28 *** Failing SMART Attributes in /tmp/smart_finish_sde *** ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 184 End-to-End_Error 0x0032 099 099 099 Old_age Always FAILING_NOW 1 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. ============================================================================ What does the "End-to-End_Error" ? Should I use the disk ? BTW. I shouldn't use the -A option when using 3 TB+ drives, right? Quote Link to comment
Automatic Posted February 23, 2013 Share Posted February 23, 2013 Well, other than the raw value (Which apparently isn't always a decimal number, so, whoopy) it looks good, although, can someone verify this:- smart_start:- Disk: /dev/sde 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 === Model Family: Seagate Maxtor DiamondMax 22 Device Model: MAXTOR STM31000340AS Serial Number: 5QJ0LLNX Firmware Version: MX15 User Capacity: 1,000,204,886,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Thu Feb 21 15:57:02 2013 GMT ==> WARNING: There are known problems with these drives, AND THIS FIRMWARE VERSION IS AFFECTED, see the following Seagate web pages: http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207931 http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207969 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: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. 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: ( 642) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 232) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103b) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table 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 119 099 006 Pre-fail Always - 205154892 3 Spin_Up_Time 0x0003 093 084 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 882 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 1 7 Seek_Error_Rate 0x000f 065 060 030 Pre-fail Always - 154727137184 9 Power_On_Hours 0x0032 089 089 000 Old_age Always - 10181 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 2 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 288 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 099 000 Old_age Always - 16 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 066 052 045 Old_age Always - 34 (Min/Max 34/34) 194 Temperature_Celsius 0x0022 034 048 000 Old_age Always - 34 (0 14 0 0) 195 Hardware_ECC_Recovered 0x001a 047 014 000 Old_age Always - 205154892 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 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Interrupted (host reset) 30% 9943 - # 2 Short offline Completed without error 00% 9917 - # 3 Short offline Completed without error 00% 9916 - 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. smart_finish:- Disk: /dev/sde 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 === Model Family: Seagate Maxtor DiamondMax 22 Device Model: MAXTOR STM31000340AS Serial Number: 5QJ0LLNX Firmware Version: MX15 User Capacity: 1,000,204,886,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Sat Feb 23 03:41:03 2013 GMT ==> WARNING: There are known problems with these drives, AND THIS FIRMWARE VERSION IS AFFECTED, see the following Seagate web pages: http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207931 http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207969 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: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. 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: ( 642) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 232) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x103b) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table 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 117 099 006 Pre-fail Always - 146458279 3 Spin_Up_Time 0x0003 093 084 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 882 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 1 7 Seek_Error_Rate 0x000f 065 060 030 Pre-fail Always - 154727267036 9 Power_On_Hours 0x0032 089 089 000 Old_age Always - 10217 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 2 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 288 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 099 000 Old_age Always - 16 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 065 052 045 Old_age Always - 35 (Min/Max 34/38) 194 Temperature_Celsius 0x0022 035 048 000 Old_age Always - 35 (0 14 0 0) 195 Hardware_ECC_Recovered 0x001a 046 014 000 Old_age Always - 146458279 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 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Interrupted (host reset) 30% 9943 - # 2 Short offline Completed without error 00% 9917 - # 3 Short offline Completed without error 00% 9916 - 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. preclear_report:- ========================================================================1.13 == invoked as: ./preclear_disk.sh -A -c 3 /dev/sde == MAXTOR STM31000340AS 5QJ0LLNX == Disk /dev/sde 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:53 (81 MB/s) == Last Cycle's Zeroing time : 3:22:10 (82 MB/s) == Last Cycle's Post Read Time : 7:24:22 (37 MB/s) == Last Cycle's Total Time : 10:47:34 == == Total Elapsed Time 35:44:01 == == Disk Start Temperature: 34C == == Current Disk Temperature: 35C, == ============================================================================ ** 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 = 117 119 6 ok 146458279 Spin_Retry_Count = 100 100 97 near_thresh 2 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 65 66 45 near_thresh 35 Temperature_Celsius = 35 34 0 ok 35 Hardware_ECC_Recovered = 46 47 0 ok 146458279 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. ============================================================================ Yes, I do notice the:- ==> WARNING: There are known problems with these drives, AND THIS FIRMWARE VERSION IS AFFECTED, see the following Seagate web pages: http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207931 http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207969 But I've used this drive for > 3 years and it hasn't locked up yet, if it does, I guess I'll just have to replace it. Quote Link to comment
Joe L. Posted February 23, 2013 Share Posted February 23, 2013 Hey! Even though I've already pre-cleared some hard drives, I have a question about this result. ========================================================================1.13 == invoked as: ./preclear_disk.sh -A /dev/sde == ST3000DM001-1CH166 W1FXXXXX == Disk /dev/sde has been successfully precleared == with a starting sector of 1 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 6:07:26 (136 MB/s) == Last Cycle's Zeroing time : 5:12:21 (160 MB/s) == Last Cycle's Post Read Time : 17:24:20 (47 MB/s) == Last Cycle's Total Time : 28:45:12 == == Total Elapsed Time 28:45:12 == == Disk Start Temperature: 26C == == Current Disk Temperature: 27C, == ============================================================================ ** 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 = 112 102 6 ok 45647152 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 99 99 99 FAILING_NOW 1 Airflow_Temperature_Cel = 72 74 45 ok 28 Temperature_Celsius = 28 26 0 ok 28 *** Failing SMART Attributes in /tmp/smart_finish_sde *** ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 184 End-to-End_Error 0x0032 099 099 099 Old_age Always FAILING_NOW 1 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. ============================================================================ What does the "End-to-End_Error" ? Should I use the disk ? BTW. I shouldn't use the -A option when using 3 TB+ drives, right? It indicated the disk has failed.!! The data sent to it did not match that written to the disk.. (probably bad internal memory or electronics on the disk) It is FAILING_NOW, therefore, you should NOT use that disk. RMA it. The "-a or -A" are meaningless on disks larger than 2.2TB and ignored, even if you supply them as command arguments. Quote Link to comment
Joe L. Posted February 23, 2013 Share Posted February 23, 2013 But I've used this drive for > 3 years and it hasn't locked up yet, if it does, I guess I'll just have to replace it. This is not good: Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 2 twice (so far) the disk was not able to spin up to speed. Typically, it indicates significant mechanical wear. There is also a lot of hardware error correction taking place. Notice now the normalized value (46) is getting closer to the failure threshold (0) and the "worst" value (14) is very close. 195 Hardware_ECC_Recovered 0x001a 046 014 000 Old_age Always - 146458279 Quote Link to comment
Just Me Posted February 23, 2013 Share Posted February 23, 2013 Thanks, I'll RMA it. Another 30 hours until I can upgrade my server Quote Link to comment
Automatic Posted February 23, 2013 Share Posted February 23, 2013 But I've used this drive for > 3 years and it hasn't locked up yet, if it does, I guess I'll just have to replace it. This is not good: Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 2 twice (so far) the disk was not able to spin up to speed. Typically, it indicates significant mechanical wear. There is also a lot of hardware error correction taking place. Notice now the normalized value (46) is getting closer to the failure threshold (0) and the "worst" value (14) is very close. 195 Hardware_ECC_Recovered 0x001a 046 014 000 Old_age Always - 146458279 If the spin-retry-count gets higher I'll start taking it as a serious number, but, I've been monitoring these drives for the last 3 months (On my desktop) and it hasn't increased recently, so, for all I know it may have been right as I was placing it in it had a dodgy PSU connection/etc. When I first got this drive I didn't do any real tests on it at-all until ~ 3 months ago. As for the Hardware_ECC, can you explain what that does? Wikipedia just says:- (Vendor specific raw value.) The raw value has different structure for different vendors and is often not meaningful as a decimal number. Only reason why I'm not so eager to take it out of my array is because I obviously no longer have any warrant on it (Had it for 3 years+) so, it's either in my array or being used for nothing. 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.