Found new drivers on Areca Website: http://www.areca.us/support/s_macos/driver/ArcMSR-1.3.4.universal.10.6.20110620.zip
because I'm booting from the RAID drive supported by the ARECA card
I'm not aware of one.Do you know if I can install the driver before the Lion upgrade?, because I'm booting from the RAID drive supported by the ARECA card
There are instances where it's valid though, such as the OS/applications volume on a high availability server (i.e. OS/apps = RAID 1).I never use my boot volume on a RAID. Asking for trouble especially with 3rd party drivers. Be warned.
I'm not aware of one.
So it looks like you'd need to make a clean installation on another drive (via external or internal on one of the MP's SATA ports). Add in the Areca drivers for Lion, shut down, add the card, reboot, then clone the current Lion OS disk to the OS volume set on the card. Then set the boot location back to the card, shut down, wait a few seconds, then restart (simple reboot tends not to load the RAID card's firmware during the boot process = card and volumes won't show up; in the case of a boot volume on the card, the system will stall).
Sounds like a lot of fun!![]()
![]()
There are instances where it's valid though, such as the OS/applications volume on a high availability server (i.e. OS/apps = RAID 1).
This would be the smart thing to do IMO.Thank you Nanofrog, I already have a clone of the boot volume (daily backup with superduper) so I'll use that one for the Lion installation, then add the ARECA drivers, clone back to the Raid volume and then boot from the array, but I think I'll wait a little until the dust settles on Lion
I'm not aware of one.
There are instances where it's valid though, such as the OS/applications volume on a high availability server (i.e. OS/apps = RAID 1).
I was just thinking of the OS volume, not the data served (i.e. working data on a separate volume, and is capable of meeting the IOPS requirement).I always find myself rebuilding those. Just did one where the previous tech did a RAID5 and sliced it up pretty bad. Rebuilds took forever and it was only a file server with fibre attached storage. Well those older G5 Xserves had crap for card drivers and were throwing error after error. I see your point but why not just have an 80GB SSD on the SATA bus if you need expanded iops?
I was just thinking of the OS volume, not the data served (i.e. working data on a separate volume, and is capable of meeting the IOPS requirement).
As per what you ran into, I'm not a fan of partitioning a single set into multiple volumes that will be run simultaneously, even if sporadically if at all possible (presume one partition was for the OS, another for working data).
Need toYup data and OS on same RAID side, only partitioned. Nice
Just thought I'd share.