Everything posted by heffneil
-
Preclear.sh results - Questions about your results? Post them here.
I ran it through and it completed. Simple question is there a decent program for viewing the reports that would format it properly? I am using Windows notepad and it isn't doing it! Thanks, Neil
-
Preclear.sh results - Questions about your results? Post them here.
So I ran the -W with the -A and it doesn't seem to have skipped the first steps? Neil
-
Preclear.sh results - Questions about your results? Post them here.
None of my new drives are showing START reports either? That is unusual isn't it? Thanks, Neil
-
Preclear.sh results - Questions about your results? Post them here.
Am I missing something? root@Storage3:/boot/preclear_reports# ls preclear_finish_ 5XW0DDKP_2012-03-27 preclear_finish_ 6YD0G5NN_2011-09-09 preclear_finish_ 6YD0G67X_2011-09-09 preclear_finish_ MJ1311YNG0W39A_2011-10-25 preclear_finish_ MJ1311YNG17ENA_2011-10-25 preclear_finish_ MJ1311YNG2A4SA_2011-10-25 preclear_finish_ MJ1311YNG2BXJA_2011-10-25 preclear_rpt_ 5XW0DDKP_2012-03-27 preclear_rpt_ 6YD0G5NN_2011-09-09 preclear_rpt_ 6YD0G67X_2011-09-09 preclear_rpt_ MJ1311YNG0W39A_2011-10-25 preclear_rpt_ MJ1311YNG17ENA_2011-10-25 preclear_rpt_ MJ1311YNG2A4SA_2011-10-25 preclear_rpt_ MJ1311YNG2BXJA_2011-10-25 preclear_start_ 5XW0DDKP_2012-03-27 preclear_start_ 6YD0G5NN_2011-09-09 preclear_start_ 6YD0G67X_2011-09-09 preclear_start_ MJ1311YNG0W39A_2011-10-25 preclear_start_ MJ1311YNG17ENA_2011-10-25 preclear_start_ MJ1311YNG2A4SA_2011-10-25 preclear_start_ MJ1311YNG2BXJA_2011-10-25
-
Preclear.sh results - Questions about your results? Post them here.
So for some reason I logged back in to my box and I only have two out of three Screen sessions and I initiated them all via telnet so none on console. I ran the -t on the drive I don't see in my other existing sessions and it says precleared however I don't have a report. So what should I do next. Results below: Pre-Clear unRAID Disk /dev/sda ################################################################## 1.13 Device Model: ST3000DM001-9YN166 Serial Number: W1F0RSQZ Firmware Version: CC4B User Capacity: 3,000,592,982,016 bytes Disk /dev/sda: 3000.5 GB, 3000592982016 bytes 255 heads, 63 sectors/track, 364801 cylinders, total 5860533168 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000 Device Boot Start End Blocks Id System /dev/sda1 1 4294967295 2147483647+ 0 Empty Partition 1 does not end on cylinder boundary. ######################################################################## ========================================================================1.13 == == DISK /dev/sda IS PRECLEARED with a GPT Protective MBR == ============================================================================ Thanks! Neil
-
Preclear.sh results - Questions about your results? Post them here.
Well that sucks nothing in there. If I was on the very last step is there a way to skip the beginning stuff and just do the last step? Thanks, Neil
-
Preclear.sh results - Questions about your results? Post them here.
So when everything can go wrong it does! My "spare" unraid server hasn't had to reboot in forever and now I have three new 3TB drives at least 22 hours in to the preclear when I come back home and the UPS was out. My question is how if any way can I determine if the preclear was completed and completed satisfactorily if it did finish. Help with this would be appreciated and save me another day! Thanks, Neil
-
Preclear.sh results - Questions about your results? Post them here.
I just ran pre-clear on two of my drives on my secondary server. they both completed and the one stayed in that server and when I added it to unraid it said it needed to format. The other drive I pulled and moved to my main server and when I added it it said it needed to be cleared?! I am running 1.11 of the script on 4.7 version of unraid. I started the clear so I am sure I screwed something up but I was wondering what could have gone wrong? "Start will record the new disk information and bring the expanded array on-line. All new disks which have not been factory-erased will be cleared first; and, the array will be available after the clear completes. This process takes time, but the array remains protected at all times. Caution: any data on the new disk(s) will be erased! If you want to preserve the data on the new disk(s), reset the array configuration and rebuild parity instead."
-
cache_dirs - an attempt to keep directory entries in RAM to prevent disk spin-up
When I run it the first time I Get the .7 seconds. cache_dirs -F -v -w -B -i "Movies" "Recordings" Executing find /mnt/disk1/Movies -noleaf Executing find /mnt/disk2/Movies -noleaf Executing find /mnt/disk3/Movies -noleaf Executing find /mnt/disk4/Movies -noleaf Executing find /mnt/disk5/Movies -noleaf Executing find /mnt/disk6/Movies -noleaf Executing find /mnt/disk7/Movies -noleaf Executing find /mnt/cache/Movies -noleaf Executed find in 0.073367 seconds, weighted avg=0.073367 seconds, now sleeping 5 seconds I have green drives (i.e. Not fast drives0 and they are all spun down so I think something is wrong here? Thanks, Neil
-
cache_dirs - an attempt to keep directory entries in RAM to prevent disk spin-up
Thanks. This is what I see now: Executing find /mnt/disk1/Movies -noleaf Executing find /mnt/disk2/Movies -noleaf Executing find /mnt/disk3/Movies -noleaf Executing find /mnt/disk4/Movies -noleaf Executing find /mnt/disk5/Movies -noleaf Executing find /mnt/disk6/Movies -noleaf Executing find /mnt/disk7/Movies -noleaf Executing find /mnt/cache/Movies -noleaf Executed find in 0.073426 seconds, weighted avg=0.073422 seconds, now sleeping 3 seconds Is that normal and a good sign? Thanks, Neil
-
cache_dirs - an attempt to keep directory entries in RAM to prevent disk spin-up
How can I figure out if this is working for me? I don't believe it is when I tried to connect from my laptop it took a long time to load up and when I dug in a little bit the drive spun up... Any help would be much appreciated. Thanks, Neil
-
cache_dirs - an attempt to keep directory entries in RAM to prevent disk spin-up
Can you tell me how you figured it out? I wanted to know the answer since I just installed and I needed to figure out if this is working properly. Thanks! Neil
-
Preclear.sh results - Questions about your results? Post them here.
Does a cache drive need to be precleared? Thanks, Neil
-
Preclear.sh results - Questions about your results? Post them here.
nope... looks to me like it stopped responding. does it respond to a smartctl report? It could be the disk, the cable, the power, the backplane/drive tray. We've seen them all. It has not been successfully pre-cleared. Trust me. try preclear_disk.sh -t /dev/sdi and see what it says. Only takes a few seconds to test if it has a pre-clear signature. Joe L. When I attempted to preclear the drive another time I would get disconnected! I ended up rebooting the machine again. I will check it out. The one drive just doesn't show up so that drive is definitely bad. I ran that command on these two WD drives but they were previously used on another installation. I ran the preclear and I don't know the results but when I ran that command I got the response: == == DISK /dev/sdi IS PRECLEARED with a starting sector of 64 == I guess how do I check to make sure the drives are good? Preclear again? Can I look at the contents of that drive? Thanks! Thanks, Neil
-
Preclear.sh results - Questions about your results? Post them here.
Again same problem. When I re-attached my screen session I see this: Elapsed Time: 14:09:49 ./preclear_disk.sh: line 1079: 0+()%(243201) : syntax error: operand expected (error token is ")%(243201) ") ========================================================================1.11 == ST32000542AS 5XW1CTY2 == Disk /dev/sdi has been successfully precleared == with a starting sector of 64 I can't imagine this is correct because 14 hours for 3 passes isn't possible on a 2TB drive. Any ideas? I am using the latest preclear scripts 1.11 I think. Thanks!
-
Preclear.sh results - Questions about your results? Post them here.
I am running preclear and I used screen. I reconnected and it looks frozen. Problem is I don't know if it truly is locked up or if this is a problem with the interface. When I run ps -al I see the following: 0 S 0 3150 2665 0 80 0 - 880 wait pts/1 00:00:26 preclear_disk.s 1 S 0 24628 3150 0 80 0 - 880 pipe_w pts/1 00:00:00 preclear_disk.s 1 S 0 24634 24628 0 80 0 - 880 wait pts/1 00:00:00 preclear_disk.s 0 D 0 24635 24634 50 80 0 - 2457 - pts/1 03:37:41 dd 0 R 0 24636 24634 24 80 0 - 434 pipe_w pts/1 01:44:07 sed 0 S 0 24637 24634 0 80 0 - 524 pipe_w pts/1 00:00:00 awk 4 S 0 24668 24654 0 80 0 - 627 pause pts/0 00:00:00 screen 4 R 0 24691 24670 0 80 0 - 519 - pts/2 00:00:00 ps Not sure if I screwed this up or if this drive is suspect. It was laying around and I thought in previous installs it was a problem so I wanted to run it through its paces before I considered using it again. Any suggestions would be greatly appreciated. Thanks, Neil
-
Preclear.sh results - Questions about your results? Post them here.
The upgrade instructions are in the announcement thread, basically yes, but there is also a newer version of the memory test file to copy in place, so three files in total for you: Upgrading an existing Flash Device ---------------------------------- Note: after upgrading, some changes may require additional user intervention, please refer to the Change Log below. If you are currently running unRAID Server 4.6 or higher, please copy the following files from the new release to the root of your Flash device: bzimage bzroot If you are currently running unRAID Server 4.5.x, 4.4.x, 4.3.x or 4.2.x, please copy the following files from the new release to the root of your Flash device: bzimage bzroot memtest Interestingly enough I had a bzroot.456 and a bzimage.456 turns out I did upgrade this server from 4.5 to 4.6 so I just copied the two files over after renaming the old ones. Also for good measure I copied the entire usb drive to a directory on my server. Going to reboot and sacrifice a lamb (just kidding about the last part)
-
Preclear.sh results - Questions about your results? Post them here.
I posed this question before and I Was looking for the reference. Thank goodness I don't upgrade often enough to remember. By config page do you mean my devices? So is realy 4.7 just those two files you have me renaming? I just want to make sure I don't screw this up. Currently I am at 4.5 so I don't know if that will make a difference... Neil
-
Preclear.sh results - Questions about your results? Post them here.
Ok great now I am going to upgrade to 4.7 and replace the suspect drive. Wish me luck! Please god don't let me mess this up
-
Preclear.sh results - Questions about your results? Post them here.
Here are the results of the -V. Can you tell me if this looks ok? ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdi /tmp/smart_finish_sdi ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 114 117 6 ok 60178126 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 68 66 45 near_thresh 32 Temperature_Celsius = 32 34 0 ok 32 Hardware_ECC_Recovered = 51 44 0 ok 60178126 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 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. Is this drive ok and ready to use now? Thanks! Neil
-
Preclear.sh results - Questions about your results? Post them here.
Yeah It just takes FOREVER! The slow one was more than 35 hours!!! I am not that patient Neil
-
Preclear.sh results - Questions about your results? Post them here.
Slow Drive. Anyone have any thoughts on these and the above results? ================================================================== 1.7 = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1, 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 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: 28C, Elapsed Time: 43:12:41 ========================================================================1.7 == ST32000542AS 5XW1LZJT == 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_V LUE Raw_Read_Error_Rate = 108 100 6 ok 16115 82 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 72 74 45 ok 28 Temperature_Celsius = 28 26 0 ok 28 Hardware_ECC_Recovered = 47 100 0 ok 16115 82 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. Thanks, Neil
-
Preclear.sh results - Questions about your results? Post them here.
Another disk with eh results: ================================================================== 1.7 = unRAID server Pre-Clear disk /dev/sda = cycle 1 of 1, 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 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: 30:53:38 ========================================================================1.7 == ST32000542AS 5XW18HK7 == Disk /dev/sda has been successfully precleared == with a starting sector of 64 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VA LUE Raw_Read_Error_Rate = 111 100 6 ok 370534 66 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 96 100 0 ok 4 Airflow_Temperature_Cel = 69 72 45 near_thresh 31 Temperature_Celsius = 31 28 0 ok 31 Hardware_ECC_Recovered = 51 100 0 ok 370534 66 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@Storage2:/boot#
-
Preclear.sh results - Questions about your results? Post them here.
Here is the results of one of the faster drives. I think there might be problems: ================================================================== 1.7 = unRAID server Pre-Clear disk /dev/sdb = cycle 1 of 1, 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 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: 29C, Elapsed Time: 30:44:05 ========================================================================1.7 == ST32000542AS 5XW11CLJ == 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_VA LUE Raw_Read_Error_Rate = 111 100 6 ok 296390 39 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 High_Fly_Writes = 95 100 0 ok 5 Airflow_Temperature_Cel = 71 74 45 ok 29 Temperature_Celsius = 29 26 0 ok 29 Hardware_ECC_Recovered = 54 100 0 ok 296390 39 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.
-
Preclear.sh results - Questions about your results? Post them here.
All three started out pretty even so this morning when I checked it I was concerned. I was going to try the fourth drive but since I am still getting this server up and running I am using trial and don't have a registered license (yet). I just ordered a new key for this machine so we will see. Thanks! Neil