Boot from USB fails with "Haiku: Panic: did not find boot partitions"

[k3ck3c]

Hello

My PC has 2 disks, I removed the Arch Linux that was on a disk (I have an empty 238 G partition), and planned to install Haiku on it.
Debian 9 is installed on the second disk.

I used etcher to create my Usb flash disk with the latest 64 bits ISO, and when I boot, I get

Haiku: Panic: did not find boot partitions

I see something similar at

https://dev.haiku-os.org/ticket/6558

I also noticed at

News about UEFI

It is merged, but not included in the nightly builds. The reason is that we can either make a BIOS-compatible, or an UEFI-compatible image, but not both in the same image. Some extra work will be needed for that. So if you want an UEFI image, you can use one of the unofficial ones (I don’t have a link at hand), or build one yourself. Don’t worry, once installed, you can update it in the normal way, so it is not a problem to start with an old-ish image.

the following

“UEFI is sensitive to the type of partition table - under Linux there are two different types - the old MBR and the new (is it GPT or something - I don’t use it) - anyway it’s necessary to use the right one with different combinations of UEFI, secure boot and legacy boot. I assume that Haiku would mimic one or the other. There are some laptops that have UEFI but won’t boot EFI images.”

some info

Xiaomi Air 13

lsblk                                     ✔  606  14:15:54

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 931,5G 0 disk
├─sda1 8:1 0 243M 0 part /boot
├─sda2 8:2 0 1K 0 part
└─sda5 8:5 0 931,3G 0 part
├─debian9–vg-root 254:0 0 923,4G 0 lvm /
└─debian9–vg-swap_1 254:1 0 7,9G 0 lvm [SWAP]
nvme0n1 259:0 0 238,5G 0 disk

sudo fdisk -l                             ✔  607  14:15:57

[sudo] Mot de passe de root :
Disque /dev/nvme0n1 : 238,5 GiB, 256060514304 octets, 500118192 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d’E/S (minimale / optimale) : 512 octets / 512 octets
Type d’étiquette de disque : dos
Identifiant de disque : 0x72206f74

Périphérique Amorçage Début Fin Secteurs Taille Id Type
/dev/nvme0n1p1 1953724787 3833325271 1879600485 896,3G 2e inconnu
/dev/nvme0n1p2 1802068328 3671441628 1869373301 891,4G 67 inconnu
/dev/nvme0n1p3 0 0 0 0B 0 Vide

Les entrées de la table de partitions ne sont pas dans l’ordre du disque.

Disque /dev/sda : 931,5 GiB, 1000204886016 octets, 1953525168 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d’E/S (minimale / optimale) : 512 octets / 512 octets
Type d’étiquette de disque : dos
Identifiant de disque : 0x625c79bd

Périphérique Amorçage Début Fin Secteurs Taille Id Type
/dev/sda1 * 2048 499711 497664 243M 83 Linux
/dev/sda2 501758 1953523711 1953021954 931,3G 5 Étendue
/dev/sda5 501760 1953523711 1953021952 931,3G 8e LVM Linux

Disque /dev/mapper/debian9–vg-root : 923,4 GiB, 991462162432 octets, 1936449536 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d’E/S (minimale / optimale) : 512 octets / 512 octets

Disque /dev/mapper/debian9–vg-swap_1 : 7,9 GiB, 8480882688 octets, 16564224 secteurs
Unités : secteur de 1 × 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d’E/S (minimale / optimale) : 512 octets / 512 octets

Thanks for any hint

[hor410]

Please, look here:
https://discuss.haiku-os.org/t/haiku-on-uefi/5773/7

[jjpx]

AFAIK NVMe is not supported yet

[leo75]

I’m not sure I understand: standard anyboot ISO aren’t compatible (yet) with UEFI?

Is there somewhere I can find prebuilt UEFI ISO for beta 1?

[PulkoMandy]

Hi,

I just have to clear up some misunderstanding since it seems everyone is complaining about their own boot problem here?

• If you get to this panic, it means the kernel is loaded already, so your problem is not UEFI vs BIOS or the like.
• If you boot from USB, then NVMe is not needed.
• I don’t know what etcher is. You can create a bootable usb disk from Linux using “cp haiku.anyboot /dev/sdx” (replace sdx with the correct device for your USB stick).

So, the possible problem I see is that your stick is not created the right way, or your USB stick or USB ports are not supported by our drivers. Try booting the stick on another machine. Try another USB stick. Try another way to write the image (with cp as I suggested, for example, this is a known working method).

If the problem is not a mis-written stick, the next step would be to enable on-screen debug and see what’s going on in the syslog. Did the USB driver find any USB ports? Did it manage to initialize them? Did it find the USB stick? Did it manage to identify the partition table on it?

[k3ck3c]

etcher is the recommended tool in a Haiku doc

I took a photo of the panic, it says

Welcome to kernel debugging land…
Thread 18 main2 running on Cpu 3
…
arch_debug_stack_trace() + 0x13

which commands do I use in order to debug this?

[hor410]

Ah… NVMe :-/ I am stupid

[PulkoMandy]

share the whole photo or the whole text. You removed the most relevant information

[k3ck3c]

[PulkoMandy]

ok, so it did not find the USB stick you are booting from; The next step would be using the syslog command and looking for everything disk-related: USB, usb_disk, and partitions and filesystems detection.
You will need to guess at which of these steps we ran into a problem.

Maybe try different USB sticks, check the stick on a different computer, and try writing things to the USB stick in a different way in case the process you used didn’t result in the right disk layout.

[k3ck3c]

here is the syslog with the same USB stick, I will try another USB key

[k3ck3c]

with another USB stick, it hangs after having lightened the first 3 icons.

if I remove the stick I get

and

[k3ck3c]

with another USB stick (128 GB)

and

[k3ck3c]

I have tested with 4 different USB sticks and on the 2 USB ports, always the same result.

and creating the Usb with cp makes no difference