Jett I did mkdir /target and mount /dev/sda1 /target/boot appeared to mount, but when I did the same for mount root: mount /dev/sda2 /target it did not mount.
*I wonder if a /target/root is missing in the directions instead of just mount /dev/sda2 /target?
*or maybe you can only mount one partition in /target?
*unless we needed to mkdir two different targets? (doubtful)
*unless your drive is lvm encrypted?
*at least with /boot mounted you could go ahead and fix the boot, if indeed boot is the problem
spitballing. the directions changed (formatting) since i used them.
I'm unfamiliar with rooting around the /target files. why are you doing that? to read logs? it reminds me of trying to jumpstart a car off the starter. it's smart, but I don't think linux allows for that.
edit: I am unsure why we are where we are: inability to mount root...A) there's gotta be a step you didn't follow...or you did some of that un-necessary steps depending on your system or B) start migrating the important stuff off that /root to a safe storage device and re-install.
solus has this to say about the emergency screen:
"This issue might happen when the /etc/fstab file contains an entry for a storage device that isn't available during system startup, for example, disconnected USB drives or unavailable network file system (NFS) mounts.
When trying to mount the device, the system fails and displays an emergency shell or error message."
could it be as simple as some moves in fstab (that's stuff I never do btw maybe someone else)? it's never that simple for me 😉
