Isn't learning fun?Yeah, again this thread has been extremely informative and I hope other n00bs like myself find all this info useful in the future too! After getting everything up and running following last night's issue I have been testing the heck out of this thing.
After removing the jumpers I haven't found any issues yet. I've been pulling out random drives, 2 at a time, rebuilding, pulling out 3, watching the array disappear and seeing what the software does as you suggested. So far it seems very easy to deal with provided you know which drives fail. MY ADVICE to anyone doing this for the first time, do what I did and label the drive bays with the serial numbers of your hard drives (see previous pics). It has saved MUCH confusion already!!!!!
Anyway, The system still responds quite well with only 3 of the 5 drives and rebuild times of the other 2 seem like they are taking 3-4 hours in the event of dual drive failure. Not sure what was going on with those jumpers being on there in the first place but I'm glad you think that may have been THE issue.
Oh and... I see how this is MUCH easier than when critical data is on the drives! And more importantly I definitely see the need for a functioning backup system!!!!!![]()
![]()
See? There actually is a method to my madness.
The PT table backup is an NVRAM solution to the write hole problem in RAID 5 & 6. It can allow you to recover the array, when it wouldn't be possible on other cards that don't have this feature. It's one of the reasons the card costs what it does, compared to say a Highpoint. (Areca designs and builds some of thier products, particularly the SAS cards they offer).On a totally unrelated note you mentioned something about the Areca cards having partition table backup. Why is this a bonus? Oh and after all of this setup that I am doing, what is going to happen to my data in the event that my card fails? Does that mean that I will have to reinitialize them and I'd lose the data or if you put in the same controller card and you connect things the same does it recognize the array? I am assuming that a card death = array death since the setup of the array is going to be stored on the controller?
There's hidden commands for the Areca. If you ever have a problem, their tech support will walk you through it. Surprisingly easy. (I'd have to go back and look up the command, as it's slipped my mind ATM).
In the case of a card failure, you just replace the card.
One of the nicest cards to have in the event of a failure. Some may not like the web browser interface to control the card, but I don't mind it. It works well, and isn't as daunting for less experienced users as the CLI (Command Line Interface) method. But I have to admit, Atto Technology has an even nicer interface. But their cards goes for more $$$.
However, you may get some corruption if the card was attempting a write when it died (limited to the specific file(s) being written at the time of the failure). In an enterprise environment, a spare card(s) are kept for just such an event. Along with drives, and even enough parts to build an entire system or two.
If you want to know what's going on, particularly with a failure, CHECK THE LOG FILES. These can save you all kinds of aggravation, including blowing the data, when it wasn't necessary. (It can show things like the drive order during a failure).
Though their native language isn't English, they do a fair job with the User's Manual. Read thoroughly, if you haven't already.