Ticket #2620 (closed bug: duplicate)
USB boot problem: "PANIC: did not find any boot partitions!"
| Reported by: | luroh | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | - General | Version: | R1/pre-alpha1 |
| Keywords: | Cc: | ||
| Blocked By: | #5 | Has a Patch: | no |
| Platform: | All | Blocking: | #3313 |
Description
Boot process panics after the 4th boot splash icon has lit up, when trying to boot from a USB stick. Stack crawl attached.
Interestingly enough, the problem doesn't trigger if I have my bootable Haiku IDE HDD attached while booting from the USB stick.
Attachments
-
sc.txt
(1.2 KB) -
added by luroh 2 years ago.
- stack trace
-
1.jpg
(288.1 KB) -
added by luroh 2 years ago.
-
2.jpg
(294.2 KB) -
added by luroh 2 years ago.
-
3.jpg
(287.3 KB) -
added by luroh 2 years ago.
-
4.jpg
(290.0 KB) -
added by luroh 2 years ago.
-
5.jpg
(295.2 KB) -
added by luroh 2 years ago.
-
6.jpg
(288.9 KB) -
added by luroh 2 years ago.
-
7.jpg
(294.4 KB) -
added by luroh 2 years ago.
-
8.jpg
(237.6 KB) -
added by luroh 2 years ago.
Change History
comment:1 Changed 2 years ago by mmlr
A stack trace in that case is not very helpful, as it is not where the problem happens. What is interesting instead is the debug output from boot either through serial debugging or per screenshots of on-screen debug output. What size is that USB stick and are you sure the whole image actually did fit on it? Bug #2602 documents the issue where a image didn't actually fit on the device.
comment:2 Changed 2 years ago by mmlr
Scratch that, in fact it's bug #2587 that documents the non-fitting image.
comment:3 Changed 2 years ago by luroh
Thank you for the instructions. There were about 15 pages of debug output of which I have attached the latter half. I believe the USB stick itself is OK, it's a USB 2.0 1GB stick onto which I copy a 200MB image, containing nothing extra but Firefox, using the command: sudo dd if=./generated/haiku.image of=/dev/sdb The same stick can boot another computer (my laptop) without any problems. The problematic computer above is a desktop machine with an Asus A8V-E Deluxe motherboard (based on the VIA K8T890 chipset).
comment:4 Changed 2 years ago by mmlr
- Status changed from new to closed
- Resolution set to duplicate
- Blocked By 5 added
The cause can be seen in the first screenshot at the top. Both the UHCI and EHCI controllers present have invalid IRQ assignments, which means that the BIOS didn't initialize interrupt routing for them. That means, this is in fact a duplicate of bug #5. If it works when you have a IDE disk connected this probably causes the BIOS to do some additional setup that it doesn't do when that's not the case. Maybe there are some USB legacy settings in the BIOS that you can try changing, otherwise there's not much you can currently do.
stack trace