Systemd boot failure

Issues & Assistance
1

I’ve been having problems booting when running Plymouth splash command so I’ve been removing the splash command to boot. Been working for the past month. Decided I wanted to permanently remove the command from my boot. So I followed this post [Tutorial] Disable or Remove Plymouth (boot splash) . I did these steps: Users of sdboot-manage may edit /etc/sdboot-manage.conf on the LINUX_OPTIONS= line.
Afterwards to regenrate entries with the options:

sudo sdboot-manage gen

And then I rebooted. Now I’m getting a failure to start file system check for my root drive and I get thrown into an emergency shell but I can’t access or type in it because it’s still locked.

[Album] imgur.com
2

I’m able to access emergency shell console with this command: SYSTEMD_SULOGIN_FORCE=1

Just need help what to do next.

3

systemctl status systemd-fsck-root.service:

Second image Imgur: The magic of the Internet

4

Update:

booted into live usb and copied sensitive files, ran sudo fsck -y for my root drive, fixed and repaired it, now booting works.