Installation not booting

I’m currently attempting to install Haiku on a USB-stick.

I’ve tried the ‘easy’ installation and the UEFI-installation.

The UEFI-installation shows up in my BIOS and if I choose the USB-stick I installed Haiku on, then it starts up and reaches the third icon if I do not have my installation media (also USB) inserted.

- It fails with: “PANIC: did not find any boot partitions!”

Edit: (it seems my keyboard is “dead” at this point; pressing keys on the keyboard does not do anything)

-However, if I do have my installation media inserted in another USB-port at the same time as I’m booting from the “fresh installation”, the Haiku from the installation-media boots (yes, I’ve chosen the fresh installation, but Haiku is running from the other USB-stick).

I’ve investigated the installation image (nightly) and it’s a ‘dos’ partition map. My UEFI-partition map is GUID.

I’ve also noticed that on the installation image, the BeFS partition is the first partition and also physically before the EFI partition. The EFI partition is about 2.8MB.

I’ve read somewhere that it was important that the BeFS partition was first in some cases, but the guide says that I should create the EFI partition first, then the BeFS partition. - Does this matter ?

Though I entered uppercase “EFIBOOT”, the name was lowercase when mounted.

I wonder if this is a UUID issue or if it has something to do with the “bootable flag” (there’s no bootable flag set in the GUID partition; eg. my own installation).

Note: The installer image works excellent, so I’m pretty sure it’s just me missing something.

1 Like

Alright, I found what the problem is.

I purchased 3 Kingston Exodia USB3 sticks. They support USB3.2 Gen 1, “blazing fast speeds”, but … they automatically “encrypt the data”.

In other words: Do NOT buy Kingston Exodia USB3.2 Gen 1 usb-sticks.

-THey work fine in a USB2.0 port, because they do not get overheated.

If you use them in a USB3.2 port, then they will quickly get hot, and they will unmount and corrupt the data - the data may even look alright, but they’re corrupted.

Writing to the stick from a USB2.0 port works, because it’s so slow, that the stick doesn’t heat up.

Anyway, in a USB 3.2 port I get the “blazing” speed of 5MB/sec. On my Raspberry Pi 4B, I have an ALDI-(junk)-docking station, which supports UAS, that one transfers 300MB/sec.

The Silicon Power card reader never gave me any trouble, I use Kingston MicroSD-cards with that one and never had corrupted data.

(Perhaps I should make another thread called “things not to buy”. :rofl: )

Anyway, I’m writing this comment from within my installed Haiku on the Kingston Exodia stick; just it’s running from the USB2.0 port.

So complete success on the Ryzen 5 9600X now. =)

(perhaps my ASRock B650M PG Lightning isn’t to blame for all the problems I had for an entire week trying to install Linux).

2 Likes

Quite cool that the system is useable despite usb2 speeds :slight_smile:

Too bad about your hw problems though…

1 Like

Most of my hardware problems were solved; it was all due to USB3.

(though the Radeon 5670 did cause a crash initially, so I removed the card and no longer use it)

I do plan on switching to the ASUS motherboard when I can afford it, because it has better PCIe slots and I do not risk frying the CPU.

I don’t feel any speed-limit when running from USB2. This is likely due to that Haiku probably loads the applications and data into memory and keeps them there, instead of like many NIX-like systems running stuff from disk.

I’m an Atari-ST/STe/MegaSTe/Falcon old-timer, so I love when applications are loaded into memory.

Anyway, moving from Raspberry Pi 4B to Ryzen 9600X is a very good experience.

Clicking things or pressing “Return” usually gives an immediate result (unless compiling, but that’s blazing fast compared to the Pi anyway).

I re-installed my Haiku using the latest nightly (to get a clean installation) and it just worked without “following a recipe”, so things are like they should be. My damaged Haiku installer started in Spanish, so I had navigation problems at first, but that helped me getting to know everything quickly. The new installation started in English and is all good.

3 Likes

I just tried a Kingston MobileLite Plus card-reader with an ADATA 64GB v30 Speed Plus MicroSDXC card. Same problem, the cards get hot and results in data-corruption. The card is rated to 160MB/sec, but even when only writing 16MB/sec, the data gets corrupted.

Possible solution would be to use the following command instead of dd/etcher/whatever to write the image:

sudo scp -l 1024 haiku-master-hrev59430-x86_64-anyboot.iso /dev/sdX


The above command limits the bandwidth to 1MB/sec, which should keep your USB-stick/card-reader cool. If not, try lowering the value until you get no data-corruption (and then lower it slightly- say to 80% of that value, just to be sure it won’t happen)

sudo wouldn’t be needed on Haiku, the above command was issued from Linux.

(note: some people say that ‘dd’ is dangerous. It’s not. it’s just as dangerous as ‘cat’, ‘cp’, ‘scp’, ‘rsync’, ‘tar’ … and whatever else can write to a device; the risky part is when /dev/something is the destination and that applies to all commands)