Skip to content
Haiku OSFix Published Updated 3 min readViews unavailable

Fixing a Haiku UEFI Installation That Boots Only from the Installer Media

A current, non-destructive Haiku UEFI recovery path covering firmware mode, GPT and ESP checks, Installer's EFI-loader tool, and boot verification.

If an installed Haiku system starts only while the USB installer is attached, the operating-system partition may be intact while firmware has no usable UEFI boot path on the internal disk. Recovery should preserve the existing EFI System Partition and other boot managers. Formatting or repartitioning first can turn a narrow loader problem into data loss.

Establish the actual boot mode

Confirm that the machine and installed Haiku architecture support UEFI and that the installer itself was booted in UEFI mode, not through a legacy compatibility path. Firmware menus often show two entries for the same USB device. A UEFI installation expects a GPT disk and a FAT32 EFI System Partition (ESP); a legacy BIOS installation follows a different chain.

Back up important data before changing partition metadata. In DriveSetup, identify disks by capacity and existing partition layout rather than by an assumed device number. Locate the internal disk’s existing ESP—normally a small FAT32 partition marked for EFI use. A dual-boot computer probably already has one. Do not initialize, erase, or recreate that partition just to add Haiku.

Use the current Installer repair action

Current Haiku development builds expose Tools → Install EFI loader in Installer. The action lists suitable FAT32 partitions on GPT disks and copies the EFI loader from the Haiku boot environment to the selected ESP. This is the preferred first repair when the option exists because it uses the loader matching the running installation media and avoids hand-copying an obsolete guide’s filenames.

Boot the installer in UEFI mode, open Installer, choose Install EFI loader, and select only the verified ESP on the internal target disk. Read the confirmation carefully. The source of the loader is the booted Haiku environment; the selected partition is the destination. Leave other vendors’ directories in the ESP untouched.

If the tool is absent, the installer may be an older image. Prefer booting a current official image and using its supported action. Manual procedures should follow the UEFI guide for that exact Haiku release; do not assume a path from an old forum post remains correct.

Check firmware discovery without erasing anything

Shut down, remove the installer USB, and open the firmware’s one-time boot menu. Look for the new Haiku entry or a generic entry corresponding to the internal disk. Some firmware ignores vendor entries but checks the standard fallback loader path; the supported installer action is designed around Haiku’s current boot files, while firmware behavior remains vendor-specific.

If no entry appears, recheck:

  • the USB and target used UEFI rather than legacy boot;
  • the internal disk is GPT and the selected partition is FAT32;
  • the ESP has free space and was writable;
  • firmware permits booting the loader and Secure Boot policy is compatible;
  • the loader was written to the internal disk, not back to the USB;
  • an aggressive firmware update did not delete or reorder boot entries.

Do not disable security features permanently as a diagnostic shortcut. Record the original firmware settings, make one reversible change, and restore it if it does not explain the failure.

Separate loader success from system-volume failure

UEFI directly starts Haiku’s loader, which then locates the system volume and continues boot. If the Haiku boot menu appears but the installed volume fails later, EFI discovery is already working. Use the Boot Loader’s volume selection, safe-mode options, and prior package states to diagnose the next stage instead of repeatedly reinstalling the EFI files.

Complete the repair by booting twice with the USB absent, confirming the intended Haiku volume, checking that other installed operating systems still boot, and recording the disk and ESP used. The safe fix adds the current Haiku loader to a known ESP; it does not destroy a shared boot ecosystem to make room for it.

Related:

Sources:

Comments