Question

TLDR;

干净安装Ubuntu 18.04
已安装的Nvidia NVS 510驱动程序sudo ubuntu-drivers autoinstall- 有4个屏幕按预期运行
重新启动后，出现错误提示：

/dev/sda2: recovering journal

/dev/sda2: clean, 187162/30490816 files, 4536721/121965056 blocks

重新启动后，我随机获得以下3个结果之一：
- 1. 信号丢失到屏幕上，数字锁定灯熄灭且无响应-死在水中
- 1. 正常启动
- 1. 拿起可启动的USB并显示该菜单，启动到Ubuntu有时会失败，有时却不会

长版：

所以我安装了干净的Ubuntu 18.04。

然后我安装了Nvidia NVS 510驱动程序，以支持4个屏幕。我使用sudo ubuntu-drivers autoinstall

进行了安装

重新启动后，出现错误提示：

/dev/sda2: recovering journal

/dev/sda2: clean, 187162/30490816 files, 4536721/121965056 blocks

然后屏幕丢失信号，并且num lock灯熄灭并且没有响应-当时死在水中。

我插入了一个可引导的USB记忆棒，并尝试使用fsck却没有任何乐趣，因为我无法umount /dev/sda2分区（稍后对此进行更多介绍）。

然后我只是选择了正常启动，然后以某种方式在我体内正常启动了。

然后我用机器做一些工作。 sudo apt update && sudo apt upgrade并重新启动。

这次，USB可启动程序没有出现，我再次死于水中。我进入BIOS并将USB移至启动顺序的上方（它已经以某种方式移下了？！），但没有启动菜单。

然后每当我死于水中时，我就一直重新启动，大约3-4次启动后，它引导进入Ubuntu没问题-很奇怪！

然后我关闭并再次开始重新启动周期，这次我得到了USB启动菜单！我只是选择了Ubuntu，但无法启动。因此，我进行了重新启动，大约5次正常启动后仍然启动（仍然显示recovering journal等消息，但是启动后进入了登录状态，所有4个屏幕均正常工作。）

这是怎么回事？它启动时似乎随机是一个事实，这使得诊断非常困难！

这是sudo fsck -fn /dev/sda2的出路：

e2fsck 1.44.1 (24-Mar-2018)
Warning!  /dev/sda2 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found.  Fix? no

Inode 3276897 was part of the orphaned inode list.  IGNORED.
Inode 3277117 was part of the orphaned inode list.  IGNORED.
Inode 3277148 was part of the orphaned inode list.  IGNORED.
Inode 3282800 was part of the orphaned inode list.  IGNORED.
Inode 3300994 was part of the orphaned inode list.  IGNORED.
Deleted inode 9175055 has zero dtime.  Fix? no

Inode 9175069 was part of the orphaned inode list.  IGNORED.
Inode 23857339 was part of the orphaned inode list.  IGNORED.
Pass 2: Checking directory structure
Entry 'Local State' in /home/adamdry/.config/google-chrome (3277619) has deleted/unused inode 3304382.  Clear? no

Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Unattached zero-length inode 3303875.  Clear? no

Unattached inode 3303875
Connect to /lost+found? no

Pass 5: Checking group summary information
Block bitmap differences:  -609152 -610368 -(13193300--13193303) -(13197243--13197245) -(13407945--13407947) -(13435314--13435315) -13475158 -13550912 -(95532034--95532036) -(95549965--95549966) -(95549978--95549979) -(95550586--95550594) +(95579694--95579702)
Fix? no

Free blocks count wrong for group #402 (4, counted=0).
Fix? no

Free blocks count wrong for group #410 (23378, counted=23376).
Fix? no

Free blocks count wrong for group #411 (23122, counted=23121).
Fix? no

Free blocks count wrong for group #2915 (22180, counted=22171).
Fix? no

Free blocks count wrong for group #2916 (8904, counted=8913).
Fix? no

Free blocks count wrong (116975747, counted=116976177).
Fix? no

Inode bitmap differences:  -3276897 -3277117 -3277148 -3282800 -3300994 +3303875 -3304382 -9175055 -9175069 -23857339
Fix? no

Free inodes count wrong (30249200, counted=30249649).
Fix? no

Inode bitmap differences: Group 403 inode bitmap does not match checksum.
IGNORED.
Block bitmap differences: Group 402 block bitmap does not match checksum.
IGNORED.
Group 410 block bitmap does not match checksum.
IGNORED.
Group 411 block bitmap does not match checksum.
IGNORED.
Group 2915 block bitmap does not match checksum.
IGNORED.
Group 2916 block bitmap does not match checksum.
IGNORED.

/dev/sda2: ********** WARNING: Filesystem still has errors **********

/dev/sda2: 249616/30498816 files (0.4% non-contiguous), 4989309/121965056 blocks

我尝试删除-n选项，以便实际上可以修复磁盘，但是我得到了

e2fsck 1.44.1 (24-Mar-2018)
/dev/sda2 is mounted.
e2fsck: Cannot continue, aborting.

运行sudo umount /dev/sda2后，我得到umount: /: target is busy.，所以我不知道如何运行fsck并获得解决问题的方法。

我将使计算机保持登录状态并运行，以便我可以尝试运行一些东西来帮助诊断问题。

任何帮助深表感谢！！：）

我的计算机随机启动，无法在使用Nvidia NVS 510驱动程序的Ubuntu 18.04全新安装上启动

0 个答案: