problem with boot, end kernel panic - not syncing: attempted to kill init!


New Member
Aug 24, 2019
Reaction score
I have a dual boot notebook, with Debian9 and Windows10.
After an update on my Debian 9, there were some problem about "unexpected inconsistency" and the system asked me to run fcsk manually. The system gave me a lot of message like "linux error reading block inode force rewrite" and after a brief search online, I decided to answered yes to all of this message, and probably this was a fault of mine.

Now Windows seems boot correctly but Debian give me message "end Kernel panic - not syncing: Attempted to kill init! exit code=0x00007f00

If I boot the system from an usb stick with Debian 10 I am able to view and access the folders and the files.

Has anyone a suggestion for me ?
What can I do ?
I have to reinstall Debian ?

Thanks in advance for the answer

Do you still have the Grub Menu?

Yes, when the system start it show me the Grub menu where I can choose which O.S. I would like to start.
If I choose Windows the boot can be done, apparently in the proper way, but if I choose Debian the system give me an error.

I post the last rows:

... Call Trace:
..... ? dump_stack+0x5c/0x78
..... ? panic+0xe4/0x242
..... ? do_exit+0xb53/0xb60
..... ? do_group_exit+0x3a/0xa0
..... ? Sys_exit_group+0x10/0x10
..... ? do_syscall_64+0x8d/0x100
..... ? entry_SYSCALL_64_after_swapgs+0x58/0xc6
.... Kernel Offset: 0x27800000 from 0xffffffff81000000 (relocation range: 0xfffffffff80000000-0xffffffffbfffffff)
[ *********] ---[ end Kernel panic - not syncing: Attempted to kill init! exit code=0x00007f00
[ ********]
When I couldn't figure how how to fix kernel panic I performed a fresh installation.

If those links didn't help than your best bet may be a fresh install.

Members online