Haiku EFI loader and rEFInd

[tamudude]

Using latest Haiku nightly in a multiboot system using rEFInd. I have setup Haiku EFI loader per this page ​https://www.haiku-os.org/guides/uefi_booting/ rEFInd boots ok and when I choose the Haiku icon, it goes to the Haiku boot loader screen. Initially I see no boot volume, but when I press enter on the line for boot volume, it shows me two identical entries for Haiku and I can choose latest/earlier versions in either. What do I need to do to:

1. Have the volume show up natively in the Haiku loader?
2. Avoid Haiku showing two identical entries for the boot volumes?

I have one NVME SSD with the following system layout /EFI /Windows /Arch /Ubuntu /TBD /TBD /Haiku

PS: I have updated this ticket with latest system info (different from when I originally reported this bug 19 months ago but problem still remains). Currently running hrev57256 x86_64

[tqh]

Do you also have the USB with Haiku install connected?

As it finds two partitions it might ask you which one to boot, not sure what the logic is right now.

[tamudude]

No, there is no usb device (other than mouse/KB unifying receiver) connected to this PC.

[tqh]

If you have linux installed can you do a:

lsblk -o NAME,FSTYPE,PARTUUID,UUID

and report the output?

[tamudude]

NAME FSTYPE PARTUUID UUID

nvme0n1

├─nvme0n1p1 vfat 3a5fbc09-b77e-4846-be01-22b5d3d6c032 86E6-0751

├─nvme0n1p2 8c312bd7-462b-421f-8873-d3c9f747684b

├─nvme0n1p3 ntfs 4213e19a-2fb9-4926-bae9-b8d6da79be0f 58121B27121B0A20

├─nvme0n1p4 ext4 9d69ff44-8b69-4cee-ace9-dd74799f4b18 72f22257-c6b8-4abc-84c4-7595fc5b4b67

├─nvme0n1p5 ext4 e9df8429-9ea2-48c2-9362-786c3362f0a3 b22ab809-065a-4311-bf88-cc0c321f3acb

├─nvme0n1p6 5c2d77ae-a1ee-4e67-8275-1d4de7b2e033

├─nvme0n1p7 5f72494c-1bfe-4ea7-afa7-56608c7c276c

├─nvme0n1p8 102f9cde-1705-480a-93d1-ce0a047bfb22

└─nvme0n1p9 befs 3d8a438c-6336-47b3-a70a-eb9f3c6b7239 4059e2584d6e1c0a

[tqh]

Looks like the partition uuid for the BFS (befs) is not the correct one, should probably be: ​https://cgit.haiku-os.org/haiku/tree/src/add-ons/kernel/partitioning_systems/gpt/gpt_known_guids.h#n64

[tqh]

Checked the code, and the current code will not find your partition when it is not the correct UUID. Why it lists several options to pick I don't know, seems that might be a bug, or it lists different potentially bootable partitions.

[tamudude]

I am not sure why the UUID would have changed. I used the Haiku installer to initialize and format the partition. I have attached screenshots of what exactly is happening. When I say it gives multiple choices, I should have meant Activation States not multiple partitions.

[pulkomandy]

I am not sure why the UUID would have changed. I used the Haiku installer to initialize and format the partition.

The Installer does not touch the partition identifier. To set this in Haiku you currently have to delete and recreate the partition using DriveSetup, when creating a partition (and before initializing it with a filesystem), DriveSetup will let you pick a partition type.

These two things (the partition UID and the filesystem it is formatted with) are independant. Both are required for an Haiku installation to work properly.

[tqh]

It would make a lot of sense for the installer to check and ask about that I think. It would help users a lot and we would probably get less issues like this.

[tqh]

I don't know why, but long ago the UUID for BFS was changed in the code. So if you did this very long ago, you would have the old one.

[tamudude]

Replying to pulkomandy:

I am not sure why the UUID would have changed. I used the Haiku installer to initialize and format the partition.

The Installer does not touch the partition identifier. To set this in Haiku you currently have to delete and recreate the partition using DriveSetup, when creating a partition (and before initializing it with a filesystem), DriveSetup will let you pick a partition type.

These two things (the partition UID and the filesystem it is formatted with) are independant. Both are required for an Haiku installation to work properly.

That worked!! I used DriveSetup to delete the partition, create a new partition in the empty space, formatted to BeFS and now everything works correctly! This bug can now be closed....that being said, perhaps consider having a check implemented in the Installer? My modus operandi has been to create placeholder partitions when setting up a multiboot PC.