GNU Abyss
kiwifarms.net
- Joined
- May 30, 2023
It all stems from your fstab being fucked up, really. Both mount not working and Dolphin not seeing partitions. There's a section on the Install page of the Arch Wiki that talks about setting up your fstab file manually, that's what I'd do personally. Also, it's very useful to have a live system on a USB drive for times like this.How would I access the drives after mounting if they are not in dolphin? And what is a good mount point? Can I set anything? Or is there a best practice?
My random guess is that your use of yay and pacman simultaneously might have contributed to this, especially if yay pulls a bunch of packages from the AUR that might potentially conflict with native ones. After tidying up fstab, I'd start by clearing pacman's package cache (
pacman -Scc) and checking which packages are orphaned (pacman -Qtdq). Run down that list and check their info (pacman -Qi). It's not really a solution, but more of a sanity check to see if the links between packages are still OK and you're not about to pull a Linus and nuke something very important. The command for removing orphaned packages is pacman -Rns $(pacman -Qtdq). Then try a full system upgrade with yay, force a refresh of the database to be safe - that is the double "y" in pacman -Syyu.Of course. My post has a link to the AUR package. Someone has probably packaged it for your distro as well, unless it's niche.Tried that and Terminal output was fatrace wasn't found. Is that a package I have to install?
bash: fatrace: command not found
