Ошибка kernel panic not syncing

Страницы: [1] 2  Все   Вниз

0 Пользователей и 1 Гость просматривают эту тему.

Страницы: [1] 2  Все   Вверх

Linux is a very reliable system that rules the server universe worldwide. It is fast, secure, and the way it is built makes it ideal for many environments in many parts of the world. However, it is not perfect and can be flawed in many ways, causing more than one headache for professionals in the field. Today, in this post, we will talk about a kernel panic that can ruin your day. We will talk about How to solve kernel panic not syncing error. Let’s go for it.

What is a kernel panic?

For an operating system to work efficiently, it must be synchronized with the various system units. If this does not happen, then there could be system crashes, which could lead to data loss and more severe damage. Kernel Panic is one such crash that occurs at the kernel level.

In short, a kernel panic is a serious boot-level error that is then displayed by the system. An indispensable aspect of this type of error is that the system cannot fix it by itself, preventing the system from booting. Although it provides a message explaining what it is, the reality is that these often work only for a kernel developer.

The kernel panic was introduced in an early version of Unix and hence Linux, and the basic premise is that hardware and software must work correctly. When the software or hardware fails, it results in an error that interrupts the startup of the system.

To be a bit more specific, the truth is that many error conditions can cause a kernel panic, including kernel code that attempts to access invalid memory.

Microsoft Windows users are typically familiar with the BSoD (blue screen of death) and a Kernel Panic is the Unix equivalent of this. Whereas in Windows or Unix, the system cannot continue its normal boot.

Although they are very common, the reality is that there is no specific reason for them. This means that it is not always easy to find a solution to this problem. However, the community support and the experiences gained to make it possible to find solutions.

What can cause a kernel panic?

Although it is not always easy to know the reasons why a kernel panic happens, it is possible to determine some causes.

• They can occur when the initramfs image is corrupted. This file is used during boot, so it is vital for the system, and if something happens to it, it will cause a kernel panic.
• An improper attempt by the operating system to read or write memory.
• Improper installation of RAM chips.
• A hardware issue could also cause a kernel panic. One of the possible causes of this is the missing driver needed in the kernel.
• Malware or software bugs
• Data corruption
• Damage to the hard disk or motherboard.
• When trying to read an invalid or disallowed memory address.

It is even possible to get a kernel panic due to faulty updates or corrupted packages.

Another common cause of a kernel panic is when the kernel has incompatibility flaws or has not been properly installed. This can happen when the compilation of the kernel has not been done properly. This happens when we want to compile the kernel source code ourselves.

What does not syncing mean in kernel panic?

As we have been explaining, a Kernel Panic can happen for many reasons. Specifically, the “not syncing” error happens when, at boot time, a serious error is encountered. That is, it happens as soon as the operating system is loaded from the grub. When this happens, there is not much we can do from the system as such.

The origin of this specific error may be due to hardware configuration problems. We have to remember that the kernel is the part of the system that takes care of the hardware management by the drivers that the rest of the system will take advantage of.

A frequent cause is when there is a power failure and the computer has been incorrectly disconnected, causing damage to either hardware or a boot file.

Another less common cause is that some hardware driver has been updated, and the new instructions are not properly supported by the kernel.

But in short, we are talking about a boot-time error. This makes it impossible to mount the system volumes, and therefore we have to resort to third-party solutions.

• How To Install Linux Mint Without USB?
• Best Game Engine For Linux
• How To Install VIEB on Linux?

How can kernel panic issues be resolved?

The solution to a kernel panic is very varied because it will depend on some of the factors that have caused it.

In most of these cases, it is necessary to have a rescue image of the system. The LIVE image of the system will allow us to have the same system but from a live session.

For cases where the error is a kernel panic not syncing, a possible solution is as follows.

When booting the system, instead of choosing the usual option to boot the system, you have to choose the *Advanced option for* to enter the recovery mode of the system.

Once the system has booted into recovery mode, open a terminal and edit the /etc/selinux/config file with a text editor. For example, using nano

nano /etc/selinux/config

And then add this to the end of the file

SELINUX=enforcing

Save the changes by pressing CTRL + O and close the editor by pressing CTRL + X.

After this, reboot the operating system.

reboot

Another possible solution to the Kernel panic not syncing fatal exception error

In this case, it is likely that the error is caused by initramfs. This could be because the file is either missing or corrupted.

The causes of missing or corrupted files are very varied, but in this case, what we have to do is to replace it with another one that is correct.

