mikechy Posted October 26, 2012 Share Posted October 26, 2012 I pre-cleared four drives and they all cleared ok. When adding them to my array, they apparently are clearing again? Both the clearing machine and the live array are using the exact same version of unRAID and I am using the latest pre-clear script. Any idea why it would not recognize those drives as already pre-cleared? Quote Link to comment
dgaschk Posted October 26, 2012 Share Posted October 26, 2012 They were not pre-cleared. Do you have reports in /boot/preclear-reports? Quote Link to comment
mikechy Posted October 26, 2012 Author Share Posted October 26, 2012 Here is the last one. I killed the others as they finished. ========================================================================1.11 == invoked as: ./preclear_disk.sh /dev/sdd == ST2000DM001-9YN164 S1E0MAHZ == Disk /dev/sdd has been successfully precleared == with a starting sector of 63 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 3:55:32 (141 MB/s) == Last Cycle's Zeroing time : 3:31:03 (157 MB/s) == Last Cycle's Post Read Time : 9:49:11 (56 MB/s) == Last Cycle's Total Time : 17:16:53 == == Total Elapsed Time 17:16:53 == == Disk Start Temperature: 28C == == Current Disk Temperature: 33C, == ============================================================================ ** 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 115 6 ok 150814296 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 67 72 45 near_thresh 33 Temperature_Celsius = 33 28 0 ok 33 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ Quote Link to comment
mikechy Posted October 26, 2012 Author Share Posted October 26, 2012 Ah wait... I just went and checked and was going to take a screenshot so you can see the serials match and it appears that they are ready to format. It's been a while since I've added a new drive but I can tell you it DEFINITELY said "Clearing" and was going 1% at a time for quite some time. Was it merely CHECKING the clearing and not really clearing again? Quote Link to comment
mikechy Posted October 26, 2012 Author Share Posted October 26, 2012 Actually it appears that the drives had HPA on them which maybe triggered it? Quote Link to comment
dgaschk Posted October 26, 2012 Share Posted October 26, 2012 Here is the last one. I killed the others as they finished. ========================================================================1.11 == invoked as: ./preclear_disk.sh /dev/sdd == ST2000DM001-9YN164 S1E0MAHZ == Disk /dev/sdd has been successfully precleared == with a starting sector of 63 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 3:55:32 (141 MB/s) == Last Cycle's Zeroing time : 3:31:03 (157 MB/s) == Last Cycle's Post Read Time : 9:49:11 (56 MB/s) == Last Cycle's Total Time : 17:16:53 == == Total Elapsed Time 17:16:53 == == Disk Start Temperature: 28C == == Current Disk Temperature: 33C, == ============================================================================ ** 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 115 6 ok 150814296 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 67 72 45 near_thresh 33 Temperature_Celsius = 33 28 0 ok 33 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ What did you kill? The pre-clear script should terminate and a command line should return. There should be nothing to kill. Are there reports in /boot/reports? Quote Link to comment
mikechy Posted October 26, 2012 Author Share Posted October 26, 2012 I killed the pre-clear reports as each finished. That report was from the last drive. that was in the preclear_reports folder. I suspect it was because there was HPA on the drives and am going to re-clear them after removing the HPA. Posted another post asking advice on my "fix" as I figured I have a different issue now. Thanks for your reply here. Quote Link to comment
dgaschk Posted October 26, 2012 Share Posted October 26, 2012 Do you mean that you deleted them? Do not delete them. Quote Link to comment
Joe L. Posted October 26, 2012 Share Posted October 26, 2012 Here is the last one. I killed the others as they finished. ========================================================================1.11 == invoked as: ./preclear_disk.sh /dev/sdd == ST2000DM001-9YN164 S1E0MAHZ == Disk /dev/sdd has been successfully precleared == with a starting sector of 63 == Ran 1 cycle == == Using :Read block size = 8225280 Bytes == Last Cycle's Pre Read Time : 3:55:32 (141 MB/s) == Last Cycle's Zeroing time : 3:31:03 (157 MB/s) == Last Cycle's Post Read Time : 9:49:11 (56 MB/s) == Last Cycle's Total Time : 17:16:53 == == Total Elapsed Time 17:16:53 == == Disk Start Temperature: 28C == == Current Disk Temperature: 33C, == ============================================================================ ** 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 115 6 ok 150814296 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 67 72 45 near_thresh 33 Temperature_Celsius = 33 28 0 ok 33 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ That is NOT the latest version of the pre-clear script. (You are two versions behind, as of this post, it is 1.13, you are on 1.11 and 1.13 has been out for quite a while.) What version of unRAID are you running? There was at least one (fairly recent) version that would not recognize a pre-cleared disk properly. If your MB added the HPA after the disks were cleared, they would no longer be detected as pre-cleared. In the same way, if you remove the HPA after pre-clearing them, they will no longer be detected as pre-cleared. If you previously assigned the drives to an array, they are no longer pre-cleared. Quote Link to comment
mikechy Posted October 26, 2012 Author Share Posted October 26, 2012 Ah, interesting. I have three fobs with unRAID on it and I wonder if that one never got the new clear script. I am running 4.7. I cleared them on a mobo that I know doesn't create the HPA as I have checked previously. I also have cleared 12 other drives on that same mobo so I know that's not the issue. The drive did however come from a DIFFERENT system that I can not say with any certainty didn't put that partition on there. I posted it's own thread as to my plan of attack to fix which basically would be remove the drives one at a time, remove the HPA, re-clear and add back. Rinse, repeat until all drives have been fixed. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.