I managed to find a problem and fix it. The problem was that /etc/kernel/cmd had the wrong UUID. Thanks for giving advice about initrd and bootloader reconfiguring, might not have found a solution without it.
I managed to find a problem and fix it. The problem was that /etc/kernel/cmd had the wrong UUID. Thanks for giving advice about initrd and bootloader reconfiguring, might not have found a solution without it.
I think I found what changes root UUID. When I used dracut-rebuild all entrie UUIDs changed to the wrong one. Now I have to find how to stop that.
I used gparted, blkid, checked fstab and by-uuid dir and no partition or drive had that UUID.
Will have a look.
I used arch-chroot. I mounted efi to efi dir with mount and used mount -o subvol=@subvolname to sub vol dir. Just incase i will reinstall nvidia drivers when booted normally. I will read about initrd. Thanks for all the info.
I have systemd-boot.
[You are right. In systemd-boot entrie it is used for root uuid. I should replace it with my root uuid right?]
Edited entrie to my root uuid and it boots. Thanks for helping me.
It doesn’t really matter if it’s usefull for others. Write it for yourself and learn from it. I myself wrote copying script for terminal and I am sure no one else going to use it just me and thats fine.
You can add unsupported extensions by using custom add-on collection.
I left but logged in to see if my deleted post and comments were restored. Some of them were restored so I edited them to nonsense
It probably happened when I was messing with SSDs. I wanted a smaller one to be root and a bigger one as home.
Edit: Kind of happy that i managed to break something and fix it.