Well we start by diagnosing the error then. That disk that cannot be found: what is it? Is it Fedora related? I suspect systemd not being able to find this partition is what is causing it to end up at the emergency shell.
/root file system is mounted in emergency mode, which is probably why you can’t find any files in there. From
¦ A special target unit that starts an emergency shell on the main console. This target does not pull in any services or mounts. It is the most minimal version of starting the system in order to acquire an interactive
¦ shell; the only processes running are usually just the system manager (PID 1) and the shell process. This unit is supposed to be used with the kernel command line option systemd.unit=; it is also used when a file system
¦ check on a required file system fails, and boot-up cannot continue. Compare with rescue.target, which serves a similar purpose, but also starts the most basic services and mounts all file systems.
¦ Use the "systemd.unit=emergency.target" kernel command line option to boot into this mode. A short alias for this kernel command line option is "emergency", for compatibility with SysV.
¦ In many ways booting into emergency.target is similar to the effect of booting with "init=/bin/sh" on the kernel command line, except that emergency mode provides you with the full system and service manager, and allows
¦ starting individual units in order to continue the boot process in steps.
Can you try to boot into
rescue.target? (May not be able to, since it also seems to require mounting all devices, but it’s worth a try). During boot, stop the grub count-down, and add
systemd-target=rescue.target to the end of the kernel command line (Let us know if you need more instructions on this).
Edit: still looking, but perhaps there’s a way to mount individual partitions manually to get a working system in emergency mode and then edit fstab to fix boot.