当我突然意识到我的所有文件都被标记为只读时，我正在使用我的虚拟机。我觉得很奇怪，所以我重新启动，然后我被提示进入“BusyBox”。由于某种未知原因，文件系统发生了错误。
我fcsk如下图所示运行。理论上，它修复了不同的错误。
由于我不完全了解所做的fcsk事情，并且根据我之前在 Windows 修复其文件系统方面的经验，我现在对文件系统是否真的“修复”或是否存在损坏的文件有点怀疑。
- 我可以相信修复过程吗？
- 有没有一种方法可以检查所有数据是否正常，而不必一个一个打开文件？
- 当发生如下图所示的错误时，会对驱动器中的实际数据产生什么影响？我可以期待部分文件损坏吗？完整的文件损坏？
一些单独的错误消息：
File /var/log/journal/d74933508486479e9b07e83b9a036776/system.journal corrupted or uncleanly shut down, renaming and replacing.
pulseaudio[815]: ALSA woke us up to write new data to the device, but there was actually nothing to write.
pulseaudio[815]: Most likely this is a bug in the ALSA driver 'snd_ens1371'. Please report this issue to the ALSA developers.
pulseaudio[815]: We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value < min_avail.
lightdm[931]: gkr-pam: unable to locate daemon control file
dbus-daemon[1035]: writing oom_score_adj error: Permission denied
colord[1570]: failed to get edid data: EDID length is too small
udisksd[1636]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
udisksd[1636]: Failed to load the 'mdraid' libblockdev plugin
udisksd[1636]: Error probing device: Error sending ATA command IDENTIFY PACKET DEVICE to '/dev/sr0': ATA command failed: error=0x01 count=0x02 status=0x50 (g-io-error-quark, 0)
pulseaudio[953]: X11 I/O error handler called
pulseaudio[953]: X11 I/O error exit handler called, preparing to tear down X11 modules
systemd[936]: xfce4-notifyd.service: Main process exited, code=exited, status=1/FAILURE
systemd[936]: xfce4-notifyd.service: Failed with result 'exit-code'.
kernel: button: module verification failed: signature and/or required key missing - tainting kernel
input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
piix4_smbus 0000:00:07.3: SMBus Host Controller not enabled!
sd 2:0:0:0: [sda] 167772160 512-byte logical blocks: (85.9 GB/80.0 GiB)
kernel: sd 2:0:0:0: [sda] Write Protect is off
kernel: sd 2:0:0:0: [sda] Mode Sense: 61 00 00 00
kernel: sd 2:0:0:0: [sda] Cache data unavailable
kernel: sd 2:0:0:0: [sda] Assuming drive cache: write through
systemd[1]: File System Check on Root Device was skipped because of a failed condition check (ConditionPathExists=!/run/initramfs/fsck-root).
systemd[1]: Starting Journal Service...
systemd[1]: Starting Load Kernel Modules...
kernel: fuse: init (API version 7.34)
systemd[1]: Starting Remount Root and Kernel File Systems...
systemd[1]: Repartition Root Disk was skipped because all trigger condition checks failed.
systemd[1]: Starting Coldplug All udev Devices...
systemd[1]: Mounted Huge Pages File System.
systemd[1]: Mounted POSIX Message Queue File System.
systemd[1]: Mounted Kernel Debug File System.
kernel: EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro. Quota mode: none.
fsck 的输出显示了几种类型的更正错误：
因此 fsck 所做的更改不会损坏任何文件。
但是，令人担忧的是，您的文件系统最初是只读的。这可能是由于内核检测到内存损坏或磁盘在使用时完全或部分脱机造成的。
如果在写入文件时出现硬件错误，则可能是文件损坏。如果磁盘在写入过程中脱机，则可能存在部分写入的文件或已创建但从未写入磁盘并且现在完全丢失的文件。
所以，直接回答你的观点：
find / -type f -mtime -1查找在最后一天修改的文件并查看其中是否有任何被截断的方法，或者使用您对系统当时正在执行的操作的了解来查看使用中的任何内容是否未完全写入。