Proxmox NVMe Boot on Dell R730: How I Fixed It (So You Don’t Have To)

Last updated on April 22nd, 2026 at 12:47 pm

Dell PowerEdge R730 running Proxmox with NVMe PCIe adapter

I recently set out to install Proxmox on a Dell server using an M.2 NVMe drive via a PCIe adapter.
I assumed it would be simple: install → reboot → done.

It wasn’t.

Proxmox NVMe Boot on the Dell PowerEdge R730 – What Actually Works

I’ll be honest — this one cost me an entire afternoon.

I’d added an M.2 NVMe via a PCIe adapter to my Dell R730, installed Proxmox onto it without a single error, rebooted confidently… and got hit with “No Boot Device Found.”

Classic.

I reinstalled three times. Checked BIOS settings I’d already checked. Googled variations of the same question for an hour. Eventually I found the answer — and it had nothing to do with anything I’d done wrong.

This guide is what I wish had existed when I started. If you’re staring at the same error, here’s exactly what’s going on and how to fix it.

The Problem – NVMe Installs Fine but Won’t Boot

This is where a lot of people get stuck.

On the R730, everything looks like it’s working:

  • The Proxmox installer sees the NVMe drive
  • You can select it and install without errors
  • The system writes the OS correctly

But when the system reboots:

The NVMe drive is not listed as a bootable device.

This creates a confusing situation where:

  • The OS is installed
  • The disk is functional
  • But the system simply refuses to boot from it

Why This Happens – NVMe Boot Support Isn’t Guaranteed

The R730 is a fantastic server — but it’s from a generation where NVMe was still relatively new, and Dell’s UEFI implementation simply didn’t include NVMe boot drivers.

So the system can detect your NVMe drive. It can install to it without issues. It just flat out refuses to boot from it natively.

The moment I understood this, everything clicked. I wasn’t doing anything wrong — the server just didn’t know how to hand boot control to an NVMe device without help.

Storage support ≠ Boot support. That’s the whole problem in one line.

The Solution – Using Clover to Enable NVMe Boot

Once I understood the limitation, the fix was actually pretty elegant.

You use Clover — a lightweight bootloader originally built for Hackintosh setups — to act as a bridge. It boots from a USB drive, loads an NVMe driver, then hands off cleanly to your Proxmox install.

I was sceptical at first. A USB bootloader felt like a hack. But it’s been rock solid in my lab — fully automatic, zero maintenance, and no noticeable performance impact after boot.

    What the Boot Process Looks Like

    Standard (What You Expect)

    BIOS → NVMe → Proxmox

    With Clover (What Actually Works)

    BIOS → USB (Clover) → NVMe → Proxmox

    Once configured, this process is automatic and you won’t even notice it’s happening.

    Step-by-Step: How to Fix NVMe Boot on R730

    Step 1 – Install Proxmox to NVMe

    Start as normal:

    • Boot from Proxmox ISO
    • Select your NVMe disk (/dev/nvme0n1)
    • Complete installation

    Don’t worry about boot issues yet—you’ll fix that next.

    Step 2 – Prepare a Clover Boot USB

    (The internal USB port on the R730 is perfect for this — it sits flush inside the chassis and you’ll never need to touch it again.)

    You’ll need:

    • A small USB drive
    • Clover bootloader files

    The critical step is enabling NVMe support inside Clover.

    Copy the NVMe driver:

    cp /EFI/CLOVER/drivers/off/UEFI/Other/NvmExpressDxe.efi \
    /EFI/CLOVER/drivers/UEFI/NvmExpressDxe.efi

    Without this file:

    Clover will not detect your NVMe drive at all.

    Step 3 – Configure BIOS on the R730

    Before booting:

    • Set Boot Mode: UEFI
    • Change SATA Mode: AHCI (not RAID)
    • Enable USB Boot
    • Set USB as first boot device

    These settings are critical—especially switching away from RAID mode.

    Step 4 – Boot Using Clover

    • Insert USB
    • Boot the server
    • Clover menu will appear
    • Press F3 to show boot options
    • Select your Proxmox NVMe install

    If everything is configured correctly:

    👉 Proxmox should now boot successfully

    Step 5 – Make It Boot Automatically

    Manually selecting the OS gets old fast.

    To automate:

    Find your EFI partition:

    fdisk -l
    blkid

    Mount it:

    mount /dev/nvme0n1p2 /mnt

    Locate boot file:

    find /mnt -iname "*.efi"

    You’ll typically find something like:

    /EFI/proxmox/grubx64.efi

    Then:

    • Edit Clover config.plist
    • Set default boot entry to this path

    Now your system will:

    • Boot → Clover → Proxmox automatically

    Performance Benefits of NVMe on Proxmox

    Once it’s working, the payoff is worth it:

    • Faster VM disk I/O
    • Better responsiveness
    • Improved ZFS performance (if used)
    • Reduced latency compared to SATA SSD

    Even with a USB bootloader in the chain, performance is unaffected after boot.

    “If you’re also setting up VLANs for your VMs, here’s how I structured my home lab network.”

    Is This Setup Reliable?

    Yes — and I was surprised by how much. I’d been running this setup for weeks before writing this post and haven’t had a single boot failure. Once Clover is configured and the USB is plugged into the internal port, it just works every time, completely automatically.

    The USB drive rarely if ever needs touching, and because Clover is so lightweight, it adds maybe a second to the boot process — if that.

      Frequently Asked Questions

      **Does the Dell R730 support NVMe boot natively?**
      No — the R730’s UEFI firmware doesn’t include NVMe boot drivers. You need a bootloader like Clover to bridge the gap.

      **Will this slow down Proxmox performance?**
      No. Clover only runs during the boot sequence. Once Proxmox is loaded, performance is identical to a native NVMe boot.

      **Which USB drive should I use for Clover?**
      Any small USB drive works. The R730’s internal USB port is ideal — it sits flush inside the chassis and never needs touching.

      **Does this work with other Dell PowerEdge servers?**
      Yes — this same method works on other older Dell servers with similar UEFI limitations, including the R720 and R620.

      Final Thoughts (And What to Do Next)

      This took me way longer to figure out than it should have — which is exactly why I wrote it up.

      If you hit “No Boot Device Found” after installing Proxmox on an NVMe in your R730, your server isn’t broken and you haven’t misconfigured anything. The hardware just needs Clover to bridge the gap. Set it up once and you’ll never think about it again.

      If this saved you time, drop a comment below — and if you’re building out your full R730 home lab, check out my complete build guide linked below.

      What to Read Next

      If you’re building out a homelab on the Dell PowerEdge R730, these are worth checking out next:

      My Full R730 Homelab Build Guide

      Scroll to Top