-
-
Preclear.sh results - Questions about your results? Post them here.
Just running this by the experts in case anything stands out as a concern, like the 2 items that say "near_thresh": root@Tower:/boot# screen ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 118 120 6 ok 168294896 Seek_Error_Rate = 60 100 30 ok 1063419 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 72 75 45 ok 28 Temperature_Celsius = 28 25 0 ok 28 Hardware_ECC_Recovered = 37 30 0 ok 168294896 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@Tower:/boot#
-
Preclear.sh results - Questions about your results? Post them here.
Someone like Joe L. will chime in with some answers I'm sure For reference, my one drive, that hasn't had any data put on it yet, but is installed in my array shows: Reads: 29072288 Writes: 5734598 Although I do have one difference in that I am running my parity drive and I would have done a full parity check before I started using the two new drives.
-
Preclear.sh results - Questions about your results? Post them here.
I don't have the answer, but just a few things to consider: If they are connected to your motherboard, two of my ports were set as "PATA" in the BIOS. I just pre-cleared 2 of the 1.5TB WD EARS drives and they took 21 hours each. Did you jump pins 7 and 8 ( picture on the top of the hard drive identifies which end pins 7 and 8 are on ) ?
-
Preclear.sh results - Questions about your results? Post them here.
Thanks... that's the one I was trying to recall from a while ago. For reference, the full command I used (in case others are wondering): /usr/sbin/hdparm -N /dev/sdb My new drive shows the exact same details as my older 1.5TB drives, so that's a good sign! root@Tower:/boot# /usr/sbin/hdparm -N /dev/sdb /dev/sdb: max sectors = 18446744072344861488/11041584, HPA setting seems invalid root@Tower:/boot# /usr/sbin/hdparm -N /dev/sdc /dev/sdc: max sectors = 18446744072344861488/11041584, HPA setting seems invalid root@Tower:/boot# /usr/sbin/hdparm -N /dev/sdd /dev/sdd: max sectors = 18446744072344861488/11041584, HPA setting seems invalid I'm am certain I dealt with the HPA a while ago, however on every drive I get "HPA setting seems invalid". Hmmmmm
-
Preclear.sh results - Questions about your results? Post them here.
My Syslog, of the pre-clear results show: User Capacity: 1,500,301,910,016 bytes All my other formatted drives are 1,465,138,552 Is their any command I can run to verify the drive will format to the same size as my others ( I had to fix half my drives before as the MSI Motherboard wrote the BIOS backup to them ) Thanks
spinbot
Members
-
Joined
-
Last visited