December 5, 20169 yr recently purchased 2x4TB Seagate ST4000DM000's and the preclear keeps hanging after a while. Preclear plugin will report 0 MB/s and the elapsed time in the script will no longer increment. I have no log output for the preclear in my syslog for some reason (not sure if this is normal) but also no HDD errors or anything like that, just nothing. I've tried preclearing both drives at the same time, and both one by one and getting the same issue. Based on the location in case, these should be on my supermirco AOC-SASLP-MV8 that has plenty of other drives already and are working fine, although none of them are 4TB. smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.4.30-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Desktop HDD.15 Device Model: ST4000DM000-1F2168 Serial Number: Z30369LH LU WWN Device Id: 5 000c50 07a75e06e Firmware Version: CC54 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5900 rpm Form Factor: 3.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Tue Dec 6 10:20:38 2016 EST 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: ( 107) 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: ( 486) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x1085) 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 100 006 Pre-fail Always - 221721448 3 Spin_Up_Time 0x0003 098 098 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 2 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 99252 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 42 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 2 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 0 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 073 073 045 Old_age Always - 27 (Min/Max 21/27) 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 - 0 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 55 194 Temperature_Celsius 0x0022 027 040 000 Old_age Always - 27 (0 18 0 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 - 27h+10m+41.811s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 7814037304 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 19592279925 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. smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.4.30-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Desktop HDD.15 Device Model: ST4000DM000-1F2168 Serial Number: Z3034NVS LU WWN Device Id: 5 000c50 07a5c5519 Firmware Version: CC54 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5900 rpm Form Factor: 3.5 inches Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b SATA Version is: SATA 3.1, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Tue Dec 6 10:20:23 2016 EST 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: ( 97) 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: ( 494) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x1085) 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 100 006 Pre-fail Always - 202234568 3 Spin_Up_Time 0x0003 098 098 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 2 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 87831 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 42 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 2 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 0 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 076 073 045 Old_age Always - 24 (Min/Max 21/27) 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 - 0 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 62 194 Temperature_Celsius 0x0022 024 040 000 Old_age Always - 24 (0 17 0 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 - 29h+45m+20.686s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 0 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 30342516864 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. my Seek_Error_Rate seems to be a lot. is this an issue?
December 6, 20169 yr Both drives look perfect. Seek_Error_Rate for both is 100, as in 100% perfect, can't get any better. A Preclear has 3 phases, the pre-read which is an initial read scan, the write zeroes step which writes to every sector, and the post read scan, which checks for errors afterward and stresses the drive a little. Do you know how far it got, and in which phase it dropped to 0 MB/s? Preclear has never reported much to the syslog, until it's all done. I really wish that had been added a long time ago, logging exactly which drive is being cleared and the start of each phase, plus any error info.
December 6, 20169 yr Author mostly it's been failing after only a few hours in the pre-read, but I did get up to zeroing twice on at least one of the drives, but eventually it stopped again. here's my preclear that "finished" this morning (after only a few hours, wow lol).. ############################################################################################################################ # # # unRAID Server Pre-Clear of disk /dev/sdn # # Cycle 1 of 3, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read in progress: (75% Done) # # # # # # # # # # # # # # # # # # # # ** Time elapsed: 5:10:48 | Current speed: 163 MB/s | Average speed: 162 MB/s # # # ############################################################################################################################ # Cycle elapsed time: 5:10:52 | Total elapsed time: 5:10:54 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status # # # # # # ATTRIBUTE INITIAL STATUS # # 5-Reallocated_Sector_Ct 0 - # # 9-Power_On_Hours 32 - # # 183-Runtime_Bad_Block 0 - # # 184-End-to-End_Error 0 - # # 187-Reported_Uncorrect 0 - # # 190-Airflow_Temperature_Cel 23 - # # 197-Current_Pending_Sector 0 - # # 198-Offline_Uncorrectable 0 - # # 199-UDMA_CRC_Error_Count 0 - # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ --> ATTENTION: Please take a look into the SMART report above for drive health issues. --> RESULT: Preclear finished succesfully. could it be an issue that its 4TB? i don't have any other 4TB drives installed right now. One of my worries originally was that it wouldn't be recognized as 4TB but it looks like it's reporting 4TB just fine.
December 6, 20169 yr Community Expert If it finished that quickly I doubt it really finished. What preclear are you using? There have been several over the years. How much RAM? Have you done a memtest recently?
December 6, 20169 yr Author If it finished that quickly I doubt it really finished. yeah, i'm sure it didn't. it didn't even finish step 1 but it said precleared successfully, lol What preclear are you using? There have been several over the years. i'm using the included grjardim 0.8 beta preclear script. is there a newer one i should be using? How much RAM? Have you done a memtest recently? i have 16GB right now. i haven't run memtest in a while. could it be an issue that its 4TB? i don't have any other 4TB drives installed right now. One of my worries originally was that it wouldn't be recognized as 4TB but it looks like it's reporting 4TB just fine.
December 6, 20169 yr I am guessing an issue like the drive stopped responding or timed out since there are no "current values" in that smart summary report. Have you looked through syslogs or diagnostics to see if there's anything of note in there?
December 6, 20169 yr Author No exception or any other kind of errors in the syslog. I have another preclear running, if it fails I'll post the diagnostics but as far as I can see preclear isn't pushing anything to syslog and there aren't any warnings or erros either.
December 6, 20169 yr I'd try swapping things round a little so that your new disks are connected to motherboard SATA ports, just as a means of getting them pre-cleared. If that works and you want to put things back afterwards then feel free - there's no capacity restriction on the SASLP-MV8.
December 6, 20169 yr Author I'd try swapping things round a little so that your new disks are connected to motherboard SATA ports, just as a means of getting them pre-cleared. If that works and you want to put things back afterwards then feel free - there's no capacity restriction on the SASLP-MV8. i was thinking if doing this as well, but if i can't preclear the drive in that slot i'm not sure how confident i would be or should be in plugging a drive from my array in there.
December 6, 20169 yr I vaguely remember an inconclusive discussion about someone struggling to pre-clear on a SASLP-MV8 port in the past. I haven't been able to locate it though. If you don't like the idea of connecting an existing array drive to the SASLP then set your array not to auto-start before shutting down and doing the swap. Do the pre-clears and then swap back before you start the array again. The downside is that you won't be able to use your server for the duration of the pre-clears (which somewhat defeats the object!). Have you tried any other disk tests on the new drives (such as badblocks)? Something like badblocks -vsw -b 4096 -c 1024 -d 1 /dev/sdX from the command line would give them a good read/write testing. (Replace sdX with the actual designation.)
Archived
This topic is now archived and is closed to further replies.