PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteThe message Kernel panic - not syncing: Attempted to kill init! means Linux could not keep process 1 (PID 1) running. PID 1 starts the rest of userspace, so the kernel stops when it exits or cannot be started. On a VPS, the practical recovery order is: preserve the disk, try the previous kernel from the provider console, then repair the kernel files, initramfs, GRUB configuration, libraries, or filesystem from a running system or rescue VM.
Need a server to try this on? Antihost offers Linux VPS plans with NVMe storage, full root access and a 14-day free trial.
The panic text is a symptom rather than a diagnosis. A missing initramfs, an incorrect root= device, damaged storage, missing dynamic libraries, and a genuine systemd crash can all produce it. The steps below separate those cases without repeatedly risking the original disk.
As an Amazon Associate I earn from qualifying purchases.
Free tools Windows power users keep installed
One-click scans. No signup required.
What “Attempted to Kill Init” means
PID 1 is the process Linux cannot lose
During boot, the kernel starts the first userspace process, normally systemd or another init implementation, as PID 1. Microsoft’s Linux troubleshooting documentation describes it plainly: “The init process is the first process to be started and should never exit.” If that process exits, crashes, or cannot be loaded, the kernel has no normal userspace supervisor and reports Kernel panic - not syncing: Attempted to kill init!.
The wording does not identify which file or package failed. The useful clue is where the boot trace stops. A failure before the root filesystem is mounted usually points to GRUB, the kernel command line, initramfs, storage, or filesystem damage. A trace that reaches userspace and then shows systemd or PID 1 exiting points more strongly to missing libraries, corrupted packages, or an init-system failure.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
Why a kernel update can trigger it
A kernel package update normally installs a kernel image, matching modules, and an initramfs, then updates the bootloader menu. If the initramfs was never generated, is empty, belongs to another kernel version, or was written while the disk was full, GRUB may boot a kernel that cannot discover the root volume. A manually edited GRUB entry can create the same result by omitting the initrd line or naming the wrong root UUID.
Protect evidence before changing the VPS
Repeated forced boots and improvised disk repairs can destroy the evidence needed to identify the failure. Use the provider’s serial console or boot-diagnostics capture to save the complete panic and the kernel version shown immediately before it.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →- Record the failing kernel. Note the version printed by the boot menu or console, plus the timestamp of the failed reboot and any package-update activity.
- Stop automatic reboot loops. Disable an automated restart action if the provider offers one, or power the VPS off cleanly through the control panel.
- Create a provider snapshot or backup. Google Cloud’s recovery guidance specifically recommends taking a snapshot before offline repair. Keep that snapshot unchanged until the repaired VPS completes a normal reboot and application checks.
- Work on a copy when possible. Attach a cloned disk to a rescue VM rather than experimenting on the only copy of the operating system.
- Do not run filesystem repair while mounted. A checker aimed at a mounted root filesystem can make damage worse.
Choose the least invasive recovery path
| Recovery path | Use it when | Strength | What you need |
|---|---|---|---|
| Provider console and older kernel | An older kernel remains in the GRUB menu and the VPS reaches a login prompt | Fastest path with no disk attachment | Serial console or equivalent out-of-band boot access |
| Repair from the running system | An older kernel boots successfully | Uses the VPS’s own package database, mounts, and bootloader | Root access and enough free space in /boot and the root filesystem |
| Rescue VM and chroot | No installed kernel reaches userspace | Works even when the guest cannot boot | Snapshot, detachable disk, rescue VM, and permission to attach the disk |
Azure, Google Cloud, and AWS document materially similar repair-VM patterns, but their console labels, attachment procedures, device names, and command wrappers differ. Follow the provider’s instructions for stopping the VPS, attaching a disk, and detaching it cleanly; the Linux repair steps inside the mounted filesystem are the part that transfers between providers.
First try the previous kernel
If the failure appeared immediately after a kernel or bootloader update, selecting the previous entry is the quickest test. Open the provider’s serial console, reboot, and interrupt GRUB when its menu appears. Depending on firmware and distribution, pressing Esc or holding Shift during the early boot phase reveals the menu; a provider console often has its own “send key” control.
- Choose Advanced options or the equivalent submenu.
- Select the older kernel and its matching recovery entry only if a normal entry is unavailable.
- Allow it to boot with the existing root configuration.
If the older kernel reaches a shell or SSH, do not immediately delete the failing entry. First inspect the boot files and package history, then repair the affected version. Keeping one known-good kernel gives you a rollback path if the rebuilt image is still wrong.
Repair from a system that still boots
Check that each kernel has a matching initramfs
List the files in /boot and compare version suffixes. A normal pair has a kernel image such as vmlinuz-VERSION and a corresponding initrd.img-VERSION or initramfs-VERSION.img. The exact names vary by distribution.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
ls -lh /boot
findmnt /boot
df -h /boot /
An empty or nearly full /boot explains why a package transaction could leave an incomplete image. Also inspect the previous boot and package-manager history:
journalctl -b -1 -e
On Debian and Ubuntu, review /var/log/apt/history.log and dpkg -l. On Fedora or RHEL-family systems, review dnf history and installed kernel packages. Look for an interrupted transaction, a removed dependency, or an update that completed without creating the expected initramfs.
Debian and Ubuntu repair
Use the package name and version already installed on the machine rather than guessing a distribution release. If the affected package is known, reinstall its kernel image and modules. A typical pattern is:
sudo dpkg --configure -a
sudo apt-get -f install
sudo apt-get install --reinstall linux-image-VERSION linux-modules-VERSION
Replace VERSION with the exact package version shown by dpkg -l. If the initramfs for that version is missing, create it; if it exists but may be stale, update it:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
sudo update-initramfs -c -k VERSION
sudo update-initramfs -u -k VERSION
Use only one of those operations for a given version: -c creates a new image, while -u updates an existing one. Then regenerate the GRUB menu:
sudo update-grub
Review the generated menu output for the repaired kernel and confirm that /boot contains its new initramfs before rebooting. If apt-get reports that the package cannot be found, identify the installed package with dpkg -l 'linux-image*' and use the matching package name from that list.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Fedora and RHEL-family repair
Reinstall the affected kernel packages with the package manager used by the installed release. For example:
sudo dnf reinstall kernel-core-VERSION kernel-modules-VERSION
Regenerate the image with the version-specific dracut command:
sudo dracut --force /boot/initramfs-VERSION.img VERSION
Check the resulting file size and timestamp. Then regenerate the GRUB configuration using the target path documented for that installation’s firmware mode. A common BIOS path is:
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
UEFI installations can use a different file under /boot/efi; do not overwrite a different target merely because the command succeeds. Use the existing distribution configuration and verify that the menu entry references the repaired kernel and initramfs.
Repair a VPS that cannot boot with a rescue VM
Attach the operating-system disk safely
Power off or stop the failed VPS as required by the provider, create or retain a snapshot, and attach a copy of the OS disk to a temporary Linux rescue VM. AWS documents attaching a root volume to another running Linux instance; Azure documents the equivalent repair-VM and chroot workflow. Device names such as /dev/vdb are examples only: identify the actual disk and partitions on the rescue VM.
lsblk -f
sudo blkid
Match filesystem UUIDs, labels, and sizes with the original layout. If the VPS uses LVM, activate its volume groups before mounting:
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
sudo vgchange -ay
Mount the root and boot filesystems
Mount the target root volume at a temporary directory, then mount separate /boot or EFI filesystems at their original paths beneath it. The following illustrates the order; replace the example devices with the volumes identified by lsblk.
sudo mkdir -p /mnt/target
sudo mount /dev/mapper/vg-root /mnt/target
sudo mount /dev/vdb2 /mnt/target/boot
sudo mount --rbind /dev /mnt/target/dev
sudo mount --make-rslave /mnt/target/dev
sudo mount -t proc proc /mnt/target/proc
sudo mount --rbind /sys /mnt/target/sys
sudo mount --make-rslave /mnt/target/sys
sudo mount --rbind /run /mnt/target/run
sudo mount --make-rslave /mnt/target/run
Do not mount a partition at /mnt/target/boot unless the original system actually had a separate boot filesystem. Mounting the wrong partition there hides the real kernel files and makes a correct repair appear to fail.
Enter the installed system with chroot
sudo chroot /mnt/target /bin/bash
Inside the chroot, / now refers to the VPS disk. Network access may not work automatically because resolver files and interfaces belong to the rescue VM. Package repair can still work from cached packages; if downloads are required, copy the rescue VM’s resolver configuration only after preserving the target’s original file and remove the temporary copy before leaving.
Rebuild packages, initramfs, and GRUB in the chroot
Run the same distribution-specific repair commands described for a booted system, but execute them after entering the chroot. First finish any interrupted package transaction, then reinstall the kernel or core packages, rebuild the initramfs for the selected version, and regenerate the boot menu. Confirm that the new image is physically present under the mounted target’s /boot.
When core libraries are missing
Red Hat examples of this panic include a missing dynamic loader or an init-system library. If the console trace names a loader such as ld-linux, a systemd library, or another file required by PID 1, reinstall the package that owns it instead of copying a library from the rescue VM. On Debian-family systems, use the package database to identify the owner and reinstall the relevant libc or systemd package. On Fedora and RHEL-family systems, reinstall the corresponding glibc or systemd package with dnf. Copying libraries from a different release can create an ABI mismatch and produce a second boot failure.
If the package database itself is inconsistent, complete the interrupted transaction before rebuilding the initramfs. A successful dracut or update-initramfs run does not repair a missing loader; both the userspace package and the boot image must be valid.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Do not reinstall the bootloader blindly
Regenerating the GRUB menu is usually safer than reinstalling GRUB’s boot code. A full bootloader installation depends on BIOS versus UEFI mode, partition layout, and the provider’s firmware configuration. Use grub-install only when you have confirmed that the bootloader itself is damaged and you know the exact firmware target. An incorrect installation can make every kernel entry inaccessible even when the kernels are healthy.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsCheck GRUB’s root and initrd references
A menu entry can look normal while pointing to the wrong disk or UUID. From the repaired system, inspect the generated configuration and compare its root=UUID=... value with blkid. Every normal Linux entry should reference both a kernel and an initramfs. If the initrd line is absent, points to a nonexistent file, or names a different version, the kernel may panic before it can mount the root filesystem.
Common signs of a root-device problem include an emergency shell that cannot find the root volume, repeated “waiting for root device” messages, or a panic immediately after the initramfs starts. Correct the underlying UUID or regenerated menu rather than editing a single temporary GRUB entry and leaving the installed configuration inconsistent.
Check the filesystem and storage offline
Google Cloud associates boot-disk damage with an unclean shutdown, a full disk, or an I/O error. Check both capacity and provider storage events. A filesystem that was full while a kernel package was writing can leave a zero-byte initramfs; repeated I/O errors can corrupt files that were previously valid.
- Leave the target filesystem unmounted, or shut down the rescue VM before checking a volume that is still mounted there.
- Run the checker appropriate for the filesystem. For an ext-family filesystem, use its ext checker with the device path. For XFS, use
xfs_repairon the unmounted device. - Read the checker’s output before accepting repairs. Do not force repeated repairs when the tool cannot make the filesystem consistent.
- If the volume remains inconsistent or hardware-level I/O errors continue, restore the snapshot to a new disk rather than repeatedly forcing boots on the damaged one.
Never run an ext-family repair against a mounted root filesystem, and do not run xfs_repair while XFS is mounted. The exact checker command depends on the filesystem type and must target the correct partition, not the whole disk containing unrelated partitions.
Recommended Free Tools
Unmount, reattach, and validate the repaired disk
After package and filesystem work is complete, leave the chroot and unmount in reverse order. Recursive unmounting helps remove bind mounts:
exit
sudo umount -R /mnt/target
If the provider requires it, deactivate LVM and detach the disk cleanly from the rescue VM. Reattach it as the VPS boot disk, boot once with verbose serial-console output, and verify:
- The expected kernel and matching initramfs are selected.
- The root filesystem mounts without emergency-mode errors.
- PID 1 remains running and systemd reaches the normal target.
- SSH accepts a connection and the VPS network is configured normally.
- Critical applications, scheduled jobs, and monitoring checks are healthy.
Keep the snapshot until the VPS has completed a normal reboot from the repaired kernel. A single successful boot proves that the immediate failure is gone; it does not prove that storage or package-management problems cannot recur.
Use the boot trace to choose the next repair
| Observed symptom | Most useful next check |
|---|---|
| Failure begins immediately after a kernel update | Boot the previous kernel, compare kernel/initramfs pairs in /boot, and inspect package history |
| GRUB shows a kernel but no matching initramfs | Rebuild the image for that exact kernel version, then regenerate the GRUB menu |
| Initramfs cannot find the root device | Compare the GRUB root= UUID with blkid and verify storage visibility |
| Boot disk reports I/O errors or filesystem inconsistencies | Snapshot first, unmount, run the filesystem-specific checker, and restore the snapshot if consistency cannot be recovered |
| Trace names a missing loader or systemd library | Reinstall the owning core package inside the running system or chroot, then rebuild initramfs |
| PID 1 starts and then exits | Read the preceding journal and systemd/kernel versions; treat it as an init-system crash rather than assuming a missing initramfs |
Prevent the next kernel-panic recovery
- Keep at least one known-good kernel until the replacement has survived a complete reboot.
- Monitor free space in both
/bootand the root filesystem before unattended kernel updates. - Retain provider snapshots or backups according to the recovery time you need, and test that a disk can actually be attached to a rescue VM.
- Enable serial-console or boot-diagnostics access before an incident; it is often the only way to select an older kernel when SSH is unavailable.
- Review package-manager failures rather than ignoring a transaction that ended with dependency or initramfs errors.
- Capture the panic trace and kernel version before making changes so a later repair can distinguish a boot-image problem from a userspace crash.
The reliable fix is therefore conditional: select an older kernel when available, repair the exact kernel and initramfs pair when the guest still boots, or use a snapshot-backed rescue VM when it does not. Validate GRUB’s root and initrd references, repair missing core libraries, check storage offline, and keep the rollback copy until the VPS completes a normal reboot.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
