Table of Contents
- How is the problem
- First aid for troubleshooting the boot Deepin
- Some important points when you use the terminal
- further reading
Here we collect a compilation of troubleshooting the boot Deepin, Specifically Bootloader. It is derived from a section Deepin problems. Most often it occurs when displaying text only seconds after turning on the computer.
You need to know a bit on terminal and have administrator permissions for these procedures.
At the start Deepin. They are generally displayed in a message:
Welcome to emergency mode! After logging in, type "journalctl -b" to view system logs, "systemctl reboot" to reboot, "systemctl default" to try again to boot into default mode. Give root password for maintenance (or type Control-D to continue):
In this Emergency Mode find options to display the record (write
journalctl -xb and press enter). If you pay attention, and you have some knowledge in English, you can check the cause of the problem. Take a picture, you can serve when planteas report in our forum.
At our Troubleshooting at startup DeepinThe best plan is to stay calm. Once you noted the problem, you can perform an Internet search. In the Wiki, for example, we noted several basic terms about Deepin. We promise not solve all problems.
Do not worry about the problem, focus on the solution. He thinks the car broke down and can not start. In this case you imagine you need a machine to check startup, the cause and the tool. That is, more or less, what you have in mind.
First we are going to Recovery, Then select on what is wrong (say, the Data of the hard drive). If all else fails, turn to the last resort, the Back.
Deepin Recovery It is a kind of "second operating system" integrated emergency. It includes most emergency applications with simple options to repair the equipment.
For this you must go to startup and select "Deepin Recovery" in the boot menu (by moving the arrow below). After test type previously assigned password. At the entry, you'll see the home screen with various applications
GPartedInstead, it helps to review the damaged partitions. Click the partition that starts Deepin (usually
Verificar) And then you will verify if the partition is in operation. Another way is to access the menu "
Intentar rescatar los datos«.
In general, most of the drawbacks are solved with the terminal. Thanks to Deepin Recovery, the above applications solve these problems. However, you will probably need to use them to full operations. You must use your administrator password (sudo).
Note: If you do not have Recovery, you will have it very difficult to solve the problem. You will have access full screenWithout graphics. You will need patience and ability to keep track of.
If the problem is too complicated, high risk do not (being unattainable), you must restore a copy of the computer. If you made a backup using Deepin Clone (For Deepin 15.5 or higher) or similar, you can reverse the problem.
Note: If the problem comes from the hard drive, you'd have to back it up as soon as possible to transfer to the new hard drive. More information to consider reviewing respect for the transfer is safe.
Here are some tips for using the terminal Troubleshooting at startup Deepin.
- From the boot menu select "Deepin Recovery"
- YTT mode for when you start select "recovery mode" in advanced mode choose "root" and have the terminal.
If a member represents root or not. The symbol '$' is a regular user and '#' when you are administrator or root. You can change these privileges with the command
su and typing the password.
It is not mandatory to use the terminal. However, you'll need when you download packages repositories. We recommend doing so via cabling.
If you want to set the IP or DNS bridge use the command:
First, check for damaged packages. These commands are used to install packages on Deepin incomplete and eliminates useless (or orphans):
-f install sudo apt && sudo apt autoremove
After so you can manage packages recommend opening the application
If you want to do now test these commands, remove the cache, update and install packages without asking:
sudo apt-cache clean && sudo apt update && sudo apt-and full-upgrade
However if you have problems
dpkg because it does not respond:
sudo dpkg -a -configure
If Deepin has damaged partition, it's probably invite you to use the command
fsck. Check out these tips.
These steps are to use this instead of the traditional manager Deepin program.
To view and open files you can see the command
cd [folder or file name] cd ..
To view the files use
Tags: Problem solving