herda05

Sorry, my version of unRaid is 5.0.5. You guys hit the nail on the head. I attached the disk to my unraid server and pre_clear.sh -t shows the full disk size, but also that the drive is not precleared. I'm running it now on that server. thanks all.

trurl, Ahh, you're probably right about the system not recognizing the drive size. I run the preclear on an old Del XPS laptop. The version of the preclear is 1.14. I'll see if I can get the xps to recognize 2tb+. My actual unraid system does recognize 4tb, as my parity drive is 4tb. If I run the preclear and laptop does not see all 4tb, would that bew why unraid does not see the clear signature on the drive? thanks.

All, I have a 4tb drive I've pre-cleared: root@Tower:/tmp# cat preclear_report_sdc ========================================================================1.14 == invoked as: ./preclear_disk.sh -A -c 3 /dev/sdc == ST4000DM000-1F2168 Z302AB81 == Disk /dev/sdc has been successfully precleared == with a starting sector of 64 == Ran 3 cycles == == Using :Read block size = 8388608 Bytes == Last Cycle's Pre Read Time : 15:01:10 (33 MB/s) == Last Cycle's Zeroing time : 17:03:33 (29 MB/s) == Last Cycle's Post Read Time : 31:09:54 (16 MB/s) == Last Cycle's Total Time : 48:14:27 == == Total Elapsed Time 159:44:48 == == Disk Start Temperature: 29C == == Current Disk Temperature: 35C, == ============================================================================ ** 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 114 6 ok 160005424 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 65 71 45 near_thresh 35 Temperature_Celsius = 35 29 0 ok 35 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. ============================================================================ No errors were recored during pre-clear. However, when I plug it into my array, it only gives the option to clear it and not just add it. I tried the preclear_disk.sh -t: Pre-Clear unRAID Disk /dev/sdc ################################################################## 1.14 Model Family: Seagate Desktop HDD.15 Device Model: ST4000DM000-1F2168 Serial Number: Z302AB81 LU WWN Device Id: 5 000c50 0793c3954 Firmware Version: CC54 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Disk /dev/sdc: 1801.8 GB, 1801763774464 bytes 255 heads, 63 sectors/track, 219051 cylinders, total 3519069872 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sdc1 64 3519069871 1759534904 0 Empty Partition 1 does not end on cylinder boundary. ######################################################################## ========================================================================1.14 == == DISK /dev/sdc IS PRECLEARED with a starting sector of 64 == ============================================================================ The thing that stands out to me though is that it reads the disk as Disk /dev/sdc: 1801.8 GB. Is that normal? Do I have to do anything special for large (2tb+) drives? thanks, Dan H.