Why RAID Controller Selection Matters
A RAID controller determines your storage subsystem’s reliability, performance, and capacity efficiency. Choosing between MegaRAID 9361, 9460, and 9560 directly impacts IOPS, throughput, and whether your storage can support NVMe.
Specifications Comparison
| Specification | 9361-8i | 9460-16i | 9560-16i |
|---|---|---|---|
| SAS Generation | SAS 3.0 (12Gb/s) | SAS 3.0 (12Gb/s), Tri-Mode | SAS 4.0 (24Gb/s), Tri-Mode |
| Physical Ports | 8 | 16 | 16 |
| Max Devices | 64 | 256 | 255 |
| Cache Size | 1GB / 2GB DDR3 | 4GB DDR4 | 4GB / 8GB DDR4 |
| RAID Levels | 0/1/5/6/10/50/60 | 0/1/5/6/10/50/60 | 0/1/5/6/10/50/60 |
| NVMe Support | No | Yes (Tri-Mode, PCIe 3.1) | Yes (Tri-Mode, PCIe 4.0) |
| SecureBoot | No | Yes | Yes |
9361-8i: The Cost-Effective SAS Classic
A widely deployed enterprise RAID controller. Suitable for general-purpose servers (HPE DL380, Dell R740), virtualization hosts, database servers, and backup/archive with RAID-6.
Key limitation: No NVMe support.
9460-16i: The Mid-Range Tri-Mode Controller
16 internal ports, 4GB cache, 12Gb/s SAS with Tri-Mode support, so SAS, SATA and NVMe drives can sit behind one card. Best for high-density storage and dense server configurations. It sits on a PCIe 3.1 host interface; step up to the 9560 when you need PCIe 4.0 bandwidth.
9560-16i: The Tri-Mode NVMe-Ready Controller
Supports SAS, SATA, and NVMe simultaneously on a PCIe 4.0 host interface, with 4GB/8GB cache and SecureBoot. Best for all-flash NVMe arrays, hybrid storage, and security-compliant deployments. The advantage over the 9460 is bandwidth, not NVMe support: the 9460 is already Tri-Mode, but its uplink is PCIe 3.1.
RAID Level Guide
| RAID | Min Drives | Efficiency | Best Use Case |
|---|---|---|---|
| RAID-0 | 1 | 100% | Cache/temp data |
| RAID-1 | 2 | 50% | OS boot, critical logs |
| RAID-5 | 3 | (n-1)/n | Read-heavy workloads |
| RAID-6 | 4 | (n-2)/n | High-capacity backup |
| RAID-10 | 4 | 50% | Database, virtualization, AI data |
Picking the controller generation for your storage tier
- 9361-8i is the SAS classic for existing spindle arrays and legacy backplanes
- 9460-16i is the mid-range tri-mode step, the usual default for a mixed SAS and NVMe array
- 9560-16i is the NVMe-ready option with the cache and lane headroom for flash-heavy workloads
RAID levels matched to the workload
- RAID 1 for small critical sets where rebuild time must be short
- RAID 5 and RAID 6 for capacity with a read-heavy mix; RAID 10 where write penalty matters
- RAID 60 for large-capacity tiers where parallel rebuild across multiple groups pays off
Cache, battery protection and rebuild risk
- Read and write cache changes rebuild time dramatically, which changes which rebuild is safe to run unattended
- A healthy CacheVault supercap is what lets a controller keep write-back mode through a power event
- On a used controller, the supercap and battery state are part of the acceptance test, not an afterthought
Related reading
- MegaRAID 9560-16i — the tri-mode NVMe-ready option
- MegaRAID 9361-8i — the SAS classic baseline
- RAID controller guide — controller fundamentals
- RAID controllers — category hub
Frequently Asked Questions
Which MegaRAID controller should I choose for a data center array?
Match the controller to the chassis and the media. 9361-8i for SAS-only spindle arrays, 9460-16i as the general tri-mode default when you have both SAS and NVMe bays, and 9560-16i for flash-heavy workloads that need the extra cache and lane headroom. If the answer is genuinely unclear, the RAID level guide below is usually the better starting point.
What is the difference between RAID 5 and RAID 6 for enterprise storage?
RAID 6 adds a second parity block, so it survives two drive failures instead of one, at the cost of one drive of capacity. That extra resilience matters when you cannot tolerate a second failure during a rebuild. RAID 5 remains reasonable for large, read-heavy sets where you have monitoring and fast spares.
How long does a RAID rebuild take and can I run it unattended?
It depends on the array size, the drive speed and the controller’s rebuild performance. What determines whether it is safe unattended is the headroom: a rebuild that runs at a fraction of the read bandwidth leaves the array responsive, and a controller with cache plus battery protection recovers faster. We will state the controller’s cache size and supercap status on any used unit.
Do I need write cache and battery protection?
Write cache with battery protection is what lets a controller acknowledge writes before they reach the media, which is a large throughput difference and the difference between surviving and losing a power event cleanly. A healthy supercap is part of what we test on a used controller, and we report its status per unit.
Is a 9460-16i worth it over a 9361-8i?
If your array includes NVMe drives or you want to run the controller in HBA mode for ZFS or TrueNAS, yes — the 9361 is SAS-only and does not offer that path. If the chassis is SAS-only and the workload is straightforward, the 9361 remains a sensible, cheaper choice.
How do you verify a used RAID controller before shipping it?
We clean, re-flash and bench-test on our own test line, then verify the part number, cache size, connector count, port mapping, firmware level and the CacheVault supercap status. We report the supercap state rather than leaving you to discover it at install time. Ask for photos of the actual card before you commit.