Unmountable xfs filesystem, btrfs cache after starting parity protection

[SvbZ3r0]

To start with, I've been using unraid for a while now with 6 disks and no parity. I recently bought 2 new 4TB disks. I swapped two of my old disks out by copying data to one of my new disks, created a new config (had to shuffle the disk order in order to fit the new disks), verified that everthing worked, and then installed the second disk as parity. As soon as it started building the parity disk, one of my older xfs disks and my btrfs cache disk glitched. I immediately paused building the parity.

 

Now, the xfs disk says "unmountable: nofilesystem", and the btrfs disk says "unsupported partition layout".

The btrfs disk is mountable as an unassigned disk, the xfs disk is not.

 

For the xfs disk, I tried running xfs_repair and got this as a result:

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.

 

How do I proceed?

Any help is appreciated. Attached disgnostics.

 

orthanc-diagnostics-20211013-0503.zip

[SvbZ3r0]

Ohh.. There's something in the logs about a duplicate UUID for the unmountable xfs drive.

I tried xfs_admin -U generate to get a new UUID, but it gave the same error about valuable metadata in a log.

Edited October 12, 2021 by SvbZ3r0
Update

[SvbZ3r0]

Follow-up:

Rebooted. xfs drive works again. Automagically.

Btrfs still has problems.

 

I'm still interested in knowing how and why the xfs drive had problems, and what I can do to not repeat that in the future.

[JorgeB]

6 hours ago, SvbZ3r0 said:

a duplicate UUID

This means the same filesystem was already mounted, cache disk is complaining of a non standard partition layout, could be MBR/GPT corruption, post the output of:

 

fdisk -l /dev/sdc

 

[SvbZ3r0]

Hi, I ended up copying all the data to my array and formatting my cache.

So.. Solved. I guess?

Sorry for the trouble.

Thanks for your time.