服务器ubuntu遇到卡死重启后一直进入emergency mode问题的解决办法

zhaorong · 发表于 linux教程 2018-6-20 14:52:54


	本帖最后由 zhaorong 于 2018-6-20 15:05 编辑由于服务器卡死，强制重启后，系统只能进入emergency mode，通过提示的命令journalctl -xb 查看日志 juli 09 15:40:16 kim-SSD-Sationary systemd-fsck[414]: /dev/sdb1 contains a file system with errors, check forced. juli 09 15:40:16 kim-SSD-Sationary systemd-fsck[414]: /dev/sdb1: Inodes that were part of a corrupted orphan linked list found. juli 09 15:40:16 kim-SSD-Sationary systemd-fsck[414]: /dev/sdb1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. 发现是挂载的挂载不上/dev/sdb1而导致系统无法正常启动，还提示说运行 RUN fsck MANUALLY 于是，先修改/etc/fstab，取消开机挂载/dev/sdb1,尝试开机 vi /etc/fstab #注释掉自动挂载/dev/sdb1的那行 reboot 重启正常进入系统挂载/dev/sdb1会提示 can't read superblock on /dev/sda1 乖乖按照提示，fsck 检查修复磁盘 <span style="font-size:14px;">sudo fsck /dev/sdb1 -y</span> 漫长等待后，重新修改 /etc/fstab 后 mount -a 就好了如果有提示 mount.nfs: Stale file handle 就 sudo umount -lf /mnt 再重新挂