My cache drive (an xfs-formatted ADATA SSD) is showing as unmountable.  I'm wondering if there's a way to try to recover any data that was on it (including a couple of VMs and my Plex server data).

 

Background:

I just returned from a long trip.  My array was up, but everything was spun down...even the cache drive.  I was able to open a share from Windows and move some files to it, but when I tried to start one of the VMs (that I had shut down prior to my trip), I got an Execution Error stating that the VM file(s) could not be found.

 

That's when I noticed that the cache was spun down.  I went into the config to set is spin down to "never" hoping that would bring it back up, but that didn't work.  I think stopped the array and started the array again.  All my shares appeared in Windows except cache.  Then I noticed that cache was saying unmountable.

 

I've tried rebooting the server, but the cache is still unmountable.

 

I'm hoping there will be a way to try to save any data that was on the drive.

 

Any help would be appreciated.  The disk log info is attached.  Note lines 17 and 37 are marked as errors.

 

Thanks in advance.

disk_log_info.txt

unraid wiki check disk filesystems

Stop the array and run:

 

xfs_repair -v /dev/sdh1

Thanks @trurl and @johnnie.black

 

I've attached the output of the check (-nv)

 

I'll admit, I'm a bit concerned by "Inode allocation btrees are too corrupted, skipping phases 6 and 7"

check_results.txt

Remove the n from the command.

Remove the n from the command.

 

Here's the output.  Should I do the -L option?

 

Phase 1 - find and verify superblock...
        - block cache size set to 1529792 entries
Phase 2 - using internal log
        - zero log...
zero_log: head block 254699 tail block 252947
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.

Yes

@johnnie.black, Thanks!  Things are looking good.  VMs are running and Plex seems to be good. 

 

Thanks!