Disk is unmountable

[logan2020]

I'm running unRAID Server Plus v6.4.1

 

I was copying files to the array. (It contains 7 disks (xfs encrypted) + 1 parity).

 

The system hard locked - I couldn't ping it and couldn't type / login on the console. Had to power down.

 

Powered back on, and tried to start the array. It started running a parity check, but I noticed that Disk 5 was showing as 'Unmountable: No file system', so I stopped the parity check, and stopped the array. 

 

Then I brought it back up in Maintenance Mode, logged in via SSH and attempted to run 'xfs_repair -v /dev/md5', but just get this message: 'xfs_repair: cannot open /dev/md5: Device or resource busy'.

 

What should I do next? (Diagnostics file is attached).

tower-diagnostics-20181008-2109.zip

[JorgeB]

If the disks are encrypted you need to use:

 

xfs_repair -v /dev/mapper/md5

 

Or use the GUI.

[logan2020]

8 hours ago, johnnie.black said:

 

xfs_repair -v /dev/mapper/md5

 

Thanks - running this gives the following output:

 

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

 

Should I run xfs_repair with the -L option?

Edited October 9, 2018 by logan2020
changed quote to code

[JorgeB]

Yes.

[logan2020]

On 10/9/2018 at 9:01 AM, johnnie.black said:

Yes.

Thanks, that fixed it. Managed to run a parity check after and everything is back up.