To achieve this, access as in the previous step to the system recovery mode. Once the system has loaded, you can use the dracut utility to generate a new one. But first, back up the old one.

cp -p /boot/initramfs-$(uname -r).img /boot/initramfs-$(uname -r).img.bak

And now if you generate a new initramfs with the command

dracut –f

Finally, reboot the system.

How to Fix kernel panic not syncing vfs: Unable to mount root Error

This type of kernel panic occurs when the system fails to mount the root file system. A possible workaround is as follows

Restart your computer in recovery mode or safe mode and when you get access to it, run the following command

sudo update-initramfs -u -k <kernel-version>

You have to replace <kernel-version> with the exact version of your kernel.

Then you have to run

sudo update-grub

This last command updates the entire bootloader. Finally, reboot the system.

Kernel panic not syncing no init found

In this case, we are talking about a bad installation because of the ISO image. Because the kernel is unable to mount the file system, it is because the image has been created incorrectly, and therefore the installation has been faulty.

In this case, there is nothing to do but reinstall the system and make sure that the image is well recorded. In addition to this, once the image has been downloaded, it is advisable to check its integrity.

How do you stop kernel panic?

Although we are not 100% free from suffering a kernel panic at some point, there are a few things we can do to minimize the risks:

• Do not touch any key system files, not even out of curiosity. Also, avoid installing applications that require special permissions.
• Take care of the hardware by avoiding violent, unforced shutdowns.
• Update the kernel frequently through software distribution channels.
• Avoid using kernels compiled by third parties. Since the configurations they may use will not always be compatible with ours.
• Along with the kernel, it is also a good idea to update GRUB frequently but always from the official repositories.

In addition to these recommendations, always keep an eye on your hardware and its performance to avoid any bad surprises.

How to resolve Kernel Panic Not Syncing on Mac?

macOS is a very reliable system, and this is one of the main reasons for its success. However, a kernel panic can occur from time to time. So, you are likely to see a message with the following, “You need to restart your computer. Press and hold the power button for several seconds, or press the Restart button”.

If you see it, and the system lets you reboot, you may never see the error again as stated in Apple’s documentation.

If it happens repeatedly, the device may be faulty, and you need to send it to technical support.

Lastly, there are third-party applications that can help you perform software maintenance to prevent this from happening again.

Conclusion

Linux is an incredibly stable system and that is why it dominates the server environment and more and more people use it as a working operating system. However, this does not make it bug-free. And one of the well-known ones is the kernel panic.

Throughout this post, we have developed the topic enough so that you have a clear idea about its causes, how to remedy it, and even take precautions so that you don’t have to deal with it.

Вообще, ошибка значит, что ядро, загрузившись, не может прочитать root file system.
Неизвестная для него файловая система, ИМХО(могу ошибаться, догадка по кофейной гуще) это проблема с диском — он исправен ? Проблема с файловой системой — до grub -а вообще доходит ? Проблема с контроллером SATA (или другим дисковым), то что она успешно поставилось не имеет значения.

Но это догадки, попробуй следующие варианты:

ну если не гугл, то фигняндекс спасёт мир:

Это:
http://forum.ubuntu.ru/index.php?topic=51611.0
За последний месяц два раза кернел паник наблюдал. Ubuntu 8.04. Решалось так:загружался с лайв сд , там в консоли sudo fsck.ext3 /dev/hda1 после этого было много ошибок, на вопрос профиксить или как? отвечал «Y». После этого две недели было спокойно, вот сегодня опять с утра сначала экран типа синего BSOD, а после перезагрузки невозможность загрузки , и чего-то-такое-на енглише. Повторил fsck, и опять в норме всё. Причину сбоев так пока и не понял, но Ubuntu жива, фс не сломалась, так что вот так…
З.Ы. /dev/hda1 это раздел с убунтой.

или это:

http://forum.ubuntu.ru/index.php?topic=22859.msg158326
Можно загрузиться с Live CD , затем
1) sudo mount /dev/sdaX /mnt //sdaХ — раздел c Linux
2) sudo chroot /mnt
Этот путь chroot я нашёл тут на форуме, лично я всегда делал немного по-другому (читай: сложнее), но надеюсь этот тоже cработает.
Итак, значит, вводим sudo chroot /mnt , ну и теперь
a)sudo update-alternatives —config usplash-artwork.so
b)sudo update-initramfs -u
Или же о просто переустановить ядро.
Добавлено позже: Так же стоит проверить диск, с которого вы ставите систему бывает иногда в этом проблема, столкнулись с подобным, потому добавил сюда.

