You are not logged in.
Today I upgraded the kernel from 4.0.1 to 4.0.4, once I rebooted, there was a filesystem corruption.
I used fsck, to fix it and once I rebooted it failed to load udev Device Manager or something.
I started to look in the forums and appears to be a problem with RAID0 setups, and mine is exactly that.
So, I tried to downgrade to 4.0.1 but I'm currently having problems doing so. What I did was:
I booted with a USB, mounted the partition and arch-chroot.
But once I use pacman -Uv /var/cache/pacman/pkg/linux-4.0.1-1-x86_64.pkg.tar.xz to downgrade the kernel
pacman starts by saying: could not open file /var/lib/pacman/local/<some pkgs> ... I canceld the downgrade and
tried to ls the location and I got a weird error, that looked like a FS corruption, I ran again fsck and it started to fix errors on those exact locations.
I tried the downgrade again, and the same errors still show up. I tried to ls the location again and no FS error this time. So I decided to ignore them and continued to downgrade the kernel.
Once I continue, it shows a bunch of times while the Image is being built an error saying awk: error while loading shared libraries: /usr/lib/libgmp.so.10: invalid ELF header
Now If I reboot there is not even a kernel panic, not even the keyboard works xD Need some help ![]()
Last edited by Tenza (2015-05-23 23:34:48)
Offline
Offline
@karol thank you, unfortunately for some of us the news was a bit late, the damage was already done.
Ok, so I saw that some people were able to fix their systems by reinstalling every package with pacman -Qnq | pacman -S --force but some still have some resonating problems.
Since I have a dated full partition clone in an external disk, instead, I'm going to backup my configs and pacman.log, and then restore the system and manually reinstall any renaming packages on pacman.log
Offline