Where as I was always told to avoid hardware raid if possible, and that's been a mantra for 15+ years.
The reason I was given is twofold. 1) If your RAID card dies it's nice to be able to plug drives into any controller and be able to access the data. 2) "look at how often MDADM fix bugs. Now look at how often your RAID card firmware gets fixed... use MDADM".
Modern filesystems like btrfs & zfs both prefer to deal with the RAID aspects themselves as it gives them far more control. Even if you're a hardware raid afficianado, I wouldn't recommend formatting (eg) ZFS on top of a hardware raid pool.
I'm not recommending some abstract hardware RAID, I'm recommending this particular card for personal use, with backup obviously. Although if you just use RAID 0 or 1, then data is perfectly readable outside of RAID with a normal SATA controller.
Even for home use I'm not sure I could recommend them.
From experience using them in servers, I'd site a handful of problems:
+ Raid 5 requires BBWC
+ Raid 6 requires licensing
+ HPE requires a support contract to download most firmware
+ When used in servers, they report non-hp drives as being in a constant fault state.
I mentioned the BBWC because the first few links I found to buy the card didn't include it.
Nice to see firmware available - in 2014 HP started requiring support contracts or warranties to download firmware updates for the servers which really turned me off them. I didn't realise RAID firmware wasn't included in that (for some reason iLO firmware isn't either, but I think that's probably because it includes OSS). For this reason alone I'd avoid HP on principal.
I'm hoping one day I can find a reasonably cheap RAID card that still supports using hte BBWC in JBOD mode...
they are different animals .. 'right tool for the right job'
hardware raid has the hw complexity / pickyness you mention, but also is safer in crashes for checksumming raid levels (e.g. 4,5,6) since the stripe checksum happens from controller->disk in hardware rather than os->controller->disk in software, so you're less likely to lose a stripe due to OS issues (all else - like bugs - being equal)
also, IO wise, any mirrored raid is going to require N*mirrors of IO on the system bus, so you're more likely to saturate it
that said, with faster tech (NVMe), individual drives can easily saturate a single card, so its 'worth' paying the multiple IO pentalty multiplexed onto multiple individual lanes since the card is more likely to be the bottleneck than the bus
also, hw raid controllers even in jbod mode might be needed to get enough device fanout, though you're not using the controller for raid in that case
The reason I was given is twofold. 1) If your RAID card dies it's nice to be able to plug drives into any controller and be able to access the data. 2) "look at how often MDADM fix bugs. Now look at how often your RAID card firmware gets fixed... use MDADM".
Modern filesystems like btrfs & zfs both prefer to deal with the RAID aspects themselves as it gives them far more control. Even if you're a hardware raid afficianado, I wouldn't recommend formatting (eg) ZFS on top of a hardware raid pool.