There was an incident with grub a few months back, which broke my PC. To avoid this, there was a post on how to switch to systemd, which I did. I installed timeshift and made regular backups. Yesterday, systemd broke, and I booted into the fallback kernel. I used timeshift to restore from a snapshot, and that broke the fallback kernel as well. Now, it only boots into emergency mode.
I’m new to Linux, and all I know how to do to fix my problems is timeshift. I have all my backups, but it’s not working. I’ve tried this chroot chatgpt recommends, but I get this “bash not found” error, and it doesn’t seem to know what to do after that. any ideas?
[root@EndeavourOS /]# sudo mount /dev/nvme0n1p2 /mnt/efi
mount: /mnt/efi: unknown filesystem type 'vfat'.
dmesg(1) may have more information after failed mount system call.
[root@EndeavourOS /]# sudo chroot /mnt
Welcome to fish, the friendly interactive shell
Type help for instructions on how to use fish
root@EndeavourOS /#
it says i am my system always says welcome to fish so i’m assuming that its right but i don’t know
should it says root or my username?
[root@EndeavourOS /]# sudo mount -o subvol=@ /dev/nvme0n1p5 /mnt
[root@EndeavourOS /]# sudo mount -o subvol=@log /dev/nvme0n1p5 /mnt/var/log
[root@EndeavourOS /]# sudo mount -o subvol=@cache /dev/nvme0n1p5 /mnt/var/cache
[root@EndeavourOS /]# sudo mount /dev/nvme0n1p4 /mnt/home
[root@EndeavourOS /]# sudo mount /dev/nvme0n1p2 /mnt/efi
mount: /mnt/efi: unknown filesystem type 'vfat'.
dmesg(1) may have more information after failed mount system call.
[root@EndeavourOS /]# sudo arch-chroot /mnt
sudo: arch-chroot: command not found
[root@EndeavourOS /]#
i don’t know, i followed the instruction as it was presented, I’m no so knowledgeable that i can be creative with this. i unmounted everything and mounted again as pasted above
the arch-chroot is working after installing the arch-install scripts but still vfat is not working
[liveuser@eos-2023.03.26 ~]$ sudo mount -o subvol=@ /dev/nvme0n1p5 /mnt
[liveuser@eos-2023.03.26 ~]$ sudo mount -o subvol=@log /dev/nvme0n1p5 /mnt/var/log
[liveuser@eos-2023.03.26 ~]$ sudo mount -o subvol=@cache /dev/nvme0n1p5 /mnt/var/cache
[liveuser@eos-2023.03.26 ~]$ sudo mount /dev/nvme0n1p4 /mnt/home
[liveuser@eos-2023.03.26 ~]$ sudo mount /dev/nvme0n1p2 /mnt/efi
mount: /mnt/efi: unknown filesystem type 'vfat'.
dmesg(1) may have more information after failed mount system call.
[liveuser@eos-2023.03.26 ~]$ ls /mnt/home
allegro
[liveuser@eos-2023.03.26 ~]$ ls /mnt
bin boot dev efi etc home lib lib64 mnt nvme0n1p2 opt proc root run sbin srv sys tmp usr var
[liveuser@eos-2023.03.26 ~]$ ls /mnt/efi
[liveuser@eos-2023.03.26 ~]$ ls /mnt/var
cache db dpkg empty games lib local lock log mail named opt run snap spool tmp
i believe i was chrooting from liveuser the terminal said this:
mount: (hint) your fstab has been modified, but systemd still uses
the old version; use 'systemctl daemon-reload' to reload.
after using systemctl command the root@ turned to liveuser and i went ahead and mounted everything once more. arch-chroot works after installing the arch-install scripts but vfat is still a problem
Please answer my question that I have asked several times. What are you chrooting from? In other words, what did you boot in the first place prior to chrooting?
i don’t understand your question to give you the answer you want to hear.
the instructions on your link says sudo arch-chroot /mnt so thats where i am.
what other information can i provide about this complicated ass system that you all seem to champion yet it finds a way to shit on you not once but twice for having the nerve to update it.
i don’t know thank you for your help i appreciate it.
