这可能是硬件问题吗?:
最近我的电脑崩溃了。我正在vim中进行编辑,接下来我知道我无法保存更改,因为文件系统是只读的。我被迫重启,现在启动时,我得到以下信息(必须手动复制,因为现在在平板电脑上):
...
Mounted /boot
Reached target Login Prompts
Reached target Timers
Reached target Sockets
Started Emergency Shell
Reached target Emergency Shell
Failed to start File System Check on /dev/disk/by-uuid/...
...
Dependency failed for /home
Dependency failed for Local File Systems
...
You are in emergency mode. After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to boot into default mode.
Give root password for maintenance (or press Control-D to continue): _
在此之前,该崩溃发生了两次。我不知道该怎么办。即使我知道此时该怎么做,我也不知道为什么文件系统首先会进入只读模式。
我将提供所有详细信息。我可能需要一段时间才能提供更多详细信息,因为我必须在触摸屏上手动编写它们,但我会做到这一点。
更新:当我写这篇文章的时候,我的电脑空转了,现在我得到以下信息:
ata2: exdeption Emask 0x10 SAct 0x0 SErr 0x4090000 action 0xe frozen
ata2: irq_stat ..., connection status changed
ata2: SError: { PHYRdyChg } 10B8B DevExch
我什么也做不了,所以我重新启动了。我按照建议运行了fsck:
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix <y>?
Inode ... was part of the orphaned inode list. FIXED.
Deleted inode ... has zero dtime. Fix<y>?
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: ... Fix?<y>
Free blocks count wrong for group ... Fix<y>
... same stuff
Inode bitmap differences ... fix
Free inodes count wrong for group ... fix
... same stuff
/dev/sda4: FILE SYSTEM WAS MODIFIED
... files (1.1% non-contiguous), ... blocks
它现在似乎可以启动,但是由于它已经崩溃了三遍,我想知道是什么引起了问题,以及这里是否存在更大的潜在问题。
要解决此问题,需要采取以下两种措施:
尽管后者尚未实现fsck -f /dev/disk/by-uuid/...
,但前者更为重要。
您的日志条目
ata2: exdeption Emask 0x10 SAct 0x0 SErr 0x4090000 action 0xe frozen
ata2: irq_stat ..., connection status changed
ata2: SError: { PHYRdyChg 10B8B DevExch
指向SATA总线上的硬件问题。以我的经验,首先(也是最容易且最有可能成功)采取的措施是重置相关磁盘的所有SATA连接,甚至更好地替换SATA电缆。
本文收集自互联网,转载请注明来源。
如有侵权,请联系[email protected] 删除。
我来说两句