PANIC: did not find any boot partitions! (boot from CD)

[denzil]

When trying to boot Haiku from CD it fails with this error message: "PANIC: did not find any boot partitions!"

This happens in Alpha 2 as well as in nightly build 38122, the CD drive and all HDDs are connected using SATA . Safe mode options don't help.

[denzil]

Screenshots from on screen debbuging are here: ​http://tmp.lunaen.com/haiku-38122-bootfailed.zip

[denzil]

Also as I was suggested on IRC:

I tried to boot from ISO image.

The computer is Core 2 machine, with 3GB RAM.

[diver]

Try ​r38293 image with an IDE stack.

[denzil]

Replying to diver:

Try ​r38293 image with an IDE stack. Note that you'll need 7-Zip 9.15 or later to unpack it.

I tried to burn it using Infra Recorder and Img Burn, but neither of those booted and it looked like they didn't even start to. Instead Windows started to boot. Assuming it's anyboot image I guess my bios or CD drive doesn't like it.

[diver]

That's odd. This image was confirmed as bootable at least by two people. After unpacking resulting file should be around 500 Mb. Try booting it in qemu first.

[denzil]

Replying to diver:

That's odd. This image was confirmed as bootable at least by two people. After unpacking resulting file should be around 500 Mb. Try booting it in qemu first.

I accidentally extracted the image incorrectly. After extracting and burning it again it boots, but hangs on the fourth icon.

[diver]

Please see ReportingBugs and try to save debug syslog or try taking pictures.
You can also try Alt-Sysreq-D to summon KDL.
If it doesn't work try to use On Screen Debug Output to see where it hangs.

[diver]

Also note that it's generally a good idea to attach pictures here in trac, also try to avoid zip files if it's possible.

[denzil]

Replying to diver:

Please see ReportingBugs and try to save debug syslog or try taking pictures.
You can also try Alt-Sysreq-D to summon KDL.
If it doesn't work try to use On Screen Debug Output to see where it hangs.

Syslog doesn't seem to work for me, there isn't "Display syslog" or "Save syslog" in the "Select debug options" menu.
It is possible to summon KDL, should I type in some commands and post results from when it hangs?
Is it enough to post last few images from screen debugging or is it necessary to post all? (Because last time I had 37 images and that seemed bit too many to post them separately.)
For now I'm posting last 3 images, and will add the rest if necessary (also the rest can be accessed at: ​http://tmp.lunaen.com/haiku-38293-IDE-small/ )

[diver]

Usually 3 last images are enough to make some assumptions, but syslogs are best.
Try to type reboot in KDL and then see if "Display syslog from previous session" menu appears in the bootloader.
From your last attachment:haiku-38293-IDE-14.jpg​ I'd say that some driver causes interrupt storm, see More than 99% interrupts of vector 11 are unhandled line. You can also try to google it.
Try typing ints and bt commands in KDL. Perhaps this can hint at which driver is causing it.
Also try to enable Safe mode as this would disable some drivers.

[tqh]

Looks like interrupts are left unhandled for at least int 11. It would be nice if you could get some system info. If you are using Linux the output of lspci -v would be nice. Thanks for posting the screenshots it helps a lot.

[denzil]

Replying to tqh and diver:

Looks like interrupts are left unhandled for at least int 11. It would be nice if you could get some system info. If you are using Linux the output of lspci -v would be nice. Thanks for posting the screenshots it helps a lot.

Just to make thing clear - the "haiku-38293-IDE-*" images are from the image diver posted in comment:3, the screen debugging pages from the nightly image looked quite different, I will post the last 4 from now as well as the output from lspci -v.
Also I got Haiku booted from USB if that helps. I had problems before, it looks my BIOS got broken somehow, but after flashing it I can boot from USB and I will try to install from it. I can't still boot from CD though and the KDL is the same as before.

[diver]

Which image you are able to boot? With IDE or ATA stack?

[diver]

Also try suggestions i made in comment:10.

[denzil]

Replying to diver:

Which image you are able to boot? With IDE or ATA stack?

The USB drive I managed to boot was Alpha 2 image, which I believe uses ATA stack.
But I actually managed to get the CD booted:
When I was trying to get Haiku installed to HDD I ended up disconnecting all my HDDs except for one (because bootmenu can be installed only on the first HDD) and after a restart the computer started to boot from CD and actually got to the installer. I will investigate how many HDDs I have to connect before the problem occurs. So far I know it happens when I have all 5 HDDs connected and doesn't when only one is connected.
Also I'm adding screenshots with the output of bt and ints.

[diver]

Can you take the same screenshots with IDE stack, perhaps it would allow us to identify which driver you can try to remove.

[scottmc]

Can you recheck this with a recent Haiku build? It may have been fixed recently.

[denzil]

Replying to scottmc:

Can you recheck this with a recent Haiku build? It may have been fixed recently.

I retested it with Haiku Alpha 3 anyboot image, but the problem persists. I can now view and save syslog in the boot manager so I will attach it.

[denzil]

Haiku Alpha 3 anyboot syslog

[waddlesplash]

Please retest after hrev53082.