Before you read, be aware that this is the story of a few failures, and what I learned, not a call for help.
I successfully installed hrev52031 in a virtual machine (VirtualBox) and now that I wanted to do some Wi-Fi & Ethernet testing I installed Haiku hrev52039 on an old laptop - sort of.
Important: I read the [Making a Haiku USB Stick](http://Making a Haiku USB Stick) guide and I decided to use Etcher to write the hybrid ISO to the USB drive.
I booted from the USB drive, I wiped all the partitions from the HDD, I created a single partition for Haiku, I formatted it and made it active, I installed Haiku and after I rebooted I saw a broken grub (I had Ubuntu previously).
I assumed there was something wrong with hrev52039 or DriveSetup, which doesn’t do anything (after the partition is formatted) when I click Change parameters… in the Partition menu, although the option is active when I have the Haiku partition selected. So I ended up reading How To Get Haiku Booted and then makebootable - What and why and how to do it manually.
So I booted Haiku from the USB drive (with Haiku installed on the HDD), I used makebootable on
/dev/disk/ata/0/master/raw, I rebooted and I got Haiku’s boot loader but it couldn’t boot for some reason. I booted from the USB drive again and, to my surprise, DriveSetup reported I had no formatted partition on my HDD. It looks like makebootable installed the boot loader but also wiped my previous installation. By the way, I used
/dev/disk/ata/0/master/0 was not accepted by makebootable.
So I reinstalled Haiku and I still had the newly installed Haiku boot loader but the OS failed to boot for some reason. But after so many tries it occurred to me that I have two volumes named Haiku:
- first, Etcher automatically (without an option to name/change the label) named the partition Haiku;
- second, each time when I formatted the newly created partition, DriveSetup proposed the volume name Haiku, which I accepted without second thoughts.
Now the more experienced people around here probably know what went wrong. Anyway, with me lacking experience with installing Haiku, I assumed the volume names are nothing but decorative, because I never encountered an OS that relied on those names to perform the installation. And with this detail not being documented, I wasted an hour trying, failing, reading then try/fail/read again until I suspected the volume names would be the problem.
So I formatted my partition again, I named it HaikuHDD and everything went well after that. So my advice to the Haiku developers is to make sure the volume names are not used this way in the installer. To everyone else, now you know how to fail at installing Haiku. So if you use Etcher like I did, make sure you don’t name your partition “Haiku”.