This message normally indicates that there is some corruption in the OSTree repository (this is the place where all operating system files and flatpak applications store their files).
Can you please run the following command:
sudo ostree fsck --all 2>&1 | tee -a ~/ostree-fsck.txt
and upload the resulting file (ostree-fsck.txt in your home directory). Additionally, please run a diagnostic (eos-diagnostics) and upload the generated file too.
It seems that your Harddrive has some errors on it:
avril 12 07:58:10 localhost systemd[1]: Starting File System Check on /dev/disk/by-uuid/d44e7b3e-e22d-4c4f-a472-aafa6704984a...
avril 12 07:58:10 localhost systemd-fsck[267]: ostree contains a file system with errors, check forced.
avril 12 07:58:12 localhost systemd-fsck[267]: ostree: Inodes that were part of a corrupted orphan linked list found.
avril 12 07:58:12 localhost systemd-fsck[267]: ostree: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
avril 12 07:58:12 localhost systemd-fsck[267]: (i.e., without -a or -p options)
avril 12 07:58:12 localhost systemd-fsck[265]: fsck failed with exit status 4.
avril 12 07:58:12 localhost systemd-fsck[265]: Ignoring error.
I would highly recommend you to first make a backup of all necessary data, then boot with a Live EOS USB and run:
It seems that the commit in question comes from an old application which isn’t even in the repositories anymore, so we need to find out on your side which application it is.
raphael@endless:~$ ostree log 13c0427271adb7a13d6a04bd7d3c41f466ed2cd6a2bb4685342c139a6ba5499e
error: No such metadata object 13c0427271adb7a13d6a04bd7d3c41f466ed2cd6a2bb4685342c139a6ba5499e.commit