• kernel panic


    Hi all-

    I have an Antergos install that’s been running beautifully for well over a year now with daily updating. This morning, I ran ‘sudo pacman -Syu’ to have a number of recent updates installed. I don’t remember all the packages, but they numbered around 15 in total. During the update, i experienced a crash of the system.

    Upon rebooting, I’m met with kernel panics each time. I get ‘loading linux kernel’ and ‘loading ramdisk’ then ‘starting version 239’ This is followed by somewhat different messages each boot.

    The latest contains:

    ERROR: resume: hibernating device 'UUID= blah blah numbers' not found
    /dev/sda3: recovering journal
    /dev/sda3: clean 500777/2048000 files, 5238540/8192000 blocks
    switch_root: failed to execute /sbin/init: Exec format error
    [   18.184307] Kernel panic - not syncing:  Attempted to kill init! exitcode=0x00007e00
    ,,,more stuff...
    

    There are also some RIP messages interspersed as well.
    This machine has 3 SDDs (one with Antergos, one with Linux Mint, and one with openSUSE). It’s not truly multiboot as I have to choose the drive I want at start from the BIOS vs. a single boot loader (if that makes sense).

    Antergos is my primary, and would really love to get it booting again. I don’t think it’s a bad drive, but maybe so. Please let me know what else I can provide and any help in restoring is GREATLY appreciated.

    Thanks!

  • @trey
    You could try booting with the Antergos USB installer stick.
    Then start a terminal and see if you can show here some info about disks and especially partition /dev/sda3 (that seems to have problems):

    su
    lsblk -fm
    fdisk -l
    

    Then it is wise to make backup (if possible) of your important files you don’t want to lose. Use a file manager for that.

    And then you could try running fsck to the partition:
    fsck /dev/sda3

    If that helps anything, you could now try rebooting.

    If the partition /dev/sda3 seems OK but cannot boot, you could also use the USB installer to arch-chroot to /dev/sda3 (assuming it is the root partition of Antergos). But before doing that, try the the above things first.

  • On yesterday update my graphical Interface crashed too… And interrupted update…
    But I complete update from TTY then and do not get any problems…

    So I would try boot from liveiso and chroot into Antergos install to complete update. And following then to regenerate images:

    sudo mkinitcpio -p linux
    sudo grub-mkconfig -o /boot/grub/grub.cfg
    

    Here you can get info on how to arch-chroot:
    https://antergos.com/wiki/de/miscellaneous/how-to-fix-grub-with-efi-boot/

  • Thank you. I have booted from the live DVD image. Here is the output of fdisk -l:

    [[email protected] ~]$ sudo fdisk -l
    Disk /dev/loop0: 2 GiB, 2135687168 bytes, 4171264 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    
    Disk /dev/sda: 223.6 GiB, 240057409536 bytes, 468862128 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: D8EB174C-0A71-479E-BFC7-F735B898EEB6
    
    Device        Start       End   Sectors   Size Type
    /dev/sda1      2048   2050047   2048000  1000M EFI System
    /dev/sda2   2050048   4098047   2048000  1000M Linux filesystem
    /dev/sda3   4098048  69634047  65536000  31.3G EFI System
    /dev/sda4  69634048 468860927 399226880 190.4G Linux filesystem
    
    
    Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: A26895F3-3E69-4528-9DCD-14C04F1B3F97
    
    Device     Start       End   Sectors   Size Type
    /dev/sdb1   2048 976773134 976771087 465.8G Linux LVM
    
    
    Disk /dev/sdc: 465.8 GiB, 500107862016 bytes, 976773168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: ACEA0C54-726D-46B5-982C-20DB37BE11AF
    
    Device       Start       End   Sectors   Size Type
    /dev/sdc1     2048   1050623   1048576   512M EFI System
    /dev/sdc2  1050624 976771071 975720448 465.3G Linux filesystem
    
    
    Disk /dev/mapper/system-swap: 31.3 GiB, 33625735168 bytes, 65675264 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    
    Disk /dev/mapper/system-home: 25 GiB, 26843545600 bytes, 52428800 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    
    
    Disk /dev/mapper/system-root: 20 GiB, 21474836480 bytes, 41943040 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes_text
    

    I know that Antergos is on the smallest drive currently (256Gb) so that would be /dev/sda

    However, I’m getting the following error when trying to mount:

    [[email protected] antergos]# mount /dev/sda2 /mnt
    mount: /mnt: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error.
    [[email protected] antergos]#
    

    Any idea what might be wrong?

    Thanks!

  • @trey
    Can you mount any of the partitions on /dev/sda?

    And why is there two “EFI System” partitions on /dev/sda?

    Could you show the output of

    lsblk -fm
    

    Could you also explain what are the contents on each partition at /dev/sda?

  • @trey said in kernel panic:

    Disk /dev/sda: 223.6 GiB, 240057409536 bytes, 468862128 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: D8EB174C-0A71-479E-BFC7-F735B898EEB6

    Device Start End Sectors Size Type
    /dev/sda1 2048 2050047 2048000 1000M EFI System
    /dev/sda2 2050048 4098047 2048000 1000M Linux filesystem
    /dev/sda3 4098048 69634047 65536000 31.3G EFI System
    /dev/sda4 69634048 468860927 399226880 190.4G Linux filesystem

    i saw also on other users output that root filesystem is named efisystem… but
    lsblk -fm will give more speaky output on gpt…

  • Thank you. Here is the requested output of ‘lsblk -fm’

    [[email protected] antergos]# lsblk -fm
    NAME            FSTYPE      LABEL    UUID                                   MOUNTPOINT                    SIZE OWNER GROUP   MODE
    loop0           squashfs                                                    /run/archiso/sfs/root-image     2G root  disk    brw-rw----
    sda                                                                                                     223.6G root  disk    brw-rw----
    ├─sda1          vfat                 A6D1-87C7                                                           1000M root  disk    brw-rw----
    ├─sda2                                                                                                   1000M root  disk    brw-rw----
    ├─sda3          ext4                 4a1da689-c125-4f89-83d5-22d7826369c5   /mnt                         31.3G root  disk    brw-rw----
    └─sda4          ext4                 9ab4acc4-a104-4167-9ad8-9d7f101f4bff                               190.4G root  disk    brw-rw----
    sdb                                                                                                     465.8G root  disk    brw-rw----
    └─sdb1          LVM2_member          RCstgx-s2w8-vUNd-x8NE-cXRo-acfc-HFj0f4                             465.8G root  disk    brw-rw----
      ├─system-swap swap                 394dfb88-5f18-4bd3-a197-97773895ce54                                31.3G root  disk    brw-rw----
      ├─system-home ext4                 edd22539-c4a2-452e-bcb4-574d42033c2f                                  25G root  disk    brw-rw----
      └─system-root ext4                 c73357e7-ec02-4d67-b80d-d1ec5b5018d5                                  20G root  disk    brw-rw----
    sdc                                                                                                     465.8G root  disk    brw-rw----
    ├─sdc1          vfat                 0022-55CF                                                            512M root  disk    brw-rw----
    └─sdc2          ext4                 73cc8cde-f16e-4c53-8aa8-ae2184c4a1f2                               465.3G root  disk    brw-rw----
    sr0             iso9660     ANTERGOS 2018-11-03-02-54-54-00                 /run/archiso/bootmnt          2.1G root  optical brw-rw----
    

    As for /dev/sda, it looks like sda3 is root (not sure why it’s showing as EFI System, and sda4 is /home. Not sure about sda2 at this point. I was trying to get the 3 systems to multiboot and likely followed some directions for EFI systems.

    This probably explains why I could boot Antergos directly in the past, but my other linux OSs could not boot Antergos from their respective grub entries.

  • /sda2 is extended partition as it looks like… but as i know it is problematic to get Arch-based systems automatic recognized by grub… @manuel can help her emore then me ;)

    And at first iam not sure if it is right and not an issue if root is named EFI-System…

  • Also, after ‘arch-chroot /mnt’ and trying to update, I’m getting the following errors on the package signatures:

    [[email protected] /]# pacman -Syu
    :: Synchronizing package databases...
     antergos is up to date
     core is up to date
     extra                                                                                                      1652.0 KiB  6.20M/s 00:00 [#################################################################################] 100%
     community                                                                                                     4.7 MiB  10.1M/s 00:00 [#################################################################################] 100%
     multilib is up to date
    :: Starting full system upgrade...
    resolving dependencies...
    looking for conflicting packages...
    
    Packages (12) gtkmm3-3.22.3-1  lib32-systemd-239.300-1  perl-parse-yapp-1.21-1  python-pyparsing-2.3.0-1  python-sphinx-1.8.1-2  python-urllib3-1.24.1-1  python2-pyparsing-2.3.0-1  python2-sphinx-1.8.1-2
                  python2-urllib3-1.24.1-1  subversion-1.11.0-1  systemd-sysvcompat-239.300-1  vivaldi-2.1.1337.36-1
    
    Total Download Size:     1.38 MiB
    Total Installed Size:  288.62 MiB
    Net Upgrade Size:        2.64 MiB
    
    :: Proceed with installation? [Y/n] 
    :: Retrieving packages...
     gtkmm3-3.22.3-1-x86_64                                                                                     1381.0 KiB  10.7M/s 00:00 [#################################################################################] 100%
     perl-parse-yapp-1.21-1-any                                                                                   36.3 KiB  11.8M/s 00:00 [#################################################################################] 100%
    (12/12) checking keys in keyring                                                                                                      [#################################################################################] 100%
    (12/12) checking package integrity                                                                                                    [#################################################################################] 100%
    error: lib32-systemd: signature from "Christian Hesse (Arch Linux Package Signing) <[email protected]>" is invalid
    :: File /var/cache/pacman/pkg/lib32-systemd-239.300-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
    Do you want to delete it? [Y/n] 
    error: python-pyparsing: signature from "Felix Yan <[email protected]>" is invalid
    :: File /var/cache/pacman/pkg/python-pyparsing-2.3.0-1-any.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
    Do you want to delete it? [Y/n] n
    error: python-urllib3: signature from "Felix Yan <[email protected]>" is invalid
    :: File /var/cache/pacman/pkg/python-urllib3-1.24.1-1-any.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
    Do you want to delete it? [Y/n] n
    error: python-sphinx: signature from "Antonio Rojas <[email protected]>" is invalid
    :: File /var/cache/pacman/pkg/python-sphinx-1.8.1-2-any.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
    Do you want to delete it? [Y/n] n
    error: python2-pyparsing: signature from "Felix Yan <[email protected]>" is invalid
    :: File /var/cache/pacman/pkg/python2-pyparsing-2.3.0-1-any.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
    Do you want to delete it? [Y/n] n
    error: python2-urllib3: signature from "Felix Yan <[email protected]>" is invalid
    :: File /var/cache/pacman/pkg/python2-urllib3-1.24.1-1-any.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
    Do you want to delete it? [Y/n] n
    error: python2-sphinx: signature from "Antonio Rojas <[email protected]>" is invalid
    :: File /var/cache/pacman/pkg/python2-sphinx-1.8.1-2-any.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
    Do you want to delete it? [Y/n] n
    error: subversion: signature from "Felix Yan <[email protected]>" is invalid
    :: File /var/cache/pacman/pkg/subversion-1.11.0-1-x86_64.pkg.tar.xz is corrupted (invalid or corrupted package (PGP signature)).
    
  • Luckily, this issue is often solved very easily with two simple commands:

    sudo pacman -Scc
    

    and then

    sudo pacman-key --refresh-keys
    

    after that, try to update again using

    sudo pacman -Syu
    

    https://antergos.com/wiki/uncategorized/update-error-involving-keyrings/

  • Thanks. I’m at home and not behind a proxy, but getting the following error when attempting to refresh the keys:

    [[email protected] /]# sudo pacman-key --refresh-keys
    gpg: refreshing 109 keys from hkp://pool.sks-keyservers.net
    gpg: keyserver refresh failed: Server indicated a failure
    ==> ERROR: A specified local key could not be updated from a keyserver.
    
  • As sda is a gpt disk, I don’t think sda2 is an extended partition.
    Maybe sda partitions are just somehow corrupted due to the crash.

    @trey If you don’t have anything worth saving on /dev/sda, I suggest you reinstall Antergos to it. And it is possible that other operating systems fail to correctly generate grub menu entries for Antergos. You can see it in file /boot/grub/grub.cfg, there should be lines for Antergos like

    initrd /boot/intel-ucode.img /boot/initramfs-linux.img
    

    but the initramfs (or intel-ucode) part may be missing (assuming you have an Intel processor!).

    These example menu entries should help you with booting Antergos: https://forum.antergos.com/topic/9039/grub-boot-examples-custom-cfg

    One of the above examples should be particularly easy (https://forum.antergos.com/topic/9039/grub-boot-examples-custom-cfg/3):

    menuentry "Antergos LTS" {
        savedefault
        set kernel=linux-lts
        search --set --file /boot/vmlinuz-$kernel
        probe -u $root --set=uuid
        linux  /boot/vmlinuz-$kernel root=UUID=$uuid rw quiet
        initrd /boot/intel-ucode.img /boot/initramfs-$kernel.img
    }
    

    The above can easily be modified for the default kernel, linux, by changing the value of the kernel variable.

  • sudo nano /etc/pacman.d/gnupg/gpg.conf
    

    The fourth line should say something like"keyserver hkp://pool.sks-keyservers.net"
    The “hkp” must be changed to “http”
    Save with [Ctrl+X]
    and try again

  • /sda2 can only be /boot then… In this case it will be hard to recover, and reinstall would be the easy solution…

  • Thank you. Happy to move this to a new thread if it makes more sense.

    I was planning to eventually move the install to a new (bigger) drive later (256G -> 512G) but wanted to get a plan to minimize the amount of ‘re-work’ I would need to do on a fresh install.

    • Wanted to copy the contents of my /home directory to a flash drive to reinstall to the new install (hidden config files, etc.). Can I copy from the mount I have now?

    • Is there some way I can make a list of the installed packages and re-install on the new drive? Or is this too much trouble?

    • Lastly, what do I need to do (if anything) to get the new drive to be the default on boot and its grub to be able to launch the other 2 distros? I had a good handle on this prior to EFI, but its introduction has really given me headaches!

    Thank you!

  • @trey

    • Check which partition is /home, either sda3 or sda4 I guess, and mount it.
      Then you can use e.g. a file manager to copy your home folder(s) to a backup drive.

    • List of installed packages can be retrieved with pacman, but if you cannot boot or arch-chroot to the system, these commands don’t work. But there’s another way: list files in /var/cache/pacman/pkg, it contains installed packages (and some older versions too). You could just store the list to a file, but probably not use the list as such, but manually select packages that you really want to install. For example:

    ls -1 /var/cache/pacman/pkg > packages.txt
    
    • That depends on your machine’s BIOS/Firmware UEFI boot settings, which OS to boot. Also, after installing Antergos you need to run command
      sudo grub-mkconfig -o /boot/grub/grub.cfg
      (which does the same as update-grub on some other systems) unless the installer didn’t do so already.
kernel125 panic8 Posts 16Views 274
Bloom Email Optin Plugin

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