Unmountable: No file system

[kjclark23]

I noticed that some of my movies were having playback errors to find they all came to one disc.  So I restarted the server just to see if that would do anything, and it made my Disc 1 to be unmountable: no file system.  I tried to follow some forums on here that had this but I believe I missed something.  The drive is now getting the data rebuild, while still being unmountable: no file system.  I have no clue what to do here, but I'm freaking out that I just lost 6TB of data.  Any help?

 

I tried doing the xfs_repair -vL /dev/md1, it didn't do anything, couldn't find anything.  I did this after taking the drive out to emulate it.  I then added the drive back and started the array, which is where it is at now.  Says the drive now needs formatted too.

[trurl]

Attach Diagnostics to your NEXT post in this thread. 

[kjclark23]

Yep, that's important.

gamingnas-diagnostics-20240307-2144.zip

[JorgeB]

Let the rebuild finish, then start the array in maintenance mode and check filesystem on disk1 using the GUI, run it without -n

[kjclark23]

Did the check without -n (leaving it blank).  Got this response:

Phase 1 - find and verify superblock... 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.

 

I assume I should go ahead and do the Check with -L option but would like to hear from you first.  

[trurl]

2 hours ago, kjclark23 said:

do the Check with -L option

Yes

[kjclark23]

Finished. This is the output.

 

Phase 1 - find and verify superblock... Phase 2 - using internal log - zero log... ALERT: The filesystem has valuable metadata changes in a log which is being destroyed because the -L option was used. - scan filesystem freespace and inode maps... clearing needsrepair flag and regenerating metadata - 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 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 2 - agno = 5 - agno = 3 - agno = 4 - agno = 1 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 (1:569424) is ahead of log (1:2). Format log to cycle 4. done

 

Sorry if it's obvious, but what do I do next?  I really don't want to mess this up.

[itimpi]

Restart the array in normal mode and the drive should now mount.

[trurl]

11 minutes ago, itimpi said:

Restart the array in normal mode and the drive should now mount.

Then post new diagnostics

[kjclark23]

Thank you very much.  This was a lot simpler than I took it.  wow.  Is there anything I should do now?

gamingnas-diagnostics-20240308-1912.zip

Edited March 9 by kjclark23

[trurl]

Nothing in lost+found so should be good.

[kjclark23]

Thank you everyone for helping me through this.  I feel very dumb now, but I was too afraid to do anything without someone else also saying to do that.  Mighty thanks!