Haiku installer KDL when using identically sized drives

[jstressman]

This is running in virtualbox 3.2.8 with Haiku hrev38812

I've been running into this bug for at least several weeks worth of revisions, since I started using a 20GB slave drive... so I don't know how long it's been around.

I did some testing tonight and oddly enough I can boot the installer fine when using 2, 4, 8, 10, 16, 18, or 19GB slave drives (primary slave), and with 21, 30, and 40GB etc... but when using a specifically 20GB sized slave disk image (both the one I was using with lots of files on it from my Haiku install, and a freshly created in vbox blank one)

Also, if I swap out the 20GB image for any other sized image, the installer will run fine and then I can swap back in my 20GB disk image and Haiku boots fine. It's only when I'm trying to boot the installer that it crashes with the 20GB slave drive.

[jstressman]

setup with Haiku formatted 20GB Backup drive (causes installer KDL)

[jstressman]

setup with untouched blank 20GB drive image, also causes installer KDL

[jstressman]

KDL caused by the 20GB blank primary slave drive image

[jstressman]

setup with blank 21GB primary slave drive boots installer fine. Every other size I tried both smaller and larger than 20GB also worked fine (2, 4, 8, 10, 16, 18, 19, 21, 30, 40GB) all other settings unchanged between tests.

[idefix]

It looks more like it can't find any boot partitions when the Master and Slave images are the same size.

What happens when you replace Haiku-dev3.vdi (20 GB) with another image with a different size (keeping Backup3.vdi as slave)?

A syslog/serial-log would also be useful.

[jstressman]

You were correct. I tested with 2 4GB disks and got the same KDL. This is the serial-debug log from that. I'm attaching serial-debug logs for the 3 combinations I tested... 4/4 KDL, 4/20 working, and 20/20 KDL.

[jstressman]

This is with the 4GB primary master and 20GB primary slave. This booted fine and started the installer.

[jstressman]

This is with the 20GB primary master and 20GB primary slave. This KDLs like the 4/4 combo did. See previous screenshot for visual.

[bonefish]

Just to sum it up again: You're trying to boot off CD, but if and only if you have attached two hard disks of the same size, the kernel doesn't find the boot partition.

I noticed that both of the hard disks are BFS formatted. You didn't by any chance try with one or both of them not being BFS formatted?

Do you build your own images or do you use the nightlies?

[jstressman]

bonefish: Every test done except for the one with the drive named "Backup3.vdi" were done with unpartitioned, unformatted disk images as created by virtualbox for the slave drives.

For instance all 3 of the serial logs I just posted were done with completely blank slave drive images.

Do you want me to try with 2 identically sized totally blank images? Both for the primary master and primary slave? And try booting from the installer CD then to see if the crash still occurs?

Ok, I've just tested with completely blank fresh 2GB disk images for primary master and slave and still get the KDL. I'm attaching the serial debug output.

[jstressman]

serial log of 2 completely blank 2GB drive images giving a KDL on the installer boot.

[jstressman]

This has been with both the images I've been building myself and with the nightlies from haiku-files.org. I just downloaded the anyboot nightly for hrev38811 and tested to confirm that it's not just my builds, but the official nightlies as well.

[jstressman]

(these are the gcc4hybrid builds for the record.)

[bonefish]

Replying to jstressman:

bonefish: Every test done except for the one with the drive named "Backup3.vdi" were done with unpartitioned, unformatted disk images as created by virtualbox for the slave drives.

For instance all 3 of the serial logs I just posted were done with completely blank slave drive images.

I looked closer only at serial-log-20GB-20GB-KDL.txt, which shows identically sized BFS volumes on both hard disks.

Do you want me to try with 2 identically sized totally blank images? Both for the primary master and primary slave? And try booting from the installer CD then to see if the crash still occurs?

Ok, I've just tested with completely blank fresh 2GB disk images for primary master and slave and still get the KDL. I'm attaching the serial debug output.

OK, thanks, that does at least rule out that the other BFS volumes caused confusion somehow.

Replying to jstressman:

This has been with both the images I've been building myself and with the nightlies from haiku-files.org. I just downloaded the anyboot nightly for hrev38811 and tested to confirm that it's not just my builds, but the official nightlies as well.

I don't suspect a build problem. I was just wondering how one could get additional debug output to you. If you build your own images, then enabling tracing would be the easiest way. Unfortunately at the moment there is no useful tracing output at all in the concerned code, so someone would have to add that first. Assuming that this problem is reproducible elsewhere, that someone could problem just debug it locally, though.

[deejam]

I have the same problem using GCC2Hybrid hrev42900 and VirtualBox 4.1.0 in Mac OS X 10.6.

I have a 10G primary master harddrive (vdi) formatted as BFS. I added a slave with the same size and formatted it as BFS. After that, I could not boot the installation CD, it would KDL as described above. Changed the slave to 20GB and reformatted, and after that I could boot the install CD.

[Vannura]

I tested and GCC2Hybrid hrev56671 booted the installer on VirtualBox 7.0.4 with 20GB Primary Master and the 20GB Primary Slave.