XFS Cache drive unmountable after power reset

[tr0910]

Because of some router issues, I had to power cycle my unRaid b6v14b

 

It came back up with an unclean shutdown as expected, but the XFS cache drive is unmountable.  With Reiser we know what to try, but what is the process to try and fix an XFS drive??  The cache drive only contains my dockers.

 

I will move to rc1 once we fix this little issue.

[tr0910]

So xfs_repair reports the following.  If unRaid 6b15 or 6rc2 both find the drive unmountable, should I mount outside of unRaid to attempt to repair??

 

Or just destroy the log and move on???

 

root@SandBox:~# fdisk -l /dev/sdb

Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
1 heads, 32 sectors/track, 122094661 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1              64  3907029167  1953514552   83  Linux
root@SandBox:~# xfs_repair /dev/sdb1
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.
root@SandBox:~#

[tr0910]

So xfs_repair reports the following.  If unRaid 6b15 or 6rc2 both find the drive unmountable, should I mount outside of unRaid to attempt to repair??

 

So how would I mount a cache drive for XFS_Repair that rc2 claims is unmountable??

[tr0910]

So I ran XFS_Repair zeroing the log and got the cache drive back working.  All the data seems to be there and there is a lost+found directory with 10 files in it.  But now Docker doesn't want to start.  I'll create a post over there to see if we can get them back working.