No kernel for booting after 2020-04-18 update

[Furby]

OK. First command works. Second command asks for this:

[manjaro-lxqt mkinitcpio.d]# downgrade linux54

Downgrading from A.L.A. is disabled on the stable branch. To override this behavior, set DOWNGRADE_FROM_ALA to 1 .
See https://wiki.manjaro.org/index.php?title=Using_Downgrade  for more details.

Available packages:

-  1)  linux54    5.4.24  1  x86_64  (local)
-  2)  linux54    5.4.27  1  x86_64  (local)
-  3)  linux54    5.4.28  1  x86_64  (local)
-  4)  linux54    5.4.30  1  x86_64  (local)
-  5)  linux54    5.4.31  1  x86_64  (local)
+  6)  linux54    5.4.33  1  x86_64  (local)

select a package by number: 6
loading packages...
warning: linux54-5.4.33-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
error: could not open file /var/lib/pacman/local/linux54-5.4.33-1/desc: No such file or directory
warning: could not fully load metadata for package linux54-5.4.33-1
error: failed to prepare transaction (invalid or corrupted package)

... and i tried it again downgrading to an even older kernel (with the same error message):

[manjaro-lxqt mkinitcpio.d]# downgrade linux54

Downgrading from A.L.A. is disabled on the stable branch. To override this behavior, set DOWNGRADE_FROM_ALA to 1 .
See https://wiki.manjaro.org/index.php?title=Using_Downgrade  for more details.

Available packages:

-  1)  linux54    5.4.24  1  x86_64  (local)
-  2)  linux54    5.4.27  1  x86_64  (local)
-  3)  linux54    5.4.28  1  x86_64  (local)
-  4)  linux54    5.4.30  1  x86_64  (local)
-  5)  linux54    5.4.31  1  x86_64  (local)
+  6)  linux54    5.4.33  1  x86_64  (local)

select a package by number: 5
loading packages...
warning: downgrading package linux54 (5.4.33-1 => 5.4.31-1)
resolving dependencies...
looking for conflicting packages...
error: could not open file /var/lib/pacman/local/linux54-5.4.33-1/desc: No such file or directory
warning: could not fully load metadata for package linux54-5.4.33-1
error: failed to prepare transaction (invalid or corrupted package)

[stephane]

we try

pacman -U linux54-5.4.34-1-x86_64.pkg.tar.zst 
pacman -U linux54-headers-5.4.34-1-x86_64.pkg.tar.zst

[Furby]

[manjaro-lxqt mkinitcpio.d]# pacman -U linux54-5.4.34-1-x86_64.pkg.tar.zst
loading packages...
error: 'linux54-5.4.34-1-x86_64.pkg.tar.zst': could not find or read package
[manjaro-lxqt mkinitcpio.d]# pacman -U linux54-headers-5.4.34-1-x86_64.pkg.tar.zst
loading packages...
error: 'linux54-headers-5.4.34-1-x86_64.pkg.tar.zst': could not find or read package

Do i have to download these packages manually first?

[stephane]

which branch are you using ?
stable or stable-staging or testing or unstable ?

[Furby]

i think it's "stable", but i am not sure. How can i confirm that?

[stephane]

do this

pacman -Syy
pacman -S pacman-static
pacman-static -Syyu

[Furby]

First two commands do what they should do. The third says:

