[SOLVED] mismatched kernel and modules

pika · 2016-02-04 08:34:58

I've a problem with my T400 running arch. I forgot to `umount` before I reinstalled some `base` packages with `arch-chroot`. Now my btrfs root disk seems kinda broken. I boot with systemd emergency boot all the time. I dont know how this thread could help me nor why it is beeing marked as solved, it is not. Neither does this one. People beeing "excited" on it won't help. I dont wanna use quotas.

I also tried:

fsck -AR -y /dev/sda3
btrfs-check --repair /dev/sda3

cryptsetup luksOpen /dev/sda3 root
fsck -AR -y /dev/mapper/root
btrfs-check --repair /dev/mapper/root

Last edited by pika (2016-02-04 16:23:57)

WorMzy · 2016-02-04 09:13:26

It is marked as solved because the message is benign. It isn't the cause of your problem. As for what is the cause of your problem, we're going to need a lot more information about it. For a start, what messages are displayed when you are dropped to the emergency shell? Post the journal from a failed boot. Stop blindly running fsck and btrfs check.

pika · 2016-02-04 09:28:35

I had to use arch-chroot again because I uninstalled netctl and NetworkManager (still dont know if I can run both at the same time, as netctl is in base and wiki tells it is a bad idea to run 2 daemons at the same time). So I run journal -xb and skip to the END with G (there are like 1000 lines in -.-):

[...]
Failed to start Load Kernel Moduels
[...]
Failed to lookup alias tp_smapi
[...]
mount: unknown filesystem ext2
boot.mount: Mount process exited, code=exited status=32
Unit boot.mount has failed
[...]
BTRFS: could not find root 8
BTRFS: could not find root 8
systemd[1]: Started Create Volatile Files and Directories
[...]
emergency.service:Failed at step EXEC spawning /bin/plymouth: No such file or directory
[...]
Timed out waiting for device sys-subsystem-net-devices-wlp3s0.device
Kernel start-up required ... seconds
Userspace start-up required ... seconds

I dont think my problem is related to plymouth or wifi. The messages tell me, /boot partition can't even be mounted.

EDIT: short summary of red lines

Last edited by pika (2016-02-04 09:33:19)

WorMzy · 2016-02-04 10:32:38

Full logs would be better, but going off that handful of messages, I would venture a guess that the kernel you're booting doesn't match the modules installed on the rootfs. From the emergency shell, post the output of

uname -a
pacman -Q linux

pika · 2016-02-04 10:54:01

I wish I could post a full log, but your post won't tell me how. I can't type all the logs by hand. When I try to mount usb stick I get unknown filesystem vfat.

uname -a
Linux T400 4.3.3.3-3-ARCH #1 SMP PREEMPT Wed Jan 20 08:12:23 CET 2016 x86_64 GNU/Linux

pacman -Q linux
linux 4.4.1-2

WorMzy · 2016-02-04 11:06:59

You could gather the logs you need in the emergency environment, then boot the liveCD and use a pastebin client to upload them (that post mentions nopaste, but there are other ways)

My theory was correct though -- you are booting linux-4.3.3-3, but your rootfs has linux-4.4.1-2. Reboot into the live environment, mount all your partitions (including /boot), and reinstall the linux package.

pika · 2016-02-04 11:24:19

How could this happen? I only forgot to umount...

pacman -S linux?

WorMzy · 2016-02-04 11:37:54

I don't know what you mean by saying you forgot to umount. What were you umounting? Why did you need to umount it before reinstalling base packages? What specific consequences did you attribute to not umounting it? Why were you reinstalling base packages in the first place?

pika wrote:

pacman -S linux?

Yes.

pika · 2016-02-04 12:10:27

I uninstalled netctl so I couldn't connect to the net, so I installed `pacman -S base base-devel` again from arch-chroot, exit but forgot to umount -R /mnt. I dont know why I had 2 different versions of linux kernel. Is it wrong to install base packages again?

Anyway thanks alot! You got me running again! <3

Last edited by pika (2016-02-04 12:11:31)

WorMzy · 2016-02-04 14:09:29

You don't need to manually unmount your partitions when exiting from the LiveCD environment. If you don't unmount them, they will be unmounted during the reboot.

When you ran that pacman command in the chroot, was your /boot partition mounted? I suspect it wasn't, so the kernel and initrds were not updated. Please note that you have probably performed a partial update by only reinstalling (and in this case updating) base and base-devel. You should do a full system update to make sure everything is up-to-date.

EDIT: You should probably change your title to reflect what the problem really was -- mismatched kernel and modules.

Last edited by WorMzy (2016-02-04 14:13:49)

pika · 2016-02-04 16:23:43

You're right, I didn't mount the /boot partition then. Thanks for help, I changed the thread title.

Arch Linux

#1 2016-02-04 08:34:58

[SOLVED] mismatched kernel and modules

#2 2016-02-04 09:13:26

Re: [SOLVED] mismatched kernel and modules

#3 2016-02-04 09:28:35

Re: [SOLVED] mismatched kernel and modules

#4 2016-02-04 10:32:38

Re: [SOLVED] mismatched kernel and modules

#5 2016-02-04 10:54:01

Re: [SOLVED] mismatched kernel and modules

#6 2016-02-04 11:06:59

Re: [SOLVED] mismatched kernel and modules

#7 2016-02-04 11:24:19

Re: [SOLVED] mismatched kernel and modules

#8 2016-02-04 11:37:54

Re: [SOLVED] mismatched kernel and modules

#9 2016-02-04 12:10:27

Re: [SOLVED] mismatched kernel and modules

#10 2016-02-04 14:09:29

Re: [SOLVED] mismatched kernel and modules

#11 2016-02-04 16:23:43

Re: [SOLVED] mismatched kernel and modules

Board footer