switchroot: mount failed: No such file or directory. Kernel panic — not syncing: Attempted to kill init! Pid: 1. comm: init Not tainted 2.6.32-400.33.2.el5uek #1 Восстановить загрузку Linux, восстановить журнал EXT3/EXT4 ФС.

Когда становится скучно, то обычно чел. начинает искать себе каких-то приключений на свою пятую точку:) Вот мне на днях надоела стабильность моего локального сервера и мне захотелось какого-то «квеста» — и пошло поехало…

В линухах есть некая фича «Journaling Block Device layer» (ака JBD, процесс jbd2/sda2-8), которая на файловых системах EXT3/EXT4 занимается журналированием событий про данные с целью их дальнейшего восстановления в случае возможных сбоев в файловой системе.

На некоторых серверах, особенно со слабой скоростью доступа к диску (hdparm -t /dev/sda1), по показаниям iotop этот самый процесс jbd2/sda2-8 довольно часто дергает диск для записи в него параллельно с другими процессами выполняющими запись на диск, что вызывает всплески I/O Wait. Идея заключалась в том, чтобы полностью избавится от журнала и обслуживающего его процесса jbd2/sda2-8 (ps aux|grep jbd2).

Теоретически я знаю, что можно только сменить способ ведения журнала (data=journal, data=ordered, data=writeback), но полностью отключить журналирование и избавится от процесса jbd2/sda2-8 невозможно, но никогда не видел последствий этого замысла на практике — вот решил попробовать вовсе избавится от журнала и посмотреть чем это закончится;)

Долго ли коротко ли, вот нашелся рецепт:

Re: Resize journal on root filesystem
http://www.redhat.com/archives/ext3-users/2002-October/msg00026.html

> I’ve remounted my root filesystem as ext2, but still when I ‘tune2fs -O
> ^has_journal’ I get
> —-
> The has_journal flag may only be cleared when the filesystem is
> unmounted or mounted read-only.
> —-

Add the tune2fs command to rc.sysinit before the root filesystem fsck is run, then reboot the machine remotely.

В «рецепте» шла речь о изменении размера журнала на корневой файловой системе (Resize journal on root filesystem), для чего нужно его сначала удалить и создать заново с нужным размером, но создание нас не интересует — удаляем:)

После перезагрузки всё было хорошо и CentOS работала стабильно, но вот после второго reboot-а загрузка CentOS накрылась медным тазом с сообщением «switchroot: mount failed: No such file or directory» и иже с ним «Kernel panic — not syncing: Attempted to kill init!«:

switchroot: mount failed: No such file or directory
Kernel panic — not syncing: Attempted to kill init!
Pid: 1. comm: init Not tainted 2.6.32-400.33.2.el5uek #1

CentOS перестала загружаться и в однопользовательском режиме (aka single user mode), но меня это ничуть не расстроило ибо ж за что боролись на то и напоролись. Итак.., приступим к восстановлению.

Чтобы восстановить загрузку CentOS нам потребуется восстановить журнал EXT3/EXT4, а для этого нужен загрузочный/установочный диск и его режим «Rescue mode», для входа в который набираем linux rescue и жмем <Enter>.

После запуска выбираем язык и клавиатуру по умолчанию EN, отказываемся от настройки сети, нажимаем «Continue» ради интереса или просто «Skip» чтобы сразу выйти в консоль ибо «Continue» нам здесь всё равно не поможет.

Теперь же, когда мы в консоли, выполняем набор команд:

Сбой в загрузке CentOS с сообщением «Kernel panic — not syncing: Attempted to kill init!» может иметь различную природу происхождения, но когда никак не получается восстановить запуск ОС, то как вариант нужно попробовать восстановить журнал EXT3/EXT4, т.е. удалить и создать заново.

Аналогичные последствия с результатом «Kernel panic — not syncing: Attempted to kill init!» будут иметь место на любых дистрибутивах Linux в случае полного удаления журнала EXT3/EXT4 или же его возможного повреждения, но в нашем случае это был CentOS GNU/Linux.

Приведённый здесь рецепт по восстановлению журнала для EXT3/EXT4 должен работать и других GNU/Linux дистрибутивах, различаться могут способы загрузки в «Rescue mode».

Ссылки по теме:

• Chapter 26. Basic System Recovery
• 26.2. Booting into Rescue Mode
• Ext3 Filesystem Documentation
• Ext4 Filesystem Documentation

