Skip to content
daniel@cosenza:~/blog
Haiku OSFix May 19, 2026 3 min read

Fixing Haiku Boot Failures with Safe Mode

Haiku won't boot normally, or hangs partway through. Here's how to use the boot loader's safe mode options to isolate which specific subsystem is actually at fault.

A Haiku system that fails to boot normally almost always has a specific, isolatable cause — a particular driver, a third-party add-on, or a hardware-acceleration path that doesn’t behave correctly on the specific machine. The boot loader’s safe mode menu exists specifically to isolate which one.

Step 1: reach the boot loader menu

Hold Shift (or Space, depending on the Haiku version) during the boot splash screen to bring up the boot loader menu, rather than letting it continue straight to a normal boot.

Haiku Boot Loader
 ├── Continue booting
 ├── Select boot volume
 └── Safe Mode Options

Step 2: try Safe Video Mode first if the failure is graphical

If the system hangs or shows corrupted graphics partway through boot, select Safe Mode Options → Safe video mode, which forces a fallback to plain VESA video rather than the normal graphics driver. If this resolves the hang, the problem is isolated to the graphics driver specifically, not the kernel or file system.

Safe Mode Options
 └── Safe video mode: ON   ← forces VESA fallback

Step 3: try disabling user add-ons if the failure looks unrelated to video

If video isn’t the issue, Disable user add-ons prevents third-party kernel add-ons (drivers or file system add-ons installed outside the base system) from loading. A boot that succeeds with this enabled, but fails without it, points at a specific installed add-on as the cause — worth checking recently installed packages or drivers for what might have introduced it.

A boot that hangs specifically while accessing storage — visible as a stall right around when the boot volume should mount — can sometimes be resolved by Disable IDE/SATA DMA, which falls back to a more conservative, non-DMA storage access mode. This trades storage throughput for compatibility, useful for narrowing down whether a storage controller’s DMA support is the actual problem.

Step 5: boot into safe mode successfully, then investigate the real cause

Safe mode getting the system to boot isn’t the end of the fix — it’s confirmation of which subsystem is at fault, letting you investigate further once you have a working system to work from: checking driver settings, removing a recently added package, or reporting the specific hardware combination if it looks like a genuine compatibility gap (see device drivers and hardware support in Haiku for why some hardware simply isn’t well supported yet).

Step 6: if nothing in safe mode helps, check the boot volume selection

Select boot volume in the boot loader menu confirms Haiku is actually trying to boot from the drive/partition you expect — a failure that looks like a driver problem is occasionally actually the boot loader attempting to boot the wrong volume entirely, especially on systems with multiple drives or a dual-boot configuration.

Why isolating the specific safe-mode option that helps matters

The value of Haiku’s safe mode menu is in its granularity — because each option targets one specific subsystem rather than being one blunt “boot minimally” switch, whichever option actually resolves the hang tells you directly where to focus further troubleshooting, rather than leaving you with a system that boots in a degraded state and no better idea of what was actually wrong.