[manjaro-lxqt etc]# pacman-static -Syyu
warning: config file /etc/pacman.conf, line 20: directive 'SyncFirst' in section 'options' not recognized.
:: Synchronizing package databases...
 core                                                                                                                171.9 KiB  1563 KiB/s 00:00 [########################################################################################] 100%
 extra                                                                                                              2015.7 KiB  1800 KiB/s 00:01 [########################################################################################] 100%
 community                                                                                                             5.9 MiB  1754 KiB/s 00:03 [########################################################################################] 100%
 multilib                                                                                                            194.5 KiB  1945 KiB/s 00:00 [########################################################################################] 100%
:: Starting full system upgrade...
error: could not open file /var/lib/pacman/local/linux54-5.4.33-1/desc: No such file or directory
resolving dependencies...
looking for conflicting packages...
warning: could not fully load metadata for package linux54-5.4.33-1
error: failed to prepare transaction (invalid or corrupted package)

[stephane]

let try this

nano /var/lib/pacman/local/linux54-5.4.33-1/desc
save ( create a file with 0 )

touch /var/lib/pacman/local/linux54-5.4.33-1/desc

see

error: could not open file /var/lib/pacman/local/.../{desc,files,mtree}: No such file or directory

Your local package database and/or metadata may become corrupted if an update process is interrupted, for example if you hard power off during an update. Metadata corruption will generally manifest in a message similar to: error: could not open file /var/lib/pacman/local/$pkgname-$pkgver-$pkgrel/desc: No such file or directory error: could not open file /var/lib/pacman/local/$pkgname-$pkgver-$pkgrel/files: No such file or directory error: could not open file /var/lib/pacman/local/$pkgname-$pkg…

[Furby]

This looks very good. After creating the file with the "touch" command, the "pacman-static -Syyu" command works an downloads many packages, including the kernel. I hope, this will work...

[stephane]

waiting end result

if ok , add linux56

mhwd-kernel -i linux56 
exit 

if not ok
return message errors

exit

[Furby]

Sorry for the late response. The update went trough, but then the boot process was scrambled. After some repairs on grub, my system started, but then the filesystem was buggy and i never had so much decisions for "repairs" to do . Then there were conflicts with my nextcloud synchronisation, but i think, i now have a stable, working and somehow "repaired" system again.

Thanks very, very much for your help.

Your last recommendation would install the 5.6 kernel on my system, right? I would rather stay at the stable 5.4 LTS kernel.

[stephane]

you can have more kernels , if trouble with one you can change
( press Esc on grub menu and select list detail )

[Furby]

Thats true, but my harddrive is so small, i rather use the small space for my files than for different kernels . My old Netbook doesn't take bigger M.2 drives than 128 GB

[freggel.doe]

@FadeMind

Use MHWD-CHROOT instead.

@Furby

When i try to install it, i get the following error-message: This is german and means, that the package "mhwd-chroot" can't be found in the repositories

Saw this discussion the other day, apparently it's already been dropped:

mhwd-chroot package - is it maintained or obsolete?

From a very recent thread there was a reference to a - to me - unknown tool. I got curious and searched for it - nothing of the kind in AUR - but a ddg search found this topic from 2018 in #technical-issues-and-assistance:tutorials section I proceeded to search for mhwd-chroot-extended but couldn't find that either. We still have a package in community called mhwd-chroot 20180408-1 which provides an extensive root mount Snipped from the mhwd-chroot-shell script ... # mount proc, sys, dev…

[Furby]

Now, with the latest update 2020-04-26, i got an error that seems to be a followińg error from my problem in 2020-04-18. The update process want's to update the kernel but stops, because it finds already existing files:

.
.
.
(132/132) Lade Paket-Dateien                                                            [##################################################] 100%
(132/132) Prüfe auf Dateikonflikte                                                      [##################################################] 100%
Fehler: Konnte den Vorgang nicht durchführen (In Konflikt stehende Dateien)
linux54: /boot/linux54-x86_64.kver existiert im Dateisystem
linux54: /usr/lib/modules/extramodules-5.4-MANJARO/version existiert im Dateisystem
mesa-vdpau: /usr/lib/vdpau/libvdpau_nouveau.so existiert im Dateisystem
mesa-vdpau: /usr/lib/vdpau/libvdpau_nouveau.so.1 existiert im Dateisystem
mesa-vdpau: /usr/lib/vdpau/libvdpau_nouveau.so.1.0 existiert im Dateisystem
mesa-vdpau: /usr/lib/vdpau/libvdpau_nouveau.so.1.0.0 existiert im Dateisystem
mesa-vdpau: /usr/lib/vdpau/libvdpau_r300.so existiert im Dateisystem
mesa-vdpau: /usr/lib/vdpau/libvdpau_r300.so.1 existiert im Dateisystem
mesa-vdpau: /usr/lib/vdpau/libvdpau_r300.so.1.0 existiert im Dateisystem
mesa-vdpau: /usr/lib/vdpau/libvdpau_r300.so.1.0.0 existiert im Dateisystem
mesa-vdpau: /usr/lib/vdpau/libvdpau_r600.so existiert im Dateisystem
mesa-vdpau: /usr/lib/vdpau/libvdpau_r600.so.1 existiert im Dateisystem
mesa-vdpau: /usr/lib/vdpau/libvdpau_r600.so.1.0 existiert im Dateisystem
mesa-vdpau: /usr/lib/vdpau/libvdpau_r600.so.1.0.0 existiert im Dateisystem
mesa-vdpau: /usr/lib/vdpau/libvdpau_radeonsi.so existiert im Dateisystem
mesa-vdpau: /usr/lib/vdpau/libvdpau_radeonsi.so.1 existiert im Dateisystem
mesa-vdpau: /usr/lib/vdpau/libvdpau_radeonsi.so.1.0 existiert im Dateisystem
mesa-vdpau: /usr/lib/vdpau/libvdpau_radeonsi.so.1.0.0 existiert im Dateisystem
mesa-vdpau: /usr/share/licenses/mesa-vdpau/LICENSE existiert im Dateisystem
Fehler sind aufgetreten, keine Pakete wurden aktualisiert.

(the german "existiert im Dateisystems" means "already existing in filesystem")

May i simply delete the files so the update-process can go along or do i have to use a specific manjaro-tool to clean the files "lost" in the filesystem from my broken update-process in 2020-04-18?

[Furby]

This error sounded familiar to me, so i searched my own history. I had a similar situation in 2019 with the update 2018-12-31. Back then, the existing files coud be overwritten with the "--overwrite" switch from pacman. Back then, i knew the name of the package, but what is the name of the package now?

[linux-aarhus]

The same rule apply - it is on a file basis - not package.

--overwrite '*'

But since you have these issues frequently - you may consider changing habit of installing system wide files using sudo make install to using a PKGBUILD. Using a PKBBUILD will let pacman keep track of the files and you will avoid these issues on updates.

[Furby]

Thanks, linux-aarhus,

i tried "--overwrite *", but that didn't do the trick. Your hint did it! The update could be done and i think, i won't have trouble with the next kernel-update.

[freggel.doe]

@Furby

i tried "--overwrite *", but that didn't do the trick.

That's because that * is not escaped/quoted correctly and interpreted by your shell before it reaches pacman.