Hey,
I’ve installed Haiku twice from DVD into a partition “Haiku Rescue” and “Haiku” with the idea beeing that Haiku can be a nightly but I have a fallback.
I’ve never used bootman before, anyway when I try to boot Haiku now it can only boot Haiku Rescue and not the other one.
It comes up “Error Loading sectors” (after that I tried to reinstall from haiku rescue → Haiku)
The disk is a brand new ssd so I am quite confused by that. Am I missing some step?
FWIW, I use BootManager in 3 disks on my main machine to boot 32/64 bits installs, and had BootMan as my main boot menu on a netbook for the last 11 years (booting Win/Lin/Haiku). Never seen that error 
Never seen that before. I have an SSD with my daily Haiku install, a 32bit Haiku, a 64bit Haiku, a “Testiku” Haiku test install, and a linux install (plus half a dozen data partitions, not set up in Bootman’s menu, ofc).
All my Haiku partitions are in an “Intel Extended Partition”.
Maybe try reinstalling BootManager from “Haiku-Rescue”, just in case some partition data changed after you reinstalled on the “Haiku” partition somehow. (Usually I only need to re-run BootManager if I change the partition table, though).
I’ve repartitioned with gpt.
Haiku boots fine! (that’s good)
So clearly the protective mbr works.
However Haiku’s bootman refuses to install to gpt saying it is an incompatible format. I don’t suppose anyone knows why?
Maybe for safety? It’s really not a good idea to mix an MBR with a GPT initialized disk. The protective MBR is really only there to stop GPT unaware partitioning tools from nuking GPT partitioned disks that they would otherwise see as empty.
Perhaps. But clearly Haiku wrote (a) boot sector that works for booting into Haiku, so i would argue that bootman itself may be possible aswell. I’m trying to read up about this a bit more currently to see if this linitation is fixable or not.
It used to work: #13076 (Bootman does not work with GPT drives) – Haiku
It looks like This was blocked deliberately because Bootman uses 4 sectors on the disk, not one. And would overwrite parts of the gpt table that way. (while gpt has a backup table at the end)
So if we want to make this work again we have to find another solution. Maybe add a tiny partition at the start with bootman in it and have the normal mbr chainload it or something.
relevant commit: https://cgit.haiku-os.org/haiku/commit/src/apps/bootmanager?id=39681c5c0f0bae606c5c3aa8f249e8410e931af4
Honestly, I’m not sure we do. I would rather have people migrate to efi and refind, or keep using mbr if they insist on using other legacy technologies like bios.
It would be nice if the bootman installer would install and configure refind, or some other boot manager, on efi systems
My computer, in this case, does not support EFI, and bootman on mbr partition table also did not work : )
Actually, EFI loaders not being hybrid (even if a build has leaked in another thread), MBR is still the best option if you want to put Haiku 32 bits and 64 bits on the same (removable) media.
That sounds like a bug that deserves a ticket.
Off-topic: +1 to waddlesplash’s suggestion in that commit:
