-
cal87 started following Hitachi 5K3000 3TB Drives - 4 available
-
Preclear.sh results - Questions about your results? Post them here.
================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sdb = 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: 34C, Elapsed Time: 43:07:15 ========================================================================1.13 == Hitachi HDS5C3030ALA630 MJ1313YNG1ZX6C == Disk /dev/sdb has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VA LUE Raw_Read_Error_Rate = 85 100 16 ok 734014 2 Temperature_Celsius = 176 214 0 ok 34 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. root@Tower2:/boot# Is this Raw Read Error Rate of any significance?
-
Preclear.sh results - Questions about your results? Post them here.
I have a Seagate 1.5TB drive that I was using in my DirecTV HD DVR. The video was freezing frequently. I replaced it with a EVDS drive, and no more freezing issues. I ran it through preclear and got the following results. Disk Temperature: 31C, Elapsed Time: 18:35:57 ========================================================================1.7 == ST31500341AS 9VS09RZ8 == Disk /dev/sdm has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdm /tmp/smart_finish_sdm ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VA LUE Raw_Read_Error_Rate = 102 115 6 ok 396794 7 Spin_Retry_Count = 100 100 97 near_thresh 2 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 1 1 0 near_thresh 284 Airflow_Temperature_Cel = 69 75 45 near_thresh 31 Temperature_Celsius = 31 25 0 ok 31 Hardware_ECC_Recovered = 49 22 0 ok 396794 7 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. 44 sectors had been re-allocated before the start of the preclear. 44 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. Is this drive ok? I am not planning to use it in my array. HTPC perhaps.
cal87
Members
-
Joined
-
Last visited