Originally Posted by justmikie
I must be a lot less curious than the average AVSForumer. You guys are keeping Tom way busy with questions
. Being the impatient type I just went ahead and bought one. I installed 3 500gb drives when I first got it. Installation went fine and I had a terabyte of space to fill. I started ripping movies and realized that I needed more space (I have 600 movies), had some "extra" paypal money and ordered 2 more 500gb disks. When I went to install them, I couldn't see the utility to stop the array (I could , however, see the files on the 2 drives).
One thing we need to work on in the s/w is better feedback about what's happening during an operation. Some operations take "a long time" and it can appear that the system is locked up when in fact it's still crunching away. For example, to "mount" a reiserfs file system it takes close to 45 seconds once the disk capacity is over around 200GB. Now when there's multiple drives to mount we try to do them in parallel, but it still takes almost 45 sec times the number of drives to complete (seems to be highly CPU-bound). Anyway, my point is that sometimes, especially when adding drives, it's possible to get into a state where it appears things have ground to a halt. I'm not saying this happend in your case, but other people have, shall I say, pointed this out to us as a problem to be addressed.
I looked on the website for help for my problem and didn't find any. It was Saturday afternoon, and my 11 year old daughter was expecting to watch a movie that night, so I panicked and shut off the power supply. When I powered back up, I couldn't see the utility or the files on the drives. Now I was in trouble. I sent Tom and email, and an hour later he called me and quickly fixed my problem. Great service, especially on a Saturday.
I also have a 9 year old daughter who expects to watch her movies when she's been told she can, and is very upset when that can't happen...........
The only downside was that it took nearly 3 hours before the array was back up. I remember the website saying something about 400gb in 45 minutes....
The system was clearing your new drives before adding them to the array. The current code executes this "clearing" operation before starting the array because it was simplest and safest to do it this way - but we'll fix this in another release. Another way to add new drives is to first "initialize" the array configuration data (via Tools menu), in effect making it think all the drives are "new". Then when started, the shares become available much faster and a backgroun operation is started to regenerate parity. A problem doing it this way is there's no recovery if a drive fails during this operaiton.
For my first performance test, I tried playing a movie and ripping one at the same time, and the playback stutters. However, playing 2 movies from the same disk at the same time worked fine.
I'd be interested in knowing some more details about your first test:
a) was ripping done on same PC as viewing?
b) was ripping writing to same disk as the one being read for viewing?
c) what's your network configuration and speed?
d) anything else happening on your network?
p.s. Compusa had 500gb on sale for $309, with a $40 rebate so I bought 2 more... it's a disease
That's a great price, but man, I hate dealing with rebates....