云服务器 linux文件系统异常an error occurren during the file system check导致服务器启动失败



文件系统宕机,重启后报错,无法启动



处理流程:

1.编辑/etc/fstab将文件系统挂载去掉

# vim /etc/fstab 



#/dev/xvdb /data ext3 defaults 1 2

#/dev/xvdc  /data1 ext3    defaults    0  0



2.重启进入系统,对两个分区进行fsck修复检测(建议使用screen,避免中途被打断)

# screen -S xvdc



# fsck -y /dev/xvdc

fsck from util-linux-ng 2.17.2

e2fsck 1.41.12 (17-May-2010)

/dev/xvdc: recovering journal

/dev/xvdc has gone 510 days without being checked, check forced.

Pass 1: Checking inodes, blocks, and sizes

Pass 2: Checking directory structure

Pass 3: Checking directory connectivity

Pass 4: Checking reference counts

Pass 5: Checking group summary information



/dev/xvdc: ***** FILE SYSTEM WAS MODIFIED *****

/dev/xvdc: 425/32768000 files (68.5% non-contiguous), 4265913/131072000 blocks



# fsck -y /dev/xvdb

fsck from util-linux-ng 2.17.2

e2fsck 1.41.12 (17-May-2010)

/dev/xvdb contains a file system with errors, check forced.

Pass 1: Checking inodes, blocks, and sizes

Free blocks count wrong for group #2637 (10474, counted=14592).

Fix? yes



Free blocks count wrong for group #2638 (9318, counted=10345).

Fix? yes



Free blocks count wrong for group #2639 (11172, counted=12429).

Fix? yes



Free blocks count wrong for group #2640 (8375, counted=8887).

Fix? yes



Free blocks count wrong (22177812, counted=22268375).

Fix? yes



Inode bitmap differences:  -19694041 -19709957 -19718159

Fix? yes



Free inodes count wrong for group #2404 (7638, counted=7639).

Fix? yes



Free inodes count wrong for group #2406 (8104, counted=8105).

Fix? yes





Free inodes count wrong for group #2407 (8088, counted=8089).

Fix? yes



Free inodes count wrong (32383813, counted=32383816).

Fix? yes



/dev/xvdb: ***** FILE SYSTEM WAS MODIFIED *****

/dev/xvdb: 384184/32768000 files (63.4% non-contiguous), 108803625/131072000 blocks



3.检测完磁盘以后打开挂载,并重新挂载,重启系统

# cat /etc/fstab 



#

# /etc/fstab

# Created by anaconda on Thu Aug 14 21:16:42 2014

#

# Accessible filesystems, by reference, are maintained under '/dev/disk'

# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info

#

UUID=94e4e384-0ace-437f-bc96-057dd64f42ee / ext4 defaults,barrier=0 1 1

tmpfs                   /dev/shm                tmpfs   defaults        0 0

devpts                  /dev/pts                devpts  gid=5,mode=620  0 0

sysfs                   /sys                    sysfs   defaults        0 0

proc                    /proc                   proc    defaults        0 0

/dev/xvdb /data ext3 defaults 1 2

/dev/xvdc  /data1 ext3    defaults    0  0



# ll /data

total 0

# ll /data1

total 0



# mount /dev/xvdb /data

# mount /dev/xvdc /data1



重启系统

# reboot

云服务器 linux文件系统异常an error occurren during the file system check导致服务器启动失败的更多相关文章

  1. redhat系统服务器重启后提示An error occurred during the file system check.

    问题描述 浪潮一台NF8480M3外观红灯报警,鉴于无法登陆带外,只能对服务器进行断电重启操作 问题现象 重启后进入开机过程并报错,报错如下内容及图片如下所示,正常来说进入此界面后直接输入root密码 ...

  2. linux系统重启后提示An error occurred during the file system check.

    一.问题描述 生产环境中一台浪潮NF8480M3外观红灯报警,鉴于无法登陆带外管理口,只能对服务器进行断电重启操作 二.问题现象 重启后进入开机过程并报错,正常来说进入此界面后直接输入root密码即可 ...

  3. an error occurred during the file system check错误的解决

    [root@GIT ~]# fsck -A /dev/mapper/VolGroup-lv_root 下面的选择,一路Y就行了,最后reboot,问题解决!

  4. an error occured during the file system check

    打开虚拟机的时候,报错: 出错原因: 我之前修改了/etc/fstab文件, 原先/etc/fstab文件中有一行是这样的: LABEL=/i01              /u01          ...

  5. error occurred during the file system check

    fsck -c 然后一路:y reboot 问题解决!!!

  6. VMware中CentOS6.5启动出现An error occurred during the file system check

     

  7. Error:/etc/fstab:Read-only file system错误的解决办法

    1.挂载60T存储,设置开机自动挂载,UUID编号配置错误导致系统无法启动 2.根据提示进入维护状态,输入root密码,进入fstab删除UUID等内容,结果报错     Error:/etc/fst ...

  8. 解决 docker 报错: Error starting daemon: error initializing graphdriver: backing file system is unsupported for this graph driver

    CentOS 7.5 x64下 sudo yum install docker -y systemctl enable docker systemctl start docker 发现启动失败 jou ...

  9. 报错解决——linux下执行sh出现异常"syntax error: unexpected end of file"

    有时我们在linux下执行一个sh文件,会报错“SYNTAX ERROR:UNEXPECTED END OF FILE”,这个现象主要是工作的系统环境改变造成的. 若最初脚本中是在windows下,使 ...

随机推荐

  1. 网络调试 adb connect

    $su #stop adbd #setprop service.adb.tcp.port 5555 #start adbd 然后在电脑端打开cmd,输入adb命令: #adb connect < ...

  2. 经典的GDB调试命令

    在你调试程序时,当程序被停住时,你可以使用print命令(简写命令为p),或是同义命令inspect来查看当前程序的运行数据.print命令的格式是: printprint /是表达式,是你所调试的程 ...

  3. 树莓派上使用DHCPig进行DHCP池耗尽攻击

    安装DHCPig 这个工具依赖Python的Scapy包,如果未安装需要使用pip工具安装. wget https://github.com/kamorin/DHCPig/raw/master/pig ...

  4. A1084. Broken Keyboard

    On a broken keyboard, some of the keys are worn out. So when you type some sentences, the characters ...

  5. isinstance和issubclass,__getattribute__,__getitem__,__setitem__,delitem__,__str__(三十五)

    isinstance(obj,cls)检查是否obj是否是类 cls 的对象 issubclass(sub, super)检查sub类是否是 super 类的派生类 class Foo: def __ ...

  6. shiro+SpringMVC 项目 配置404页面

    说的配置404,大家都会想到去web.xml里面配置 <error-page> <error-code></error-code> <location> ...

  7. (next_permutation)Ignatius and the Princess II hdu102

    Ignatius and the Princess II Time Limit: 2000/1000 MS (Java/Others)    Memory Limit: 65536/32768 K ( ...

  8. 监听INPUT值的即时变化

    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/ ...

  9. 关于Java形参和实参的理解

    源码地址:https://github.com/mynawang/javabasic-summary/tree/master/chapter01 1.方法的形参中,java的基本数据类型是传值调用,对 ...

  10. Elasticsearch之中文分词器插件es-ik的自定义词库

    它在哪里呢? 非常重要! [hadoop@HadoopMaster custom]$ pwd/home/hadoop/app/elasticsearch-2.4.3/plugins/ik/config ...