Restarted my array to fix a parity drive. Now one drive says "Unmountable: No file system"

[thejellydude]

Not really sure what's going on, but since it's a 12tb drive, I'm hoping it's an easy fix. I was in the middle of a parity rebuild, but I stopped it since I assume missing an entire drive might be important. Are there possibly some commands I can run in terminal to fix things?

nasbox-diagnostics-20210127-0311.zip

[JorgeB]

Check filesystem on disk2.

[JorgeB]

Also some ATA errors on parity, check/replace cables.

[thejellydude]

I just replaced the cable on the parity drive. Are you talking about the 30 UDMA CRC error count?

Also, I'm stuck on the Check Filesystem process. I ran check filesystem, and it looks like I didn't get any errors?

XFS_REPAIR Summary Wed Jan 27 02:59:04 2021 Phase Start End Duration Phase 1: 01/27 02:58:23 01/27 02:58:23 Phase 2: 01/27 02:58:23 01/27 02:58:29 6 seconds Phase 3: 01/27 02:58:29 01/27 02:58:58 29 seconds Phase 4: 01/27 02:58:58 01/27 02:58:59 1 second Phase 5: Skipped Phase 6: 01/27 02:58:59 01/27 02:59:04 5 seconds Phase 7: 01/27 02:59:04 01/27 02:59:04 Total run time: 41 seconds

But the drive still won't mount properly. I then tried to do a repair command, but got "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 delete the log? I feel very out of my wheelhouse here. Thank you again for any and all help.

Edited January 27, 2021 by thejellydude

[JorgeB]

Use -L

[itimpi]

Having to use the -L option is quite normal.   That is mentioned here in the online documentation that can be accessed via the Manual link at the bottom of the unraid GUI.