dev/sda1: clean, 552599/6111232 files, 7119295/24414464 blocks
After I turn on my laptop this message appears. The system never boots, the message just stays there.
Ask Ubuntu is a question and answer site for Ubuntu users and developers. It only takes a minute to sign up.Sign up to join this community
I have had this problem occur a few times, and every time it was ODDLY Nvidia's fault - yes COUNTER-INTUITIVELY
If in Ubuntu after a long painful reboot run:
sudo apt-get purge nvidia*
or if locked try Ubuntu's awesome way of troubleshooting and try: Ctrl+Alt+F1 through F7 to get to "TTY1-7" and run the same thing. Reboot for good measure, and re-install Nvidia's Proprietary Drivers.
I experienced the same problem; though Mark's (top answer) solution didn't immediately work (since ctrl+alt+F2 etc. brings up a flickering TTYL which is nearly impossible to use), his suggested cause was correct, as it was a problem with the nvidia driver.
Also for beginners like me, here's the fool-proof step-by-step solution:
Boot into safe mode (recovery mode). Enter this mode by holding the left shift key when the computer starts.
in terminal, type:
sudo apt-get purge nvidia*
sudo ubuntu-drivers autoinstall #Make sure you have internet connection
Other solutions suggested elsewhere didn't work (e.g. installing
sudo apt-get update)
(This worked on my dual booted computer (Windows 10 and Ubuntu 18.04)
my error message was
/dev/nvme0n1p5: clean, nnn/nnn files, nnn/nnn blocks
I solved this by fixing the installation of my display manager (gdm3)
sudo apt install gdm3
Story behind this:
I was upgrading from Ubuntu 18 to 20. I have dual OS installed (Ubuntu 20 and Windows 10) on my Xiaomi laptop, no nvidia or AMD graphics card, Intel Core i5 8th gen.
Log in to your terminal
You can do this via reboot and choose recovery mode or press alt+f2 or ctrl+alt+f2 when the screen is stuck
Connect to a network
You can do this using
iwconfig <your-wifi-adapter> essid <network-name> key <network-password>
Do basic recovery steps
sudo apt update sudo apt clean sudo apt autoremove sudo apt update && sudo apt upgrade sudo dpkg --configure -a sudo apt install -f
This should do the trick, but just to make sure, continue to the next step.
Check display manager
$ cat /etc/X11/default-display-manager /usr/sbin/gdm3
systemctl status display-manager or
/etc/init.d/gdm3 status make sure your display manager's status is active then
sudo dpkg-reconfigure gdm3.
If it shows
/usr/sbin/dpkg-reconfigure: gconf2 is broken or not fully installed
then there is your problem.
Fix the broken package
sudo apt install gdm3
Let's first check your file system for errors.
To check the file system on your Ubuntu partition...
sudo fsck -f /
If for some reason you can't do the above...
gpartedand determine which /dev/sdaX is your Ubuntu partition
sudo fsck -f /dev/sdaX# replacing X with the number you found earlier
If step 1. doesn't fix your problem, then do this.
sudo cat /etc/fstab
pending fix here...
If you dual boot with Windows, then do this in Windows.
change what the power buttons do
change options that are unavailable
powercfg /h off(turns off hibernation)
chkdsk /f c:
I had the same problem. Neither of the answers worked for me. I have an old laptop with an Atom processor without Nvidia graphics. Thus, I've adopted an alternative solution with
nomodeset mode as follows:
nomodeset, and press Enter. An
xwill appear to its left. Then press Esc, and press Enter to "Try Ubuntu without installing" or "Install it".
I got into trouble with another laptop (ThinkPad T430) and I fixed that by disabling the discrete graphic card (Nvidia) in BIOS.
A mechanical issue with the hard drive can trigger an fsck execution on boot and that could be the cause of an error message of the following type:
dev/sdaX: clean, ******/******* files, *******/******** blocks
If the other solutions to this question don't work try swapping the hard drive with another replacement hard drive. It should also be noted that even low-priced budget SSDs have better performance than HDDs.
I am not sure if this will work for everyone but I managed to fix this by removing every occurrence of
/etc/default/grub file and then by executing
This was because
nomodeset disables the use of any graphic driver. I disabled my
nouveau drivers before installing nvidia ones.
Though this might not be the case with everyone.
The closest answer I found helpful to solve my problem was this one and I hope it will help you too
I just had a similar problem and I found problem was that the UUID for the EFI partition in
/etc/fstab is not correct. I fixed it using the following:
Boot using live system USB/CD, open terminal, and check UUIDs for partitions root and EFI
fdisk to know which is the EFI partition and make sure it's in the correct format (EFI system partition)
fdisk -l /dev/sdX
Mount the root partition
mount /dev/sdXX /mnt
then check the fstab file
If the UUID values are different, edit the value in the fstab file to match the correct UUID
use nano, gedit, vi, or whatever you want to edit and save fstab and reboot
that worked for me.
I believe the values changed because I installed Windows after installing Linux in my case.
If you have these symptoms:
Then there is a chance that GNOME Display Manager is not starting for some reason (eg due to a recent Ubuntu update).
systemctl status display-managergives an error or shows that the GNOME Display Manager is not both loaded and active.
cat /var/log/syslog | grep "Starting GNOME Display Manager")
If so, then type
sudo apt install --reinstall ubuntu-desktopto reinstall
I reinstalled Nvidia drivers and the PC started working:
ctrl+alt+f2 or f3
Log in with your account
Run these commands:
sudo add-apt-repository ppa:graphics-drivers/ppa sudo apt update sudo apt install nvidia-settings
(thanks to @Shahad and his solution at https://askubuntu.com/a/1218483/750140)
You can avoid running fsck by booting into recovery mode and editing the file /etc/fstab to temporarily change the final 1 to 0 for the affected partition:
sudo nano /etc/fstab
Then reboot. If that gives a blank screen instead, reboot again, and press 'e' at the Grub menu. This time, omit the kernel parameters 'quiet splash' before resuming boot. You might get more helpful information to see where it is getting stuck - probably at the next step to do with gdm (or other login manager being used), or the system logging service. If you fail to rescue the existing installation, do a fresh installation using a wired internet connection so that it installs, makes the right settings, and updates correctly.
My issue was due to large size of Syslog file in
/var/log/syslog. It has filled my HDD. So I have fixed it by the following steps.
/var/log/Syslogin your HDD
For more info see this answer.