Error Codes Wiki

Linux Kernel Panic — Not Syncing

Criticalboot

About Linux Kernel Panic

Linux "kernel panic - not syncing" is a fatal kernel error where the system cannot continue and halts immediately. This guide covers everything you need to know about this topic, including common causes, step-by-step solutions, and answers to frequently asked questions.

Here are the key things to understand: Most severe Linux error — complete system halt. Stack trace displayed on screen (if console available). Cannot be recovered without reboot. Similar to Windows BSOD. Understanding these fundamentals will help you diagnose and resolve this issue more effectively.

The most common reasons this occurs include: VFS: Cannot open root device — wrong root= parameter. init not found — missing /sbin/init or systemd. Out of memory during early boot. Kernel module bug or hardware incompatibility. Identifying the root cause is the first step toward finding the right solution.

To resolve this, follow these recommended steps: Note the panic message — it identifies the cause. For "VFS: Cannot open root device": fix GRUB root parameter. For "init not found": boot from live USB and check /sbin/init. For hardware issues: boot with nomodeset kernel parameter. If these steps do not resolve the issue, consider consulting additional resources or a qualified professional.

This article is part of our Linux Error Codes collection on Error Codes Wiki. We provide comprehensive, up-to-date information to help you find solutions quickly.

Quick Answer

What does "not syncing" mean?

The kernel will not attempt to sync (write) data to disk before halting — the error is too severe.

Overview

Linux "kernel panic - not syncing" is a fatal kernel error where the system cannot continue and halts immediately.

Key Details

  • Most severe Linux error — complete system halt
  • Stack trace displayed on screen (if console available)
  • Cannot be recovered without reboot
  • Similar to Windows BSOD

Common Causes

  • VFS: Cannot open root device — wrong root= parameter
  • init not found — missing /sbin/init or systemd
  • Out of memory during early boot
  • Kernel module bug or hardware incompatibility

Steps

  1. 1Note the panic message — it identifies the cause
  2. 2For "VFS: Cannot open root device": fix GRUB root parameter
  3. 3For "init not found": boot from live USB and check /sbin/init
  4. 4For hardware issues: boot with nomodeset kernel parameter

Tags

linuxbootkernel panictroubleshootingfix

More in Boot

Frequently Asked Questions

The kernel will not attempt to sync (write) data to disk before halting — the error is too severe.