当前位置:网站首页>[persistent problems of NVIDIA driver] - - /dev/sdax:clean, xxx/xxx files, xxx/xxx blocks - the most complete solution

[persistent problems of NVIDIA driver] - - /dev/sdax:clean, xxx/xxx files, xxx/xxx blocks - the most complete solution

2022-06-11 01:01:00 Life is like Zhaoxu

LC

introduction

In relation to Ubuntu In the learning environment , Bloggers encountered a very thorny problem in the early stage of research , I have tried to find a solution on both Chinese websites and extranets , Realizing that this problem is a magical one , Its difficulty seems to be adaptive , There are a lot of people on the website , They used a completely different approach , But they all solved this problem , And for bloggers , This problem may be more difficult , The significance of this paper is to sort out and summarize all the solutions to this problem , I hope it can save you time .

Introduction to the problem

According to the effect

 Insert picture description here
The display effect of this problem is , Start up ubuntu System time , This message will be displayed on the computer screen in black before entering the system , /dev/sdax:clean,xxx/xxx files,xxx/xxx blocks, among sda The last number is from 1 To 5 Both ,xxx It doesn't matter if some of them are numbers

Question meaning

This problem can be understood from two perspectives :

  • Paper meaning : That is, there is not enough memory in a storage directory , So the solution is to delete the file , Make the memory meet the requirements .
  • The actual meaning : When the computer starts, it will automatically check whether the memory in the storage directory is insufficient , This is a normal message , Prove that there is no file system error on the computer , If there are no other questions , In fact, this message can be ignored , It can open normally .
  • Drive problem : However , If, as the actual meaning says , It should open normally , The reason why it cannot be opened is NIVIDIA The problem of , Graphics driver error , So we need to start with the graphics card driver .

resolvent

Storage problems

If it is found in the problem display that the previous number is indeed too large , That is, there is a storage problem , Please use the solution of this title :

  • First step : Use the shortcut keys to enter debug mode :Ctrl + alt + F1, Note here that you can try it yourself F1-7, As long as you can access the interface ;
  • The second step : Check the usage of the attached hard disk :df -h
     Insert picture description here
  • The third step : If you can see from the mounting that the memory of a storage directory is full , Some space should be cleared :

Method of removal 1:

sudo apt-get autoremove// Uninstall all packages that are automatically installed and no longer in use 
sudo apt autoremove --purge snapd
rm -rf /etc/X11/xorg.conf
cp /etc/X11/xorg.conf.failsafe /etc/X11/xorg.conf

Method of removal 2:
find Mount point -size +1G( View the mount point Files larger than a certain size )
Switch to a directory where large files exist , Delete large files rm -rf Directory name
The example shows after deletion , Obviously, the available space under the mount point becomes larger , however / Free space has not changed , At this point, you need to perform the following operations after switching back to the mount point du -h -x --max-depth=1
If the capacity does not change after deletion , You can kill the process that occupies the file , Release space :lsof -n | grep delete

Graphics card driver problem ( You should also enter command line mode first )

  • Method 1: Unload and reload nvidia drive
cat /proc/driver/nvidia/version
sudo apt remove nvidia-*
sudo apt-get remove --purge nvidia*
sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt-get install --reinstall ubuntu-desktop
sudo service gdm3 status
sudo service gdm3 start
sudo apt update
sudo apt upgrade
apt autoremove
sudo reboot
  • Method 2:
sudo apt update
sudo apt-get install aptitude
sudo aptitude install xserver-xorg-video-intel
sudo reboot
  • Method 3: Failed to enter command line mode , First select... At startup Advanced Mode entry ubuntu, Select the old kernel version /recovery Pattern , Then enter the terminal interface through the shortcut key

Ubuntu, with Linux 4.13.0-26-generic
Ubuntu, with Linux 4.13.0-26-generic (upstart)
Ubuntu, with Linux 4.13.0-26-generic (recovery mode)
Ubuntu, with Linux 4.10.0-42-generic

  • Method 4:GRUB analysis

stay BIOS Guide interface press “Esc” Press the key to enter the selection menu , choice ubuntu, And press “e” Enter edit mode :
 Insert picture description here
The boot run level is given at the end of the line ,3– Multi user mode , Pure text
 Insert picture description here
Press CTRL+X/F10 Boot system , Enter command line mode
If you want to enter command line mode every time you boot up , You need to do the following :
take /etc/default/grub File configuration under , take GRUB_CMDLINE_LINUX_DEFAULT In one line, change to "quiet splash 3" Save after exit , Use update-grub Command to regenerate based on these changes /boot Under the GRUB2 The configuration file , Restart to enter the command line mode .

  • Method 5: modify grub Guide item

Enter terminal mode :
sudo gedit /etc/default/grub
find quiet splash And add it later nomodeset
sudo update-grub
If the above command cannot be executed , execute sudo cp /usr/share/grub/default/grub /etc/default/grub

Modify startup file : The solution here is more complicated , Just give a link to the solution : Problem solving

  • Method 6: Repair display manager gdm3

Enter terminal mode :
iwconfig <your-wifi-adapter> essid <network-name> key <network-password>

sudo apt update
sudo apt clean
sudo apt autoremove
sudo apt update && sudo apt upgrade
sudo dpkg --configure -a
sudo apt install -f

$ cat /etc/X11/default-display-manager
/usr/sbin/gdm3
sudo apt install gdm3

  • Method 7: Open pendulum , Unload the drive directly , The problem disappears

summary

This question is basically about NVIDIA A stubborn problem of graphics card driver , Bloggers have tried all the methods , You can only choose to delete the driver for the time being , Through research, we can find , The problem may be the conflict between the driver version and the kernel version , I hope to find more accurate solutions in the future .

 Insert picture description here

原网站

版权声明
本文为[Life is like Zhaoxu]所创,转载请带上原文链接,感谢
https://yzsam.com/2022/162/202206102352123528.html