• Kernel panic - not syncing: No working init found. after Kernel update


    Yesterday I came to work, it was not possible to login to my work pc, it was locked before. So, I restarted the work pc and then I got the following screen.

    Failed to execute /init (error -2)
    Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance.
    CPU: 7 PID: 1 Comm: swapper/0 Not tainted 4.10.1-1ARCH #1
    

    Kernel panic screen

    Back at home I updated my home pc and I got a kernel update, after that I got the same screen and can not boot my system anymore. So I think the kernel update is the problem. Also both pc have different hardware.

    I already tried to pass: init=/usr/lib/systemd/systemd as kernel parameter in GRUB, but it does not work.

    What can I do to boot my system again?

  • boot up with fallback kernel…
    On Bootscreen choose advanced and then Fallback…

  • @joekamprad said in Kernel panic - not syncing: No working init found. after Kernel update:

    boot up with fallback kernel…
    On Bootscreen choose advanced and then Fallback…

    I also tried that, but it does not work.

  • rescue would be booting with liveiso and chroot, try to rebuild initram
    with:

    sudo mkinitcpio -p linux
    
  • do you have something explicit kernel related features done?
    ZFS maybe?

  • @joekamprad said in Kernel panic - not syncing: No working init found. after Kernel update:

    rescue would be booting with liveiso and chroot, try to rebuild initram
    with:

    sudo mkinitcpio -p linux
    

    I will try it, but first I need to study the article.

    @joekamprad said in Kernel panic - not syncing: No working init found. after Kernel update:

    do you have something explicit kernel related features done?
    ZFS maybe?

    No, I have traditional ext4.

  • @joekamprad said in Kernel panic - not syncing: No working init found. after Kernel update:

    rescue would be booting with liveiso and chroot, try to rebuild initram
    with:

    sudo mkinitcpio -p linux
    

    It does not work.

    [[email protected] ~]$ sudo arch-chroot /run/media/antergos/system
    [[email protected] /]# sudo mkinitcpio -p linux
    ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
      -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
    ==> Starting build: 4.10.2-1-ARCH
      -> Running build hook: [base]
      -> Running build hook: [udev]
      -> Running build hook: [autodetect]
      -> Running build hook: [modconf]
      -> Running build hook: [block]
      -> Running build hook: [keyboard]
      -> Running build hook: [keymap]
      -> Running build hook: [resume]
      -> Running build hook: [filesystems]
      -> Running build hook: [fsck]
    ==> Generating module dependencies
    ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
    bsdcpio: Failed to set default locale
    ==> Image generation successful
    ==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
      -> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
    ==> Starting build: 4.10.2-1-ARCH
      -> Running build hook: [base]
      -> Running build hook: [udev]
      -> Running build hook: [modconf]
      -> Running build hook: [block]
    ==> WARNING: Possibly missing firmware for module: aic94xx
    ==> WARNING: Possibly missing firmware for module: wd719x
      -> Running build hook: [keyboard]
      -> Running build hook: [keymap]
      -> Running build hook: [resume]
      -> Running build hook: [filesystems]
      -> Running build hook: [fsck]
    ==> Generating module dependencies
    ==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
    bsdcpio: Failed to set default locale
    ==> Image generation successful
    [[email protected] /]# 
    

    I get the same error at boot. What can I do now?

  • I am not the kernel pro…
    But seems very unusual …

    Do you mounting both / and /boot? because image have to be written in /boot and as far as i now standard on Antergos is a /boot partition on its own.

  • @joekamprad said in Kernel panic - not syncing: No working init found. after Kernel update:

    I am not the kernel pro…
    But seems very unusual …

    Do you mounting both / and /boot? because image have to be written in /boot and as far as i now standard on Antergos is a /boot partition on its own.

    I have a /boot folder.:

    [[email protected] /]# ls /boot/
    efi  grub  initramfs-linux-fallback.img  initramfs-linux-lts-fallback.img  initramfs-linux-lts.img  initramfs-linux.img  syslinux  vmlinuz-linux  vmlinuz-linux-lts
    
    [[email protected] /]# blkid
    /dev/loop0: TYPE="squashfs"
    /dev/sda1: LABEL="swap" UUID="..." TYPE="swap" PARTUUID="..."
    /dev/sda2: LABEL="efi" UUID="..." TYPE="vfat" PARTUUID="..."
    /dev/sda3: LABEL="system" UUID="..." TYPE="ext4" PARTUUID="..."
    /dev/sdb1: LABEL="home" UUID="..." TYPE="ext4" PARTUUID="..."
    /dev/sdc1: UUID="2017-02-05-05-15-18-00" LABEL="ANTERGOS" TYPE="iso9660" PTUUID="02ee78f6" PTTYPE="dos" PARTUUID="02ee78f6-01"
    /dev/sdc2: SEC_TYPE="msdos" LABEL="ARCHISO_EFI" UUID="33B4-BB26" TYPE="vfat" PARTUUID="02ee78f6-02"
    [[email protected] /]# 
    
  • If I try to generate the GRUB menu, I get an error.:

    [[email protected] /]# grub-mkconfig -o /boot/grub/grub.cfg
    Generating grub configuration file ...
    Found theme: /boot/grub/themes/Antergos-Default/theme.txt
    Found linux image: /boot/vmlinuz-linux-lts
    Found initrd image: /boot/initramfs-linux-lts.img
    Found fallback initramfs image: /boot/initramfs-linux-lts-fallback.img
    Found linux image: /boot/vmlinuz-linux
    Found initrd image: /boot/initramfs-linux.img
    Found fallback initramfs image: /boot/initramfs-linux-fallback.img
      WARNING: Failed to connect to lvmetad. Falling back to device scanning.
    grub-probe: error: cannot find a GRUB drive for /dev/sdc1.  Check your device.map.
    done
    [[email protected] /]# 
    

    What does that mean?

  • I found the problem. It was a broken symlink, /usr/lib64 should link to /usr/lib. In my case, in /usr/lib64 was a Feedreader folder. I booted Antergos USB live stick and installed the Arch install scripts .

    sudo pacman -S arch-install-scripts
    sudo arch-chroot /path/to/system/partion
    

    Then I uninstalled Feedreader, recreated the symlink and initramfs.

    sudo pacman -R feedreader
    cd /usr
    sudo ln -s lib lib64
    sudo mkinitcpio -p linux
    
  • /usr/lib64 should be a symlink shure! and i do not think installation path of feedreader are right on installing to /usr/lib64… as /usr/lib64 is linked to /usr/lib installation should write to /usr/lib/ instead…

    https://github.com/Antergos/antergos-packages/blob/master/antergos/feedreader/PKGBUILD

    https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=feedreader

  • On my encrypted home pc, I had to decrypt my root / partition before arch-chroot.

    sudo modprobe -v dm-mod
    sudo modprobe -v dm-crypt
    blkid
    sudo cryptsetup luksOpen /dev/sda2 crypt   # /dev/sd2 found with blkid
    

    Also I had to mount to boot partition.

    blkid
    mount /dev/sda1 # /dev/sd1 found with blkid
    
upgrade74 update55 boot error6 kernel panic3 Posts 13Views 9205
Bloom Email Optin Plugin

Looks like your connection to Antergos Community Forum was lost, please wait while we try to reconnect.