[SOLVED] UEFI firmware raid in mageia 4

[vzawalin1]

I have just purchased a Clevo P370SM-A laptop with an SSD and two identical hybrid hdd. The AMD UEFI firmware (exact release version tba) allows setting up RAID 0 or 1 on two or more SATA disks. MGA4 is now installed on the SSD with the two sshds in raid 0 (at firmware level). MGA4 recognises the two sshds individually in Dolphin and the Drake partitioner. Earlier, in attempting this exercise with current versions of Ubuntu and OpenSuse, I found that the raid 0 'array' showed up in Dolphin as a single device with twice the space. There were issues in these trials with actually using the raid disk for anything, but it seemed to be there. OpenSuse also insisted on installing itself entirely on the raid array under UEFI boot control. I don't recall if Ubuntu had been installed (by the resellers) for UEFI boot or not, as I was then trying to get my mind around UEFI in the first place.
Is there a viable way to get MGA4 to recognise a firmware (aka UEFI) defined raid array and if not, is this likely to be implemented in MGA5? I remember reading somewhere that full UEFI support would be implemented in MGA5. Any comments will be greatly appreciated.

[doktor5000]

See https://wiki.mageia.org/en/UEFI_how-to and for the planned Mageia 5 features https://wiki.mageia.org/en/FeatureMageia5_Review
UEFI is not on that list, and if there's no UEFI support, probably that array will not be recognised.

Although I've no clue why you want to waste the capacity of one of those SSD drives on a RAID 0 ...

[vzawalin1]

Doktor5000,
thank you for your reply and the informative references.
Raid 0 for the two WD 1TB hybrid 5400 rpm disks was considered primarily because they were already there and to somewhat improve handling of large video and audio files. The SSD cache in hybrid drives is said to be mostly efffective for repetitive access to small files.
The pure SSD remains the system 'disk' with attendant improvement in general responsiveness. I now use the hybrid drives individually for swap, /var, /tmp, /home and all is well.

[xboxboy]

I don't know if this might apply or not, but I've had trouble with mdadm recognising my raid arrays, and have had to fall back to using dmraid, even though mdadm has superseeded dmraid as the driver of choice for my particular chip set.

See the following for my solution:
https://forums.mageia.org/en/viewtopic.php?f=7&t=5191&p=40652#p40652

[vzawalin1]

Thank you xboxboy and ghmitch for your comments.
What I had was fake-raid. In following up bug-report 9440 and your posts via the link, I now have some idea where to start. Neither dmraid nor the other adm application were installed, as I did not know about them.
Since my first post, I have set up partitions on each mechanical disk in software raid. This works, but it would be particularly useful to have a raid array accessible to Linux MGA4 and to windows-only video editing applications. For this, fake raid will be necessary and xboxboy, I will certainly follow up your suggestion re the filter code.
Thanks agin.

[xboxboy]

Glad I could help. I wasted DAYS on that. I've tried on Mga4 & Mga5 alpha, but mdadm will just not work for me.