After replacing a poor drive last week and finishing a parity check I noticed 3 drives were Unmountable: Unsupported or no file system

At first, I had the option to check the file system on them but not anymore. It's there for the other drives. The output mentioned incorrect UUID. I foolishly thought I could fix it by doing a new config. So my parity drives are wiped.

 

I've tried XFS Repair via command line but I can't seem to mount the drive, most likely doing it wrong.

 

 

Can someone advise, please?

 

tower-diagnostics-20240922-1506.zip

If you stop the array and change the file system to explicitly be ‘xfs’ and then restart the array the check file system option will be there.

Thanks. That got the repair file system back. I'm getting mismatched uuid on all 3. Can you advise what to do next, please?

 

Phase 1 - find and verify superblock...
        - block cache size set to 143776 entries
Phase 2 - using internal log
        - zero log...
* ERROR: mismatched uuid in log
*            SB : acb55318-7711-4ec0-af30-6b10e819cd29
*            log: 7e311a51-b254-420b-9a69-a20ba0c01b5f
zero_log: head block 44243 tail block 44239
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.

 

2 hours ago, T800 said:

'm getting mismatched uuid on all 3.

That's kind of strange, but the only option is to continue with -L to see if it can be corrected.

Thanks. Ran that on all 3. Two came fixed but lost the data, one wouldn't fix.

For the one that failed, if there's no backup, you can try a file recovery app like UFS explorer, it may be able to recover most data.

Luckily on Friday before all this happened, Disk 10 (the one that has failed now) was swapped out due to an error so I still have it full with no changes so I'll swap it with that for now. 

1 hour ago, T800 said:

I still have it full with no changes so I'll swap it with that for now. 

What exactly do you mean by that? If you put that drive back in Unraid while parity is valid Unraid will overwrite it with the emulated unmountable data currently there.

I don't have valid parity. I mistakingly did a new config trying to fix this issue. 

As long as no parity slots are occupied you can add the drive back without issue.

I added the drive back but that also said Unmountable. This time I removed it from the array and repaired the file system via Unassigned devices and it fixed it and didn't lose any data from it.