You are not logged in.
Never thought I'd author a post describing a kernel panic but here goes:
switch_root: failed to execute /sbin/init: Input/output error
Kernel panic - not syncing: Attempting to kill init! exitcode=0x00000100
Pid: 1, comm: switch_root Not tainted 3.5.3-1-ARCH #1
Call Trace:
panic+0x81/0x17b
do_exit+0x792/0x800
do_group_exit+0x34/0xa0
sys_exit_group+0x18/0x20
sysenter_do_call+0x12/0x28
This occurred on my i686 virtualbox after preforming the latest update which included some systemd stuff. I haven't moved the vbox over to systemd yet however. Love to hear suggestions as to causes.
/var/log/pacman.log:
[2012-08-30 14:54] starting full system upgrade
[2012-08-30 14:54] removed libsystemd (188-2)
[2012-08-30 14:54] removed systemd-tools (188-2)
[2012-08-30 14:54] Generating locales...
[2012-08-30 14:54] en_US.UTF-8... done
[2012-08-30 14:54] en_US.ISO-8859-1... done
[2012-08-30 14:54] Generation complete.
[2012-08-30 14:54] upgraded glibc (2.16.0-3 -> 2.16.0-4)
[2012-08-30 14:54] upgraded cracklib (2.8.18-2 -> 2.8.19-1)
[2012-08-30 14:54] upgraded filesystem (2012.7-1 -> 2012.8-1)
[2012-08-30 14:54] ln -s '/usr/lib/systemd/system/getty@.service' '/etc/systemd/system/getty.target.wants/getty@tty1.service'
[2012-08-30 14:54] :: Append 'init=/bin/systemd' to your kernel command line in your
[2012-08-30 14:54] bootloader to replace sysvinit with systemd
[2012-08-30 14:54] installed systemd (189-3)
[2012-08-30 14:54] upgraded initscripts (2012.08.3-1 -> 2012.08.3-2)
EDIT: I setup the box for systemd and appended init=/bin/systemd to the boot line; the same kernel panic occurs except:
switch_root: failed to execute /bin/systemd: Exec format error
Kernel panic - not syncing ...
Last edited by graysky (2012-08-31 15:30:09)
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
switch_root: failed to execute /sbin/init: Input/output error Kernel panic - not syncing: Attempting to kill init! exitcode=0x00000100 Pid: 1, comm: switch_root Not tainted 3.5.3-1-ARCH #1 Call Trace: panic+0x81/0x17b do_exit+0x792/0x800 do_group_exit+0x34/0xa0 sys_exit_group+0x18/0x20 sysenter_do_call+0x12/0x28
EDIT: I setup the box for systemd and appended init=/bin/systemd to the boot line; the same kernel panic occurs except:
switch_root: failed to execute /bin/systemd: Exec format error Kernel panic - not syncing ...
I'd be trying to figure out why it can't find /sbin/init or /bin/systemd.
It's apparently missing in your initramfs-linux.img.
Check your /etc/mkinitcpio.conf to see what hooks you have.
I may have to CONSOLE you about your usage of ridiculously easy graphical interfaces...
Look ma, no mouse.
Offline
I cannot even chroot into the thing although I can mount it just fine.
# chroot /newarch /bin/bash
chroot: failed to run command ‘/bin/bash’: Input/output error
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
It may be worth checking disk UUIDs and fstab to make sure that they haven't gotten screwed up.
Ryzen 5900X 12 core/24 thread - RTX 3090 FE 24 Gb, Asus Prime B450 Plus, 32Gb Corsair DDR4, Cooler Master N300 chassis, 5 HD (1 NvME PCI, 4SSD) + 1 x optical.
Linux user #545703
Offline
Not using UUIDs with this... /dev/sdaX and they are fine. Ran e2fsck -v -f /dev/sda[1,3] and found nothing. Confused
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
graysky,
This occurred on my i686 virtualbox after preforming the latest update which included some systemd stuff. I haven't moved the vbox over to systemd yet however.
I am sorry, I lost the bubble in reading the thread. You are running in a virtual machine. What is the host? I could not tell if it was Linux, or a toy OS.
Have you tried the image on a different host?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
I am sorry, I lost the bubble in reading the thread. You are running in a virtual machine. What is the host? I could not tell if it was Linux, or a toy OS.
Have you tried the image on a different host?
Ah, sorry, I never stated:
Host OS: Arch x86_64
Guest OS: Arch i686
To your 2nd question, no. Only Arch x86_64.
I am beginning to think that my hdd image is corrupted somehow but running e2fsck on both the guest and host media revealed nothing.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
This has to be a virtualbox bug. I made a new vdi hardrive image. Copied over my old image's /boot and / partitions (via tar files) and got the same error when I tried to choot into the /newarch
# chroot failed to run command /bin/bash: Input.output error
WTF?
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
...finally gave up and restored a 2-week old backup of the image. Quick pacman -Syu and I'm back up again. Sure would like to know what happened.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline