Sounds good 
looking for conflicting packages...
error: could not open file /mnt/var/lib/pacman/local/gcc-libs-13.2.1-5/desc: No such file or directory
warning: could not fully load metadata for package gcc-libs-13.2.1-5
error: failed to prepare transaction (invalid or corrupted package)
[manjaro ~]# ls /mnt/var/cache/pacman/pkg/linux*
/mnt/var/cache/pacman/pkg/linux510-5.10.197-1-x86_64.pkg.tar.zst
/mnt/var/cache/pacman/pkg/linux510-5.10.197-1-x86_64.pkg.tar.zst.sig
/mnt/var/cache/pacman/pkg/linux510-5.10.200-1-x86_64.pkg.tar.zst
/mnt/var/cache/pacman/pkg/linux510-5.10.200-1-x86_64.pkg.tar.zst.sig
/mnt/var/cache/pacman/pkg/linux510-5.10.205-1-x86_64.pkg.tar.zst
/mnt/var/cache/pacman/pkg/linux510-5.10.205-1-x86_64.pkg.tar.zst.sig
/mnt/var/cache/pacman/pkg/linux510-5.10.211-1-x86_64.pkg.tar.zst
/mnt/var/cache/pacman/pkg/linux510-5.10.211-1-x86_64.pkg.tar.zst.sig
/mnt/var/cache/pacman/pkg/linux61-6.1.55-1-x86_64.pkg.tar.zst
/mnt/var/cache/pacman/pkg/linux61-6.1.55-1-x86_64.pkg.tar.zst.sig
/mnt/var/cache/pacman/pkg/linux61-6.1.62-1-x86_64.pkg.tar.zst
/mnt/var/cache/pacman/pkg/linux61-6.1.62-1-x86_64.pkg.tar.zst.sig
/mnt/var/cache/pacman/pkg/linux61-6.1.69-1-x86_64.pkg.tar.zst
/mnt/var/cache/pacman/pkg/linux61-6.1.69-1-x86_64.pkg.tar.zst.sig
/mnt/var/cache/pacman/pkg/linux61-6.1.80-1-x86_64.pkg.tar.zst
/mnt/var/cache/pacman/pkg/linux61-6.1.80-1-x86_64.pkg.tar.zst.sig
/mnt/var/cache/pacman/pkg/linux63-rt-6.3.1_rt13-1-x86_64.pkg.tar.zst
/mnt/var/cache/pacman/pkg/linux63-rt-6.3.1_rt13-1-x86_64.pkg.tar.zst.sig
/mnt/var/cache/pacman/pkg/linux63-rt-virtualbox-host-modules-7.0.8-2-x86_64pkg.tar.zst
/mnt/var/cache/pacman/pkg/linux63-rt-virtualbox-host-modules-7.0.8-2-x86_64.pkg.tar.zst.sig
so should I add linux63 to the pacman -r /mnt ⌠command?
Should recreate those with --dbonly, but cba to test if it works.
Just create those manually
touch /mnt/var/lib/pacman/local/$pkgname-$pkgver-$pkgrel/{desc,files,mtree}
and replace vars accordingly.
That doesnât exist for a year probably. Leave it as is. 6.1 and 6.6.
touch /mnt/var/lib/pacman/local/gcc-libs-13.2.1-5/{desc,files,mtree}
did not result in any answer from the terminal
I donât unterstand the --dbonly cba part of your answer
Yeah forget about that. Rerun update.
Update ended with error:
(1437/1437) checking for file conflicts
error: failed to commit transaction (conflicting files)
followed bei endless lines like
linux-api-headers: /mnt/usr/include/amd-generic/auxvec.h exists in filesystem
The start terms are
last line is:
Errors occured, no packages were upgraded
The correct chroot command is sudo manjaro-chroot -a
Eh. Add --overwrite="*" to the end of the command.
worked now and finished without errors.
now try manjaro-chroot -a again?
Now try booting into it.
Error remains
Fehler: Datei "/boot/vmlinuz-6.1-x86:64" nicht gefunden.
Fehler: Sie mĂźssen zuerst den Kernel laden.
Beliebige Taste drĂźcken, um fortzusetzen
That doesnât make sense but ok. Try chrooting now then and reinstall kernels again.
chroot -a worked
How to reinstall kernels?
is it
sudo mhwd-kernel --install linux61
?
Are you joking? Why would you install Manjaro on someone elses PC if you donât know even basic commands?
sudo pacman -Syu linux66{,-headers} linux61{,-headers}
Please post output of it.
Why i installed it on someone elses PC: Because she wanted to get away from Windows and I for myself never had any problems using Linux. The user experience for me was just good, never had to have any knowledge, so we thought, it could work. Maybe a false cue.
[manjaro /]# sudo pacman -Syu linux66{,-headers} linux61{,-headers}
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
warning: linux66-6.6.19-1 is up to date -- reinstalling
warning: linux61-6.1.80-1 is up to date -- reinstalling
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
Packages (5) pahole-1:1.26-1 linux61-6.1.80-1 linux61-headers-6.1.80-1
linux66-6.6.19-1 linux66-headers-6.6.19-1
Total Download Size: 52.04 MiB
Total Installed Size: 544.32 MiB
Net Upgrade Size: 265.54 MiB
:: Proceed with installation? [Y/n] Y
Proceed?
I did Proceed, as you told me to reinstall the kernels - so makes sense to reinstall them
Did work without any further errors and now I can boot again!
Thank you very much for your intense help!!!
And sorry for being such a noob 
It doesnât affect me. Itâs you who will have problems if you donât know how to maintain your system. There is a lot more to it than just pressing update button. 
it does affect you as you spend your free time with my problems - Thank you!
Maybe open source OS is not yet appropriate for everyone.
On the other hand, she switched from Windows, as windows update killed her PC
Itâs not that itâs open source (Itâs not even that as a whole), itâs that itâs rolling distro. You have to at least read Announcements threads, etc. Anyway, good luck.