Boot problem - Kernel panic - not syncing: Attempt to kill init! exit code=0x00007f00

JakeJake · 08-24-2019, 03:55 AM

Hi.
I have a notebook with a dual boot, Debian and one other O.S.
Everything is always working properly, until the last update.
After that 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 messages, and probably this was a fault of mine, too much lightness.

Now after the choice on grub the other O.S. do the boot and the system seems to work properly but Debian can't do the boot and give me this:

.... Call Trace:
[...] [....] ? dump_stack...
[...] [....] ? panic+...
[...] [....] ? do_exit...
[...] [....] ? do_group_exit...
[...] [....] ? SyS_exit_group...
[...] [....] ? do_syscall...
[...] [....] ? entry_SYSCALL_64_after_swapgs...
[...] Kernel Offset: ... from ....(relocation range: ........)
[...] ---[ end Kernel panic - not syncing: Attempted to kill init! exit code=0x00007f00

I have a bootable usb stick with Debian 10, if I boot the O.S. from it, i can able to view the disk drive and the data on it.

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

Thanks in advance who can answer

mrmazda · 08-29-2019, 03:22 AM

Actually it could be that you need a new disk. The timing of after updates to Debian could be coincidence possibly induced by lots of writing to the / filesystem. I suggest before doing anything else to do

Code:

smartctl -t long /dev/sdX

to find out if the disk is failing. If it is, you'll need to try further to recover any important personal data that isn't already backed up, then install on a new disk. Even if it checks out OK it may be too late to recover the whole filesystem and need to reformat and reinstall.

Have you tried booting from a prior kernel instead of the latest?

JakeJake · 08-30-2019, 02:40 AM

Thank you for the answer.

Code:

smartctl -t long /dev/sdX

Another user told me to do that.
When I run this command, at the output I read "Status Completed: read failure
Remaining 90%
Lifetime 6843"

He has already suggested me to change the disk.