Ubuntu 18.04 fsckd 未完成文件系统检查过程,也无法通过按 Ctrl+C 取消该过程

卡尔蒂克

我的系统在 Ubuntu 18.04 上运行卡在fsckd检查中,我无法取消此检查,也无法在出现以下提示后看到检查的任何进度。

fsckd-cancel-msg:Press Ctrl+C to cancel all filesystem checks in progress

支票截图

我试过跳过支票,但没有运气。

我想找出这里的实际问题是什么,因为文件系统检查需要很长时间,以及首先启动此文件系统检查过程的原因。

跳过此检查是一个不错的选择吗?如果是这样,您能否指导我完成需要完成的工作。如果跳过检查不是一个好的选择,那么需要做什么。

任何帮助都感激不尽。

海尼玛

Let's check the basics first, by performing a manual fsck...

  • boot to a Ubuntu Live DVD/USB
  • open a terminal window
  • type sudo fdisk -l
  • identify the /dev/XXXX device name for your "Linux Filesystem"
  • type sudo fsck -f /dev/XXXX # replacing XXXX with the number you found earlier
  • repeat the fsck command if there were errors
  • type reboot

Update #1:

Ah, you've partitioned your disks slightly out of the ordinary, so we'll have to fsck the other partitions also.

  • boot to a Ubuntu Live DVD/USB
  • open a terminal window
  • type the following commands...
    • sudo fsck -f /dev/sda4
    • sudo fsck -f /dev/sda1
    • sudo fsck -f /dev/sdb1
    • sudo fsck -f /dev/sda5

Update #2:

We're investigating high read/seek/ECC error rates on sdb (HDD).

There may also be a Ubuntu software issue, or sda (SSD) firmware issue.

Update #3:

In looking at gparted for sda (SSD) I see /var is full.

I'd recommend:

  • full backup of important files from /home/username from sdb (HDD)
  • perform firmware update on sda (SSD) if required
  • wipe sda (SSD) and install fresh Ubuntu WITHOUT separate /var or /home
  • do not install anything on sdb and we'll do a bad block scan, and see if fsckd problem is gone

Update #4:

Bad block scan on sdb...

If sdb is not empty, use the appropriate partition number (probably sdb1 in your case) for the sdXX parameter below. If sdb is empty, assure that there's at least one large ext4 partition, which will probably be sdb1, and then use that for sdXX.

Note: do NOT abort a bad block scan!

sudo e2fsck -fcky /dev/sdXX # read-only test

or

sudo e2fsck -fccky /dev/sdXX # non-destructive read/write test (recommended)

-k 很重要,因为它保存了之前的坏块表,并将任何新的坏块添加到该表中。如果没有 -k,您将丢失所有先前的坏块信息。

-fccky 参数...

   -f     Force checking even if the file system seems clean.

   -c     This option causes e2fsck to use badblocks(8) program  to  do  a
          read-only  scan  of  the device in order to find any bad blocks.
          If any bad blocks are found, they are added  to  the  bad  block
          inode  to  prevent them from being allocated to a file or direc‐
          tory.  If this option is specified twice,  then  the  bad  block
          scan will be done using a non-destructive read-write test.

   -k     When combined with the -c option, any existing bad blocks in the
          bad blocks list are preserved, and any new bad blocks  found  by
          running  badblocks(8)  will  be added to the existing bad blocks
          list.

   -y     Assume  an answer of `yes' to all questions; allows e2fsck to be
          used non-interactively.  This option may not be specified at the
          same time as the -n or -p options.

更新#5:

坏阻塞完成。SMART Data 表明读取/ECC 错误现在为零!如果读取/搜索/ECC 错误返回,则怀疑 SATA 电缆或 SATA 端口有问题。监视 sdb 的 SMART 数据。

重新安装没有特殊分区的 Ubuntu,除了 ext4 sdb1 上的 /home,如果您与 Windows 共享文件,可能还有 sdb2 NTFS 分区。

本文收集自互联网,转载请注明来源。

如有侵权,请联系 [email protected] 删除。

编辑于
0

我来说两句

0 条评论
登录 后参与评论

相关文章