KDL trying to mount boot filesystem during bootup

[dstritt]

Using the nightly hrev47054, and trying any other dating all the way back to before PM merging this happens since I just started to use nightlies, I get a KDL "Divide Error Exception" durring boot on the center icon (disk with leaf), saying it failed to mount boot filesystem. This is from anyboot burned USB, or ISO burned CDR. Safe mode options, several combinations of them, have no effect. There doesn't seem to be a boot log, because the system freezes, and I have to unplug and plug the computer back in. Also tried both USB drives I have, burned from within Windows usimg ImageWriter.

Computer is HP Pavilion a1440n, modified (RAM, New HD, etc), but processor and motherboard are the original.

I am new to reporting boot errors, so if there is any info you need, or something I need to try to get info for you, please ask.

[dstritt]

Upgraded motherboard and CPU, so unless someone can reproduce this on their hardware, you might as well close it. All nightlies are working fine now.

[dstritt]

OK, it's happening on new hardware, but I narrowed down the cause. My old system had 2 optical drives hooked up, but one was never used, always empty. I successfully installed a recent nightly, but when I boot up with no disc in the drive, I get the same KDL. Insert any disc (not blank) in the drive, and it boots just fine.

[christof]

I have the same problem when trying to boot hrev47105 (x86 GCC 2 Hybrid) anyboot from USB on my desktop with Intel Core i5-4570. The system has a HDD and a DVD drive (no disk inserted).

I will attach a screenshot with a stack trace now. Please let me know if there is any other useful info I could provide.

This looks very similar to #9489.

[christof]

KDL stack trace

[korli]

christof, well, the code ​here expects a non-zero block size. Can you eventually add a check for "partition->block_size != 0"?

[TmTFx]

Exactly the same bug for me on a Asus M5A97R2.0 mobo (on a M5A99X EVO works flawlessy)

[waddlesplash]

I'll build an image for testing when I get the time to. Also, there's a forum post here that mentions this bug: ​https://www.haiku-os.org/community/forum/how_install_pkgman

[waddlesplash]

Hm. It appears that this is a duplicate of #9489, although because it has more info, I'll leave both open. (That ticket has some more development discussion...)

The correct way to solve this is to add a check at ​http://cgit.haiku-os.org/haiku/tree/src/system/kernel/disk_device_manager/KDiskDeviceManager.cpp#n1358 I think. Would that stop the device from being used if it had media (e.g. CD) placed in it (long) after the boot finished?

[waddlesplash]

I just got this one myself when mounting and then removing a CD in VirtualBox. Working on a patch that actually works...

[waddlesplash]

Patch v2.

[waddlesplash]

This fixed the problem for me. See commit message in patch for more info.

[axeld]

Patch looks good, just the comment is superfluous - it's perfectly fine to filter out bogus values when they appear. A better comment would explain why such a value gets there in the first place.

I would think it's already a bug that the identify process is started in this case.

[jessicah]

Fixed in hrev47468