[Solved] Kernel panic: Assert unreachable

Development OS
1

Tried to boot in ‘safe mode’…same thing came up…“Assert unreachable”…

I was wondering why there was an extension to the files named__Dirty…
Maybe because of this …

Any other people facing this issue?

1 Like
2

Posting from linux…any suggestions to resolve this are welcome…please

3

Regression from a change I made yesterday (or really, a bug uncovered by a new assertion I added yesterday.) I’m working on a fix.

4

Should be fixed in hrev58198. Please let me know if the problem persists.

1 Like
5

Me too. I tried to restore previous state - I have failed.

  1. attempted to reach boot options
    to select hrev58191 as previous state - but failed.
    I just waited to get in after a long time - 3 times … but never happened. once the machine get out of this Haiku’s “scanning and building up your choices” stuff and I saw the reboot happened automatically -

  2. Then I switchewd to R1B5 thumbdrive as I thought I would restore it with file operations.
    2.A I inserted the Nightly thumbdrive
    2.B I removed the *hrev58197* packages from directory /boot/system/packages/, those I installed today afternoon, and caused the KDL
    2.C I copied back the *hrev58191* packages and activated_packages file from last state dir. into /boot/system/packages/
    2.D Stopped R1B5 Haiku, I left Nightly USB thumbrive only -
    2.E I booted now :
    Finally reached boot(loader) menu (hrev56xxx+59 – I assume it was still from R1B4 as I upgraded nightly also earlier from beta)
    Well if I reach automatically the boot menu it does not mean some good news for me - it is sorrow and painful experience from the past …

Oh yeah - it stated it had not found bootable Haiku drive !..
So the known issue -
I made rescan volumes - 3 times … again. Still remained ‘None’

  1. .Booted again R1B5 Haiku
    3.A in DriveSetup I checked nightly BFS - there were no more boot mark on the corresponding drive icon.
    3.B I confirmed to set Active - nothing changed. restarted DriveSetup.
    3.C run makebootable - two times on devices as it has seen in df output - finally understood I must use the mount point instead. Executed - but seems it also does not help. In DriveSetup it had remained simple BFS volume - the flad System has not appeared among them. Only R1B5 volume has it.

BFS is healthy - at least for running ‘checkfs -c’ I got a healthy BFS report.

# for anyone, who would answer these Qs

Would it be help if the efiboot file replaced on haiku esp partition with a newer one ?

Or just re-creating helps ? I would avoid it if I can save somehow my actual Haiku Nightly install !..

6

I am unable to figure out how to boot the os, safe mode also leads to KDL

I can update after I sucessfully boot up

Please suggest how to boot into previous …hrev
I have not yet cleared this via filwip since this …hrev did not successfully boot up…old state still available

7

See the last troubleshoot point at the User Guides page on the Boot Loader

8

Though I have not used filwip and cleaned the last state, since hrev58197 did not boot sucessfully, old state should remain in the pc
But, bootloader does not present it…
Pl. See the attached photo

20241004_220413
20241004_2204131920×885 94.4 KB

9

You have to enter the list. You select Haiku actual state, press Enter and a flat list of states appear.

10

I was looking for the hrev number…196 which was not shown
anyway, the last date shown I selected…and it booted
Updated to hrev…198…all ok