debian文件系统变成只读了…Read-only file system

共计 4408 个字符，预计需要花费 12 分钟才能阅读完成。

网友回复：

注册 ： mount -o remount, rw /

ultramancliub： 服务器在德国 HZ，经历了一次不正常的机房断电，就这样了。

AD 盖 ： mount: /: mount point not mounted or bad option. 复制代码

ultramancliub： 先 lsblk, 查看是根分区是挂在哪块硬盘上，然后 / 改成对应设备目录 (/dev/xxx)

ultramancliub： lsblk NAME        MAJ:MIN RM  SIZE RO TYPE  MOUNTPOINT nvme0n1     259:0    0  3.5T  0 disk ├─nvme0n1p1 259:1    0    2G  0 part │ └─md0       9:0    0    4G  0 raid0 [SWAP] ├─nvme0n1p2 259:2    0  512M  0 part │ └─md1       9:1    0  511M  0 raid1 /boot ├─nvme0n1p3 259:3    0  3.5T  0 part │ └─md2       9:2    0    7T  0 raid0 / └─nvme0n1p4 259:4    0    1M  0 part nvme1n1     259:5    0  3.5T  0 disk ├─nvme1n1p1 259:6    0    2G  0 part │ └─md0       9:0    0    4G  0 raid0 [SWAP] ├─nvme1n1p2 259:7    0  512M  0 part ├─nvme1n1p3 259:8    0  3.5T  0 part │ └─md2       9:2    0    7T  0 raid0 / └─nvme1n1p4 259:9    0    1M  0 part 复制代码 目前是这样的，软 RAID0

AD 盖 ： 将 / 改为 /dev/md2 重新挂载

ultramancliub： 检查下分区和盘是否有损坏。。。进 ro 是一种保护措施。。。大概跟主板防呆插口一样。防呆插口插不上不要大力出奇迹哦

AD 盖 ： [email protected]:~#  mount -o remount, rw /dev/md2 mount: /dev/md2: mount point not mounted or bad option. [email protected]:~#  mount -o rw /dev/md2 mount: /: /dev/md2 already mounted on /. [email protected]:~#  mount -o remount, rw /dev/md2 mount: /dev/md2: mount point not mounted or bad option. 复制代码 还是和“/”一样的结果，

zccyun： 就是坏了，要修复才会恢复。

注册 ： 目录内容都在。目前只读状态下可以通过什么命令检查磁盘？

注册 ： mount -o remount, rw /dev/md2 / 这样试下

ultramancliub： 这种情况直接发 TK 啊

AD 盖 ： 映象中 fsck 解决吧，当然，fsck 完也可能就彻底挂了 赶紧备份，然后 fsck，然后再不行重新安装吧

mix： mount -o remount, rw /dev/md2 / mount: bad usage Try ‘mount –help’ for more information. 复制代码 魔怔了

sdqu： 我目前服务器还是可以正常启动进入 ROOT。在这个状态下执行 FSCK？

ultramancliub： 多打了个空格

ultramancliub： dmesg -C;  mount -oremount,rw /; dmesg

Damenly： 最好是在单用户模式下执行 fsck，正常模式下文件系统直接挂掉，我干过这蠢事。不过已经 ro 了也许可以，不是太确定。反正备份是王道了。

Damenly： mount -o remount,rw /dev/md2 / mount: /: mount point not mounted or bad option. [email protected]:~# mount -o remount,rw /dev/md2 / mount: /: mount point not mounted or bad option. [email protected]:~# mount -oremount,rw / mount: /: mount point not mounted or bad option. [email protected]:~# mount -oremount,rw /dev/md2 / mount: /: mount point not mounted or bad option. 复制代码 还是一样的提示。

注册 ： 嗯，HZ 的 AX101 物理服务器，有上周的数据备份，近 3 周没有进行过网站数据更新。

注册 ： 那就先 ro 的情况下备好份，然后申请 kvm 进去修，或者直接重装。文件系统出问题和硬盘有坏道一样，就算修好了，心里也有疙瘩。

ultramancliub： fsck -y /dev/md2 fsck from util-linux 2.33.1 e2fsck 1.44.5 (15-Dec-2018) /dev/md2 contains a file system with errors, check forced. Pass 1: Checking inodes, blocks, and sizes Inodes that were part of a corrupted orphan linked list found.  Fix? yes Inode 38207491 was part of the orphaned inode list.  FIXED. Inode 38207492 was part of the orphaned inode list.  FIXED. Inode 38207493 was part of the orphaned inode list.  FIXED. Inode 38207494 was part of the orphaned inode list.  FIXED. Inode 38207495 was part of the orphaned inode list.  FIXED. Inode 38207496 was part of the orphaned inode list.  FIXED. Inode 38207497 was part of the orphaned inode list.  FIXED. Inode 66977981 was part of the orphaned inode list.  FIXED. Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Block bitmap differences:  -272703720 -272704090 -273208010 -(273711520–273711535) -273718089 -273731985 -274641818 -(276865984–276865999) -(305702159–305702161) -307003252 -535873457 -535891462 -(799060000–799060004) Fix? yes Free blocks count wrong for group #8322 (22302, counted=22304). Fix? yes Free blocks count wrong for group #8337 (29714, counted=29715). Fix? yes Free blocks count wrong for group #8353 (30875, counted=30893). Fix? yes Free blocks count wrong for group #8381 (1832, counted=1833). Fix? yes Free blocks count wrong for group #8449 (13551, counted=13567). Fix? yes Free blocks count wrong for group #9329 (9397, counted=9400). Fix? yes Free blocks count wrong for group #9368 (511, counted=512). Fix? yes Free blocks count wrong for group #16353 (14918, counted=14919). Fix? yes Free blocks count wrong for group #16354 (12740, counted=12741). Fix? yes Free blocks count wrong for group #24385 (21575, counted=21580). Fix? yes Free blocks count wrong (1456744708, counted=1456744757). Fix? yes Inode bitmap differences:  -(38207490–38207497) -66977981 Fix? yes Free inodes count wrong for group #9328 (4074, counted=4082). Fix? yes Free inodes count wrong for group #16352 (90, counted=91). Fix? yes Free inodes count wrong (234070322, counted=234070331). Fix? yes /dev/md2: ***** FILE SYSTEM WAS MODIFIED ***** /dev/md2: ***** REBOOT SYSTEM ***** /dev/md2: 179909/234250240 files (0.6% non-contiguous), 417246411/1873991168 blocks [email protected]:~# mount -o rw /dev/md2 / mount: /: /dev/md2 already mounted on /. 复制代码 最后在无法卸载分区的情况下执行磁盘修复命令解决问题。

sdqu： 搞定就好 应该是因为是在 ro 模式下，所以 fsck 成功了。

ultramancliub： 谢谢各位小伙伴们的友情协助。