I got this issue with ubuntu 18.04, on upgrading my distro from 16.04 to 18.04, The boot process throws, Kernel Panic

e2fsck
sbin/init: No Such file or Directory
Kernel Panic - Not Syncing : Attempted to kill init !

In order to resolve this, I booted from Live Ubuntu 18.04 disk, then i replaced the contents of my filesystem directories

/bin & /sbin

with the corresponding content of the directories /bin & /sbin of stock filesystem of Live Ubuntu disk.

First find the disk partition which has the probelm in my case it was /dev/sda5 now boot from the live disk and mount /dev/sd5 with the Live Disk

open terminal and run the following commands to replace the contents

cp -r -i /bin /media/ubuntu/<name of your partition folder>
cp -r -i /sbin /media/ubuntu/<name of your partition folder>

example:

cp -r -i /bin  /media/ubuntu/cdfb882d-e33c-49b5-8965-fea541464686/bin/
cp -r -i /sbin /media/ubuntu/cdfb882d-e33c-49b5-8965-fea541464686/sbin/

shutdown the pc and reboot.

Done
Hope this may help!

UNIX-based systems can sometimes be hard to troubleshoot, especially if the problem doesn’t let your system reach the GUI. Now there are a lot of things that can go wrong during a computer’s boot process, but the kernel not loading is perhaps the most troublesome. 

In this article, we’re taking a look at the kernel panic not syncing error in Linux and macOS systems, its causes and what you can do to fix the problem.

What causes this error?

There are a number of reasons why you might see kernel panic errors. Some common causes include:

• Insufficient disk space.
• Incompatible kernel version.
• The kernel or system package wasn’t fully installed during an update. 
• Missing initrd or initramfs file from the boot directory or the updated kernel configuration post-update.
• Incompletely installed kernel or system packages due to insufficient space during an update. 

Also read: What does ./ mean in Linux?

How to fix this on Linux?

If you’re using Linux, try these two fixes.

Free up some space

The most obvious solution to the problem is to free up some space on your boot partition or drive to give the operating system some breathing space and install any missing dependencies. 

Alternatively, if you’ve just updated your OS, try removing the old kernel to free up some space. Here’s how.

Step 1: Boot into grub and select Advanced options.

Step 2: Log in with your credentials and run the df command. Check if the /boot directory is completely full or not.

Step 3: Remove the old Linux kernel by using the following command.

sudo apt-get autoremove

Now restart your PC and you should be able to boot without errors. 

Use a live CD/USB

If the aforementioned fix doesn’t work or creating space on the boot drive isn’t getting your OS started, chances are you’ve missed a critical system package or part of the kernel out due to insufficient space. This can be fixed by reinstalling the required parts or the entire core file package for the OS using a live CD or USB drive. 

Also read: How to fix Windows 2000 runtime error?

How to fix this on macOS?

If you’re facing the error on macOS, the solutions are a bit different. Try out these three fixes. 

Check your hardware

The first thing you should do is check to see if your hardware peripherals are causing a problem. You can do this by shutting down your mac and removing all hardware peripherals before rebooting. If the system boots fine, plug the devices once to single out the faulty peripheral.

Try Safe Mode

Another thing you can try is rebooting your Mac in safe mode to see if a software component is causing problems. Safe mode only loads up the core files required for the OS to boot and isolates all other software. 

All you have to do is hold down the Shift key when rebooting your Mac and select Safe Mode from the list of option that appears. If your computer boots fine, chances are a third-party program you recently installed is causing problems.

Update your programs or apps

Updating your programs without being able to access the GUI can be challenging, but luckily the default macOS package manager, homebrew, can update any outdated programs from the command line. You can update existing packages using the following command.

brew update

Also read: How to fix ‘Sudo command not found’ error on Linux?

Доброго времени суток. На машине с дебианом рухнула система. Теперь при загрузке выдаёт «kernel panic — not syncing: vfs: unable to mount root fs on unknown-block(0,0)»
Гуглил, но в большинстве своём там ситуации были после обновления ядра, и соответственно советы идут вплоть до пересборки ядра. Опыта сборки нет, всегда пользовался готовыми дистрибутивами и пакетами.
Есть Live-CD, с него загрузился — раздел с системой есть. В какую сторону копать?
Операционка на диске одна. Память прогнал через Memtest, ошибок нет.

UPD: Проблема решена, спасибо всем за помощь. Дело оказалось в отсутствующем файле корневой ФС (initrd.img-3.2.0-4-amd64). Нашёл такой же на другом сервере, скопировал, всё заработало.