June 6, 201412 yr Author Don't get me wrong.. The time it takes sucks! But I will never put a new disk in a system WITHOUT pre-clearing it first! That goes for windows disks too!! Again, Thanks Joe! Jim
June 17, 201412 yr I just finished pre-clearing a 3TB Red drive. Can someone double check the attached results? Currently I have the following 3 disk setup: P: 2TB WD20EARS (jumpered) 1: 750GB Samsung 2: 750GB Samsung I would like to suffle these disks down and slot the new drive in as parity. I remember when I did the install on the EARS drive a lot of talk about jumpers/aligned/unaligned etc... Can I just re-assign the disks from the disk management page or is there something I need to watch out for especially? Much appreciated for any advice. preclear_finish_WD-WMC4N1806503_2014-06-17.txt preclear_rpt_WD-WMC4N1806503_2014-06-17.txt preclear_start_WD-WMC4N1806503_2014-06-17.txt
June 18, 201412 yr I just finished pre-clearing a 3TB Red drive. Can someone double check the attached results? Currently I have the following 3 disk setup: P: 2TB WD20EARS (jumpered) 1: 750GB Samsung 2: 750GB Samsung I would like to suffle these disks down and slot the new drive in as parity. I remember when I did the install on the EARS drive a lot of talk about jumpers/aligned/unaligned etc... Can I just re-assign the disks from the disk management page or is there something I need to watch out for especially? Much appreciated for any advice. Looks great. No sectors re-allocated or pending re-allocation. Reassign the new disk as your parity disk, let it compute parity... Then, perform a parity check. (That will prove you can read the parity bytes you stored) Only then should you move any other drives. Joe L.
June 20, 201412 yr I just finished pre-clearing a 3TB Red drive. Can someone double check the attached results? Currently I have the following 3 disk setup: P: 2TB WD20EARS (jumpered) 1: 750GB Samsung 2: 750GB Samsung I would like to suffle these disks down and slot the new drive in as parity. I remember when I did the install on the EARS drive a lot of talk about jumpers/aligned/unaligned etc... Can I just re-assign the disks from the disk management page or is there something I need to watch out for especially? Much appreciated for any advice. Looks great. No sectors re-allocated or pending re-allocation. Reassign the new disk as your parity disk, let it compute parity... Then, perform a parity check. (That will prove you can read the parity bytes you stored) Only then should you move any other drives. Joe L. All went according to plan. Am constantly amazed by the disk upgrade process reading the parity drive, works like a charm.
June 20, 201412 yr I precleared a 5T external drive in its USB container, and it completed successfully and verified as precleared afterwards. I then removed the disk from the USB enclosure and added it to the server as a SATA disk. It is being recognized correctly and the preclear signature verifies. But I noticed that the reported drive size is very slightly different. When it was precleared in the USB chasis it thought the drive size was 4,883,770,548K, but when it connected directly to the SATA port it is reporting a size of 4,883,770,552K (difference of 4K). Do I need to preclear the disk again? If not would unRAID see that the partition as not completely filling the disk and go into its own clear. Thanks for your thoughts on this.
June 21, 201412 yr I could not get a HDD to preclear since it kept telling me that it was already part of the array... "sdb" but it was not a totally new drive anyways I don't get why I could not preclear it. It was not part of the array. Anyways I just added to the array with out the script but can you please tell me if this readings look ok? Thank you. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 148 144 021 Pre-fail Always - 3575 4 Start_Stop_Count 0x0032 098 098 000 Old_age Always - 2329 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 089 089 000 Old_age Always - 8067 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 098 098 000 Old_age Always - 2307 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 80 193 Load_Cycle_Count 0x0032 197 197 000 Old_age Always - 11198 194 Temperature_Celsius 0x0022 116 100 000 Old_age Always - 27 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 2
June 22, 201412 yr I precleared a 5T external drive in its USB container, and it completed successfully and verified as precleared afterwards. I then removed the disk from the USB enclosure and added it to the server as a SATA disk. It is being recognized correctly and the preclear signature verifies. But I noticed that the reported drive size is very slightly different. When it was precleared in the USB chasis it thought the drive size was 4,883,770,548K, but when it connected directly to the SATA port it is reporting a size of 4,883,770,552K (difference of 4K). Do I need to preclear the disk again? If not would unRAID see that the partition as not completely filling the disk and go into its own clear. Thanks for your thoughts on this. you'll have to let us know.... If the verify option of the preclear script shows it is OK, odds are you'll be fine. You've basically used two different SATA controllers, and the one reported a slightly different size. try preclear_disk.sh -t /dev/sdX and see what it says. Since the math used by the preclear script when verifying a signature is the same as used by unRAID, if it says it is precleared, odds are good unRAID will think so too.
June 29, 201412 yr Hi togehter, I have new 4TB disk and tried to preclear it in two different servers. I alwas get the following message at the end: = unRAID server Pre-Clear disk /dev/sdg = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Elapsed Time: 11:48:47 ========================================================================1.15 == == SORRY: Disk /dev/sdg MBR could NOT be precleared == == out4= 00000 == out5= 00000 ============================================================================ 0+0 records in 0+0 records out 0 bytes (0 B) copied, 7.1247e-05 s, 0.0 kB/s 0000000 After that I have to reboot that preclear recognizes that drive again and if i run a preclear_disk.sh -t /dev/sdg it says: ################################################################## 1.15 Device Model: WDC WD40EFRX-68WT0N0 Serial Number: WD-WCC4E1714880 LU WWN Device Id: 5 0014ee 2b4d4275f Firmware Version: 80.00A80 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Disk /dev/sdg: 4000.8 GB, 4000787030016 bytes 255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0xf3034ac4 Device Boot Start End Blocks Id System ######################################################################## failed test 1 failed test 2 00000 00000 00000 00000 failed test 3 00000 00000 00000 00000 failed test 5 failed test 6 ========================================================================1.15 == == Disk /dev/sdg is NOT precleared == 0 0 4294967295 ============================================================================
July 1, 201412 yr Hi togehter, I have new 4TB disk and tried to preclear it in two different servers. I alwas get the following message at the end: = unRAID server Pre-Clear disk /dev/sdg = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Elapsed Time: 11:48:47 ========================================================================1.15 == == SORRY: Disk /dev/sdg MBR could NOT be precleared == == out4= 00000 == out5= 00000 ============================================================================ 0+0 records in 0+0 records out 0 bytes (0 B) copied, 7.1247e-05 s, 0.0 kB/s 0000000 After that I have to reboot that preclear recognizes that drive again and if i run a preclear_disk.sh -t /dev/sdg it says: ################################################################## 1.15 Device Model: WDC WD40EFRX-68WT0N0 Serial Number: WD-WCC4E1714880 LU WWN Device Id: 5 0014ee 2b4d4275f Firmware Version: 80.00A80 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Disk /dev/sdg: 4000.8 GB, 4000787030016 bytes 255 heads, 63 sectors/track, 486401 cylinders, total 7814037168 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disk identifier: 0xf3034ac4 Device Boot Start End Blocks Id System ######################################################################## failed test 1 failed test 2 00000 00000 00000 00000 failed test 3 00000 00000 00000 00000 failed test 5 failed test 6 ========================================================================1.15 == == Disk /dev/sdg is NOT precleared == 0 0 4294967295 ============================================================================ if it is unable to read the pre-clear signature it wrote, then either the disk is bad, or the disk controller is bad, or the disk just stopped responding meaning it is no longer working with your disk controller for some reason. (the "zero bytes copied" seems to indicate the latter) 0+0 records in 0+0 records out 0 bytes (0 B) copied, Does the disk then respond to a smartctl command? Or is it completely un-responsive? smartctl -A /dev/sdX Of course, it is possible for it to be something else... what version unRAID are you using? 32bit? or 64 bit? Joe L.
July 1, 201412 yr ========================================================================1.14 == ST3320311CS == Disk /dev/sdb has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 113 117 6 ok 57888365 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 64 71 45 near_thresh 36 Temperature_Celsius = 36 29 0 ok 36 Hardware_ECC_Recovered = 59 57 0 ok 57888365 No SMART attributes are FAILING_NOW ========================================================================1.14 == ST3320311CS == Disk /dev/sdc has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 119 114 6 ok 225771406 Start_Stop_Count = 37 37 20 near_thresh 65535 Power_On_Hours = 82 83 0 ok 15778 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 1 1 0 near_thresh 794 Airflow_Temperature_Cel = 64 71 45 In_the_past 36 Temperature_Celsius = 36 29 0 ok 36 No SMART attributes are FAILING_NOW Are these drives okay to use?
July 2, 201412 yr ========================================================================1.14 == ST3320311CS == Disk /dev/sdb has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 113 117 6 ok 57888365 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 64 71 45 near_thresh 36 Temperature_Celsius = 36 29 0 ok 36 Hardware_ECC_Recovered = 59 57 0 ok 57888365 No SMART attributes are FAILING_NOW ========================================================================1.14 == ST3320311CS == Disk /dev/sdc has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdc /tmp/smart_finish_sdc ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 119 114 6 ok 225771406 Start_Stop_Count = 37 37 20 near_thresh 65535 Power_On_Hours = 82 83 0 ok 15778 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 1 1 0 near_thresh 794 Airflow_Temperature_Cel = 64 71 45 In_the_past 36 Temperature_Celsius = 36 29 0 ok 36 No SMART attributes are FAILING_NOW Are these drives okay to use? yes, although the second disk had FAILED SMART IN THE PAST when the airflow temperature normalized value went below the affiliated failure threshold. You apparently baked that disk at one point? (was it in an external case with no fan?) You are also using an older version of the pre-clear script... A newer one has been released. (no need to re-do the pre-clear, yours went fine)
July 2, 201412 yr Hi Joe L. thanks for the response. I use unRAID version 5.0.5 32bit The disk didn't respond to any smartctl command after the preclear ended with this message, it's completely un-responsive. I tried a dd to clear the mbr, that worked. After that I tried it with more then 1024 bytes and it crashed so I'll return that drive because I think it's bad. Testing in 2 other systems reproduced that error so the disk controller of my unRAID Server cannot be the problem. Duff
July 2, 201412 yr I have a failed Preclear on a 2 - WB 3TB Green drive. I need help to sort it out - I am using the new drive as a new party drive. Thanks in advance Here is the report at the end (for one of the drives): ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 31C, Elapsed Time: 35:06:39 ========================================================================1.15 == WDCWD30EZRX-00SPEB0 WD-WCC4E1038872 == [b]Disk /dev/sdf has NOT been precleared successfully[/b] == skip=27800 count=200 bs=8388608 returned 53039 instead of 00000 skip=33000 count=200 bs=8388608 returned 15727 instead of 00000 skip=44200 count=200 bs=8388608 returned 41477 instead of 00000 skip=47400 count=200 bs=8388608 returned 56230 instead of 00000 skip=53600 count=200 bs=8388608 returned 59573 instead of 00000 skip=154000 count=200 bs=8388608 returned 30072 instead of 00000 skip=254600 count=200 bs=8388608 returned 11513 instead of 00000 skip=270800 count=200 bs=8388608 returned 24718 instead of 00000 skip=283600 count=200 bs=8388608 returned 14849 instead of 00000 skip=285400 count=200 bs=8388608 returned 20271 instead of 00000 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 121 122 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. I am running version 5B14 UNRaid The both drives responds to smartctl. One output is below: root@HAL_9000:/boot# smartctl -A /dev/sdf smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 100 253 021 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 4 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 73 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 4 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 0 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 25 194 Temperature_Celsius 0x0022 122 106 000 Old_age Always - 30 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0
July 3, 201412 yr Hi Joe L. thanks for the response. I use unRAID version 5.0.5 32bit The disk didn't respond to any smartctl command after the preclear ended with this message, it's completely un-responsive. I tried a dd to clear the mbr, that worked. After that I tried it with more then 1024 bytes and it crashed so I'll return that drive because I think it's bad. Testing in 2 other systems reproduced that error so the disk controller of my unRAID Server cannot be the problem. Duff Ouch... an unresponsive disk could be a real headache in an unRAID server. I'm unhappy it failed, but in the long term, for your data, you are better off RMA'ing int. Joe L.
July 3, 201412 yr I have a failed Preclear on a 2 - WB 3TB Green drive. I need help to sort it out - I am using the new drive as a new party drive. Thanks in advance Here is the report at the end (for one of the drives): ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 31C, Elapsed Time: 35:06:39 ========================================================================1.15 == WDCWD30EZRX-00SPEB0 WD-WCC4E1038872 == [b]Disk /dev/sdf has NOT been precleared successfully[/b] == skip=27800 count=200 bs=8388608 returned 53039 instead of 00000 skip=33000 count=200 bs=8388608 returned 15727 instead of 00000 skip=44200 count=200 bs=8388608 returned 41477 instead of 00000 skip=47400 count=200 bs=8388608 returned 56230 instead of 00000 skip=53600 count=200 bs=8388608 returned 59573 instead of 00000 skip=154000 count=200 bs=8388608 returned 30072 instead of 00000 skip=254600 count=200 bs=8388608 returned 11513 instead of 00000 skip=270800 count=200 bs=8388608 returned 24718 instead of 00000 skip=283600 count=200 bs=8388608 returned 14849 instead of 00000 skip=285400 count=200 bs=8388608 returned 20271 instead of 00000 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 121 122 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. I am running version 5B14 UNRaid The both drives responds to smartctl. One output is below: root@HAL_9000:/boot# smartctl -A /dev/sdf smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 100 253 021 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 4 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 73 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 4 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 0 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 25 194 Temperature_Celsius 0x0022 122 106 000 Old_age Always - 30 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 A drive that returns different values than what was written to it is a real pain in the neck. It could be a bad drive, it could be a poorly regulated power supply line to the drive, it could be a bad disk controller, or even bad memory. I'd start with a memory test of the server, preferably overnight, or at least several passes to make sure it is not falsely leading you to think the disk is bad. Joe L.
July 3, 201412 yr Joe L Thanks for the reply - sorry for my ignorance - how to run a server memory test? Thanks, I have a failed Preclear on a 2 - WB 3TB Green drive. I need help to sort it out - I am using the new drive as a new party drive. Thanks in advance Here is the report at the end (for one of the drives): ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 31C, Elapsed Time: 35:06:39 ========================================================================1.15 == WDCWD30EZRX-00SPEB0 WD-WCC4E1038872 == [b]Disk /dev/sdf has NOT been precleared successfully[/b] == skip=27800 count=200 bs=8388608 returned 53039 instead of 00000 skip=33000 count=200 bs=8388608 returned 15727 instead of 00000 skip=44200 count=200 bs=8388608 returned 41477 instead of 00000 skip=47400 count=200 bs=8388608 returned 56230 instead of 00000 skip=53600 count=200 bs=8388608 returned 59573 instead of 00000 skip=154000 count=200 bs=8388608 returned 30072 instead of 00000 skip=254600 count=200 bs=8388608 returned 11513 instead of 00000 skip=270800 count=200 bs=8388608 returned 24718 instead of 00000 skip=283600 count=200 bs=8388608 returned 14849 instead of 00000 skip=285400 count=200 bs=8388608 returned 20271 instead of 00000 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 121 122 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. I am running version 5B14 UNRaid The both drives responds to smartctl. One output is below: root@HAL_9000:/boot# smartctl -A /dev/sdf smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF READ SMART DATA SECTION === SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 100 253 021 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 4 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 73 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 4 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 0 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 25 194 Temperature_Celsius 0x0022 122 106 000 Old_age Always - 30 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 A drive that returns different values than what was written to it is a real pain in the neck. It could be a bad drive, it could be a poorly regulated power supply line to the drive, it could be a bad disk controller, or even bad memory. I'd start with a memory test of the server, preferably overnight, or at least several passes to make sure it is not falsely leading you to think the disk is bad. Joe L.
July 3, 201412 yr Joe L Thanks for the reply - sorry for my ignorance - how to run a server memory test? Thanks, When you boot UnRAID you get a menu prompt to either boot UnRAID to run MEMtest. You should just have to reboot (with a monitor attached) to see the option and be able to select it.
July 3, 201412 yr A drive that returns different values than what was written to it is a real pain in the neck. It could be a bad drive, it could be a poorly regulated power supply line to the drive, it could be a bad disk controller, or even bad memory. I'd start with a memory test of the server, preferably overnight, or at least several passes to make sure it is not falsely leading you to think the disk is bad. Joe L. Have run the memory test 5 passes now, all OK. Next stop? I have two drives that did the same thing. I have upgrades to Unraid OS 5.0.5 - thinking maybe a compatibility issue between the OS and preclear 1.15 (5B15 and preclear 1.13 worked fine together for the 2TB drives I was using). With this upgrade, I plan to try pre clear again to see if it is that issue. Any other guidance appreciated. SH
July 3, 201412 yr A drive that returns different values than what was written to it is a real pain in the neck. It could be a bad drive, it could be a poorly regulated power supply line to the drive, it could be a bad disk controller, or even bad memory. I'd start with a memory test of the server, preferably overnight, or at least several passes to make sure it is not falsely leading you to think the disk is bad. Joe L. Have run the memory test 5 passes now, all OK. Next stop? I have two drives that did the same thing. I have upgrades to Unraid OS 5.0.5 - thinking maybe a compatibility issue between the OS and preclear 1.15 (5B15 and preclear 1.13 worked fine together for the 2TB drives I was using). With this upgrade, I plan to try pre clear again to see if it is that issue. Any other guidance appreciated. SH You can try, but the preclear script does absolutely nothing that the normal reading and writing of files would not do. I would suspect a hardware issue. If you have the same issue with two drives, and memory tests good, suspect the disk-controller, or power supply. (how many drives are attached? What capacity supply? How many 12 volt rails? )
July 3, 201412 yr You can try, but the preclear script does absolutely nothing that the normal reading and writing of files would not do. I would suspect a hardware issue. If you have the same issue with two drives, and memory tests good, suspect the disk-controller, or power supply. (how many drives are attached? What capacity supply? How many 12 volt rails? ) Config: ANTEC 750W - HCG750 (It has 4 -12 V, 40A rails). Attached is a total of 12 drives total. ASUS PBZ68-V LX motherboard with 6 on-board controller slots (all 6 in use) Supermicro AOC-SASLP-MV8 controller (8 drive capability - 6 in use) When I have been running pre clear, I don't have the array all the way up - just to the point where the config is ok (as I am replacing my dead parity drive). Other places to look, thanks SH
July 5, 201412 yr A drive that returns different values than what was written to it is a real pain in the neck. It could be a bad drive, it could be a poorly regulated power supply line to the drive, it could be a bad disk controller, or even bad memory. I'd start with a memory test of the server, preferably overnight, or at least several passes to make sure it is not falsely leading you to think the disk is bad. Joe L. Have run the memory test 5 passes now, all OK. Next stop? I have two drives that did the same thing. I have upgrades to Unraid OS 5.0.5 - thinking maybe a compatibility issue between the OS and preclear 1.15 (5B15 and preclear 1.13 worked fine together for the 2TB drives I was using). With this upgrade, I plan to try pre clear again to see if it is that issue. Any other guidance appreciated. SH You can try, but the preclear script does absolutely nothing that the normal reading and writing of files would not do. I would suspect a hardware issue. If you have the same issue with two drives, and memory tests good, suspect the disk-controller, or power supply. (how many drives are attached? What capacity supply? How many 12 volt rails? ) After the upgrade to Unraid OS 5.0.5, I reran preclear 1.15 - success on both drives!! Thanks SH
July 16, 201411 yr Pre clearing two 2TB SATA drives right now. I just had this happen about six minutes into the first one. Thoughts? = = = Elapsed Time: 0:06:40 ================================================================== 1.14 = unRAID server Pre-Clear disk /dev/sdi = cycle 1 of 3, partition start on sector 64 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it = **** This will take a while... you can follow progress below: = = = = = = = = Elapsed Time: 0:06:45 0+0 records in 0+0 records out 0 bytes (0 B) copied, 0.00134184 s, 0.0 kB/s ./preclear_disk.sh: line 656: let: percent_wrote=(0 / ): syntax error: operand e xpected (error token is ")") Wrote 0 bytes out of bytes (% Done) ./preclear_disk.sh: line 1867: / (1405475789 - 1405475763) / 1000000 : syntax er ror: operand expected (error token is "/ (1405475789 - 1405475763) / 1000000 ") ========================================================================1.14 == WDCWD20EADS-00R6B0 WD-WCAVY6713758 == Disk /dev/sdi has been successfully precleared == with a starting sector of 64 ============================================================================ ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ** Changed attributes in files: /tmp/smart_start_sdi /tmp/smart_finish_sdi ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VA LUE Raw_Read_Error_Rate = 200 ok Spin_Up_Time = 182 ok Start_Stop_Count = 99 ok Reallocated_Sector_Ct = 200 ok Seek_Error_Rate = 200 ok Power_On_Hours = 83 ok Spin_Retry_Count = 100 ok Calibration_Retry_Count = 100 ok Power_Cycle_Count = 100 ok Power-Off_Retract_Count = 200 ok Load_Cycle_Count = 198 ok Temperature_Celsius = 122 ok Reallocated_Event_Count = 200 ok Current_Pending_Sector = 198 ok Offline_Uncorrectable = 199 ok UDMA_CRC_Error_Count = 200 ok Multi_Zone_Error_Rate = 191 ok No SMART attributes are FAILING_NOW 919 sectors were pending re-allocation before the start of the preclear. a change of -919 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. a change of 0 in the number of sectors re-allocated. SMART overall-health status = root@Tower:/boot#
July 17, 201411 yr I had some error that I don't remember seeing from my previous preclear run on other disks. Here is what I saw: 1 Raw_Read_Error_Rate 0x000f 118 100 006 Pre-fail Always - 186259920 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 10 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 542595 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 37 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 10 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 066 060 045 Old_age Always - 34 (Min/Max 25/40) 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 - 2 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 19 194 Temperature_Celsius 0x0022 034 040 000 Old_age Always - 34 (0 19 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 - 37h+21m+26.922s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 7815643906 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 23849293036 Is that something to be worried about? Did I purchase a bad drive? I'll post my full log here: Disk: /dev/sdg smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Seagate Desktop HDD.15 Device Model: ST4000DM000-1F2168 Serial Number: S3008HXA LU WWN Device Id: 5 000c50 06d3abfb6 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 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: 6.0 Gb/s) Local Time is: Wed Jul 16 12:36:47 2014 EDT 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: ( 512) 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 118 100 006 Pre-fail Always - 186259920 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 10 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 100 253 030 Pre-fail Always - 542595 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 37 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 10 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 066 060 045 Old_age Always - 34 (Min/Max 25/40) 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 - 2 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 19 194 Temperature_Celsius 0x0022 034 040 000 Old_age Always - 34 (0 19 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 - 37h+21m+26.922s 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 7815643906 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 23849293036 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. Thanks so much for your help!
July 17, 201411 yr Pre clearing two 2TB SATA drives right now. I just had this happen about six minutes into the first one. Thoughts? = = = Elapsed Time: 0:06:40 ================================================================== 1.14 = unRAID server Pre-Clear disk /dev/sdi = cycle 1 of 3, partition start on sector 64 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it = **** This will take a while... you can follow progress below: = = = = = = = = Elapsed Time: 0:06:45 0+0 records in 0+0 records out 0 bytes (0 B) copied, 0.00134184 s, 0.0 kB/s ./preclear_disk.sh: line 656: let: percent_wrote=(0 / ): syntax error: operand e xpected (error token is ")") Wrote 0 bytes out of bytes (% Done) ./preclear_disk.sh: line 1867: / (1405475789 - 1405475763) / 1000000 : syntax er ror: operand expected (error token is "/ (1405475789 - 1405475763) / 1000000 ") ========================================================================1.14 == WDCWD20EADS-00R6B0 WD-WCAVY6713758 == Disk /dev/sdi has been successfully precleared == with a starting sector of 64 ============================================================================ ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ./preclear_disk.sh: line 831: [: : integer expression expected ** Changed attributes in files: /tmp/smart_start_sdi /tmp/smart_finish_sdi ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VA LUE Raw_Read_Error_Rate = 200 ok Spin_Up_Time = 182 ok Start_Stop_Count = 99 ok Reallocated_Sector_Ct = 200 ok Seek_Error_Rate = 200 ok Power_On_Hours = 83 ok Spin_Retry_Count = 100 ok Calibration_Retry_Count = 100 ok Power_Cycle_Count = 100 ok Power-Off_Retract_Count = 200 ok Load_Cycle_Count = 198 ok Temperature_Celsius = 122 ok Reallocated_Event_Count = 200 ok Current_Pending_Sector = 198 ok Offline_Uncorrectable = 199 ok UDMA_CRC_Error_Count = 200 ok Multi_Zone_Error_Rate = 191 ok No SMART attributes are FAILING_NOW 919 sectors were pending re-allocation before the start of the preclear. a change of -919 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. a change of 0 in the number of sectors re-allocated. SMART overall-health status = root@Tower:/boot# It is likely the disk just stopped responding at all. the script is attempting to interpret the output of the smartctl program and the output of the "dd" command. Obviously, the output is not what was expected. If you type smartctl -a /dev/sdX I doubt you'll get a report. Look for a loose cable, (or a dead drive) Joe L.
July 17, 201411 yr I had some error that I don't remember seeing from my previous preclear run on other disks. Here is what I saw: All you posted is the output of a smartctl report. It looks fine. What error are you seeing? Joe L.
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.