Alpha.Ars Posted December 11, 2022 Share Posted December 11, 2022 One of my drives died and I replaced it. The drive rebuilded completely and once it was done I got this error: (Unmountable: Wrong or no file system). I started following the spaceinvader's video and saw I had a strage report in the xfs_repair status: Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... would write modified primary superblock Primary superblock would have been modified. Cannot proceed further in no_modify mode. Exiting now. I'm not sure what I'm supposed to do at this point. Could someone guide me a little ? Quote Link to comment
trurl Posted December 11, 2022 Share Posted December 11, 2022 Attach Diagnostics to your NEXT post in this thread Quote Link to comment
Alpha.Ars Posted December 11, 2022 Author Share Posted December 11, 2022 I forgot about it, there you go: arialis-mserver-diagnostics-20221211-1429.zip Quote Link to comment
JorgeB Posted December 11, 2022 Share Posted December 11, 2022 Run xfs_repair again without -n or nothing will be done. Quote Link to comment
Alpha.Ars Posted December 11, 2022 Author Share Posted December 11, 2022 I runned it again without anything: Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... writing modified primary superblock sb realtime bitmap inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 129 resetting superblock realtime bitmap inode pointer to 129 sb realtime summary inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 130 resetting superblock realtime summary inode pointer to 130 Phase 2 - using internal log - zero log... 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. Quote Link to comment
Alpha.Ars Posted December 11, 2022 Author Share Posted December 11, 2022 I will try following the video since this message is similar to the message shown in the video at: 6:56. I'll update when I have something. Quote Link to comment
Solution Alpha.Ars Posted December 11, 2022 Author Solution Share Posted December 11, 2022 I ran the xfs_repair with -L and got verry little files back. Quote Link to comment
trurl Posted December 11, 2022 Share Posted December 11, 2022 post new diagnostics Quote Link to comment
Alpha.Ars Posted December 19, 2022 Author Share Posted December 19, 2022 Sorry, I did not see I got a reply. I went for an old backup I had laying somewhere and thought is was good enough. Thanks for your help! Quote Link to comment
jermcel Posted January 26, 2023 Share Posted January 26, 2023 I am also having an issue of Unmountable: Wrong or no file system on Disk2 of my array. Currently, it is being emulated, but regardless of what I have tried it will not mount.. I attaching my diagnostics on here if someone is able to read and understand what is going on I would appreciate it. Regards, JC tower-diagnostics-20230125-1751.zip Quote Link to comment
JorgeB Posted January 26, 2023 Share Posted January 26, 2023 9 hours ago, jermcel said: Wrong or no file system on Disk2 of my array. Check filesystem on disk2, note that both parity and disk1 appear to be failing. Quote Link to comment
trurl Posted January 26, 2023 Share Posted January 26, 2023 15 hours ago, jermcel said: Currently, it is being emulated What do you mean? Disk2 is not disabled in those diagnostics. It is unmountable though. Good thing it isn't being emulated since your other failing disks would be involved with that. 7 hours ago, JorgeB said: parity and disk1 appear to be failing Disk3 doesn't look too good either. Was disk2 disabled and did you perhaps rebuild disk2 using those other failing disks? That could certainly explain why it is unmountable. How did you let yourself get to this point where you have multiple failing disks? Do you have Notifications setup to alert you immediately by email or other agent as soon as a problem is detected? Do you have backups of anything important and irreplaceable? 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.