If the card is sitting there and doesn't come ready as normal, it is due to some kind of failure of communication between the controller and the drive(s) and/or expander(s) it is connected to. When it does successfully boot, are there any errors you can see in the BIOS? Can you post your logs? Have you updated to 1.50 firmware (you must update all 4 files, not just the FIRM file). If you remove the 2 SSD's and the 4 additional drives, does the problem resolve itself (if you do something like this, make sure that you have a complete backup of course, that activate incomplete raidset is disabled and that you don't go further than the bios prompts). If it does, readd the drives one at a time until you find the failure.
The LUN etc is 0/0/0 for the SSD's boot drive. I did upgrade to F/W 1.50 and did all four files. The lack of communication between card and drives sounds like a logical explanation. Earlier this morning I booted, shut down and rebooted, then restarted. Each time I tested this way, there was no problem. That is, the POST went as it's supposed to. When I get home later tonight, I'll try again. If I run into problems, I will try to post the logs. I assume you mean the Areca logs.
BTW, each time I have added drives, there has been a problem with the card recognizing the drives. The first was a non-boot raid 0 array (2 each WD 2TB drives). That time I got the message that the bios file was not loaded. It took a few boots and reboots for a couple of days, then finally everything worked well. It's almost as if you have to "burn in" the card/firmware each time I add a raid set.