What's worse: if you try and mount the drives, it doesn't say "this looks like a raid1 volume, I don't have drivers for that, please upgrade to access this data", it says something more like "data corrupt, would you like to format this drive? [Yn]" :/
As far as hardware RAID controllers, at least you get a battery-backed write cache that will "just work" without the OS, right? As in, you don't need to boot the OS to finish flushing. Or maybe I've just bought into the hardware RAID marketing. It does seem simpler, as in less to deal with, to let the card do it and just present whatever volumes desired to the OS.
Same thing on Windows 7 (that may be limited to the pro/entreprise editions)
Since windows server 2012. The OS has "storage spaces" which is a full management solution for RAID and volumes and physical disks. It's somewhat similar to the ZFS/zpool/mdraid/dmcrypt tooling, EXCEPT it's all in a single software, unified, way easier to use and with a nice GUI.
IMO. Software raid and disk management is utter shit on Linux. They are easily lagging > 10 years behind but that's just my point of view.
Make a simple search on google on "how to resize a partition on linux" and you get ten tutorials, all of which give different steps, none of which work.
There are at least 7 different tools for managing disks on linux most of which vary by distribution and version: fdisk, mkfs, partx, parted, growpart, mdraid, dmcrypt...
Little story: The auto extending of partitions on boot (i.e. a critical thing in cloud environment) has been broken in debian stable for more than 6 months.
It's calling "growpart" that is calling other tools, one of which is "partx". Some flags are changing between versions and it breaks the whole toolchain, unless all software versions are carefully selected.
We could continue on why do some of the tools only accept cylinder and block counts as size??? or why is gparted a terrible GUI for managing disks.