You are not logged in.

#1 2018-09-13 17:31:26

black-clover
Member
Registered: 2018-05-29
Posts: 6

Kernel panic after upgrade

Hello,

I upgraded my system yesterday and after rebooting I get a kernel panic message: not syncing: VFS.
If I boot with the fallback option, it says libjson.c.so.4 is missing.

How can I fix this?

Offline

#2 2018-09-13 17:59:04

levi
Moderator
From: UK
Registered: 2018-06-16
Posts: 201

Re: Kernel panic after upgrade

Do these symptoms also happen with boot from cold?  A quick bit of internet-search-fu suggests it's possible to get this if your last kernel upgrade ran out of space on your boot partition, although usually pacman's checks should stop that happening to you I'd hope.  What partitions have you set up and how full are they?

Offline

#3 2018-09-13 22:41:59

black-clover
Member
Registered: 2018-05-29
Posts: 6

Re: Kernel panic after upgrade

The partition is only 25% full.
Yes. I tried several boots cold, also 2 different kernels and the fallback.
I also copied libjson.c.so.4 manually from another partition to /usr/lib.

Offline

#4 2018-09-14 01:31:15

levi
Moderator
From: UK
Registered: 2018-06-16
Posts: 201

Re: Kernel panic after upgrade

Okay, that's ruled out.  The next thing I'd try is rebuilding your initramfs using mkinitcpio.  There are guides out there.

Offline

#5 2018-09-14 01:41:41

black-clover
Member
Registered: 2018-05-29
Posts: 6

Re: Kernel panic after upgrade

I cannot boot into the system.
Could I rebuild intramfs chrooting into arch?

Offline

#6 2018-09-14 02:16:52

levi
Moderator
From: UK
Registered: 2018-06-16
Posts: 201

Re: Kernel panic after upgrade

Yes, that's how you first get an initramfs when you're installing arch for the first time.

Offline

#7 2018-09-14 05:22:39

black-clover
Member
Registered: 2018-05-29
Posts: 6

Re: Kernel panic after upgrade

I tried to chroot into arch (from debian on another partition) and run mkinitcpio but get error: ==> ERROR: /proc must be mounted!
Is there a way to obviate error or mount /proc from the running system?

Offline

#8 2018-09-14 05:54:13

andreas_baumann
Administrator
From: Zurich, Switzerland
Registered: 2017-08-10
Posts: 568
Website

Re: Kernel panic after upgrade

mount /proc inside the chroot (that's what arch-chroot is doing, but on non-Arch you don't have arch-chroot).

mount -t proc proc /proc

You can also try to run arch-chroot on a non-arch system, it's standard bash in the end..

Online

#9 2018-09-14 13:27:26

levi
Moderator
From: UK
Registered: 2018-06-16
Posts: 201

Re: Kernel panic after upgrade

But can you get archchroot from anywhere other than an arch install iso?  I guess it might be in a package, but that's not in the base or base-devel set on a running system.  And especially if you've only got a debian install running, what's the simplest way to get it?

Offline

#10 2018-09-14 21:34:51

black-clover
Member
Registered: 2018-05-29
Posts: 6

Re: Kernel panic after upgrade

Hi,

I've booted from the install iso, arch-chrooted into arch and tried to rebuild initramfs in several ways.
I always got some sort of errors.
Eventually, I found it easier to just backup my files on a USB and reinstall it.

Lesson learned is to be more careful when I upgrade the system.
Sometimes I get error warnings about some packages whose signature is invalid or which seem corrupted.
I assume this has to be expected, since it must be hard to keep up with arch development even in the arch 32 stable repo.
Great distro anyway and an amazing job keeping it going.
Thanks for the help.

Cheers.

Offline

#11 2018-09-15 19:47:21

levi
Moderator
From: UK
Registered: 2018-06-16
Posts: 201

Re: Kernel panic after upgrade

There was a thing around a year ago where we had to update some keys, but that was very much new distro blues with that timing I suspect.  In normal running, I've not had any signature errors, and certainly nothing indicating corruption (just things being signed with keys it doesn't know about yet, in the absolute worst case).

Offline

Board footer

Powered by FluxBB