The RAID boot drive has long been an awkward corner of EPYC servers. Protecting the system disk traditionally means adding a hardware RAID card: it consumes a PCIe slot, adds power and BOM cost, and brings its own management toolchain. The cheap route is Linux mdraid — fine for data volumes, but UEFI boot means handling the ESP and the bootloader yourself, and drive-LED and hot-plug integration depends on extra OEM tooling. Otherwise you run a single NVMe drive unprotected: when the system disk dies, the whole server stops. On Intel, VMD+VROC answered this long ago with "bootable RAID straight from CPU-attached NVMe"; AMD server platforms have lacked an equivalent. Now the fill-in has a date: Graid Technology announced that VROC is coming to AMD EPYC in 2027-02, starting with Linux RAID 1 boot-drive protection and requiring no dedicated RAID controller. The announcement came in Graid's official press release (2026-11-16), with StorageReview following up on 2026-11-20.

How VROC works: RAID at the CPU PCIe root complex, the HBA disappears

Graid VROC product brief and technical specification sheets (official document photo, Intel Xeon 6 and AMD EPYC roadmap)
Graid VROC product brief and technical specification sheets (official document photo, Intel Xeon 6 and AMD EPYC roadmap)

VROC (Virtual RAID on CPU) hangs NVMe SSDs directly off the CPU's PCIe root complex, with firmware (UEFI) and OS drivers cooperating to deliver RAID — no discrete RAID card/HBA in the data path. After taking VROC over from Intel, Graid returned it to active development on Xeon 6 with backing from Lenovo and Supermicro; the official product page positions it as "bootable RAID 0/1/5/10, no HBA", available 2026 Q3, launching on Xeon 6 D and W. Its claims versus legacy HBA-based RAID (vendor figures, Intel platform, 8-drive RAID 0, methodology in official footnotes, results may vary): up to 45% higher IOPS, up to 31% lower latency, up to 49% better power efficiency and up to 75% lower TCO, with throughput up to about 29GB/s and read IOPS up to about 6M. These numbers belong to the Intel platform and cannot be extrapolated to the unreleased EPYC version.

From Intel to AMD: the 2027 roadmap

CPU-native RAID concept render from the Graid VROC page
CPU-native RAID concept render from the Graid VROC page

On Intel, VROC is built on Intel VMD and UEFI and supports RAID 0/1/5/10 under Windows, Linux and VMware ESXi (the Graid product page additionally lists ESXi RAID 1/5 on the roadmap). EPYC platforms have no Intel VMD, and Graid has not said what mechanism replaces it or which EPYC generations are covered — the two biggest blanks in this announcement. The official roadmap (features vary by platform; timelines subject to change):

TimingPlanned VROC features on AMD EPYC
2027-02Linux support; RAID 1 boot-drive protection
2027 H1RAID 0/5/10; drive-status LED management; hot-plug
2027 H2Out-of-band management; Windows support; SATA support; self-encrypting drives (SED), including SED hot-plug

Graid says final testing and integration are underway with several server OEMs, none named. Founder and CEO Leander Yu put it plainly: "Customers shouldn't have to change their data-protection strategy just because they choose a different processor platform." EPYC is only the starting point, with more server and edge platforms planned. Graid's SC26 booth is 1326.

Why RAID 1 boot drives come first

Boot drives need availability, not bandwidth. RAID 1 mirrors two drives: either one can fail and the system still boots, rebuild logic is simple and CPU pressure is low — the safest first step for firmware-level bootable RAID. RAID 5/10 adds parity and striping, a much larger validation surface, so slotting them into 2027 H1 is reasonable. This also extends Graid's product division of labor: VROC guards boot and OS volumes (the product page also mentions database volumes), GPU-accelerated SupremeRAID guards the performance data tier, and SupremeIO does KV cache acceleration — the two already coexist on Intel platforms, and the EPYC roadmap enters through the same boot-drive role. For operations, "mirror the system disk, treat data volumes separately" is the cleanest fault-domain split anyway.

Three routes compared: hardware RAID card, mdraid, VROC

DimensionHardware RAID cardLinux mdraidVROC (Graid)
Form factorDiscrete PCIe card, occupies a slotKernel software, zero hardwareCPU PCIe direct + UEFI/drivers
BootableNativeRAID 1 requires handling ESP and the bootloader yourselfNative (firmware level)
ManagementSeparate toolchainmdadm + homemade scriptsPlatform-integrated; LED/out-of-band on the roadmap
CostCard + power + BOMZero license, consumes ops hoursNo card; licensing model unpublished
Main riskThe card itself is a failure point and single pointRebuilds consume host CPU; integration is DIYAlso consumes host CPU (vendor claims minimal overhead); EPYC implementation details unpublished

Two sobering points. First, VROC is still CPU-based RAID at heart: parity and rebuilds consume host compute, not the full offload of a hardware card; the vendor's "minimal overhead" claim needs testing under your workload, especially RAID 5 rebuilds overlapping business peaks. Second, ecosystem details decide the operations experience: Intel VROC historically differentiated licensing by RAID level and SSD brand, and Graid's licensing model on EPYC (paid or not, hardware key required or not, a restricted SSD compatibility list or not) is unpublished — confirm it in writing before procurement.

Advice for server operations and procurement

For service providers maintaining mixed Xeon and EPYC fleets (including server repair and integration teams like ours), the value is toolchain convergence: one RAID and management interface across both platforms standardizes spares strategy, system images and fault-handling SOPs. But get the timing right: the 2027-02 first release covers only Linux RAID 1 boot drives — Windows fleets wait until 2027 H2, and RAID 5/10 data volumes wait for 2027 H1 subject to OEM qualification; hardware-card or mdraid setups running stably in production need no mid-lifecycle teardown. When purchasing new EPYC machines, put "VROC support or not, covered generations, SSD compatibility list, rebuild and hot-plug demonstration, LED and BMC integration" into the RFQ, and demand a written qualification matrix from the supplier. Also per the official product page, the 24-month roadmap Graid is shaping with Tier 1 OEMs lists GDS, OpenBMC, PLDM5 out-of-band firmware updates, SED hot-plug, NVMe HDD and PCIe Gen6 — the direction is right, but these remain plans.

Sources & verification notes (accessed 2026-11-22)