当前位置:网站首页>[Galaxy Kirin V10] [desktop] can't be started or the screen is black

[Galaxy Kirin V10] [desktop] can't be started or the screen is black

2022-07-04 10:35:00 GUI Anjun @kylinos

scene 1: The system starts up and enters UEFI Interactive Shell 

Solution : Host hardware problem , To turn it off , Then unplug the system power cord , Discharge the system , Then reconnect the power cord , Start the machine normally .

scene 2: The system cannot enter the desktop after startup , Has been stuck in loading Linux loading ramdisk Interface

Solution : Host hardware problem , Check whether the host memory module is loose , Unplug it again .

scene 3: The following errors are reported when the system is running or restarted :

Solution : Host hardware problem , Plug and unplug the memory module again and restart the system

scene 4:busybox problem

  Solution : This problem is generally caused by the disk file system damage caused by forced shutdown , You can enter exit, Then you will see the echo , such as :

“/dev/sda2 contains a file system with errors,check forced.

Inodes that were part of a corrupted orphan linked list found.

/dev/sda2:UNEXPECTED INCONSISTENCY:RUN fsck MANUALLY.(i.e.,without -a or -p option)

fsck exited with status code 4

The root filesystem on /dev/sda requires a manual fsck......”

The damaged drive letter will be prompted in the observation echo , As mentioned above /dev/sda2, If it is a solid-state disk, it will generally echo similar /dev/nvme0n1p2, Here you can find the corresponding damaged drive letter according to the actual situation , Then execute the following repair command :

# fsck  -fy   /dev/sda2         // Fill in the actual damaged drive letter path in the following disk path

Wait for the repair command to complete , Press ctrl  alt  delete Just restart the system with the key combination

原网站

版权声明
本文为[GUI Anjun @kylinos]所创,转载请带上原文链接,感谢
https://yzsam.com/2022/02/202202141417493303.html