Messed my system with uname different from actual version of linux

Lilith · 2013-07-28 13:54:18

Hi guys,

some days ago i'm running into problems with my system because my netbook (asus 1215b) doesn't work properly.

So i check the log and found that i have a different version from uname command and the kernel installed. So i downgraded the kernel by my cache of pacman and now when i boot from arch i receive:

systemd-fsck[204]: unexpected inconsistency; run fsck manually // (tried without results)
Welcome to emergency mode! After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to booy into default mode.
Give root password for maintenance
or type Control-D to continue):

If i put my root password i grant the root access but i don't know what i can do, so i'm here!

I hope someone is able to help me, thanks guys.

Last edited by Lilith (2013-07-28 13:55:46)

cfr · 2013-07-28 15:13:27

What were the installed version and the uname version? There was an issue recently with 3.10.2 which might have caused this issue. If so, updating the system should fix the issue as that will get you 3.10.3 which seems not to have the problem.

If not, I would start with journalctl -xb.

falconindy · 2013-07-28 16:30:51

cfr wrote:

There was an issue recently with 3.10.2 which might have caused this issue.

I sincerely doubt this. OP's problem is nothing new, and is always caused by the /boot partition not being mounted for kernel upgrades, or a failure to copy the new kernel and initramfs to the EFI system partition before rebooting.

Lilith · 2013-07-28 16:52:16

cfr wrote:

What were the installed version and the uname version? There was an issue recently with 3.10.2 which might have caused this issue. If so, updating the system should fix the issue as that will get you 3.10.3 which seems not to have the problem.
If not, I would start with journalctl -xb.

I believe 3.10.2 for uname and 3.10.3 for the kernel so i downgraded the kernel to have the same version and later i'll updated everything but it is fucked before i can do this.
I understand my problem (i think) but now how i can repair this issue?

I tried but i receive other several errors and later i return to the same point from where i boot.

cfr · 2013-07-28 19:54:13

falconindy was right, then. (falconindy is, as somebody recently pointed out, always right.)

What do you mean by saying it is messed up before you can do "this"? You mean you downgraded the kernel (as you said in your original post) and meant to update everything later but somehow cannot? Why?

I tried but i receive other several errors and later i return to the same point from where i boot.

What did you try? What errors did you get? Which point?

EDIT: You should be able to recover using a live media. Boot into the live environment, mount your partitions (especially your boot partition), configure the network, arch-chroot and redo pacman -Syu. See the wiki for more details.

Last edited by cfr (2013-07-28 19:56:29)

Trilby · 2013-07-28 20:03:09

Uname gives the running kernel. Had you rebooted since you upgraded. It is perfectly normal and expected for uname to be one version behind the installed kernel if you don't reboot regularly.

If such a case is the cause of problems, downgrading certainly shouldn't be the first step in solving the problems.

Last edited by Trilby (2013-07-28 20:04:07)

ewaller · 2013-07-28 21:03:21

In my opinion, you are fighting two problems. One is the kernel/modules mismatch. I would not expect that to cause the volume corruption. The first task is to boot from something else and fix the corrupted volume. Once fsck likes it again, then work on the kernel/modules mismatch.

https://wiki.archlinux.org/index.php/Fsck

Lilith · 2013-07-30 10:39:12

Hi guys,

sorry for the late. I fixed everything by entering in live usb like someone suggested me, chroot and pacman -Syu!

@cfr i tried "journalctl -xb" and received several errors. I returned from where i start before do "journalctl -xb" with that.
You right Trilby, now i have understand.
Yes ewaller i'll do certainly! Anyway i start this zoo because i saw on the log (/var/log/catalyst-install.log):

--------
2013-07-29 04:51:01
Building fglrx module for 3.10.3-1-ARCH kernel ...
--------
Kernel header files are absent: directory /usr/lib/modules/3.10.3-1-ARCH/build doesn't exist! Game over

--------

My bad!
Thanks for the help as always guys

cfr · 2013-07-30 23:16:40

Well, does it exist?

Arch Linux

#1 2013-07-28 13:54:18

Messed my system with uname different from actual version of linux

#2 2013-07-28 15:13:27

Re: Messed my system with uname different from actual version of linux

#3 2013-07-28 16:30:51

Re: Messed my system with uname different from actual version of linux

#4 2013-07-28 16:52:16

Re: Messed my system with uname different from actual version of linux

#5 2013-07-28 19:54:13

Re: Messed my system with uname different from actual version of linux

#6 2013-07-28 20:03:09

Re: Messed my system with uname different from actual version of linux

#7 2013-07-28 21:03:21

Re: Messed my system with uname different from actual version of linux

#8 2013-07-30 10:39:12

Re: Messed my system with uname different from actual version of linux

#9 2013-07-30 23:16:40

Re: Messed my system with uname different from actual version of linux

Board footer