Kernel panic not syncing attempted to kill init exitcode 0x00007f00 как исправить

3

I was trying to update libc in our Ubuntu server but it failed and now when I reboot the server I get a error message:

Kernel panic — not syncing — Attempted to kill init!

and it just hangs.

What is the solution to this problem? The server is used by 10 people so I don’t want to reinstall erasing their data.

1. Mount the centos live cd and boot
2. Go into rescue mode and wait for it load up
3. Read the terminal to see where it mounted the OS
4. Go into OS
5. vim or nano /etc/selinux/config
6. Make sure SELINUX=enforcing or disabled

answered Apr 18, 2014 at 6:42

Booting from CD to rescue the installation and editing /etc/selinux/config: changed SELINUX from enforcing to permissive. Rebooted and system booted

/etc/selinux/config before change:

SELINUX=enforcing and SELINUXTYPE=permissive

/etc/selinux/config after change:
SELINUX=permissive and SELINUXTYPE=permissive

I just came across this problem when I replaced a failing disk. I had copied over the system files to the new disk, and was good about replacing the old disk’s UUID entry with the new disk’s UUID in fstab.

However I had not replaced the UUID in the grub.conf (sometimes menu.lst) file in /boot/grub. So check your grub.conf file, and if the «kernel» line has something like

kernel ... root=UUID=906eaa97-f66a-4d39-a39d-5091c7095987 

it likely has the old disk’s UUID. Replace it with the new disk’s UUID and run grub-install (if you’re in a live CD rescue you may need to chroot or specify the grub directory).

answered Apr 27, 2015 at 1:01

Mount remount the /
Eg.

1. mount -o remount,rw /dev/xyz /
2. sed -i 's/1 1/0 0/' /etc/fstab
3. sed -i 's/1 2/0 0/' /etc/fstab
4. reboot

Hello,

I get a Kernel Panic sometimes during shutdown of my PC.

Kernel panic — not syncing: Attempted to kill init! exitcode=0x00007f00

Can you guide me through this?

Thank you in advance.

Please give us information about your install by entering this command in a terminal:

Select </> from the mini toolbar above the textbox where you type your reply and enclose the results of the command between the code markers [code]Results[/code]. This will let us know how Mint sees your hardware.

Also, your image is not showing.

Hello SMG,
Thank you for your help.

Here is what you asked!

System:
  Kernel: 5.4.0-56-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 4.6.7 wm: muffin 4.6.3 dm: LightDM 1.30.0 
  Distro: Linux Mint 20 Ulyana base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop Mobo: Gigabyte model: G31M-S2L v: x.x serial: <filter> 
  BIOS: Award v: F3 date: 11/20/2007 
CPU:
  Topology: Dual Core model: Intel Core2 Duo E6750 bits: 64 type: MCP 
  arch: Core Merom rev: B L2 cache: 4096 KiB 
  flags: lm nx pae sse sse2 sse3 ssse3 vmx bogomips: 10667 
  Speed: 2000 MHz min/max: 2000/2667 MHz Core speeds (MHz): 1: 2000 2: 2000 
Graphics:
  Device-1: AMD Redwood XT [Radeon HD 5670/5690/5730] 
  vendor: PC Partner Limited driver: radeon v: kernel bus ID: 01:00.0 
  chip ID: 1002:68d8 
  Display: x11 server: X.Org 1.20.8 driver: ati,radeon 
  unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz 
  OpenGL: renderer: AMD REDWOOD (DRM 2.50.0 / 5.4.0-56-generic LLVM 10.0.0) 
  v: 3.3 Mesa 20.0.8 compat-v: 3.1 direct render: Yes 
Audio:
  Device-1: Intel NM10/ICH7 Family High Definition Audio 
  vendor: Gigabyte GA-D525TUD driver: snd_hda_intel v: kernel 
  bus ID: 00:1b.0 chip ID: 8086:27d8 
  Device-2: AMD Redwood HDMI Audio [Radeon HD 5000 Series] 
  vendor: PC Partner Limited driver: snd_hda_intel v: kernel bus ID: 01:00.1 
  chip ID: 1002:aa60 
  Sound Server: ALSA v: k5.4.0-56-generic 
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet 
  vendor: Gigabyte driver: r8169 v: kernel port: d000 bus ID: 03:00.0 
  chip ID: 10ec:8168 
  IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 149.05 GiB used: 49.75 GiB (33.4%) 
  ID-1: /dev/sda vendor: Samsung model: HD161HJ size: 149.05 GiB 
  speed: <unknown> serial: <filter> rev: 0-19 scheme: MBR 
Partition:
  ID-1: / size: 145.21 GiB used: 49.75 GiB (34.3%) fs: ext4 dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 37.0 C mobo: N/A gpu: radeon temp: 44 C 
  Fan Speeds (RPM): N/A 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list 
  1: deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://ftp.cc.uoc.gr/mirrors/linux/linuxmint/packages ulyana main upstream import backport
  2: deb http://ftp.cc.uoc.gr/mirrors/linux/ubuntu/packages focal main restricted universe multiverse
  3: deb http://ftp.cc.uoc.gr/mirrors/linux/ubuntu/packages focal-updates main restricted universe multiverse
  4: deb http://ftp.cc.uoc.gr/mirrors/linux/ubuntu/packages focal-backports main restricted universe multiverse
  5: deb http://security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
  6: deb http://archive.canonical.com/ubuntu/ focal partner
