bmfrosty Posted September 15, 2013 Share Posted September 15, 2013 I hope I within topic here, but even if I'm not, this is probably the place to do it rather than starting a new thread. I found that preclear absolutely wrecked the speed of my array while it was happening. I stopped it, and the array sped back up. I'm using the onboard SATA ports. Could this be attributed to cruddy onboard sata? Would I be better off buying a SAS HBA and feeding off of that instead? Quote Link to comment
garycase Posted September 15, 2013 Share Posted September 15, 2013 I found that preclear absolutely wrecked the speed of my array while it was happening. I stopped it, and the array sped back up. Unless you're using a very slow CPU [e.g. a single-core Atom or a very old Pentium] this should not be the case. And in general the onboard SATA ports are the best ones to use. So ... check the BIOS to confirm you have the SATA mode set to AHCI. Quote Link to comment
bmfrosty Posted September 16, 2013 Share Posted September 16, 2013 Unless you're using a very slow CPU [e.g. a single-core Atom or a very old Pentium] this should not be the case. And in general the onboard SATA ports are the best ones to use. So ... check the BIOS to confirm you have the SATA mode set to AHCI. No. Shouldn't be a CPU issue. I'm running this: root@maxi:~# cat /proc/cpuinfo | grep "model name" model name : AMD A6-5400K APU with Radeon HD Graphics model name : AMD A6-5400K APU with Radeon HD Graphics root@maxi:~# And my drives are all (except the 500gig one I was replacing): root@maxi:~# smartctl -i /dev/sde | grep Model Device Model: WDC WD30EFRX-68AX9N0 root@maxi:~# I'm just wondering if the onboard controller might have been getting overwhelmed. I'm currently in process of rebuilding on to the new 3TB drive (from the 500GB), and it's running at about 100MB/s. Quote Link to comment
garycase Posted September 16, 2013 Share Posted September 16, 2013 Well, the rebuild is going at a VERY good rate, so all's working well now. But a single pre-clear should NOT have caused the array to run notably slower than normal. I've done two pre-clears at once with my Atom and still been able to use the array at normal speeds. One of life's little mysteries I suppose. See if your next pre-clear has the same issue ... but in any event, they're such a rare activity that I wouldn't worry about it as long as everything else is working well. Quote Link to comment
RokleM Posted September 23, 2013 Share Posted September 23, 2013 Any issues with these two new 4T's? ========================================================================1.13 == invoked as: ./preclear_disk.sh -c 3 -M 4 -m rxxxm /dev/sdh == ST4000DX000-1CL160 xx == Disk /dev/sdh has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 8:51:02 (125 MB/s) == Last Cycle's Zeroing time : 8:01:22 (138 MB/s) == Last Cycle's Post Read Time : 19:29:42 (57 MB/s) == Last Cycle's Total Time : 27:32:04 == == Total Elapsed Time 91:32:21 == == Disk Start Temperature: 29C == == Current Disk Temperature: 40C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdh /tmp/smart_finish_sdh ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 117 100 6 ok 152625539 Seek_Error_Rate = 75 100 30 ok 32540935 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 99 100 0 ok 1 Airflow_Temperature_Cel = 60 71 45 near_thresh 40 Temperature_Celsius = 40 29 0 ok 40 Hardware_ECC_Recovered = 35 100 0 ok 152625539 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. 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. ========================================================================1.13 == invoked as: ./preclear_disk.sh -m rxxxm -c 3 -M 4 /dev/sdi == ST4000DM000-1F2168 xx == Disk /dev/sdi has been successfully precleared == with a starting sector of 1 == Ran 3 cycles == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 9:36:21 (115 MB/s) == Last Cycle's Zeroing time : 8:27:13 (131 MB/s) == Last Cycle's Post Read Time : 19:41:18 (56 MB/s) == Last Cycle's Total Time : 28:09:31 == == Total Elapsed Time 94:12:21 == == Disk Start Temperature: 28C == == Current Disk Temperature: 31C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdi /tmp/smart_finish_sdi ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 117 99 6 ok 125490320 Seek_Error_Rate = 60 100 30 ok 1130916 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 97 100 0 ok 3 Airflow_Temperature_Cel = 69 72 45 near_thresh 31 Temperature_Celsius = 31 28 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 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. 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
garycase Posted September 23, 2013 Share Posted September 23, 2013 They look fine. The first one has a relatively low value for the ECC_Recovered parameter, but that's an informational value, not a critical SMART parameter. But the key values are all okay; and neither has any reallocated sectors ... so you're in good shape. Quote Link to comment
RokleM Posted September 23, 2013 Share Posted September 23, 2013 They look fine. The first one has a relatively low value for the ECC_Recovered parameter, but that's an informational value, not a critical SMART parameter. But the key values are all okay; and neither has any reallocated sectors ... so you're in good shape. Something I should keep an eye on? Was going to make this one the parity becuase of the speed... Quote Link to comment
garycase Posted September 23, 2013 Share Posted September 23, 2013 It could simply be the way Seagate reports SMART parameters for that model -- different manufacturers report these differently; and sometimes it's even different on different models. But yes, I'd do a SMART report periodically and see if that value degrades further (gets smaller). Quote Link to comment
Hypknox Posted September 27, 2013 Share Posted September 27, 2013 Hey guys, it's been quite a while since I've added any drives to my array. I just finished preclearing a couple Toshiba PH3300U-1I72 3TB drives, here are the results. Everything seems okay to me, but I'm interested in other opinions. Thanks for the feedback! (2nd Drive results in next post) preclear_start__43NPB2HXS_2013-09-25.txt preclear_rpt__43NPB2HXS_2013-09-25.txt preclear_finish__43NPB2HXS_2013-09-25.txt Quote Link to comment
Hypknox Posted September 27, 2013 Share Posted September 27, 2013 2nd Drive results: preclear_start__43NPAKPYS_2013-09-25.txt preclear_rpt__43NPAKPYS_2013-09-25.txt preclear_finish__43NPAKPYS_2013-09-25.txt Quote Link to comment
garycase Posted September 27, 2013 Share Posted September 27, 2013 Both drives look good. Quote Link to comment
Inimical Posted October 2, 2013 Share Posted October 2, 2013 How does this look? ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 118 100 6 ok 176700400 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 7 100 0 near_thresh 93 Airflow_Temperature_Cel = 66 70 45 near_thresh 34 Temperature_Celsius = 34 30 0 ok 34 No SMART attributes are FAILING_NOW Thanks! preclear_start__Z300S3DM_2013-10-01.txt preclear_rpt__Z300S3DM_2013-10-01.txt preclear_finish__Z300S3DM_2013-10-01.txt Quote Link to comment
garycase Posted October 2, 2013 Share Posted October 2, 2013 How does this look? The report looks good except I don't like the High Fly Write value. But that's not unusual for Seagate drives, so it's probably fine. Quote Link to comment
RobJ Posted October 4, 2013 Share Posted October 4, 2013 How does this look? ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE High_Fly_Writes = 7 100 0 near_thresh 93 How does this look? The report looks good except I don't like the High Fly Write value. I concur. It's strange to see a brand new drive with 93 High_Fly_Writes already, and no other adverse numbers. It could possibly be a faulty sensor, but I'd monitor this drive more than normal, because it *may* have mechanical issues that will shorten its lifetime. But so far, I have never heard of any drives that have failed, whose only SMART warning was a large number of High_Fly_Writes, so we don't want to unnecessarily alarm you. Right now, the drive is fine, and may be fine for years, but I would not be surprised if this drive failed sooner than others of the same model. Quote Link to comment
grither Posted October 9, 2013 Share Posted October 9, 2013 Hi all! i was having parity errors, ran smart reports on all 20 of my drives, and 3 of my drives resulted in having pending sector reallocations. i cleared data off all 3 drives, and am in the process of preclearing here's the results of the preclear...looks like all 41 pending reallcoations have been reallocated. i should add its quite an old drive... any recommendations? its out of warranty... should i add back to my array and keep an eye on it? ditch it? i guess its a judgement call but advice is welcome! ========================================================================1.13 == invoked as: ./preclear_disk.sh -M 4 /dev/sdt == WDC WD30EZRS-00J99B0 WD-WCAWZ0251948 == Disk /dev/sdt 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 : 9:38:55 (86 MB/s) == Last Cycle's Zeroing time : 9:54:39 (84 MB/s) == Last Cycle's Post Read Time : 19:52:11 (41 MB/s) == Last Cycle's Total Time : 39:26:46 == == Total Elapsed Time 39:26:46 == == Disk Start Temperature: 36C == == Current Disk Temperature: 34C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdt /tmp/smart_finish_sdt ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 118 116 0 ok 34 No SMART attributes are FAILING_NOW 41 sectors were pending re-allocation before the start of the preclear. 41 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 -41 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. ============================================================================ ============================================================================ == == S.M.A.R.T Initial Report for /dev/sdt == Disk: /dev/sdt smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD30EZRS-00J99B0 Serial Number: WD-WCAWZ0251948 Firmware Version: 80.00A80 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: Exact ATA specification draft version not indicated Local Time is: Mon Oct 7 21:43:13 2013 CDT 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: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: (53280) 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 153 147 021 Pre-fail Always - 9308 4 Start_Stop_Count 0x0032 094 094 000 Old_age Always - 6899 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 080 080 000 Old_age Always - 14726 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 098 098 000 Old_age Always - 2388 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 206 193 Load_Cycle_Count 0x0032 173 173 000 Old_age Always - 82545 194 Temperature_Celsius 0x0022 116 101 000 Old_age Always - 36 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 41 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 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/sdt == Disk: /dev/sdt smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD30EZRS-00J99B0 Serial Number: WD-WCAWZ0251948 Firmware Version: 80.00A80 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: Exact ATA specification draft version not indicated Local Time is: Wed Oct 9 13:10:00 2013 CDT 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: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: (53280) 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 153 147 021 Pre-fail Always - 9308 4 Start_Stop_Count 0x0032 094 094 000 Old_age Always - 6899 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 080 080 000 Old_age Always - 14765 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 098 098 000 Old_age Always - 2388 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 206 193 Load_Cycle_Count 0x0032 173 173 000 Old_age Always - 82545 194 Temperature_Celsius 0x0022 118 101 000 Old_age Always - 34 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 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 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
garycase Posted October 9, 2013 Share Posted October 9, 2013 The drive looks fine -- in fact the "pending" sectors tested okay, so SMART didn't even reallocate them (you still have 0 reallocated sectors). It's also not all that old a drive -- at least not in terms of power-on hours. It's got less than 15,000 POH ... I've got drives in my array with over 40,000 hours. As you noted, it's a judgment call whether or not to use them. Personally, I'd just use it for a backup drive. Probably 1/3 to 1/2 of my backup drives are repurposed drives like that -- either had minor issues (like your drive), or were replaced with larger drives. Quote Link to comment
grither Posted October 9, 2013 Share Posted October 9, 2013 hi there! i have a second drive's preclear result (mine is also the previous post). thought it might be best to have these results in a separate post. overall i think these look okay, but there is one error called 'reported uncorrect' which i've never seen before... think its a concern? this drive used to be my parity drive, and i recently removed it to upgrade to a 4tb parity. my plan was to add the former drive to the array (ie add this precleared drive to the array) but just a bit unsure what this indicator means. ========================================================================1.13 == invoked as: ./preclear_disk.sh -M 4 /dev/sdc == ST3000DM001-9YN166 W1F0A74C == Disk /dev/sdc 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 : 17:00:19 (49 MB/s) == Last Cycle's Zeroing time : 8:59:07 (92 MB/s) == Last Cycle's Post Read Time : 14:22:40 (57 MB/s) == Last Cycle's Total Time : 40:23:08 == == Total Elapsed Time 40:23:08 == == Disk Start Temperature: 33C == == Current Disk Temperature: 33C, == ============================================================================ ** 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 = 119 105 6 ok 212052856 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 67 67 45 near_thresh 33 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/sdc == Disk: /dev/sdc smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-9YN166 Serial Number: W1F0A74C 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: Mon Oct 7 21:40:26 2013 CDT 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 105 099 006 Pre-fail Always - 9611664 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 097 097 020 Old_age Always - 3335 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 074 060 030 Pre-fail Always - 12974673520 9 Power_On_Hours 0x0032 085 085 000 Old_age Always - 13364 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 70 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 099 099 000 Old_age Always - 1 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 067 063 045 Old_age Always - 33 (Min/Max 30/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 - 47 193 Load_Cycle_Count 0x0032 086 086 000 Old_age Always - 28237 194 Temperature_Celsius 0x0022 033 040 000 Old_age Always - 33 (0 20 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 - 47579647707130 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 26207571582031 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 13735539661044 SMART Error Log Version: 1 ATA Error Count: 1 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 1 occurred at disk power-on lifetime: 12787 hours (532 days + 19 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 d1 00 ff ff ff ef 00 03:13:56.421 READ DMA EXT 25 d1 00 ff ff ff ef 00 03:13:56.401 READ DMA EXT 35 d1 60 ff ff ff ef 00 03:13:56.395 WRITE DMA EXT 35 d1 00 ff ff ff ef 00 03:13:56.392 WRITE DMA EXT 35 d1 a0 ff ff ff ef 00 03:13:56.389 WRITE DMA EXT 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/sdc == Disk: /dev/sdc smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-9YN166 Serial Number: W1F0A74C 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: Wed Oct 9 14:03:34 2013 CDT 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 119 099 006 Pre-fail Always - 212052856 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 097 097 020 Old_age Always - 3335 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 074 060 030 Pre-fail Always - 12974855868 9 Power_On_Hours 0x0032 085 085 000 Old_age Always - 13404 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 70 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 099 099 000 Old_age Always - 1 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 067 063 045 Old_age Always - 33 (Min/Max 30/36) 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 - 47 193 Load_Cycle_Count 0x0032 086 086 000 Old_age Always - 28237 194 Temperature_Celsius 0x0022 033 040 000 Old_age Always - 33 (0 20 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 - 13052405614626 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 27093875101718 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 14329507908586 SMART Error Log Version: 1 ATA Error Count: 1 CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 1 occurred at disk power-on lifetime: 12787 hours (532 days + 19 hours) When the command that caused the error occurred, the device was active or idle. After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 d1 00 ff ff ff ef 00 03:13:56.421 READ DMA EXT 25 d1 00 ff ff ff ef 00 03:13:56.401 READ DMA EXT 35 d1 60 ff ff ff ef 00 03:13:56.395 WRITE DMA EXT 35 d1 00 ff ff ff ef 00 03:13:56.392 WRITE DMA EXT 35 d1 a0 ff ff ff ef 00 03:13:56.389 WRITE DMA EXT 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
garycase Posted October 9, 2013 Share Posted October 9, 2013 Same comment as above => SMART looks okay, but it's a judgment call whether or not to return them to service. Looks like another good candidate for your backup pool Quote Link to comment
grither Posted October 9, 2013 Share Posted October 9, 2013 thanks Gary, no one could ever accuse you of not being a champion for backups!!! :D do you happen to know what the 'reported uncorrect' error means? seems like some of these smart criteria are serious, and some are not, but i've never heard about this one before Quote Link to comment
garycase Posted October 9, 2013 Share Posted October 9, 2013 SMART parameter 187 reports the # of read errors that could not be corrected via the ECC code. Your report still shows a good value for this (99), so I'd just consider it an anomaly and not worry about it. Seagate reports a lot of parameters that other drive manufacturer's don't show ... and most of those extra ones are of little-to-no utility for really analyzing a drive's status. [but they cause a lot of worry ] r.e. being a champion for backup => I certainly believe in backups. My point r.e. these drives is that you've had issues with them; they still look okay; but your "confidence" level is probably low. Using these for backups reduces the number of backup drives you need to buy if you don't already have enough. I know many folks don't bother to backup their arrays -- that's simply a personal choice. I tell all my friends/clients a very simple rule: Always assume your system is going to have a catastrophic failure at midnight => if there's anything you're going to be upset about losing when that happens, back it up; if not; don't worry about it. Quote Link to comment
grither Posted October 10, 2013 Share Posted October 10, 2013 thanks Gary... that's probably a good way to look at backups for me, i tend to burn to dvd almost everything before it goes on my server... the exception is super large movie files....so if i had a catastrophic loss, i could reload the most important parts off dvd but it would be a chore for sure. but at least its something Quote Link to comment
garycase Posted October 10, 2013 Share Posted October 10, 2013 for me, i tend to burn to dvd almost everything before it goes on my server I did the same for several years -- still have 6 400-disc folders full of DVDs. But as the hard drives got large enough, it was FAR more convenient, and less expensive, to simply copy everything to a backup disk before copying it to the servers. A TB of disk space costs ~ $50 (or less) => but can hold over 200 DVDs. So if you paid $0.25/blank DVD, you'd be spending the same amount -- and you'd still have to burn all the DVDs. I simply keep my current backup disk in a caddy; copy everything I'm adding to the server to the backup disk; and when the disk gets full, simpy put it in a case (I use WiebeTech DriveBoxes [ http://www.officemax.com/office-supplies/safes/security-fire-safes/product-prod5014223?cm_mmc=Googlepla-_-Office%20Supplies-_-Safes-_-Security%20Fire%20Safes&ci_src=17588969&ci_sku=23619602 ]; and pop in the next backup disk. Quote Link to comment
grither Posted October 10, 2013 Share Posted October 10, 2013 Great suggestion. Will give it some thought Quote Link to comment
jbuszkie Posted October 10, 2013 Author Share Posted October 10, 2013 How long have some of your 4T drives taken? It's trending that mine will be well over 24hrs.. Possibly closer to 48! Almost 10 hours for the pre-read! :-) Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.