0

I have Ubuntu 20.04 and Windows 10 on my computer and it uses NVIDIA drivers. When I enter Ububtu this message appears:

/dev/sda5 clean, 525049/30343168 files, 13164811/121342720 blocks

For fixing this problem, I've already tried the solution below:

"dev/sda1: clean, ..." This message appears after I startup my laptop, then it won't continue booting

But it didn't work. I've run following commands on recovery mode:

sudo apt update
sudo apt upgrade
sudo apt purge nvidia*
sudo ubuntu-drivers autoinstall

It seems like the problem is not due to the Nvidia drivers. What could be the cause of this problem and how can I solve it?

I removed all the nvidia packages with sudo apt purge package_name, then with autoinstall, I reinstalled them with sudo ubuntu-drivers autoinstall, but I still got the same error message.

Also, I checked disk with the df -H command. None of the filesystems were in 100% use.

karel
  • 122,292
  • 133
  • 301
  • 332
user33
  • 1

3 Answers3

1

First things first, we need to diagnose the issue further, it might have nothing to do with nvidia drivers but something is causing the system to hang. To start with in recovery mode run
sudo nano /etc/default/grub file and remove the quiet flag from the line GRUB_CMDLINE_LINUX_DEFAULT then run

sudo update-grub

Reboot and you should see a lot more messages and maybe you might see what your problem is. Maybe its a stop job that is hanging indefinitely but it should give you the name.

If you cannot get into recovery mode or the quiet option is not in that file, when you are in grub, hit e on the MAIN ubuntu option, then find the line that starts with linux, there should be a quiet flag on that line, remove it, and it should do the same as above, but it is only temporary and the quiet flag will come back after a reboot

xXTeraXx
  • 11
  • 1
0

Check your disk isn't full.

Linux will not boot and stop at that message if your root filesystem is 100% full.

Also post the contents of /var/log/Xorg.0.log

Matias N Goldberg
  • 1,179
-1

No one mentioned the obvious goto, so i will at the grub screen pick second option which is the rescue kernel and boot it, have a look at the options given there fix broken packages being one of those options ,

Hears a thinking out of the box solution again when at grub screen pick normal boot which is the first option press the e key on the keyboard to edit scroll down to the line where it says root = delete everything after the = on that particular line and then type in after the = rw,init=/bin/bash save with f10 key then boot with return key
this will sometimes if your in luck throw you into root shell but i think your still going to need your root password .

If you got that far next place maybe to look systemctl list-unit-files systemctl cat name of service and systemctl status name of service also gives good info where name of service means the particular name of unit you want to investigate example systemctl status x11-common was the drive even mounted sudo mount ,,,cant give anymore of that command then that as it varies on each particular system. According to content written in fstab file ,,location of fstab file,,,, /etc/fstab but i use this ,, mount /dev/sda1 /mnt/sda1

bit
  • 1