All modern Arecas, as far as I know, are SAS/SATA controllers. I'm using all SATA drives with mine.
Way back in the day, I had an Areca 1170, which had 24 SATA ports on it, but that was like 10 years ago. So you're talking about controllers with only SATA ports on them?
Martin, my friend is reporting that this latest version fixed all his instability issues, so I'd say everything appears to be working 100% now with regards to Areca support. My friend is expecting a 1883 controller soon. I'll be sure to report any findings he has with it once he gets it online.
Doh, not sure how I missed that. Yep, works fine.
From my perspective, everything looks great now. My front with the 1880 is having some issues with this latest version. He stated the following:
--- cut ---
This version is very buggy for me. When I ran it again, it showed the IPMI...
One thing I'm noticing with this version, if I minimize the sensor window, all (HWiNFO) windows minimize and I don't see a way to bring them back. I still see it running under Background processes in Task Manager.
My friend tested the new version and it now shows each raid set as a node.
About the only issue he's having, is that under Sensors, the raid set stats are not showing up. I don't have that issue in my 1882 controllers.
I'll see if I can get a DBG file from him.
EDIT. DBG file...
Another question, I'm using Aquasuite and HWiNFO together. It appears that I have to keep the HWiNFO sensor window open in order for the sensor readings that I'm mapping over to Aquasuite to refresh in real time. Is that the expected behavior?
Looking really good.
There are a few minor issues however:
1. The drives are at the same 'level' as the controller, not under it.
2. There are about 80 RAID Array devices that, when expanded, contains a dupe of all the drives behind the Areca controller.
I also checked under...
DBG file for server 1 (Brama):
DBG file for server 2 (Argon):
I have the drives configured to spin down if the array has not been accessed for 30 minutes. That was the case for the drives...
Yes, it does filter out those invalid devices.
I believe the max number of supported devices is 36 per expander. See here:
I also ran the latest version on my 2nd server. The output looks good here as well: