zbarisopen Posted October 28, 2022 Share Posted October 28, 2022 (edited) Attached are the diagnostics, I tried to reboot with no luck. Any help is much appreciated! Two disks now have "Unmountable: Wrong or no file system" - two disks at one time and I have only a single parity. zbaraid-diagnostics-20221028-1234.zip Edited October 28, 2022 by zbarisopen Quote Link to comment
JorgeB Posted October 29, 2022 Share Posted October 29, 2022 Check filesystem on both. Quote Link to comment
zbarisopen Posted October 29, 2022 Author Share Posted October 29, 2022 (edited) Thanks! I tried that and got this error on both drives: Phase 1 - find and verify superblock... - block cache size set to 536592 entries Phase 2 - using internal log - zero log... zero_log: head block 998348 tail block 998344 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. xfs_repair -v /dev/md4 Phase 1 - find and verify superblock... - block cache size set to 536592 entries Phase 2 - using internal log - zero log... zero_log: head block 998348 tail block 998344 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. I also did the extended smart test on both drives with 0 errors. Edited October 29, 2022 by zbarisopen Quote Link to comment
Solution ChatNoir Posted October 29, 2022 Solution Share Posted October 29, 2022 5 hours ago, zbarisopen said: If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Quote Link to comment
zbarisopen Posted October 30, 2022 Author Share Posted October 30, 2022 It worked! Both drives are back. Thank you!!!!!!!! 2 Quote Link to comment
Recommended Posts
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.