Can't boot and failed to repair while arch-chroot

So, I did update as usual with yay, and in the middle of the update the GUI (Plasma) went off, and I was left with the terminal only on black screen. The update was really slow, not because of the internet speed, but AFTER having downloaded the packages, the installation was slow,
Eventually, if ended but with some error messages. (I did not wrote them down).
I performed a new yay update at the end, but got a “failed to synchronize all databases (no server configured for repository)” message.
So I checked my /etc/pacman.d/mirrorlist AND endeavouros-mirrorlist, both were fine.

I rebooted from the terminal…. and then, got stuk with a “UTMP system failed” at the boot. (after opening my luks partition).USB, I did chroot, opened the luks… try to update but again, same message : failed to synchronize all databases…..

I also try to perform a kernel-install (I am with Systemd boot) but it failed.
Any idea before I reinstall everything ??? :neutral_face:

Go back into the arch-chroot. Be sure to mount your EFI partition at /efi and then run sudo reinstall-kernels

If you get an error when you run that, please the exact error here.

Thanks Dalto. The boot is mounted at EFI. I get this error for every kernel (arch, lts and zen) : depmod: ERROR: Could not create index ‘modules.dep’. Output is truncated: No space left on device

The EFI partition is used only at 29%
But now, running lsblk, I see that my data partition is full at….. 99% !!!

Can it be the issue ? I can try to remove soem data with ch-root…

Yes, that is probably the issue. Try cleaning up your package cache.

After that though you will need to finish the update and if it doesn’t do it automatically, you will need to run reinstall-kernels

Does endeavour not doing this by it self in some amount of time ?

No, we would have no way of knowing which files you want deleted.

I mean the downloaded/cached files from yay/pacman. If you update it holds a few older versions but i thought these get removed after a few weeks.

You have to enable it yourself. It can be done via the eos-welcome tool also.

Yes, exactly, that is also what I was referring to. Everyone has a different preference here. Some people want to keep them forever, others what a certain number of versions others want to purge packages they no longer have installed. It is all personal preference.

There is a timer you can enable paccache.timer to clean it up if you want to. That is provided by upstream Arch.

Yes and i think i did use it after the installations on my machines since i see only a few packages per app. Thought this was set auto in endeavour.

OK, now a stupid question (I know.. .there is no such things). I can enter my home directory with cd home , but then I can’t see anything. ls returns… nothing. What am I doing wrong ?
Maybe I need to go to “mnt/home” ? but the second time I use ls from the root directory… again, it does not return anything.

Do you actually use cd home or cd /home ? Sorry read this wrong. But try it with a live ISO, you might be able to reach it.

cd /home didn’t change the directory. cd home did, but then once in home, ls does not returns anything

Going to sleep now…. will check back in the morning (here)….Thanks

Could not sleep… (Adrenaline). I resolve the issue. @dalto was right, it was a space issue. And I could enter my home directory after mounting arch-root…. the right way (I had mounted @ but not @home !!). After booting in my system I could update it and reinstall the kernels.

Only issue is that I got twice the same kernel… (so 4 entries per kernel, with the fallbacks.) But I managed to delete the duplicate entries and now all good. Going to bed, this time. Thanks again.