Have a boot error where Ubuntu fails to properly startup after giving the line:
dev/sdb1: clean, ***/*** files, ***/*** blocks
where dev/sdb1 is my root file system. This error popped up after my computer crashed for an unknown reason about 50 boot attempts ago after running a python script. No clue why it went down on that boot and didn't check journalctl when it first occurred. My computer has persistently had the issue where in my windows OS, the system spontaneously crashes. With ubuntu, further, I have had related issues before that turned out to just be related to the nvidia graphics driver bug. Here, however, I am at a loss. I have tried the following after googling around a ton the last 3 hours:
- Uninstall and reinstall
nvidia-related packages; - Uninstall and do not reinstall
nvidia-related packages; - Uninstall and reinstall
xserver-xorg-video-intel; - running memtester (showed nothing informative after 5 loops and exited without error/warning/problem of note with status indicating memory health); system doesn't seem to have
memtest86+in the grub menu as it is 64 bit and apparently it is no longer supported with UEFI and I don't have another computer on which I can create a bootable media formemtest86; - Running my Windows OS dual-booted (operates without obvious error for the 20 minutes I played around with it to double check);
- Recovery mode in Ubuntu is functional spottily (on a few recovery attempts the system hung in the same place as a normal boot sequence, though this only happened once);
- Ensuring that nouveau drivers are disabled by uninstalling and reinstalling nouveau, and manually setting it to mode
0;
Thus far my efforts to fix the problem have been less-than-fruitful, so I'm at a loss. Link to journalctl output provides the output of journalctl --boot=-1 after my most recent boot attempt (prior to entering recovery mode via grub which is how I am writing this now) was to the default grub option of ubuntu, which hung at the line noted above, and then I pressed the power button on my desktop to reset. I really have no clue what to do with journalctl output, so hoping somebody can make some sense of this. My last thought that I personally have to do is reflash the BiOS, but I really don't want to do that ideally as I've never done it before, and it is very strange to me that my Windows OS and recovery mode for ubuntu are functional if there were a potential BiOS issue, which leads me to believe it is ubuntu-related. Not sure how to proceed; any help is much appreciated.
memtester; do you think this is good enough? Or ismemtest86really that much better? Also, what is the "best" way to test device storage? That is a good idea as my windows partition which seems to be functional is on a different storage device. – Eric Jul 01 '20 at 20:32smartctl; HDD is not a root partition nor has any system-level data on it but that comes up clean too.memtestergives clean RAM as well. Any other thoughts? Or perhaps one of these utilities is no good that I used? – Eric Jul 02 '20 at 02:11