@robgriff444 downgrading systemd to version 239 did it!
Looks like version 240 may be having some issues, according the bug reports:
At first I ran into this problem after running updates. Figuring this was just another case of some default solutions being changed, I then did a reinstall, but the problem persists. After GRUB tries to boot linux, it shows the following messages:
Starting version 240 ERROR: device 'UUID=3e992dc0-80c1-40b5-af96-d5cb68c4e44f' not found. Skipping fsck. mount: /new_root: can't find UUID=3e992dc0-80c1-40b5-af96-d5cb68c4e44f. You are now being dropped into an emergency shell. sh: can't access tty; job control turned off [rootfs ]#
I’ve tried live-booting and chroot-ing to run
grub-mkconfigand still same problem.
I’ve tried changing the system from UEFI to Legacy, new MSDOS partition table, and reinstalling, same problem.
With and without swap, fresh install each time, same problem.
With and without dedicated home drive, fresh install each time, same problem.
This system (a Lenovo Thinkstation P510 desktop) was working as of yesterday (2019-1-8), ran updates yesterday, booted up this morning and now nothing on it works … thoughts?