You are not logged in.
After upgrading a few packages, I'm greeted with a kernel panic tombstone when trying to boot my system:
My transcription from a photo of my monitor (If there are any typos, my bad):
Failed to execute /init (error -13)
Starting init: /sbin/init exists but couldn't execute it (error -13)
Starting init: /bin/init exists but couldn't execute it (error -13)
Starting init: /bin/sh exists but couldn't execute it (error -13)
Kernel paniv - not syncing: No working init found. Try passing init= options to kernel.
CPU: 3 PID: 1 Comm: swapper/0 not tainted 4.16.13-2 ARCH #1
...
Luckily, I have the option to boot arch in an "Advanced mode" (from initramfs if i recall corectly, and then the system works. Otherwise I would be completely locked out.
Solving kernel panics are way over my head, but i checked some other threads, and here are some commands and outputs that perhaps could be relevant:
~> ls -l /boot
drwxr-xr-x 6 root root 1024 Jun 11 22:03 grub/
-rw-r--r-- 1 root root 48181612 Jun 11 10:00 initramfs-linux-fallback.img
-rw-r--r-- 1 root root 10036 Jun 11 21:24 initramfs-linux.img
-rw-r--r-- 1 root root 1670656 May 7 23:11 intel-ucode.img
drwx------ 2 root root 12288 Mar 30 2016 lost+found/
-rw-r--r-- 1 root root 5240688 Jun 1 20:45 vmlinuz-linux
~> cat /etc/fstab
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
# /dev/mapper/storage-root
UUID=e156cd7f-49d4-4fb2-85b8-9c2fad6db52b / ext4 rw,relatime,data=ordered 0 1
# /dev/sda1
UUID=1a2b37b9-2add-4241-8029-62ef92f3c57d /boot ext2 rw,relatime,block_validity,barrier,user_xattr,acl 0 2
# /dev/mapper/storage-swap
UUID=2bd4ed59-0cb1-4e0f-99ad-390340857dc4 none swap defaults 0 0
~> sudo blkid
/dev/sda1: UUID="1a2b37b9-2add-4241-8029-62ef92f3c57d" TYPE="ext2" PARTUUID="f52ce293-01"
/dev/sda2: UUID="7691d404-00f0-4c46-b271-09dabf6ef4fc" TYPE="crypto_LUKS" PARTUUID="f52ce293-02"
/dev/mapper/lvm: UUID="DmYmQy-hI0k-Slys-9thy-2PvG-ddd8-3KYS0o" TYPE="LVM2_member"
/dev/mapper/storage-swap: UUID="2bd4ed59-0cb1-4e0f-99ad-390340857dc4" TYPE="swap"
/dev/mapper/storage-root: UUID="e156cd7f-49d4-4fb2-85b8-9c2fad6db52b" TYPE="ext4"
~> fdisk -l
Disk /dev/sda: 119.2 GiB, 128035676160 bytes, 250069680 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: dos
Disk identifier: 0xf52ce293
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 409599 407552 199M 83 Linux
/dev/sda2 409600 250068991 249659392 119G 8e Linux LVM
Disk /dev/mapper/lvm: 119 GiB, 127823511552 bytes, 249655296 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/storage-swap: 8 GiB, 8589934592 bytes, 16777216 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/storage-root: 111 GiB, 119231479808 bytes, 232873984 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
~> sudo cat /etc/default/grub
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Arch"
GRUB_CMDLINE_LINUX_DEFAULT="quiet amdgpu.si_support=1 radeon.si_support=0"
GRUB_CMDLINE_LINUX="cryptdevice=UUID=7691d404-00f0-4c46-b271-09dabf6ef4fc:lvm root=/dev/mapper/storage-root resume=/dev/mapper/storage-swap"
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable Hidden Menu, and optionally hide the timeout count
#GRUB_HIDDEN_TIMEOUT=5
#GRUB_HIDDEN_TIMEOUT_QUIET=true
# Uncomment to use basic console
GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
#GRUB_COLOR_NORMAL="light-blue/black"
#GRUB_COLOR_HIGHLIGHT="light-cyan/blue"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/path/to/wallpaper"
#GRUB_THEME="/path/to/gfxtheme"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
#GRUB_SAVEDEFAULT="true"
I'm not sure if this provides info that can solve the problem - let me know if there is another command that provides more relevant information.
Thanks so much in advance!
EDIT: As you can see, I have added some kernel parameters in grub to make use of my hybrid graphic card. I doubt this is causing the kernel to panic however, since the parameters have been there for many months.
EDIT2: Just to clarify: All the commands and output have been gathered after booting in "Advanced mode" (from initramfs) as I mentioned above.
Last edited by wololos (2018-06-12 09:22:57)
Offline
Your initramfs-linux.img is less than 10kB - I'd say it's corrupted.
Re-run mkinitcpio (https://wiki.archlinux.org/index.php/Mkinitcpio), watch out for errors and check the resulting image sizes and also
file /boot/initramfs-linux.img
lsinitcpio /boot/initramfs-linux.img
Offline
Your initramfs-linux.img is less than 10kB - I'd say it's corrupted.
Re-run mkinitcpio (https://wiki.archlinux.org/index.php/Mkinitcpio), watch out for errors and check the resulting image sizes and alsofile /boot/initramfs-linux.img lsinitcpio /boot/initramfs-linux.img
This was indeed the issue - I ran the command:
sudo mkinitcpio -p linux
and rebooted the system - it now works flawlessly again.
Nice catch - thank you very much!
This thread can now be closed I believe.
Offline
You can mark your thread as [Solved] by editing your first post and prepending it to the title.
Offline
No, it can't. (Mods close threads if they don't want anybody to post to them anymore, happens for necrobumps) - but you can mark it [solved] by editing your initial post and altering the subject line ;-)
Edit: ninja'd by Jason.
Last edited by seth (2018-06-11 21:34:32)
Offline
Thanks again!
Offline