Info:
  Processes: 194 Uptime: 7m Memory: 2.92 GiB used: 1.29 GiB (44.3%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Shell: bash 
  v: 5.0.17 running in: gnome-terminal inxi: 3.0.38 

I hope that’s more helpful.

I tried to upload a photo of the screen during that Kernel Panic several times but I couldn’t.

Please bear in mind that this happens sometimes, not always, during the shutdown process.

Thanks again mate!

I assume the process does eventually shut down even though you see a kernel panic? Or are you having to kill the power for it to shut down?

I didn’t see anything in your hardware which might indicate a problem. The fact that it does not happen all the time may make it harder to tract down, but checking the log files may give a clue as to what the source might be.

You will want to get a copy of the log for a boot cycle which ended with the kernel panic. You can do that after you boot up the next time with the following:

journalctl -b -1 | tee >(gzip --stdout > journalctl_$USER.gz)

This command will write the prior system log to the file journalctl_(yourname).gz and to your screen. The file will be located in your /home/login_name directory. The file will contain the entire boot cycle from start-up through shutdown, so you will probably want to start at the end of the file and then go back to the point of the panic and see what happened before it.

The -b -1 part tells it to not use the current boot cycle, but to go back to the prior one.

Hello again SMG,

Thank you for your time.

The PC stacks on the Kernel Panic screen and nothing happens afterwards. I have to force the shutdown by keeping pressed the power button.

Shall I do this after the next kernel Panic or can I do that now?
So far there is no other kernel Panic.

Someone recommended me to go jump to LMDE 4. Does it worth it? Should I go back LM 19.3?

Another problem I face is that I cannot see the local Windows machines and Server but I can see my Linux Mint 19.3 laptop and the laptop can see both the server and Windows machines.

Do you think that all these problems can be solved by moving back either to LMDE 4 or LM 19.3?

Thank again!

I have been experiencing the same intermittent problem. Sometimes the shutdown process simply hangs at the ‘washing machine’ screen, sometimes I see the kernel panic screen and sometimes it all shuts down properly. This has only started happening since I upgraded to Mint 20. I am running Mint 20 Ulyana on a 64 bit dual core Dell Inspiron desktop.

I also have a Packard Bell, 64 bit, dual core laptop which has NEVER shut down properly since Mint 16 (I think) but which did shut down properly on prior versions.

Is there an error in the grub process or in the kernel itself which is causing these problems?

johnwgpaton wrote: ⤴Fri Dec 11, 2020 7:09 am
I have been experiencing the same intermittent problem. Sometimes the shutdown process simply hangs at the ‘washing machine’ screen, sometimes I see the kernel panic screen and sometimes it all shuts down properly. This has only started happening since I upgraded to Mint 20. I am running Mint 20 Ulyana on a 64 bit dual core Dell Inspiron desktop.

I also have a Packard Bell, 64 bit, dual core laptop which has NEVER shut down properly since Mint 16 (I think) but which did shut down properly on prior versions.

Is there an error in the grub process or in the kernel itself which is causing these problems?

You have different hardware, so please follow forum rules and create your own thread for your issues. In that thread, make sure to supply the information requested in Section 5 of READ: How To Get Help!.

Hermis_hb wrote: ⤴Fri Dec 11, 2020 6:42 amThe PC stacks on the Kernel Panic screen and nothing happens afterwards. I have to force the shutdown by keeping pressed the power button.

Shall I do this after the next kernel Panic or can I do that now?

If a panic happened recently then we could probably do this now. We would just need to get an idea of when it happened so we are looking at the correct timeframe. Am I correct to assume you see the word «panic» on the screen when this happens? Let me know and I’ll make another post on how we can get to the log information that relates to the kernel panic.

Hermis_hb wrote: ⤴Fri Dec 11, 2020 6:42 amSo far there is no other kernel Panic.

In another thread a person was having issues where the laptop would reboot instead of shutting down, but it would only do it sometimes. Turns out it would happen when a certain dock was connected to the laptop. I do not know if there are different pieces of hardware that you attach to your computer that might be why sometimes this happens and other times it does not. That is something to consider until we get a chance to look at the logs.

Hermis_hb wrote: ⤴Fri Dec 11, 2020 6:42 amSomeone recommended me to go jump to LMDE 4. Does it worth it? Should I go back LM 19.3?

I do not know the reason for those recommendations unless someone thinks an older kernel might work better on your older hardware. Because we do not yet know the source of the problem, there is no way to know if that would be better.

Hermis_hb wrote: ⤴Fri Dec 11, 2020 6:42 amAnother problem I face is that I cannot see the local Windows machines and Server but I can see my Linux Mint 19.3 laptop and the laptop can both see the server and Windows machines.

That is a different issue and you should make a separate thread for it.

If you saw the word «panic», we can search the logs for it now. However, we may have to do a couple of searches to find the information leading up to the panic.

journalctl | grep -i "panic" | tee >(gzip --stdout > journalctl_$USER.gz)

This command will write any logged issues relating to panic to the file journalctl_(yourname).gz and to your screen. The file will be located in your /home/login_name directory.

If the results are not very long, you can post them within code tags in your next replay. If they are long, just attach the file to your next post.

Hermis_hb wrote: ⤴Fri Dec 11, 2020 2:07 pm
I’ve done but the txt file is empty.

I try again when panic is happens.

Thank you again mate.

Try it again, only this time use exitcode instead of panic. You did list the word exitcode in your title. I thought a kernel panic listed the word panic in the log line, but it’s possible I am wrong.

It is also possible it has been a while since it happened and those older log messages rolled off what is being saved.

Bookmarks