Comment 13 for bug 1683105

Well, tbh, I am having similar issues on another machine running RAID-0 (striped), so I do think that dm-raid is required on that too. Maybe it's RAID-1 (mirror) that doesn't need it but instead needs the dm-mirror module?

In any case, I understand the risks. I'm trying this out as research because there are circumstances that using "fakeraid" may be beneficial, for example recent cases where several Lenovo and Asus laptops are locked into "fakeraid" in addition to Secure Boot as a form of lock in to Windows 10- I'm convinced that with the use of kpartx + dmraid and proper disk preparation, one could get those working with Linux without the use of kernel hacks (my machines currently have their disks set up as GPT, but with a MBR compatibility partition for booting legacy GRUB).

I'm also interested in the aspect where the system would assign memory for read-caching to further improve performance (one AMD system I have assigns 256MB of system memory for this).

I also wish to research NVidia's claim that the NForce's RAID is hardware accelerated (both machines I have the RAID issue on runs off these NForce 980a motherboards).

Lastly, I use drive trays on one of the two builds, it seems to have reliability issues if the drives in them are set up as AHCI, but behaves properly if the drives are set up as RAID-0.