I got to looking at the boot screen and saw more of what the line that said
"[FAILED] Failed to start Load Kernel Modules.
See ‘systemctl status systemd-modules-load.service’ for details. "
I looked that part up and found
Turns out the same stuff happened there.
I uninstalled virtualbox for now, rebooted, the error disappeared along with
all the stuff it said it was loading, I kinda like that screen lol, but I’m wondering if when it does show up, it means something might be wrong? idk
I might have put something in wrong when I redid virtualbox
All seems good now I guess.
[[email protected] ~]$ systemctl status systemd-modules-load.service
[sudo] password for major:
● systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
Active: active (exited) since Thu 2019-05-09 20:11:13 EDT; 1min 49s ago
Process: 221 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=0/SUCCESS)
Main PID: 221 (code=exited, status=0/SUCCESS)
May 09 20:11:13 beholder systemd-modules-load: Inserted module 'crypto_user'
May 09 20:11:13 beholder systemd-modules-load: Inserted module 'sg'
May 09 20:11:13 beholder systemd: Started Load Kernel Modules.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
Anyway, looked at the last journal, and did find this
May 09 20:11:17 beholder kernel: EXT4-fs (sda4): warning: mounting fs with errors, running e2fsck is recommended
idk what this means though
beholder systemd-udevd: Process '/usr/bin/alsactl restore 0' failed with exit code 99.
I need to know how/where to properly do the e2fsck.
It would seem it won’t run while mounted I guess bc it’s fixing disk errors like chkdsk did for win, but want to do it right without breaking stuff and not sure where to do it lol
I’ll mark this solved and try to pay more attention when I revisit the virtualbox setup, it always seems to give me issues someplace haha