Opened 4 years ago

Closed 2 years ago

#16935 closed bug (fixed)

Boot fails with "PANIC: did not find any boot partitions!"

Reported by: Paradoxon Owned by: nobody
Priority: normal Milestone: R1/beta4
Component: System/Kernel Version: R1/Development
Keywords: boot-failure Cc:
Blocked By: Blocking:
Platform: x86-64

Description

Trying again to get haiku 64 bit working on my schenker slim, brought me on directly to kdl when enabeling all save modes. Kdl occurs on the 4th icon

Attachments (2)

_20210509_180616.JPG (2.3 MB ) - added by Paradoxon 4 years ago.
IMG_20210728_102648_sml.jpg (676.6 KB ) - added by topolinik 3 years ago.
KDL when booting R1beta3

Change History (11)

by Paradoxon, 4 years ago

Attachment: _20210509_180616.JPG added

comment:1 by korli, 4 years ago

Summary: Kdl on bootBoot fails with "PANIC: did not find any boot partitions!"

comment:2 by Paradoxon, 4 years ago

i could narrow down the safemode option which is the cause. This kdl only happens when local apic is enabled. Else it just crashs with a crazy app server error

Last edited 4 years ago by Paradoxon (previous) (diff)

comment:3 by diver, 4 years ago

Component: Kits/Kernel KitSystem/Kernel

Is this with UEFI or BIOS booting?

Also please create a new ticket about this app_server crash.

comment:4 by kallisti5, 4 years ago

I can confirm seeing this on my Ryzen 1800x desktop. USB 3 Hub + three different USB 3 Flash drives. System fully powered off inbetween each attempt. Each boot attempted 3 times. All EFI boot.

  • hrev55104 x86_64
    • Refind: No boot partitions KDL
    • Native: No boot partitions KDL
  • hrev55100 x86_64
    • Refind: No boot partitions KDL
    • Native: No boot partitions KDL

We have had this issue for quite some time. I made sure my new desktop board had a PS2 port so KDL keyboard would work :-D

syslog from hrev55104:

usb xhci -1: using message signaled interrupts
usb xhci -1: starting XHCI host controller
usb xhci -1: successfully started the controller
usb xhci -1: interface version: 0x0100
usb xhci -1: ...
...
usb hub 84: port 2: new device connected (pretty sure this is the flash drive)
usb error xhci 2: unsuccessful command 11, error USB transaction (4)
usb error xhci 2: unable to set address
usb xhci 2: transfer error on slot 3 endpoint 1: Stall
usb error control pipe 85:  timeout waiting for queued request to complete
usb xhci 2: cancel queued transfers (1) for pipe 0xffffffff80858c80
usb error hub 84: error updating port status
usb error hub 84: debouncing port 2 failed: General system error
...
usb hub 84: port 2: new device connected
usb error xhci 2: unsuccessful command 11, error USB transaction (4)
usb error xhci 2: unable to set address
...
Last edited 4 years ago by kallisti5 (previous) (diff)

by topolinik, 3 years ago

Attachment: IMG_20210728_102648_sml.jpg added

KDL when booting R1beta3

comment:5 by topolinik, 3 years ago

I can confirm this appearing on R1beta3 (screenshot attached). I flashed the 64 bit anyboot image file onto an USB stick and booted, always crashing at the fourth icon.

Edit: my cpu is an intel i7 7500u @2.7 GHz (2+2 cores)

Last edited 3 years ago by topolinik (previous) (diff)

comment:6 by waddlesplash, 3 years ago

Keywords: boot-failure added

comment:7 by waddlesplash, 3 years ago

Please retest under a recent nightly, and extract more of the syslog if you can.

comment:8 by topolinik, 3 years ago

I flashed hrev55607 on my USB stick and now it boots properly (i7 7500u on UEFI), I can setup a BeFS partition and install my OS - everything goes smooth.

I'm afraid I don't know how to extract syslog, can you point me to some docs ?

comment:9 by waddlesplash, 2 years ago

Milestone: UnscheduledR1/beta4
Priority: blockernormal
Resolution: fixed
Status: newclosed

If it boots successfully then the problem is fixed and I don't really need a syslog.

The original ticket author has not replied in almost a year, so let's consider this fixed.

Note: See TracTickets for help on using tickets.