UNMOUNTABLE: NOT MOUNTED (SOLVED)

[AC-Gamer]

Hey guys , having a bit of an issue I'm hoping you all can help out with. I have a dell r710 I was adding a new 16tb hard drive to and without thinking I removed two hard drives to add more screws to the case since the last time I put them in I was short and only used 1 screw. I should have spun the server down but didn't and when I put them back in they weren't working any more, the array took a couple days to rebuild the drives but now that they are done its saying they are still UNMOUNTABLE: NOT MOUNTED. I found a post about this 

https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui

and spun the server up in maintenance mode to run a xfs test on one of the 2 drives that isn't working, using -nv as it recommends and comes back with the following 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.

 

that forum doesn't cover this response nor did this one that closely resembled my problem

 

 I'm worried about what to do next for risk of losing all the data on them, any help would be greatly appricatated 

 

Edit-- Using -v I got the following

 

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 - block cache size set to 1838016 entries sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 128 resetting superblock root inode pointer to 128 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... zero_log: head block 305435 tail block 305431 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'm a little nervous about doing anything that can result in all the data being lost so forgive me asking for clarification but when it says to unmount and remount the drives is it referring to a command or does it want me to spin down the server and unmount the two drives spin up the server and down again and remount them? if so I've done this once before when the drives stopped working the first time showing the unmountable message and that's what prompted the parity rebuild. Should I do it again? or should I use the -L to force it and patiently risk a lose of data as a last resort?

 

Second Edit, spun the server down out of maintenance and back into normal mode and one of the two drives mounted and is fully working, should I use the -L for the last remaining drive not working?

Edited November 14, 2022 by AC-Gamer

[JorgeB]

1 hour ago, AC-Gamer said:

Second Edit, spun the server down out of maintenance and back into normal mode and one of the two drives mounted and is fully working, should I use the -L for the last remaining drive not working?

If xfs_repair - v asks for -L use it.

[AC-Gamer]

Went ahead and ran the -L as you suggested 

 

Phase 1 - find and verify superblock... sb root inode value 18446744073709551615 (NULLFSINO) inconsistent with calculated value 128 resetting superblock root inode pointer to 128 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... 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... sb_icount 0, counted 15744 sb_ifree 0, counted 295 sb_fdblocks 2929199537, counted 27301763 - 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 - process newly discovered inodes... Phase 4 - check for duplicate blocks... - setting up duplicate extent list... - check for inodes claiming duplicate blocks... - agno = 0 - agno = 1 - agno = 6 - agno = 8 - agno = 7 - agno = 5 - agno = 2 - agno = 9 - agno = 3 - agno = 10 - agno = 4 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:152289) is ahead of log (1:2). Format log to cycle 4. done

 

I shut down the array and brought it back up and all is well in the world, I cant thank you enough for this jorgeB, I know my problem was a lot like the others but pulling the trigger on something like this and potentially losing so much data is nerve racking, having you guys here to ask for help but more so reassurance we are doing the right thing is incalculable. Thank you again Jorge I cant say that enough.