磁盘挂载失败:mount: wrong fs type, bad option, bad superblock on /dev/vdb1 故障排除-Toy模板网

这篇具有很好参考价值的文章主要介绍了磁盘挂载失败:mount: wrong fs type, bad option, bad superblock on /dev/vdb1 故障排除。希望对大家有所帮助。如果存在错误或未考虑完全的地方，请大家不吝赐教，您也可以点击"举报违法"按钮提交疑问。

1. 故障现象

磁盘挂载失败:mount: wrong fs type, bad option, bad superblock on /dev/vdb1 故障排除,Linux,linux,运维,服务器


mount: wrong fs type, bad option, bad superblock on /dev/vdb1,
       missing codepage or helper program, or other error

       In some cases useful info is found in syslog - try
       dmesg | tail or so.

2. 故障排除

造成这个故障是因为原来内网的服务器上阿里云.在内网时是用的vg,用SMC上云之后VG就不再支持,默认被转成了vdb1,格式还是xfs
使用命令查看详细报错

dmesg | tail

获取到以下报错

[ 2084.391811] XFS (vdb1): Mounting V5 Filesystem
[ 2084.404936] XFS (vdb1): Corruption warning: Metadata has LSN (2077:25717) ahead of current LSN (1:2). Please unmount and run xfs_repair (>= v4.3) to resolve.
[ 2084.406745] XFS (vdb1): log mount/recovery failed: error -22
[ 2084.407574] XFS (vdb1): log mount failed

那么就尝试修复.

 xfs_repair /dev/vdb1

经过几秒的修复过程

# xfs_repair /dev/vdb1
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan and clear agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - agno = 4
        - agno = 5
        - agno = 6
        - agno = 7
        - agno = 8
        - agno = 9
        - agno = 10
        - agno = 11
        - agno = 12
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 4
        - agno = 8
        - agno = 3
        - agno = 6
        - agno = 5
        - agno = 1
        - agno = 7
        - agno = 9
        - agno = 10
        - agno = 2
        - agno = 11
        - agno = 12
Phase 5 - rebuild AG headers and trees...
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
Maximum metadata LSN (2077:25717) is ahead of log (1:2).
Format log to cycle 2080.
done