Okay I'll give context to all this because this is really annoying me at this point and I really want to resolve this and get back to working on other things. This is what I get for wanting a storage solution for my photos and videos. (I'm a photographer/videographer).

Anyway, I had a 8TB drive that had an error on it that caused me to rebuild the drive. It worked for about 2 weeks and then it said it was "Unmountable: wrong or no file system". So I said screw it, instead of trying to fix it, I'll replace the drive with a 12TB drive. So I put this new 12TB in and rebuilt the drive. I didn't preclear or format the drive before rebuilding and it still says it's "Unmountable: wrong or no file system".

So I know from the main page that I can format the drive, my issue is the warning that comes up before I format it. There's one line that says "discarding all data currently on the disks and update parity to reflect this." So will parity be updated and remove all the data that was on the 8TB drive? (it was almost full) Am I understanding this correct? If so, what is the next course of action?warlock-diagnostics-20250726-0050.zipwarlock-smart-20250726-0048.zip

Rebuilding an unmountable disk will result in another unmountable disk.

Jul 26 00:34:58 Warlock kernel: XFS (md4p1): Corruption detected. Unmount and run xfs_repair

Check filesystem for disk4

16 hours ago, JorgeB said:

Check filesystem for disk4

So after some reading, I did a check of the drive via the GUI and I got this output...

I've yet to click the "fix" button in the GUI under "Check Filesystem Status"

Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
ALERT: The filesystem has valuable metadata changes in a log which is being
ignored because the -n option was used.  Expect spurious inconsistencies
which may be resolved by first mounting the filesystem to replay the log.
        - scan filesystem freespace and inode maps...
agf_freeblks 2271491, counted 2271401 in ag 4
agf_freeblks 1876851, counted 1876759 in ag 6
block (2,80781038-80781199) multiply claimed by cnt space tree, state - 2
agf_freeblks 4125404, counted 4125712 in ag 2
agf_freeblks 519469, counted 519516 in ag 7
agf_freeblks 1871672, counted 1871668 in ag 5
agf_freeblks 2316713, counted 2316761 in ag 1
agf_freeblks 13222371, counted 13222420 in ag 3
sb_fdblocks 20450170, counted 34075088
        - found root inode chunk
Phase 3 - for each AG...
        - scan (but don't clear) agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
data fork in ino 3129813387 claims free block 393742246
data fork in ino 3263282003 claims free block 407656320
        - agno = 2
data fork in ino 4321751974 claims free block 540216784
data fork in ino 4321751976 claims free block 540217030
data fork in ino 4321751979 claims free block 540216224
data fork in ino 4321751981 claims free block 540211746
data fork in ino 4321751983 claims free block 618228804
data fork in ino 4321751988 claims free block 540216932
data fork in ino 5188886533 claims free block 648680731
        - agno = 3
data fork in ino 6451319329 claims free block 822665964
data fork in ino 6451319331 claims free block 821131745
data fork in ino 6451319333 claims free block 820201564
data fork in ino 6451319335 claims free block 824908196
        - agno = 4
data fork in ino 9389366867 claims free block 1206826617
data fork in ino 9389366869 claims free block 1168505373
data fork in ino 9389366869 claims free block 1168505515
data fork in ino 9389366876 claims free block 1168510252
        - agno = 5
        - agno = 6
data fork in ino 13180588852 claims free block 1619548451
        - agno = 7
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
free space (2,1802628-1802669) only seen by one free space btree
free space (2,3345611-3345842) only seen by one free space btree
free space (2,80781200-80781324) only seen by one free space btree
free space (2,111656941-111657049) only seen by one free space btree
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 4
        - agno = 1
        - agno = 3
        - agno = 2
        - agno = 6
        - agno = 5
        - agno = 7
setting reflink flag on inode 6451319323
setting reflink flag on inode 6451319337
setting reflink flag on inode 15101598200
Missing reference count record for (3/16405905) len 115 count 2
Missing reference count record for (4/94768151) len 277 count 2
Missing reference count record for (7/39302994) len 137 count 2
setting reflink flag on inode 15214246528
setting reflink flag on inode 15214246552
setting reflink flag on inode 15214246564
setting reflink flag on inode 9359712613
setting reflink flag on inode 9359712618
setting reflink flag on inode 9389366871
setting reflink flag on inode 9389366874
setting reflink flag on inode 9389366876
No modify flag set, skipping phase 5
Phase 6 - check inode connectivity...
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify link counts...
No modify flag set, skipping filesystem flush and exiting.

If it's not obvious, you need to click the FIX button.

Every time I think I have a handle on things I seem to make a mistake. So I wanted to make sure.

I pressed the FIX button and now the drive is rebuilding.

Can you expand on that? The FIX button will try to repair the filesystem, not rebuild the disk.

Yes, after I pressed the FIX button it did it's thing and I decided to check it again. This check came up with no problems so I started a rebuild. Currently it's 50% rebuilt and doesn't have the "Unmountable" warning next to the disk.

Edited July 28, 2025Jul 28 by Herdie27

Right, the disk was still disabled, but if it's mounting now it should be OK. Any errors during the rebuild post new diags.

😬 aaah okay. If any errors I'll let you know, thanks so much for your help!

No errors during rebuild. Checked the log as well and didn't see anything wrong. Everything looks to be back to normal.