Intel RST, VMD, RAID, and AHCI Explained for Ubuntu

Before Ubuntu can use a disk, it needs a supported way to communicate with it. The hardware and firmware that manage this path are often described together as the storage controller.

This lesson contains several similar-looking names. You do not need to memorize all of them. You mainly need to recognize which kind of setting you are looking at and avoid changing it before choosing whether Windows must remain.

Recognize three groups of storage terms

These names describe different parts of the route between Ubuntu and a disk. A firmware screen may show more than one group at the same time.

Where the setting lives: BIOS and UEFI

Firmware is startup software built into the computer. It checks hardware and prepares the machine before Windows or Ubuntu starts.

BIOS is the older kind of PC firmware. UEFI is its modern replacement. People often use “BIOS” as a general name for the setup screen even when the computer actually uses UEFI.

For this lesson, BIOS or UEFI is where you inspect the computer’s storage settings. It is not the name of the SSD or the storage mode.

How the drive communicates: SATA and NVMe

SATA is a connection and command family used by many hard drives and SSDs. NVMe is a protocol designed for solid-state storage, commonly connected through PCI Express.

A computer can contain SATA storage, NVMe storage, or both. These terms describe how storage communicates, not whether Ubuntu should erase or preserve it.

How firmware presents the storage: AHCI, RAID, RST, and VMD

AHCI is a standard interface for accessing SATA storage. It gives operating systems a conventional controller mode they commonly support.

RAID can combine physical disks into a logical storage arrangement for redundancy, performance, or both. A firmware menu may also use a RAID label on a computer that has only one visible drive. That label alone does not tell you whether a real multi-disk RAID arrangement contains important data.

Intel Rapid Storage Technology (RST) is an Intel storage solution that can manage disks and RAID configurations. Ubuntu’s installer may report an RST conflict when it cannot access disks through the active arrangement.

VMD, or Intel Volume Management Device, lets supported Intel platforms manage NVMe devices through an Intel-controlled storage path. A firmware screen may expose a VMD switch without using the word RST.

These terms can overlap in one computer design, but they are not interchangeable labels on every machine. The exact menu wording and effect depend on the model.

Recognize possible firmware labels

Manufacturer wording varies. Examples include:

• RAID On
• Intel RST
• RST Premium
• VMD Controller
• Enable VMD
• SATA Operation
• Storage Controller Mode
• AHCI
• AHCI/NVMe

An example label is not an instruction. Find the exact model’s official service or firmware guide. Record the original value with a written note or privacy-safe photograph before making one change.

Why Ubuntu can report an RST conflict

You may see an RST warning in the installer, or you may find that the internal SSD is absent even though UEFI detects it.

Canonical explains that the installer can detect some RAID configurations but may be unable to access disks grouped or presented through RST. Depending on the computer, the supported resolution may involve turning off RST or changing the controller protocol to AHCI.

That does not prove every missing SSD is an RST problem. Firmware must detect the disk first. Hardware failure, a disabled slot, an unusual controller, or another platform issue can produce a similar symptom.

First decide whether Windows must remain. Then follow the matching branch below instead of changing the first familiar-looking menu item.

Branch A: Windows will be erased

Use this branch only when the written decision from Lesson 1.1 is to remove Windows completely.

1. Verify the backup by opening several copied files from another device.
2. Record the original controller and VMD/RST settings.
3. Confirm the internal disk appears in UEFI setup with the expected capacity.
4. Change only the relevant documented storage option for this model, for example from a RAID/RST mode to AHCI or by disabling the VMD controller that hides the target.
5. Save the firmware change and boot the Ubuntu USB in UEFI mode.
6. Choose Try Ubuntu and open Terminal.
7. Run the read-only device list.

lsblk -o NAME,SIZE,TYPE,FSTYPE,MODEL,MOUNTPOINTS

8. Confirm that the internal model and capacity now appear separately from the USB.

If the drive remains missing, restore the recorded firmware value rather than changing unrelated settings. Seek model-specific help.

Branch B: Windows must be kept

Stop before changing the controller directly. Windows was installed expecting its current controller path and might respond with an inaccessible boot device or recovery prompt after a blind switch.

1. Back up important Windows files.
2. Check BitLocker or Device Encryption status.
3. Back up and test access to the BitLocker recovery key.
4. Read BitLocker and Ubuntu Dual Boot.
5. Follow Canonical’s current Reconfigure Windows to use AHCI guide from beginning to end.
6. Use the model manufacturer’s official firmware steps for the controller change.
7. Start Windows after the change and confirm that it boots normally and files are intact.
8. Only then return to Try Ubuntu and rerun lsblk.

This lesson deliberately does not excerpt registry changes. A partial registry recipe separated from Canonical’s backup, BitLocker, firmware, and recovery sequence is more dangerous than a clear link to the maintained full procedure.

Common mistakes and recovery

Disabling every VMD or RAID-related option. Change one documented setting, record it, and test. Some systems use these features for more than one device.

Assuming AHCI applies to every NVMe design. Firmware implementations differ. Use the model documentation and Canonical’s RST guidance, not a copied menu name.

Skipping Windows verification. When Windows must stay, boot it successfully after the controller preparation before returning to Ubuntu.

Forgetting the recovery key. Firmware and boot changes can trigger BitLocker recovery even when data is not being intentionally decrypted.

Claiming the original cause after several changes. Restore a controlled baseline and change one variable if you need a reliable diagnosis.

What to learn next

If Windows remains on the computer, continue to BitLocker and Ubuntu Dual Boot: Prepare Windows Safely. When the internal drive is visible and Windows preparation is complete, read Ubuntu Installation Options Explained.