tstorzuk

Just curious if this is possible, to have more than one parity drive running on a server. If so, what are the benefits/detriments to having more than one?

Thanks for the information. Ok, I think the drives I have run are good so far. The 3rd batch of 6 drives has finished since my last post. When I get home tonight, I'll be running my 4th and final batch of drives on this server through preclear. Preclear actually does recognize my 3TB HDD's (as you can see from the detailed report I attached in my previous post). It's just unRAID that doesn't. I'm hoping that the stable 5.0 release will be ready by the time I run my final set of HDD's through preclear. And when it is ready, I'll find out if it can recognize my multiple controller cards.

If you've been following my posts, I'm new to unRAID. I don't have it installed yet even, but I am going through the process of preclearing all of my drives on my newest server. I have 24 HDD's that I'm going through the preclear process and am on my 3rd batch of 6. I can only run 6 drives at a time as my multiple controller cards are not recognized by version 4.7. And I'm not interested in testing out the development series yet. I will wait until I have run through all my preclear checks. I am running each drive 6 times through preclear, as I do not want to worry much about having a failure. It takes a lot of time to recover from one, and I currently have one of my servers sitting around waiting until I have time to correct/replace one of it's faulty drives. It takes a lot to get into my servers as they are all crammed into a storage closet, at the very back. I have to move full shelving units and my deep freezer out of the way to wheel out the server rack.....then disconnect LOADS of cables. The last time I took it out of the storage room, I took some photos. Attached is one to show you what I'm talking about. I'm not sure what to look for in the results, so I'm posting one of them here. I tried to post 6 in this thread (1 batch), but it exceeded the maximum allowed characters by more than 4 times!!! So if someone could point out which areas to look at, and what types of numbers to watch out for it would be greatly appreciated. 1st disk to finish ========================================================================1.13 == invoked as: ./preclear_disk.sh -r 65536 -w 65536 -b 2000 -A -c 6 -m [email protected] /dev/sdc == ST3000DM001-1CH166 W1F1GJDG == Disk /dev/sdc has been successfully precleared == with a starting sector of 1 == Ran 6 cycles == == Using :Read block size = 65536 Bytes == Last Cycle's Pre Read Time : 6:35:04 (126 MB/s) == Last Cycle's Zeroing time : 5:33:50 (149 MB/s) == Last Cycle's Post Read Time : 11:55:20 (69 MB/s) == Last Cycle's Total Time : 17:30:15 == == Total Elapsed Time 112:42:31 == == Disk Start Temperature: 29C == == Current Disk Temperature: 31C, == ============================================================================ ** 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 = 117 100 6 ok 131179216 Seek_Error_Rate = 63 100 30 ok 2312779 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 94 100 0 ok 6 Airflow_Temperature_Cel = 69 71 45 near_thresh 31 Temperature_Celsius = 31 29 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 6. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 6. 0 sectors were pending re-allocation after post-read in cycle 1 of 6. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 6. 0 sectors were pending re-allocation after post-read in cycle 2 of 6. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 6. 0 sectors were pending re-allocation after post-read in cycle 3 of 6. 0 sectors were pending re-allocation after zero of disk in cycle 4 of 6. 0 sectors were pending re-allocation after post-read in cycle 4 of 6. 0 sectors were pending re-allocation after zero of disk in cycle 5 of 6. 0 sectors were pending re-allocation after post-read in cycle 5 of 6. 0 sectors were pending re-allocation after zero of disk in cycle 6 of 6. 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.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-1CH166 Serial Number: W1F1GJDG Firmware Version: CC24 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: Thu Jun 6 22:32:51 2013 MDT 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: ( 89) 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 100 100 006 Pre-fail Always - 949336 3 Spin_Up_Time 0x0003 094 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 42 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 908 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 5 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 42 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 069 045 Old_age Always - 29 (Lifetime Min/Max 26/29) 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 - 40 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 87 194 Temperature_Celsius 0x0022 029 040 000 Old_age Always - 29 (0 23 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 253 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 39058432589824 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 66 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 14474 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/sdc == Disk: /dev/sdc smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-1CH166 Serial Number: W1F1GJDG Firmware Version: CC24 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: Tue Jun 11 15:15:21 2013 MDT 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: ( 89) 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 117 099 006 Pre-fail Always - 131179216 3 Spin_Up_Time 0x0003 094 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 42 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 063 060 030 Pre-fail Always - 2312779 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 118 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 42 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 094 094 000 Old_age Always - 6 190 Airflow_Temperature_Cel 0x0022 069 068 045 Old_age Always - 31 (Lifetime Min/Max 26/32) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 40 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 87 194 Temperature_Celsius 0x0022 031 040 000 Old_age Always - 31 (0 23 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 - 64029372448881 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 35163223210 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 76403288396 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. == ============================================================================

I think I found the page that tells you what to look for/at; http://lime-technology.com/forum/index.php?topic=2817.msg123770#msg123770 Ok, good to know that everything looks good. I'm onto my second batch of 6 HDD's. It will run through the 6 passes like the other 6 drives. Should take about 5 days. If everything goes well, I'll be done the rest of the 24 drives in just over 2 weeks. Thanks for all your help.

This one took the longest to run; ========================================================================1.13 == invoked as: ./preclear_disk.sh -r 65536 -w 65536 -b 2000 -A -c 6 -m [email protected] /dev/sdd == ST3000DM001-1CH166 Z1F1PYV8 == Disk /dev/sdd has been successfully precleared == with a starting sector of 1 == Ran 6 cycles == == Using :Read block size = 65536 Bytes == Last Cycle's Pre Read Time : 6:47:38 (122 MB/s) == Last Cycle's Zeroing time : 6:34:20 (126 MB/s) == Last Cycle's Post Read Time : 12:35:10 (66 MB/s) == Last Cycle's Total Time : 19:10:35 == == Total Elapsed Time 123:25:48 == == Disk Start Temperature: 28C == == Current Disk Temperature: 31C, == ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 117 100 6 ok 144715112 Seek_Error_Rate = 60 100 30 ok 8592231509 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 70 72 45 near_thresh 30 Temperature_Celsius = 30 28 0 ok 30 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 6. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 6. 0 sectors were pending re-allocation after post-read in cycle 1 of 6. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 6. 0 sectors were pending re-allocation after post-read in cycle 2 of 6. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 6. 0 sectors were pending re-allocation after post-read in cycle 3 of 6. 0 sectors were pending re-allocation after zero of disk in cycle 4 of 6. 0 sectors were pending re-allocation after post-read in cycle 4 of 6. 0 sectors were pending re-allocation after zero of disk in cycle 5 of 6. 0 sectors were pending re-allocation after post-read in cycle 5 of 6. 0 sectors were pending re-allocation after zero of disk in cycle 6 of 6. 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/sdd == Disk: /dev/sdd smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-1CH166 Serial Number: Z1F1PYV8 Firmware Version: CC24 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: Thu Jun 6 22:34:21 2013 MDT 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: ( 89) 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 100 100 006 Pre-fail Always - 987960 3 Spin_Up_Time 0x0003 094 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 41 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 855 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 5 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 41 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 070 045 Old_age Always - 28 (Lifetime Min/Max 25/28) 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 - 39 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 86 194 Temperature_Celsius 0x0022 028 040 000 Old_age Always - 28 (0 22 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 253 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 271115515592704 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 66 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 14551 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/sdd == Disk: /dev/sdd smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-1CH166 Serial Number: Z1F1PYV8 Firmware Version: CC24 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 Jun 12 02:00:10 2013 MDT 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: ( 89) 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 117 099 006 Pre-fail Always - 144715112 3 Spin_Up_Time 0x0003 094 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 41 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 060 057 030 Pre-fail Always - 8592231509 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 128 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 41 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 100 000 Old_age Always - 0 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 070 069 045 Old_age Always - 30 (Lifetime Min/Max 25/31) 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 - 39 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 86 194 Temperature_Celsius 0x0022 030 040 000 Old_age Always - 30 (0 22 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 - 238516713816188 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 35163223186 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 76399377753 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. == ============================================================================ Anything from these show any signs of possible errors???

I know I read about this before I left on vacation, but can't find it anywhere with any of the searches that I have performed. I finished 6 cycles of preclear on my first 6 HDD's. I want to compare them to each other and see which of them might become a problem in the future. Here's the one that ran the fastest; ========================================================================1.13 == invoked as: ./preclear_disk.sh -r 65536 -w 65536 -b 2000 -A -c 6 -m [email protected] /dev/sdc == ST3000DM001-1CH166 W1F1GJDG == Disk /dev/sdc has been successfully precleared == with a starting sector of 1 == Ran 6 cycles == == Using :Read block size = 65536 Bytes == Last Cycle's Pre Read Time : 6:35:04 (126 MB/s) == Last Cycle's Zeroing time : 5:33:50 (149 MB/s) == Last Cycle's Post Read Time : 11:55:20 (69 MB/s) == Last Cycle's Total Time : 17:30:15 == == Total Elapsed Time 112:42:31 == == Disk Start Temperature: 29C == == Current Disk Temperature: 31C, == ============================================================================ ** 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 = 117 100 6 ok 131179216 Seek_Error_Rate = 63 100 30 ok 2312779 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 94 100 0 ok 6 Airflow_Temperature_Cel = 69 71 45 near_thresh 31 Temperature_Celsius = 31 29 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 6. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 6. 0 sectors were pending re-allocation after post-read in cycle 1 of 6. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 6. 0 sectors were pending re-allocation after post-read in cycle 2 of 6. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 6. 0 sectors were pending re-allocation after post-read in cycle 3 of 6. 0 sectors were pending re-allocation after zero of disk in cycle 4 of 6. 0 sectors were pending re-allocation after post-read in cycle 4 of 6. 0 sectors were pending re-allocation after zero of disk in cycle 5 of 6. 0 sectors were pending re-allocation after post-read in cycle 5 of 6. 0 sectors were pending re-allocation after zero of disk in cycle 6 of 6. 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.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-1CH166 Serial Number: W1F1GJDG Firmware Version: CC24 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: Thu Jun 6 22:32:51 2013 MDT 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: ( 89) 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 100 100 006 Pre-fail Always - 949336 3 Spin_Up_Time 0x0003 094 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 42 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 908 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 5 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 42 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 069 045 Old_age Always - 29 (Lifetime Min/Max 26/29) 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 - 40 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 87 194 Temperature_Celsius 0x0022 029 040 000 Old_age Always - 29 (0 23 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 253 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 39058432589824 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 66 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 14474 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/sdc == Disk: /dev/sdc smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST3000DM001-1CH166 Serial Number: W1F1GJDG Firmware Version: CC24 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: Tue Jun 11 15:15:21 2013 MDT 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: ( 89) 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 117 099 006 Pre-fail Always - 131179216 3 Spin_Up_Time 0x0003 094 094 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 42 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 063 060 030 Pre-fail Always - 2312779 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 118 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 42 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 094 094 000 Old_age Always - 6 190 Airflow_Temperature_Cel 0x0022 069 068 045 Old_age Always - 31 (Lifetime Min/Max 26/32) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 40 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 87 194 Temperature_Celsius 0x0022 031 040 000 Old_age Always - 31 (0 23 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 - 64029372448881 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 35163223210 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 76403288396 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. == ============================================================================

A night of running, to see how fast it works. So far they're all at about 99% on the Pre-read of the first of 6 cycles at just over 6.5 hours. I see one has changed to Zeroing 1 of 6. How many stages are there per cycle? I'd like to get an idea of how to calculate how long it should take. I'm not concerned with how long it will take for the preclear to run. I just hope that it takes up at least the amount of time while I'm gone. Because I'll have to run it again 3 more times to check all of my HDD's. I did read this; 1. gets a SMART report 2. pre-reads the entire disk 3. writes zeros to the entire disk 4. sets the special signature recognized by unRAID 5. verifies the signature 6. post-reads the entire disk 7. optionally repeats the process for additional cycles (if you specified the "-c NN" option, where NN = a number from 1 to 20, default is to run 1 cycle) 8. gets a final SMART report 9. compares the SMART reports alerting you of differences. but I'm not sure as to which of these 9 are going to be a full read or write stage. I'm guessing from the above that there will be the 3 in RED that are the ones that take a good deal of time. If I am correct, based on the pre-read performance it could finish in just under 5 days. So far they are all averaging around 130 MB/s and a temp of 29-30 deg. Looks good. BTW, I love unMenu's myMAIN tab. It's easy to refresh and see how all the drives are doing, and what stage they're at. No need to get into telnet & screen. But I will check that out shortly to see what type of information it gives. Yup, I did install and test the mail command. Set it up with a gmail account as there was a great topic in which someone covered how they got theirs working.....and I just followed suit; http://lime-technology.com/forum/index.php?topic=26414.msg230995#msg230995 Totally forgot to grab one of my UPS' from my other set-ups. I'll keep my fingers crossed that I don't have any problems while I'm gone. It is only a week. I know I left some questions, but I think I'll still set this to [sOLVED]. The server is up and running preclear. Thanks a TON for all your help so far Joe. Totally amazing!

Ahhh, I couldn't wait to find out if my code was correct or not. But it's running on all 6 disks. Thanks for all the help so far. I'm not going to change this to [sOLVED] yet in case my code isn't quite right. I could stop the preclears tomorrow and run the proper code instead??? Actually, I'm not sure if I could stop preclear once it's been initiated. To a night of running!!!! Cheers!!!

Ok, I found out that my router was giving me problems. Shut it down for a while, and now it's working fine. I have unMenu, preclear, screen and SMTP loaded and have successfully tested SMTP too. So, now I need a bit of help with running preclear on the first 6 drives. I'm going to want them to run for 6 cycles (I'm going on vacation for a week, so might as well let them go). And I'm going to want an email sent to me letting me know when they've finished and what the results were.....so I'm guessing this would be the code to input for each drive (lettered b,c,d,e,f and g); ./preclear_disk.sh -r 65536 -w 65536 -b 2000 -A -c 6 -m [email protected] /dev/sdb Would this be correct for the first drive? Is everything in the right order? Does it matter what order everything goes in? I'm getting excited to start this running. I'm using the stable version 4.7 that was shipped to me. I'll upgrade it once I get back. I'm not too worried about the controller cards at this point. Just getting the drives to test is a huge step forward.

Yup, can't read them through the controller cards. I've even crossflashed them to IT mode (straight passthrough). Oh well, I guess I'll have to figure something else out afterwards. But at least I might be able to run the preclear on them now. UUUGHHHH!!! Now I can't log into the server to set up Mail and SSMTP to email me when the preclears are done!!! I've even rebooted the server.....frustration!!

Nope, they all have power. All the drive bays are lit up. I have a redundant power supply, so it's not going to be that either. Ugh. I'll have to unscrew the fan plate to switch out the SFF8087x8087 cables for a couple of break out cables to hook to the motherboard....... Then I'll see if anything changes.

Ok, I've got the server up and running. Loaded unMenu, preclear and screen. Going through the tutorial step by step, and went to list my available drives; preclear_disk.sh -l And I got back the following; =================================1.13 Disks not assigned to the unRAID array (potential candidates for clearning) ===================================== No un-assigned disks detected So I guess I can't even read the drives in my server.....weird. Must be the controller cards that I have (3x IBM M1015)? But I think unRAID can see the controllers, because when I type in; demsg|grep SATA|grep link it spits out the following; ata4: SATA link down (SStatus 0 SControl 300) ata5: SATA link down (SStatus 0 SControl 300) ata3: SATA link down (SStatus 0 SControl 300) ata6: SATA link down (SStatus 0 SControl 300) ata1: SATA link down (SStatus 0 SControl 300) ata2: SATA link down (SStatus 0 SControl 300) Or would those just be the SATA headers on my motherboard that it can find? The mobo does have 6...... I could connect to those, but then for sure I wouldn't be able to use my whole system on unRAID, unless someone knows what else I could do?

Joe, That is sweet!! I'll have to check it out tonight when I'm at my server. Going to update as [RESOLVED]

Joe, That's exactly what I'd like to do. Wait until 5.0 comes out and upgrade then. Wish I had known before, but live and learn. Is there a step-by-step for noobs how to run the preclear on the drives (max 6 at a time as per your previous post in my other topic)? I'm a complete noob to unRAID, and also don't know Linux. Best of both worlds!!

jonathanm, I did have a temporary version. I wanted to test it out and see what I could do with it before getting my keys. I was able to run memtest for 36+ hours on that temporary version, so that saved me some time. "just got my USB" and "I just received my USB keys". I got my USB keys last night (maybe I'm using the wrong term "keys", probably should be "Flash Device" or "Flash Drive"). Preinstalled with version 4.7. On the web site when I ordered them, it didn't mention what version I was going to get. It only mentions; Registration Keys are small encrypted files placed on your USB Flash Device that enable support for additional hard drives. There are two registration key types: Plus - Supporting up to 7 drives, Plus is ideal for medium-sized Media Servers. Pro - Supporting up to 24 drives (21 in version 4.7), go Pro to build a truly massive Media Data Server. <----this is the one that I bought So I want to know which versions support 24 drives, which versions support 3TB drives, and how to get the version that supports both installed onto my USB keys.

Joe, Thanks for taking the time and answering everything I had asked. I'm going to set this topic to [sOLVED] and ask any new questions in a new topic. Cheers!

Nope, I got 20 data drives + parity + cache.

Hello all, Quick question. I just received my USB keys for my PRO licenses. Plugged one into my Motherboard, booted up and went into the GUI. In the GUI, I found that I only had 22 drives available in the Devices tab. I thought I was supposed to have 24 drives.... Registration Keys are small encrypted files placed on your USB Flash Device that enable support for additional hard drives. There are two registration key types: ?Plus - Supporting up to 7 drives, Plus is ideal for medium-sized Media Servers. ?Pro - Supporting up to [b]24 drives [/b] (21 in version 4.7), go Pro to build a truly massive Media Data Server. When I bought my USB keys, there was no mention of what version I was going to get. unRAID Server Pro USB Flash … 2-Pack $169 ?Two 8GB USB2.0 Flash Devices ?unRAID Server Pro pre-installed and bootable I ended up getting version 4.7. So how do I get a version that supports 24 drives? Which versions support 24 drives? Are those versions compatable with 3TB drives? Thanks for the help.

Not sure if this would help, but....... In Windows Explorer, browse to the share on your server. Typically, everything is sorted by Name (1). If you hit the Type (2) header, it will sort all files by type (in your case, *.iso files). Scroll up/down to find everything that is NOT an ISO file, highlight them all, hit the delete button. Yes to multiple file delete (only if you are sure that you picked the right files).

Yup, I've been running memtest now for 34:32:04, and will let it run until it's hit 36-48 hours. Even though I'm getting anxious to start running preclear. As for running preclear on multiple hard disc drives (HDD's) at once, I've been reading up on it, but have a couple of questions. 1. Do I need unMENU installed to run multiple sessions of preclear without having multiple sessions of telnet open? If I do run unMENU, how do I find out the stats of each preclear session, if I want to check on it's progress from time to time? Also how do I find out the information about each session when they complete (I have read that it can be set up to send an email to notify when it finishes, but does that email contain the info about the session results)? 2. If I have multiple computers, can I run multiple sessions of preclear from each PC (PC#1 running 6 sessions, PC#2 running 6 sessions, PC#3 running 6 sessions, etc....)? Or should I only try running preclear from one computer telneting to the server? 3. My server has a quad core CPU and 24 HDD's. How many sessions of preclear could I run at once? (Does it make a difference as to which version of unRAID I own as to how many HDD's I can run it on at once [i have bought the PRO version but am still waiting for it to arrive and am just using the basic version right now]? I know it could take up to 600 days to properly run preclear on all HDD's for the maximum 20 times each, doing it one at a time. So I'd like to reduce that as much as possible. But on the other hand, if it's a CPU intesive process, I don't want to overload the CPU constantly for months on end).

I really don't know where to post this, but I thought it should be available to others that might not understand what the actual installation instructions should say for Windows users. This is directly from the LimeTech Installation page, and been modified to show a few little things that are missing; ------------------------------------------------------------------------- Instructions Step 1: Unzip the contents of the unRAID Server release zip file that you downloaded onto your hard drive, in a location that you will remember. Step 2: Plug the Flash into your PC and re-format it using Windows: Open My Computer (XP) or Computer (Vista/Win7), right-click your Flash device and select Format… For File system, leave what Windows sets as default. For Volume label, enter UNRAID (all-caps). Select Quick Format and click Start. Step 3: Click on your Flash device (to open it) and drag the entire contents of the unRAID Server release folder to the Flash drive (the files that you unzipped in Step 1). Step 4: For Windows XP, click the file make_bootable.bat file (it may show as make_bootable depending on what your file display settings are in Windows Explorer). A DOS window will open and run the syslinux utility on the Flash. For Windows Vista or Windows 7, right-click the make_bootable.bat file and select Run as administrator (it may show as make_bootable depending on what your file display settings are in Windows Explorer). Step 5: Once again, right-click your Flash device in My Computer or Computer and select Eject. Your Flash device is now ready to boot into unRAID Server OS. ------------------------------------------------------------------------- Anyhow, just though I'd give this out to help other users. Cheers.

Thanks a lot for the info. I wasn't seeing anything directly related to hard disc drive tests in the previous posts' links. And I'm still reading through all of the information in them (links to links to links.....). I'll keep my eye out for the preclear run info. I had found memtest in the FAQ in regards to parity errors. Wouldn't have thought to have run it unless I saw some parity errors after being up and running.

Hello all, I'm new to the unRAID community. It was suggested to me recently as an option to FreeNAS, as it's easier to use and set up (not my words). So, I ordered my USB keys a couple of days ago, and in anticipation of their arrival thought to get started with getting some information straightened out. The OS will be going into a brand new server. So the first thing I will want to do is check all of the hard drives to see if they are functioning properly, have any bad sectors, and test them for 2-4 weeks before transferring files onto them. How do I do these tasks? I do not know unRAID at all, so please, step by step instructions so that I can get a detailed list of what each test has done, and how long it has taken on each hard drive (so I can compare between drives how fast each task has taken). Next, I'll need to probably set up unRAID so that all of my hard drives are useable. I'll ask how to do that in a future post, once I have tested all of the drives. The next step would be getting the NIC set up so that I can share the server with my various computers/media playing devices throughout the house. I'll ask how to do that in a future post, once I have tested all of the drives. The last step would be sharing out the hard drives. I'll ask how to do that in a future post, once I have tested all of the drives. Thanks for all your help.