Opened 13 years ago
Closed 9 years ago
#7826 closed enhancement (fixed)
PANIC: did not find any boot partitions!
| Reported by: | Veristeron | Owned by: | axeld |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | Partitioning Systems/GPT | Version: | R1/alpha3 |
| Keywords: | Cc: | mmlr, jessicah | |
| Blocked By: | Blocking: | ||
| Platform: | All |
Description
I'm trying to install Haiku on EMachines eM350. In each try it stop on disk checking with problems concerning boot partitions.
Kernel stack: 0x821a7000 to 0x821ab000
Same problem exists on alpha3 and hrev42433 revision.
Attachments (7)
Change History (14)
by , 13 years ago
| Attachment: | IMG_0350.JPG added |
|---|
comment:1 by , 13 years ago
Hi,
I have the same kind of issues when I try to install haiku from iso image on the
following machine :
Gigabyte EP35-DS3R
Quad Core Q9450
NVIDIA GTX460
2 harddrives(WDC6400AAKS)
I wanted to install it on sdb3 and I even tried to flag it as bootable but it didn't help...
See attachment labeled Panic to see exactly what is going on.
follow-up: 3 comment:2 by , 13 years ago
The only interesting information besides the actual partition layout (the gparted shots should suffice) is the syslog. There are basically only two possible reasons why the kernel doesn't find the boot volume: 1. A driver issue is preventing the hard disk from being found (correctly) or 2. our partitioning system implementation isn't happy with the partition table (e.g. because it is non-standard/broken or because of a bug). Either way, the syslog should contain the answer.
follow-up: 4 comment:3 by , 13 years ago
Replying to bonefish:
The only interesting information besides the actual partition layout (the gparted shots should suffice) is the syslog. There are basically only two possible reasons why the kernel doesn't find the boot volume: 1. A driver issue is preventing the hard disk from being found (correctly) or 2. our partitioning system implementation isn't happy with the partition table (e.g. because it is non-standard/broken or because of a bug). Either way, the syslog should contain the answer.
Ok so how can I help you more ?
comment:4 by , 13 years ago
Replying to smartmobili:
Ok so how can I help you more ?
Please provide a syslog. Have a look at http://dev.haiku-os.org/wiki/ReportingBugs#Syslog for the preferred way to do that. If that doesn't work, there's a syslog command in KDL, that prints the syslog page-wise on screen. Please take pictures of the pages. BTW, half (or even less) the resolution of your previous pics would still be perfectly readable.
comment:5 by , 13 years ago
| Cc: | added |
|---|---|
| Owner: | changed from to |
| Status: | new → assigned |
I didn't notice that before, but apparently your second drive is GPT partitioned. I don't think we do support booting off GPT partitioned drives yet. We do have a partitioning system implementation for it, but it doesn't seem to be enabled neither in the boot loader nor as boot module for the kernel. I don't know, if there's a reason for that or not. Reassigning to the original author, CC to the last modifier.
comment:6 by , 10 years ago
This instruction is just a help for new Haiku OS tester:
Current possible way to resolve this problem: just unplug all USB devices before boot haiku os. After boot the devices can be plug again.
comment:7 by , 9 years ago
| Cc: | added |
|---|---|
| Component: | Partitioning Systems → Partitioning Systems/GPT |
| Platform: | x86 → All |
| Resolution: | → fixed |
| Status: | assigned → closed |
| Type: | bug → enhancement |
Panic