Re: [arch-general] Kernel panic - after upgrade
2015-01-18 15:27 GMT+01:00 Savya <mailinglists@hawkradius.com>:
On Sun, Jan 18, 2015, at 11:22 PM, Csányi Pál wrote:
I upgrade today my Arch linux desktop. Later when I did a reboot, on the screen I can to read followings:
Failed to execute /init )error -2) Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
I upgraded my system with yaourt-gui.
What can I do to get mz Arch linux desktop back?
I'm not completely sure, but I think you might try to pass the init=/usr/bin/systemd option to the kernel. Just edit the corresponding line in the bootloader and add this line to the end. In the long run, maybe you need to add the systemd hook to your initramfs?
I'm not completely sure about this solution, so just check it out.
I did so but get another error: Failed to execute /init (error -2) Failed to execute /usr/bin/systemd (error -2). Attempting defaults... -- Regards from Pal
2015-01-18 15:39 GMT+01:00 Csányi Pál <csanyipal@gmail.com>:
2015-01-18 15:27 GMT+01:00 Savya <mailinglists@hawkradius.com>:
On Sun, Jan 18, 2015, at 11:22 PM, Csányi Pál wrote:
I upgrade today my Arch linux desktop. Later when I did a reboot, on the screen I can to read followings:
Failed to execute /init )error -2) Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/init.txt for guidance.
I upgraded my system with yaourt-gui.
What can I do to get mz Arch linux desktop back?
I'm not completely sure, but I think you might try to pass the init=/usr/bin/systemd option to the kernel. Just edit the corresponding line in the bootloader and add this line to the end. In the long run, maybe you need to add the systemd hook to your initramfs?
I'm not completely sure about this solution, so just check it out.
I did so but get another error: Failed to execute /init (error -2) Failed to execute /usr/bin/systemd (error -2). Attempting defaults...
I even tried with option: init=/usr/bin/init but that failed too. -- Regards from Pal
Csányi Pál wrote in message <CAONhAovzSgs87pFfp1G0NiK_=u-Y-FTKWB6-8+Mq1dMzKxLATQ@mail.gmail.com>:
I did so but get another error: Failed to execute /init (error -2)
You don't seem to have a valid /usr/bin/init anymore, try booting on an usb key and see what happened to it.
Failed to execute /usr/bin/systemd (error -2). Attempting defaults...
It should be init=/usr/lib/systemd/systemd /usr/bin/systemd does not exist.
2015-01-18 16:06 GMT+01:00 Damien Robert <damien.olivier.robert+gmane@gmail.com>:
Csányi Pál wrote in message <CAONhAovzSgs87pFfp1G0NiK_=u-Y-FTKWB6-8+Mq1dMzKxLATQ@mail.gmail.com>:
I did so but get another error: Failed to execute /init (error -2)
You don't seem to have a valid /usr/bin/init anymore, try booting on an usb key and see what happened to it.
Failed to execute /usr/bin/systemd (error -2). Attempting defaults...
It should be init=/usr/lib/systemd/systemd /usr/bin/systemd does not exist.
I booted with a systemrescuecd and want to repaire my Arch linux system. How can I do that? -- Regards from Pal
On 2015.01.18 17:12, Csányi Pál wrote:
2015-01-18 16:06 GMT+01:00 Damien Robert <damien.olivier.robert+gmane@gmail.com>:
Csányi Pál wrote in message <CAONhAovzSgs87pFfp1G0NiK_=u-Y-FTKWB6-8+Mq1dMzKxLATQ@mail.gmail.com>:
I did so but get another error: Failed to execute /init (error -2)
You don't seem to have a valid /usr/bin/init anymore, try booting on an usb key and see what happened to it.
Failed to execute /usr/bin/systemd (error -2). Attempting defaults...
It should be init=/usr/lib/systemd/systemd /usr/bin/systemd does not exist.
I booted with a systemrescuecd and want to repaire my Arch linux system.
How can I do that?
Maybe try reinstalling the whole base package group? -- Thanks, Giedrius
2015-01-18 16:19 GMT+01:00 Giedrius Statkevičius <giedrius.statkevicius@gmail.com>:
On 2015.01.18 17:12, Csányi Pál wrote:
2015-01-18 16:06 GMT+01:00 Damien Robert <damien.olivier.robert+gmane@gmail.com>:
Csányi Pál wrote in message <CAONhAovzSgs87pFfp1G0NiK_=u-Y-FTKWB6-8+Mq1dMzKxLATQ@mail.gmail.com>:
I did so but get another error: Failed to execute /init (error -2)
You don't seem to have a valid /usr/bin/init anymore, try booting on an usb key and see what happened to it.
Failed to execute /usr/bin/systemd (error -2). Attempting defaults...
It should be init=/usr/lib/systemd/systemd /usr/bin/systemd does not exist.
I booted with a systemrescuecd and want to repaire my Arch linux system.
How can I do that?
Maybe try reinstalling the whole base package group?
I think I must to chroot into my Arch linux system. How can I do that? -- Regards from Pal
On January 18, 2015 4:23:45 PM CET, "Csányi Pál" <csanyipal@gmail.com> wrote:
I think I must to chroot into my Arch linux system. How can I do that? Just mount your rootfs to /mnt and boot to /mnt/boot and `sudo chroot /mnt', it should be available on your rescue cd. Or if on the arch install media, substitute arch-chroot for chroot, and use the root user instead of sudo. --Oliver Temlin
On Sun, 18 Jan 2015 16:30:12 +0100, Oliver Temlin wrote:
Just mount your rootfs to /mnt and boot to /mnt/boot and `sudo chroot /mnt', it should be available on your rescue cd.
Assumed the rescue CD should come with systemd, instead of chroot you could use systemd-nspawn. Mount the rootfs and then run sudo systemd-nspawn -D /mount/point
2015-01-18 17:02 GMT+01:00 Ralf Mardorf <ralf.mardorf@rocketmail.com>:
On Sun, 18 Jan 2015 16:30:12 +0100, Oliver Temlin wrote:
Just mount your rootfs to /mnt and boot to /mnt/boot and `sudo chroot /mnt', it should be available on your rescue cd.
Assumed the rescue CD should come with systemd, instead of chroot you could use systemd-nspawn.
Mount the rootfs and then run
sudo systemd-nspawn -D /mount/point
What I did sofar is the following: Boot with Arch linux live cd. lsblk Note: my root / partition is on /dev/sda3 mkdir /mnt/arch mount /dev/sda3 /mnt/arch systemd-nspawn -D /mnt/arch mkinitcpio -p linux Here I exit from the prompt and reboot the machine, but get the same error message: can't run init. What did I wrong? -- Regards from Pal
On January 18, 2015 5:49:37 PM CET, "Csányi Pál" <csanyipal@gmail.com> wrote:
What I did sofar is the following:
Boot with Arch linux live cd. lsblk Note: my root / partition is on /dev/sda3 mkdir /mnt/arch mount /dev/sda3 /mnt/arch systemd-nspawn -D /mnt/arch mkinitcpio -p linux
Here I exit from the prompt and reboot the machine, but get the same error message: can't run init.
What did I wrong?
You missed that the base group should be reinstalled, as the error is not with the ramdisk, but with the files of systemd. Just run `pacman -S base' after systemd-nspawn. --Oliver Temlin
On Sun, Jan 18, 2015 at 10:57 AM, Oliver Temlin <temlin@gmail.com> wrote:
On January 18, 2015 5:49:37 PM CET, "Csányi Pál" <csanyipal@gmail.com> wrote:
mkinitcpio -p linux
You missed that the base group should be reinstalled, as the error is not with the ramdisk, but with the files of systemd. Just run `pacman -S base' after systemd-nspawn.
To try and help you out I ran a listing of what's in the normal (default options) initramfs. The only change I make is to add lvm2, everything else is out of the box. http://pastebin.com/hGT6jSN4 $ egrep -v "^(#|$)" /etc/mkinitcpio.conf MODULES="" BINARIES="" FILES="" HOOKS="base udev autodetect modconf block lvm2 filesystems keyboard fsck" The output in the pastebin shows: /sbin/init -> /usr/bin/init -> /usr/bin/busybox hth, -te
On Sun, 18 Jan 2015 11:03:59 -0600, Troy Engel wrote:
HOOKS="base udev autodetect modconf block lvm2 filesystems keyboard fsck"
HOOKS="base udev autodetect modconf block filesystems keyboard vboxhost" I removed fsck ;). Use mkinitcpio fsck hook and rw on the kernel commandline or don't use the hook and ro on the kernel commandline.
On Sun, Jan 18, 2015 at 11:35 AM, Ralf Mardorf <ralf.mardorf@rocketmail.com> wrote:
HOOKS="base udev autodetect modconf block filesystems keyboard vboxhost"
I removed fsck ;). Use mkinitcpio fsck hook and rw on the kernel commandline or don't use the hook and ro on the kernel commandline.
I think you missed the point where we're trying to help someone with what the defaults are and things should look like to try and help him save his system from disaster. $ tar -JxOf /var/cache/pacman/pkg/mkinitcpio-18-2-any.pkg.tar.xz etc/mkinitcpio.conf | grep ^HOOKS HOOKS="base udev autodetect modconf block filesystems keyboard fsck" Right now he's in a bad way, let's not get off into the weeds; e.g. you have virtualbox so you'd just screw him up more if he tried to use your HOOKS line. -te
2015-01-18 17:57 GMT+01:00 Oliver Temlin <temlin@gmail.com>:
On January 18, 2015 5:49:37 PM CET, "Csányi Pál" <csanyipal@gmail.com> wrote:
What I did sofar is the following:
Boot with Arch linux live cd. lsblk Note: my root / partition is on /dev/sda3 mkdir /mnt/arch mount /dev/sda3 /mnt/arch systemd-nspawn -D /mnt/arch mkinitcpio -p linux
Here I exit from the prompt and reboot the machine, but get the same error message: can't run init.
What did I wrong?
You missed that the base group should be reinstalled, as the error is not with the ramdisk, but with the files of systemd. Just run `pacman -S base' after systemd-nspawn.
Well, I did so but can't to run successfully the `pacman -S base' command because of some difficulties. It complains about existing files and folder: it won't overwrite the /usr/lib64 folder. What can I do now? -- Regards from Pal
Here I exit from the prompt and reboot the machine, but get the same error message: can't run init.
What did I wrong?
You missed that the base group should be reinstalled, as the error is not with the ramdisk,
there's no /init outside of the ramdisk, so his problem seems to be in the initramfs, but probably because his base system is a bit borked and it mkinitcpio creates the initramfs out of it. Well, I did so but can't to run successfully the `pacman -S base'
command because of some difficulties. It complains about existing files and folder: it won't overwrite the /usr/lib64 folder.
post the exact errors you're getting -- damjan
El 18/1/2015 16:23, "Csányi Pál" <csanyipal@gmail.com> escribió:
2015-01-18 16:19 GMT+01:00 Giedrius Statkevičius <giedrius.statkevicius@gmail.com>:
On 2015.01.18 17:12, Csányi Pál wrote:
2015-01-18 16:06 GMT+01:00 Damien Robert <damien.olivier.robert+gmane@gmail.com>:
Csányi Pál wrote in message <CAONhAovzSgs87pFfp1G0NiK_=u-Y-FTKWB6-8+Mq1dMzKxLATQ@mail.gmail.com>:
I did so but get another error: Failed to execute /init (error -2)
You don't seem to have a valid /usr/bin/init anymore, try booting on
an usb
key and see what happened to it.
Failed to execute /usr/bin/systemd (error -2). Attempting defaults...
It should be init=/usr/lib/systemd/systemd /usr/bin/systemd does not exist.
I booted with a systemrescuecd and want to repaire my Arch linux system.
How can I do that?
Maybe try reinstalling the whole base package group?
I think I must to chroot into my Arch linux system. How can I do that?
-- Regards from Pal
You may boot with archlinux ISO. Then install pacstrap base and base-devel
participants (8)
-
Csányi Pál
-
Damien Robert
-
Damjan Georgievski
-
Giedrius Statkevičius
-
Maykel Franco
-
Oliver Temlin
-
Ralf Mardorf
-
Troy Engel