Verifying Installation Media Integrity
The most common cause of this error is a corrupted or improperly written installation ISO. If the checksum of the downloaded file does not match the official values from Canonical, the bootloader files may be incomplete. Always verify the SHA256 sum before burning the image. Use tools like balenaEtcher or Rufus in DD mode rather than ISO mode for server installations, as they write the image byte-for-byte to the drive, preserving the necessary boot sectors.
If you are using a physical server with limited USB port support, try switching ports to USB 3.0 or 2.0 depending on controller compatibility. Some older server motherboards struggle with high-speed controllers during the early boot phase. Additionally, ensure the USB drive is formatted correctly; FAT32 is often required for UEFI booting, while ext4 might be needed for specific legacy setups.
Adjusting BIOS and UEFI Settings
Server hardware often defaults to strict security settings that block external boot devices. Enter the BIOS setup by pressing F2, Del, or F12 during power-on. Locate the Boot Order menu and move your USB drive to the first position. If you see an option for "Secure Boot," disable it temporarily. Ubuntu Server 24.04 supports Secure Boot, but some enterprise firmware implementations have bugs that prevent third-party bootloaders from loading.
Check the SATA Operation mode as well. Switch between AHCI and RAID (or Intel RST) if the installer fails to detect the internal drives after the initial boot. AHCI is generally preferred for standard installations unless you are configuring hardware RAID. Save changes and reboot. If the system still reports no boot device, check if the USB was detected in the BIOS list at all. If it is missing, the hardware interface may be incompatible.
Checking Partition Table and Disk Layout
If the USB boots but fails to install or find the target disk, the issue may lie in the partition table of the destination drive. GPT partition tables are required for UEFI systems, while MBR is used for Legacy BIOS. You can check the current layout using lsblk or fdisk -l from a live session. Ensure the target disk has a valid EFI System Partition (ESP) if you are installing on UEFI.
Sometimes, residual partitions from previous installations confuse the installer. Wipe the disk using dd if=/dev/zero of=/dev/sdX bs=1M status=progress where sdX is your target disk. This removes old bootloader signatures and partition headers. After wiping, restart the installation process. The installer should now create a fresh partition scheme without conflicts.
Dedicated IPMI or BMC Access
For rack-mounted servers, direct console access may be difficult. Use the Integrated Management Module (IMM), iLO, or IPMI to mount the ISO virtually. This method bypasses physical USB limitations entirely. Log into the BMC web interface, navigate to Virtual Media, and attach the Ubuntu ISO. Set the virtual CD-ROM as the primary boot device in the remote console.
This approach also allows you to view the full boot log remotely, which is invaluable for diagnosing silent failures. If the virtual media fails to mount, check the network configuration of the BMC. Ensure it is on the same subnet as your workstation and that firewall rules allow VNC or HTML5 console connections. Some BMCs require specific Java applets or browser extensions for virtual media to function correctly.
How to Install Specific Linux Kernel Headers can also assist if you need to compile custom drivers for specialized hardware detected via IPMI logs, ensuring compatibility before finalizing the OS installation.Network Boot Considerations
In data center environments, PXE boot is often preferred over local media. If you are attempting to boot from the network, ensure the DHCP server provides the correct next-server address and boot file name. The Ubuntu Server installer uses netboot.tar.gz for minimal network installations. Verify that the TFTP server hosting these files is accessible and contains the correct version matching your server architecture (amd64 or arm64).
Misconfigured DNS or proxy settings in the PXE environment can also lead to boot timeouts that resemble "device not found." Check the network cable connections and switch port configurations. Enable VLAN tagging if your network requires it, and pass the appropriate tags through the PXE client configuration. Test connectivity with a simple ping command from the PXE shell before proceeding.
Hardware Compatibility Checks
Certain NVMe drives or RAID controllers are not supported by the default kernel in Ubuntu Server 24.04. If your hardware is very new or very old, you may need to use a newer kernel version. Download the HWE (Hardware Enablement) stack ISO or add nomodeset to the GRUB command line if display issues prevent boot progression. While nomodeset does not fix boot device errors directly, it helps isolate graphics-related hangs that stop the installer from initializing storage drivers.
Review the Ubuntu Certified Hardware List for your specific server model. If your storage controller is listed as unsupported, consider using a different PCIe slot or adding a compatible SATA expansion card. Sometimes, simply changing the physical connection type can resolve detection issues that software troubleshooting cannot fix.
Frequently Asked Questions
Why does my USB drive disappear from the BIOS boot menu?
This usually happens because the BIOS only lists devices with valid bootable partitions. If the USB was written incorrectly, it lacks the necessary boot sector. Re-flash the drive using Rufus in DD mode or balenaEtcher to ensure the correct structure is created.
Can I enable Secure Boot for Ubuntu Server 24.04?
Yes, Ubuntu Server 24.04 supports Secure Boot out of the box. However, if you experience boot failures, disable it temporarily to rule out firmware incompatibilities. You can re-enable it later once the system is installed and updated.
What should I do if the installer cannot see my hard drive?
Check the SATA operation mode in BIOS, switching between AHCI and RAID. Also, verify that the drive is not locked by a previous encryption or RAID configuration. Wiping the disk with zeros often clears conflicting metadata that hides the drive from the installer.
Is PXE boot faster than USB for large data centers?
PXE boot eliminates physical media handling and allows centralized management, making it more efficient for scaling. However, it requires robust network infrastructure and a configured TFTP/DHCP server. For single-server setups, USB remains simpler and more reliable.
How do I access the boot menu on a Dell PowerEdge server?
Press F11 during POST to access the One-Time Boot Menu. For deeper configuration, press F2 to enter System Setup. Ensure that Virtualization Technology and VT-d are enabled if you plan to use virtual media features via iDRAC.