19th November 2016, 12:29
I am not really sure. But we have a special case here as the proprietary nvidia driver was in use here. I fear that the fsck at boot run and it was asking about correcting the corruption detected but the nvidia driver stopped that message from displaying.
Otherwise a regulary fsck is of course run every 30 days or 120 mounts anyway and should fix such issues. As the plymouth splash was not the problem here the only culprit on my list can be the nvidia driver.
Otherwise a regulary fsck is of course run every 30 days or 120 mounts anyway and should fix such issues. As the plymouth splash was not the problem here the only culprit on my list can be the nvidia driver.