heffneil

I understand and agree with all of you above. I guess the question is this: Lets say I take a drive and short stroke it to 2.2 and make one my parity and add one to the data pool because I need the extra 200 gigs and the parity has to be equal to the biggest drive (right?). So I do that and everything runs ok. I am sure I can find out on this forum how to do that with HDParm. Next question is when 5.x is released and supports 3 TB drives then what? Can I expand them or do I need to reformat / preclear again?! Just wondering what is next. I am sure that is a loaded question only because 5.0 isn't out yet and no one really knows but I guess I am trying to get comfortable with my options for now. I would hate to load up these 3 TB drives as 2.2 or 2.0's and then have to shuffle data around to get them to expand when the time is right. Thanks! Neil

I know this has been discussed at length but I now have 4 - 3tb drives that I have precleared. The question is what do I do with them in 4.7? Upgrading to a beta isn't an option for me no matter how good it is. I'm not sure I should have pre cleared these normally but I gave it a shot. Took 48 hours for each drive! Holy cow! So what are my options and what is everyone else doing? Thanks! Neil

I wonder if humidity makes your data stick

Not to add fuel to the fire but I did purchase a few 3 TB drives since 2TB just doesn't seem the proper way to spend money on space. I would like to run those drives but not in a beta. My data is too important and my chassis is filling up so I am in the midst of a bit of a conundrum as to how to expand my server... I would like 5.0 to go final but be of final quality and not just stamped so. I monitor this forum in great hopes that finality will come sooner - or later. Patiently, Neil

Just my opinion but I found these switches to really stink. They drop a lot of packets and I had trouble streaming on my sagetv box anything with HD. Replaced the switch with a quality one and it has been ok since.

I am using -a. Here is my command: rsync -avrtH /mnt/user/Movies/ storage2::mnt/user/Movies Thanks, Neil

Guys I am running rsync between my two boxes and for some reason a couple of files keep wanting to be rsynced. So I looked at the files that are there on the destination server and they say 1/31/11 which I thought was odd. So I run it again and it stays the same. I finally manually copy the files between the two shares via my windows box using explorer and now the problem seems fixed. This isn't the first time this happened. Just thought I would mention it if anyone else sees something like this. Thanks! Neil

I just precleared a new drive entirely and added it in devices. I started the array and it still shows it as mounting. In the past I thought it would mount it and then give me the option or format. I don't think this is the proper behavior. Any ideas? I can't stop the array within the web interface? It has been about 10 minutes now. 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

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

I was trying to install cache_dir when I noticed my flash mount is empty. I logged in and the /boot directory too is empty. I looked t the server and the light on the thumb drive was off. I pulled it and plugged it back in for it to turn on however both are still empty. I am a bit concerned to reboot and not sure what I should do next. Any thoughts or suggestions? Thanks, Neil

I am running screen so I can pre-clear a drive. I have been trying to get it finished but it has been really really tough because the screen session can't be re-attached. When I go to attach it it get an error saying: Cannot Exec 'session.....' : No such file or directory Any ideas to fix this would be greatly appreciated! Thanks, Neil

Apparently that was the problem although I set it for what I think is 20 gigs from another thread and had to restart the array to get it to start working. Boy do write occur MUCH faster.... Thanks! and I would love some clarification on the min disk space. In the morning I will research further. Thanks! Neil

I think the problem is I didn't set a min free space for each share just for the cache drive? Any thoughts on this. The min space thing isn't very intuitive. I was just reading other threads about it and I don't know if it is because it is so late but I don't quite get it? Neil

I enabled it under each share. I am getting the following in logs: Jul 24 00:47:04 Storage shfs: cache disk full This is impossible because: Device Model/Serial Mounted File System Temp Size Used %Used Free /dev/sda1 WDC_WD2002FAEX-007BA0_WD-WMAY00638319 /mnt/cache * 2.00T 33.63M 1% 2.00T

I am trying to use my cache drive. I am writing to the shares and on that share I have Use Cache Disk to Yes. I have even rebooted. I am not sure why it isn't working but all of my writes are not occurring on the cache drive? Any thoughts on what could be going on and what to check? I wonder if I have the wrong min disk space free option set (too high) It is currently 60000000000 which I believe is 60 gigs. Probably too high but still shouldn't affect files smaller than 60 gigs from going to the cache drive? The drive is new and totally free in terms of available space. 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? 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

I did kill the process and the machine went down cleanly. Now if only I had an older machine to firmware update my stupid drives Thanks! Neil