July 30, 20223 yr 自从升级到6.10.x后,Docker和VM经常崩溃,并且有这样的提示。 实在找不到解决方法,尝试重装Unraid,重装后,第一块主硬盘显示Unmountable: Wrong or no file system 我需要怎样做才能拯救回我的数据? 我尝试在维护模式下启动了阵列,并且对disk1进行了check file system的操作, 加了-nv参数, 得到以下的报告。 Edited July 30, 20223 yr by eplang
July 31, 20223 yr I see that you emailed support and @ManuelR replied to you. Are you still having issues?
July 31, 20223 yr Author 1 hour ago, AndrewZ said: I see that you emailed support and @ManuelR replied to you. Are you still having issues? The problem still exists. I tried using this command and got a report like this, I don't know what to do next. root@eplangNAS:~# xfs_repair -v /dev/md1 Phase 1 - find and verify superblock... - block cache size set to 2988832 entries Phase 2 - using internal log - zero log... zero_log: head block 2966631 tail block 2959032 ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this.
July 31, 20223 yr Author Solution 9 minutes ago, JorgeB said: Use -L thank you very much, i got the disk1 back.
October 24, 20223 yr On 7/31/2022 at 2:29 AM, eplang said: 自从升级到6.10.x后,Docker和VM经常崩溃,并且有这样的提示。 请问楼主,如何解决这个问题,我最近也遇到了。研究两天了。里面有很多数据。很烦躁。谢谢!
December 9, 20223 yr On 10/25/2022 at 1:44 AM, kai666 said: 我遇到和楼主一样的问题,虚拟机是放在那块磁盘里的,显示Unmountable,执行xfs_repair -v /dev/md1, 返回结果和楼主的一致,然后加上- L参数,xfs_repair -v -L /dev/md磁盘,重启整列就好了,但是不知道什么原因。。。
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.