The messages you photographed were because it was a scheduled fsck (file system check) OR more likely, the machine was not cleanly shutdown last time, thus it was done to try and prevent data loss. If you see this message, the usual cause was the machine was not cleanly shutdown last time (ie. power off via button, power loss or other cause). To prevent it use a command, or kernel (SysRq) key combination to tell your system to shutdown.
– guivercAug 28 '20 at 10:44
That's not something I can answer with the information you provided, as the crash cause is not shown. A lot of people appear to have issues with graphics drivers, but it might be a hardware issue as well, or something entirely different. You will have to boot a LiveUSB and then try to diagnose the issue with it. Otherwise there's nothing you can do to your machine in this state that will help.
– ApolloLVAug 28 '20 at 10:41
If you've been waiting for more than a few minutes, then it won't be resolving itself and you can just shut it down.
– ApolloLVAug 28 '20 at 10:41
fsck
(file system check) OR more likely, the machine was not cleanly shutdown last time, thus it was done to try and prevent data loss. If you see this message, the usual cause was the machine was not cleanly shutdown last time (ie. power off via button, power loss or other cause). To prevent it use a command, or kernel (SysRq) key combination to tell your system to shutdown. – guiverc Aug 28 '20 at 10:44