heffneil
-
Posts
345 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by heffneil
-
-
So I ran the -W with the -A and it doesn't seem to have skipped the first steps?
Neil
-
None of my new drives are showing START reports either? That is unusual isn't it?
Thanks,
Neil
-
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_disk.sh -?
You'll see all the options.
You can try the "-t" option to see if the pre-clear signature was written to the disk. That would indicate it did all but the post-read phase.
Yes, you can skip the initial pre-read. Use the "-W" option.
Joe L.
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
-
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
-
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
-
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."
-
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
-
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
-
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
-
I figured it out and it's working but how to i get it to cache beyond a certain folder
my config is like this
/boot/cache_dirs -d 9 -m 3 -M 5 -p 200 -e ".custom" -e "mysql" -w
my share is like this
/TV Show/showname/season/file.mkv
/Movies/MovieName/file.mkv
and so on
but when i hit the tv show directory the drives start to spin up to show all the shows, how to I get it to cache all the way to the file.mkv
so if i click on the season folder the drives still don't 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
-
Does a cache drive need to be precleared?
Thanks,
Neil
-
nope... looks to me like it stopped responding. does it respond to a smartctl report?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!
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
-
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!
-
This is the output I got recently on my suspect drive while preclearing:
= Post-Read in progress: 3% complete.
( of 2,000,398,934,016 bytes read )
Elapsed Time: 29:55:11
./preclear_disk.sh: line 1080: 0+()%(243201) : syntax error: operand expected (error token is ")%(243201) ")
========================================================================1.11
== ST32000542AS 5XW1CTY2
== Disk /dev/sdi has NOT been precleared successfully
== skip=3800 count=200 bs=8225280 returned instead of 00000 skip=6000 count=200 bs=8225280 returned instead of 00000
============================================================================
Any ideas what is broken here?
I am running this:
preclear_disk.sh -A -c 3 /dev/sdi
Thanks!
Neil
-
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
-
The server is totally rebuilt with that one drive and everything looks great! Thanks for all the help!
Neil
-
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
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)
-
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
-
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
-
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
-
If you think it was near the end you can use the "-V" optionCrap I was afraid you would say that. I mean being 24 hours in to whats another 30 hours
It will skip to the verification phase. (the post read phase)
= Step 1 through 9 skipped, verify phase will be performed next
= Step 10 of 10 - The MBR is NOT verified un-aligned cleared.
= However, its MBR is verified cleared for 4k-alignment
= starting on sector 64
= Post-Read in progress: 0% complete.
( 1,645,056,000 of 2,000,398,934,016 bytes read ) 104 MB/s
Disk Temperature: 34C, Elapsed Time: 0:00:18
So I don't know if this is ok or not? Any thoughts? I wasn't sure if the -V would tell me if everything was kosher?
-
I got two more drives cooking in another server. No one ever answered my question about the script 1.7 vs. 1.9?
See about two or three comments higher.
Thanks,
Neil
-
Crap I was afraid you would say that. I mean being 24 hours in to whats another 30 hours
Preclear.sh results - Questions about your results? Post them here.
in User Customizations
Posted
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