I am having a problem deploying and capturing images with FOG on a HPE MicroServer Gen11 using Intel VROC RAID1.

Environment:

• FOG 1.5.10.1754
• Ubuntu 24.04.3 LTS
• Latest FOS kernel and init tested (20260306)
• HPE MicroServer Gen11
• Intel VROC SATA RAID Controller
• PCI ID: 8086:2826
• RAID1 volume named “SISTEMA”
• RAID size: 150 GB
• Two 1 TB SATA drives

Symptoms:

• Windows Server 2025 installs and boots correctly on the RAID1 volume.
• Intel VROC reports the array as healthy.
• Sysprep completes successfully.
• FOG can capture and deploy the image.
• However, after deployment the RAID becomes degraded and Windows fails to boot with INACCESSIBLE_BOOT_DEVICE (0x7B).

What I found:

• In FOS debug mode, lsblk only shows the physical disks:

/dev/sda 931.5G
/dev/sdb 931.5G

The RAID volume itself is never exposed as an md device.

mdadm can detect the Intel IMSM metadata:

mdadm --examine /dev/sda

Output includes:

Magic : Intel Raid ISM Cfg Sig
RAID Level : 1
Array Size : 150.00 GiB
Volume Name : SISTEMA

However:

mdadm --detail-platform

returns:

mdadm: imsm capabilities not found for controller:
/sys/devices/pci0000:00/0000:00:17.0 (type SATA)

Additional tests performed:

• Updated bzImage to 20260306
• Updated init.xz to 20260306
• Tested IMSM_NO_PLATFORM=1 mdadm --assemble --scan
• Tested mdadm -IRs
• Tested mdadm --assemble --scan --force

None of these create an md device and lsblk continues to show only sda and sdb.

It appears that FOS can read the IMSM metadata but cannot assemble or expose the Intel VROC RAID volume, causing deployment to operate directly on the physical disks instead of the RAID volume.

Has anyone successfully used Intel VROC (PCI ID 8086:2826) with FOG/FOS?

Any advice, patches, custom kernels, custom init.xz images, or mdadm workarounds would be greatly appreciated.

Thank you.