I run my arch on gnome and was updating the system. The system froze during update, I tried waiting but nothing worked so I used the power button to turn it completely off. When I tried loging in it started giving me :- https://imagebin.ca/v/7zErQblLuBss

Now I went through guides online they said using Ctrl alt f2 etc but that didn't work. Other said to use live iso and use mount and chroot so went and did that, I couldn't do it at first and faced various problems but atlast I successfully did and one command updated the system.

mount /dev/nvme0n1p2/mnt
mount /dev/Nvme0n1p2 /mnt/boot
arch-chroot/mnt
Pacman -Syu

I was trying to use commands to mount and chroot but I couldn't go pass the second command, idk why after trouble shooting I used this command

pacstrap /mnt base linux linux-firmware

And it triggered an update and after the update I tried
Arch-chroot/mnt
And Pacman -Syu

And rebooted and the problem is still there

This is the picture commands I did after trying again
https://imagebin.ca/v/7zF8WaXU0vW4

All of this but the problem at the top still persists
https://imagebin.ca/v/7zErQblLuBss

I have important data on the drive, If I couldn't recover the system I would still want the data from the drive. If you know how to solve this kindly help me or help me to recover my data, thanks.

Always a bad idea. Try the REISUB method explained at the link below next time.

https://gist.github.com/genyrosk/795...48561966d48ebf

It appears that your update has completed but the system was damaged somehow.

What does that mean? The top of what? Are you referring to the messages in your image?

Does that mean you do not have a backup?

Your update seems to have worked and now you are unable to login, is that the current status?

Might want to boot up a live session of gparted and run a check on files in gparted.

I've fixed a couple a boot problems doing this.

Just be sure the partition in question to be checked is unmounted first.

After I did this. Login worked like it should. Won't hurt anything to try this.
File checks are safe when unmounted.

I second rokytnji's advice. While in a live session, you might also look at the log files, particularly /var/log/boot.log or equivalent (perhaps messages or syslog). It might give more detail as to what precisely is going wrong.

Try booting the system into recovery mode. This guide has the steps: https://www.linuxtechi.com/boot-arch...e-rescue-mode/
Once you are in you can try running your update again to see if that fixes things.