KuniD Posted March 28, 2016 Share Posted March 28, 2016 Opportunity has come up to buy a used (2 month old) ST8000AS0002 at a decent price. I asked for a SMART readout out and the person sent this; I have to admit I'm no expert at analysing SMART results, what do you all think? Quote Link to comment
JorgeB Posted March 28, 2016 Share Posted March 28, 2016 SMART looks fine, at least once reached 57C, not ideal but not over the limit, so it should be fine. Quote Link to comment
danioj Posted March 28, 2016 Share Posted March 28, 2016 SMART is fine. Temperature is no issue. Not even a bit. Any suggestion it is is Anecdoatal. The drives have operating temperature up to ~70'C. Quote Link to comment
JorgeB Posted March 28, 2016 Share Posted March 28, 2016 SMART is fine. Temperature is no issue. Not even a bit. Any suggestion it is is Anecdoatal. The drives have operating temperature up to ~70'C. Agree that it shouldn't be a problem, but most disks, including this one, have a max operating temperature of 60C. Quote Link to comment
danioj Posted March 28, 2016 Share Posted March 28, 2016 SMART is fine. Temperature is no issue. Not even a bit. Any suggestion it is is Anecdoatal. The drives have operating temperature up to ~70'C. Agree that it shouldn't be a problem, but most disks, including this one, have a max operating temperature of 60C. True Blue ... Quote Link to comment
KuniD Posted March 28, 2016 Share Posted March 28, 2016 Great. Re temp's all my ST8000AS0002's are running at 31-38 deg C so hopefully I'll be giving it a better home ;-) Gotta love the Fractal R5! This'll be 8Tb Archive drive no 6! Quote Link to comment
garycase Posted March 28, 2016 Author Share Posted March 28, 2016 ... This'll be 8Tb Archive drive no 6! Have you seen Daniel's mod to the R5 that allows you to install 18 drives? ... only 12 more 8TB drives to go to fill it up Quote Link to comment
KuniD Posted March 30, 2016 Share Posted March 30, 2016 ... This'll be 8Tb Archive drive no 6! Have you seen Daniel's mod to the R5 that allows you to install 18 drives? ... only 12 more 8TB drives to go to fill it up Just read up on it, wow who knew you could cram that many in ;-) Unfortunately I've got a huge tower cooler on my Xeon, so I won't able to hang any off the top. Additional four at the bottom could happen though... ! Quote Link to comment
methanoid Posted March 30, 2016 Share Posted March 30, 2016 ... This'll be 8Tb Archive drive no 6! Have you seen Daniel's mod to the R5 that allows you to install 18 drives? ... only 12 more 8TB drives to go to fill it up Can't find it.. my search skills fail Unless its the one with 14 HDDs and 2 SSDs? I did that in my old R3 but wondered if there was a better way to fit 18 drives ... the 14+2 drive one just looks the same to me Quote Link to comment
danioj Posted March 30, 2016 Share Posted March 30, 2016 ... This'll be 8Tb Archive drive no 6! Have you seen Daniel's mod to the R5 that allows you to install 18 drives? ... only 12 more 8TB drives to go to fill it up Can't find it.. my search skills fail Unless its the one with 14 HDDs and 2 SSDs? I did that in my old R3 but wondered if there was a better way to fit 18 drives ... the 14+2 drive one just looks the same to me Here is the post about my mod in my build thread: https://lime-technology.com/forum/index.php?topic=37567.msg458891#msg458891 Quote Link to comment
KuniD Posted April 2, 2016 Share Posted April 2, 2016 Archive drive no. 4 (sdf) pre-clear results: ================================================================== 1.15b = unRAID server Pre-Clear disk /dev/sdf = cycle 3 of 3, partition start on sector 1 = = 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: 29C, Elapsed Time: 134:20:09 ========================================================================1.15b == ST8000AS0002-XXXXX XXXXXXXXX == Disk /dev/sdf has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 118 119 6 ok 201104656 Seek_Error_Rate = 78 76 30 ok 81325946 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 71 72 45 ok 29 Temperature_Celsius = 29 28 0 ok 29 Hardware_ECC_Recovered = 118 119 0 ok 201104656 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. Here's the long SMART result for the above drive === 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: ( 0) 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: ( 951) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x30a5) SCT Status 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 - 144272752 3 Spin_Up_Time 0x0003 090 090 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 13 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 079 060 030 Pre-fail Always - 86332858 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 860 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 13 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 063 045 Old_age Always - 28 (Min/Max 21/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 - 17 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 50 194 Temperature_Celsius 0x0022 028 040 000 Old_age Always - 28 (0 21 0 0 0) 195 Hardware_ECC_Recovered 0x001a 117 099 000 Old_age Always - 144272752 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 - 66743791780146 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 93768319256 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 128604004367 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 Completed without error 00% 856 - # 2 Extended offline Completed without error 00% 543 - # 3 Extended offline Aborted by host 90% 528 - 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. Archive drive no. 5 (sdf) pre-clear results: ================================================================== 1.15b = unRAID server Pre-Clear disk /dev/sdg = cycle 3 of 3, partition start on sector 1 = = 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: 33C, Elapsed Time: 135:32:29 ========================================================================1.15b == ST8000AS0002-XXXXX XXXXXXXXX == Disk /dev/sdg has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdg /tmp/smart_finish_sdg ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 103 100 6 ok 5306480 Seek_Error_Rate = 75 100 30 ok 38391244 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 67 70 45 near_thresh 33 Temperature_Celsius = 33 30 0 ok 33 Hardware_ECC_Recovered = 103 100 0 ok 5306480 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. Here's the long SMART result for the above drive 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: ( 0) 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: ( 957) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x30a5) SCT Status 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 - 202585176 3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 1 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 076 060 030 Pre-fail Always - 43445070 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 163 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 1 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 069 065 045 Old_age Always - 31 (Min/Max 22/35) 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 - 4 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 29 194 Temperature_Celsius 0x0022 031 040 000 Old_age Always - 31 (0 22 0 0 0) 195 Hardware_ECC_Recovered 0x001a 119 099 000 Old_age Always - 202585176 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 - 96052648607899 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 46884159680 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 64301985610 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 Completed without error 00% 159 - 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. Just about to start pre-clear on drive number 6... Quote Link to comment
danioj Posted April 2, 2016 Share Posted April 2, 2016 Archive drive no. 4 (sdf) pre-clear results: ================================================================== 1.15b = unRAID server Pre-Clear disk /dev/sdf = cycle 3 of 3, partition start on sector 1 = = 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: 29C, Elapsed Time: 134:20:09 ========================================================================1.15b == ST8000AS0002-XXXXX XXXXXXXXX == Disk /dev/sdf has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 118 119 6 ok 201104656 Seek_Error_Rate = 78 76 30 ok 81325946 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 71 72 45 ok 29 Temperature_Celsius = 29 28 0 ok 29 Hardware_ECC_Recovered = 118 119 0 ok 201104656 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. Here's the long SMART result for the above drive === 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: ( 0) 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: ( 951) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x30a5) SCT Status 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 - 144272752 3 Spin_Up_Time 0x0003 090 090 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 13 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 079 060 030 Pre-fail Always - 86332858 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 860 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 13 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 063 045 Old_age Always - 28 (Min/Max 21/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 - 17 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 50 194 Temperature_Celsius 0x0022 028 040 000 Old_age Always - 28 (0 21 0 0 0) 195 Hardware_ECC_Recovered 0x001a 117 099 000 Old_age Always - 144272752 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 - 66743791780146 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 93768319256 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 128604004367 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 Completed without error 00% 856 - # 2 Extended offline Completed without error 00% 543 - # 3 Extended offline Aborted by host 90% 528 - 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. Almost perfect preclear and extended SMART test. I say almost as I note that the Raw_Read_Error_Rate variable decreased after the preclear and then after the extended SMART test too. I don't think it is anything to worry about BUT I would just keep an eye on it for further decreases. Archive drive no. 5 (sdf) pre-clear results: ================================================================== 1.15b = unRAID server Pre-Clear disk /dev/sdg = cycle 3 of 3, partition start on sector 1 = = 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: 33C, Elapsed Time: 135:32:29 ========================================================================1.15b == ST8000AS0002-XXXXX XXXXXXXXX == Disk /dev/sdg has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdg /tmp/smart_finish_sdg ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 103 100 6 ok 5306480 Seek_Error_Rate = 75 100 30 ok 38391244 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 67 70 45 near_thresh 33 Temperature_Celsius = 33 30 0 ok 33 Hardware_ECC_Recovered = 103 100 0 ok 5306480 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. Here's the long SMART result for the above drive 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: ( 0) 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: ( 957) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x30a5) SCT Status 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 - 202585176 3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 1 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 076 060 030 Pre-fail Always - 43445070 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 163 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 1 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 069 065 045 Old_age Always - 31 (Min/Max 22/35) 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 - 4 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 29 194 Temperature_Celsius 0x0022 031 040 000 Old_age Always - 31 (0 22 0 0 0) 195 Hardware_ECC_Recovered 0x001a 119 099 000 Old_age Always - 202585176 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 - 96052648607899 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 46884159680 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 64301985610 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 Completed without error 00% 159 - 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. Perfect results here. I would deploy both of these into service without hesitation (noting of course the ongoing monitoring of 1 attribute on the first disk). Quote Link to comment
tyrindor Posted April 21, 2016 Share Posted April 21, 2016 Anyone got data rebuild times with a system using all 8TB shingled drives? I see mixed resulted in here, one person claiming (4!) days and another claiming 16 hours. Quote Link to comment
JorgeB Posted April 21, 2016 Share Posted April 21, 2016 Anyone got data rebuild times with a system using all 8TB shingled drives? I see mixed resulted in here, one person claiming (4!) days and another claiming 16 hours. The time I posted on your other thread was from a rebuild, it's also on this thread somewhere. Quote Link to comment
KuniD Posted April 23, 2016 Share Posted April 23, 2016 Drive number 6... ================================================================== 1.15b = unRAID server Pre-Clear disk /dev/sdg = cycle 3 of 3, partition start on sector 1 = = 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: 139:47:27 ========================================================================1.15b == ST8000AS0002-1NA17Z XXXXXXXX == Disk /dev/sdg has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdg /tmp/smart_finish_sdg ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 102 117 6 ok 3736704 Seek_Error_Rate = 76 64 30 ok 42251182 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 69 75 45 In_the_past 31 Temperature_Celsius = 31 25 0 ok 31 Hardware_ECC_Recovered = 102 117 0 ok 3736704 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. And long SMART results === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED See vendor-specific Attribute list for marginal Attributes. 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: ( 0) 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: ( 961) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x30a5) SCT Status 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 - 205822928 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 9 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 076 060 030 Pre-fail Always - 47334209 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 371 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 9 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 071 043 045 Old_age Always In_the_past 29 (0 10 32 23 0) 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 - 5 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 461 194 Temperature_Celsius 0x0022 029 057 000 Old_age Always - 29 (0 9 0 0 0) 195 Hardware_ECC_Recovered 0x001a 119 099 000 Old_age Always - 205822928 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 - 1795296329978 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 58085129483 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 64307117065 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 Completed without error 00% 355 - 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. If all is well this'll take me to 40Tb parity protected, think I'll pause at this point ;-) Quote Link to comment
tyrindor Posted April 25, 2016 Share Posted April 25, 2016 Why run the long SMART test after preclear? Just curious, does it sometime detect issues that the preclear would not? I've never used Seagate drives, so the way they log their SMART reports are pretty confusing to me. What are the main things i'm looking for? Quote Link to comment
danioj Posted April 25, 2016 Share Posted April 25, 2016 Why run the long SMART test after preclear? Just curious, does it sometime detect issues that the preclear would not? I've never used Seagate drives, so the way they log their SMART reports are pretty confusing to me. What are the main things i'm looking for? it was suggested to me that after a preclear a good idea would be for a final SMART long test on each drive. It does take another day or so for the 8TB's AND it's similar to the post read BUT it puts a mark in the SMART Test logs (which is a nicety for me) and provides a final confidence using the drives formal testing tool. This was the justification from WeeboTech a while ago. I feel the same way these days: I like to put that log entry into to the smart logs so that I know when the drive was put in service for data usage. When I have a question, or on some maintenance period, I can review the test logs and/or run another test, thus putting another line in the log for review. Quote Link to comment
tyrindor Posted April 25, 2016 Share Posted April 25, 2016 I guess i'm just crazy. I've been using unRAID with ~40 drives 24/7 for about 8ish years now and have had two failures - both over 3 years of age and successfully rebuilt. I've had a good dozen drives fail within the first few hours of a preclear (~25% DOA from Newegg until I stopped buying from them). I typically skip the post read entirely, before we had the updated script the post read took AGES! I only do 1 preclear as well. I just can't bring myself to wait an entire week for a drive to do 3 preclears, and then another day to do a extended SMART test. I'd be interested to know stats on how many drives have successfully completed 1 preclear, but failed during the next 2. My gut tells me roughly 2-5% drives will fail the first preclear, but less than 1% of those 2-5% will fail during the next 2 preclears. In my experience, if a new drive is going to fail it does so very quickly - or at the bare minimum - it'll have SMART issues. Quote Link to comment
BRiT Posted April 25, 2016 Share Posted April 25, 2016 If I remember properly, I've had more drives fail during the 2nd or 3rd preclear cycle than the first cycle. Quote Link to comment
BobPhoenix Posted April 25, 2016 Share Posted April 25, 2016 I've had several drives fail in the 2nd and 3rd pass. But your percentages are probably close. Quote Link to comment
tyrindor Posted April 25, 2016 Share Posted April 25, 2016 If I remember properly, I've had more drives fail during the 2nd or 3rd preclear cycle than the first cycle. That's surprising.... With no smart errors of any kind after the 1st cycle? A faulty drive could probably last 2-3 cycles before complete failure but i'd be surprised if that same drive had no SMART errors after the 1st cycle. I may be wrong here, just seems like that'd rarely be the case. Quote Link to comment
BRiT Posted April 25, 2016 Share Posted April 25, 2016 If I remember properly, I've had more drives fail during the 2nd or 3rd preclear cycle than the first cycle. That's surprising.... With no smart errors of any kind after the 1st cycle? A faulty drive could probably last 2-3 cycles before complete failure but i'd be surprised if that same drive had no SMART errors after the 1st cycle. I may be wrong here, just seems like that'd rarely be the case. Yes. I had 2 drives hit with read-failures with SMART read-failures showing up on SMART short test results that only happened in cycle 3; the SMART reports for after cycle 1 and cycle 2 were perfect. It's why I always do 3 cycles of preclear. I've had a few other drives with actual re-allocated and pending re-allocations. Those were RMA'd for replacements. Quote Link to comment
tyrindor Posted April 26, 2016 Share Posted April 26, 2016 If I remember properly, I've had more drives fail during the 2nd or 3rd preclear cycle than the first cycle. That's surprising.... With no smart errors of any kind after the 1st cycle? A faulty drive could probably last 2-3 cycles before complete failure but i'd be surprised if that same drive had no SMART errors after the 1st cycle. I may be wrong here, just seems like that'd rarely be the case. Yes. I had 2 drives hit with read-failures with SMART read-failures showing up on SMART short test results that only happened in cycle 3; the SMART reports for after cycle 1 and cycle 2 were perfect. It's why I always do 3 cycles of preclear. I've had a few other drives with actual re-allocated and pending re-allocations. Those were RMA'd for replacements. It'd be interesting to see someone take a very large sample of drives (500+), put them through 20 preclear cycles, and see how many failures happen at each cycle. My guess is you'd see 2-5% fail during the first preclear, and roughly the same amount of failures at cycle 2 as cycle 20 (less than 1% each cycle). Why? Because even though some consumer drives advertise "24x7 workload", they don't mean 100% load 24x7. They mean spun up 24x7 with some reads/writes every now and then. Fully loading a consumer grade drive for an entire week (3 cycles) may cause problems in itself. Another reason is that 2 full reads and 1 full write is generally enough to get out of the "early failure" zone, and any failures after that are typically random failures that can happen at any time on any drive. I'd wager if you started running 5 cycles, you'd see just as many drives failing on cycles 4-5 as cycles 2-3. This is just my opinion, so if 3 preclears makes someone feel safer than by all means. Personally, i'll stick with 1 preclear and avoid all that extra wear and tear. My theory is based off 4 unRAID servers (76 drives 24/7), and over double that many drives upgrading over the last ~8 years. Never had a drive pass the first preclear, than fail within 5 years of typical usage. I'd say 80% of those drives I skipped the post-read too. Quote Link to comment
Mercantides Posted May 27, 2016 Share Posted May 27, 2016 What spin down time should be used for these drives? Does the drive spin down if it is still shingling? Backstory: I've set up a new server with 2 of these as data drives and 3rd as the parity drive. I've temporarily mounted my old drives in the same server to transfer all of my files over. The first transfers of 2TB worth of movies went fine with speed averaging 40MB/s but the second transfer of tv data is only getting 10MB/s or worse. Notes: I originally started the tv transfer before the movies transfer was finished. I thought it would speed up after the movies transfer finished but it didn't. My tv data includes .tbn, .nfo, and .jpg files so it's possible these small files were causing issues but I've deleted them all and the transfer is still slow. The data is being moved from 4 different drives one at a time. The same drives that the movies were on. Often a transfer completes overnight or while I'm at work so there are hours between the end of one transfer and the start of the next. When I start the next transfer the first 5GB - 25GB or so will be fast but then it slows down again. I've tried both mv on the command line and midnight commander to move the files. My current hypothesis is that the default spin down time of 15 minutes is not enough for the drive to finish its shingling activity if it's seriously backed up. If the persistent cache is empty then the first 25GB of writes should be fast, shouldn't they? Is there anything I can do to diagnose this issue further? Quote Link to comment
Helmonder Posted May 27, 2016 Share Posted May 27, 2016 What spin down time should be used for these drives? Does the drive spin down if it is still shingling? Backstory: I've set up a new server with 2 of these as data drives and 3rd as the parity drive. I've temporarily mounted my old drives in the same server to transfer all of my files over. The first transfers of 2TB worth of movies went fine with speed averaging 40MB/s but the second transfer of tv data is only getting 10MB/s or worse. Notes: I originally started the tv transfer before the movies transfer was finished. I thought it would speed up after the movies transfer finished but it didn't. My tv data includes .tbn, .nfo, and .jpg files so it's possible these small files were causing issues but I've deleted them all and the transfer is still slow. The data is being moved from 4 different drives one at a time. The same drives that the movies were on. Often a transfer completes overnight or while I'm at work so there are hours between the end of one transfer and the start of the next. When I start the next transfer the first 5GB - 25GB or so will be fast but then it slows down again. I've tried both mv on the command line and midnight commander to move the files. My current hypothesis is that the default spin down time of 15 minutes is not enough for the drive to finish its shingling activity if it's seriously backed up. If the persistent cache is empty then the first 25GB of writes should be fast, shouldn't they? Is there anything I can do to diagnose this issue further? It does not work that way.. "shingling" is a part of a regular write cycle, so its not saved up or something like that.. the drive will never spin down without a completed write.. 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.