disk1 Unmountable: Unsupported or no file system

[BTPBen]

My Disk1 on my Array started acting up the other day. I am not really sure the precursor. But now it is showing up as an Unmountable drive. 

 

When I start the array I only get an option to Format the drive. I really don't want to lose all the data on my drive again. I've tried restarting the array in Maintenance Mode and I have run a parity check which came back 8132 errors so, I am kind of hopeful the data is still there. I am just not sure how to recover at this point. 

 

And my brain just said 'if the drive wasn't working and I left "write corrections to parity" checked all my disk1 data is gone isn't it?

 

[JonathanM]

38 minutes ago, BTPBen said:

it is showing up as an Unmountable drive. 

https://docs.unraid.net/unraid-os/troubleshooting/data-recovery/#unmountable-disks

Whatever you do, DON'T format.

[BTPBen]

Thank you, my File system type says xfs but I don't see an mdX 

 

xfs_repair -v /dev/mdX

should I use sde instead of mdX?

 

xfs_repair -v /dev/sdX1

 

[JonathanM]

10 minutes ago, BTPBen said:

should I use sde instead of mdX?

No.

 

Is there a section directly below the screenshot you posted?

[BTPBen]

Okay, I see my confusion: I got confused by the instructions in "checking and repairing" because I was trying to read it all before doing anything.  Ran the repair with the -n, then tried to run it with no options. 

 

Edit: Here are the results of the -n run:

 

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
ignored because the -n option was used.  Expect spurious inconsistencies
which may be resolved by first mounting the filesystem to replay the log.
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan (but don't clear) agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - 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 = 1
        - agno = 3
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
Maximum metadata LSN (1:281984) is ahead of log (1:281875).
Would format log to cycle 4.
No modify flag set, skipping filesystem flush and exiting.

 

and without -n

 

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 am thinking at the point since it's "unmountable" when I start the array I should just run with -L?

 

Edited June 5 by BTPBen

[JonathanM]

16 minutes ago, BTPBen said:

I should just run with -L

this.

[BTPBen]

Worked perfectly!