Troubleshooting VMD During an Ubuntu Dual-Boot Installation

When the Ubuntu installer cannot see the internal NVMe disk during a dual-boot installation, Intel VMD (Volume Management Device) is a common cause. VMD changes how the storage controller is presented, so disk detection depends on the distribution version, kernel, and device vendor configuration.

Changing VMD affects how the existing Windows installation boots. Back up important data, save the BitLocker recovery key, and record the original BIOS settings before making changes.

Symptoms and concepts

Typical symptoms include:

• The Ubuntu installer shows an empty disk list.
• Windows Disk Management sees the NVMe disk, while the Ubuntu Live environment does not.
• The BIOS storage settings include VMD, Intel Volume Management Device, RAID, or Storage Controller options.

VMD is a storage management controller on Intel platforms. After VMD is disabled, some devices are presented through the more general AHCI or standard NVMe path, which may allow the Ubuntu installer to detect /dev/nvme0n1.

Protection steps before changing settings

1. Back up important files in Windows and on existing partitions.
2. Check the BitLocker state in Windows and save the recovery key.
3. Record VMD, boot mode, Secure Boot, and disk-mode settings in the BIOS.
4. Prepare Windows installation media or a system recovery disk.
5. Record the device model and read the vendor’s guidance for VMD, RAID, and dual boot.

Changing the disk mode may trigger BitLocker recovery verification or affect the vendor recovery partition. Prepare the recovery path before making the change.

Confirm that Ubuntu really cannot see the disk

Open a terminal in the Ubuntu Live environment:

lsblk -o NAME,SIZE,TYPE,FSTYPE,MOUNTPOINTS
sudo dmesg | grep -iE 'nvme|vmd|ahci|raid'
sudo lspci -nn | grep -iE 'vmd|nvme|sata|raid'

Focus on these results:

• Whether /dev/nvme0n1 or another NVMe device appears.
• Whether the PCI device list contains a VMD or RAID controller.
• Whether the kernel log reports a controller initialization failure.

When the disk already appears in lsblk, the issue may involve the installer’s partition screen, disk encryption, available storage, or boot-mode configuration. Continue with the relevant line of investigation.

Option 1: Keep VMD enabled

When keeping VMD enabled, use this order:

1. Use a newer Ubuntu installation image and an updated kernel.
2. Check whether the computer vendor provides a Linux storage-controller driver or dual-boot instructions.
3. Confirm that the VMD and RAID configuration is consistent in the BIOS.
4. Verify disk detection in the Live environment before starting the installation.

Support for VMD varies across distribution and hardware combinations. When the installer still cannot detect the disk, evaluate a storage-mode change.

Option 2: Switch storage mode through Windows Safe Mode

When Windows was installed in VMD mode, disabling VMD directly in the BIOS may cause INACCESSIBLE_BOOT_DEVICE. Setting Windows to Safe Mode first allows the system to initialize the storage driver after the switch.

1. Set Safe Mode in Windows

1. Press Win + R and enter msconfig.
2. Open the Boot tab.
3. Select Safe boot and choose Minimal.
4. Apply the setting and restart; confirm that Windows enters Safe Mode.

2. Disable VMD in the BIOS

1. Restart the computer and enter the BIOS using the key shown by the device, commonly F2 or Del.
2. Find the VMD option under Advanced, Storage, VMD Setup Menu, or a similar page.
3. Set Enable VMD Controller to Disabled.
4. Save and exit.

BIOS menu names and locations vary by vendor. Photograph the original settings before changing them so that they can be restored.

3. Return Windows to normal boot

After Windows enters Safe Mode:

1. Run msconfig again.
2. Clear Safe boot.
3. Apply the setting and restart; confirm that Windows reaches the desktop normally.

Boot from the Ubuntu installation media again and use lsblk to check whether the NVMe disk appears.

Recovery paths when problems occur

Repeatedly switching the storage mode increases troubleshooting complexity. Change one variable at a time and verify the current system state before moving to the next step.

Checks after installation

After Ubuntu is installed, verify in order:

1. Ubuntu boots normally and detects the NVMe disk.
2. Windows boots normally.
3. The BIOS boot mode matches the mode used during installation.
4. BitLocker, Windows Update, and the vendor recovery tools are working normally.
5. The lsblk, findmnt, and disk-space results are as expected.

lsblk -f
findmnt /
df -h

The correct VMD approach depends on the device, the Windows installation state, and the Ubuntu version. A public tutorial should place BIOS differences, data backup, and Windows recovery steps before the commands.

References

• Ubuntu Desktop installation tutorial
• Ubuntu community: UEFI