Hi,

I am kind of new to unraid and my server was running perfectly fine for a long time.
But after I upgraded from 7.1.3 to 7.2.2 a message appeared on one of my drives, when I start the array: Unmountable: wrong or no file system. It is one of the two data drives in my array.

If i check the xfs_repair status, it says:

Phase 1 - find and verify superblock... couldn't verify primary superblock - not enough secondary superblocks with matching geometry !!! attempting to find secondary superblock...

Even when the repair finishes, nothing happens.

Has someone any ideas on how to fix it? And hopefully without losing the data on this drive😱

I also attached a diagnostics file, that can maybe help with a solution or find the reason this happen in the first place.

Thank you very much in advance🫶 and a happy new year!

unraidnas-diagnostics-20251217-2058.zip

Edited January 1Jan 1 by Tyrus

7 minutes ago, Tyrus said:

If i check the xfs_repair status

Exactly how did you do this? Very easy to get the command line wrong. You should use the webUI to check filesystem.

1 hour ago, trurl said:

Exactly how did you do this? Very easy to get the command line wrong. You should use the webUI to check filesystem.

I put the array in maintenance mode, went to the drive and under settings i pressed the "check" button under the "check file system" menu. It ran for a long time and the button changed to "fix" but it didn't do anything as far as I can tell, even though it ran againg for a long time, after pressing the "fix" button.

Edited January 1Jan 1 by Tyrus

Have you restarted the array in normal mode?

yes, it's still showing up as unmountable.

Disk2 is being detected as precleared, assuming that was not done recently, the issue comes from before.

post the output from fdisk -l /dev/sdb

9 hours ago, JorgeB said:

Disk2 is being detected as precleared, assuming that was not done recently, the issue comes from before.

post the output from fdisk -l /dev/sdb

Before the update the disks weren't showing any errors or messages and worked fine.

I tried to run the "check file system" thing again and pressed fix. When it finished it said "File system corruption detected." and I could press "fix" again and it started an other round of "fixing" and it is running now. But I tried all of this before.

This is what fdisk -l /dev/sdb said:

Disk /dev/sdb: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors

Disk model: ST4000NE001-2MA1

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 4096 bytes

I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disklabel type: dos

Disk identifier: 0x00000000

Device Boot Start End Sectors Size Id Type

/dev/sdb1 1 4294967295 4294967295 2T 0 Empty

Edited January 2Jan 2 by Tyrus

That confirms the disk has a precleared partition layout; it's not even using the full disk, and I don't see how that could be related to the upgrade, but, if parity was valid, you can try rebuilding the disk, that would make Unraid recreate the partition correctly.

To try, unassign that disk, start the array and post new diags.

P.S. Don't start to rebuild on top of the old disk if the emulated disk doesn't mount.

I understand that the disk seems to be only precleared without any data but it wasn't showing up like that before the update.
And I have also been copying data on the disk, since the other (sdc) is full. If it has been running in emulated mode the whole time, shouldn't it have said so?

unraidnas-diagnostics-20260103-1142.zip

Edited January 3Jan 3 by Tyrus

1 hour ago, Tyrus said:

If it has been running in emulated mode the whole time, shouldn't it have said so?

The disk wasn't being emulated; only now it is.

With the array running, post the output from

xfs_repair -v /dev/md2p1

I don't understand how it was running before then. Because as far as I could tell, no data was missing.

Started the command. Will report as soon as it finishes.

EDIT:
Sorry, could not find valid secondary superblock

Exiting now.

Edited January 3Jan 3 by Tyrus

On 1/3/2026 at 12:43 PM, JorgeB said:

The disk wasn't being emulated; only now it is.

With the array running, post the output from

xfs_repair -v /dev/md2p1

So, the command wasn't able to fix this.

And I have done some digging and I am missing files for sure that were on this drive.

So I have started thinking about the pre-cleared state.
And the only time the drive was precleared was when I updated my parity disc to an 8TB drive and used the old parity drive as a second hdd(sdb) in the array. I followed the official instructions HERE
But after that, the drive was working and I copied files to the larger array which were also on the "new"(sdb) drive, since the other, original drive(sdc) was full.
The only problem I had was, that I had tons of parity errors. Like 50+mil.

Could it be that by fixing the parity problems, the drive was put back in the pre-cleared state because I messed something up?
That was also around the time I did the update. But there was still no error showing up. The error "Unmountable: wrong or no file system" appeared only after the update. Could it be that the restart needed for the update triggered an issue that would have shown the error even with a "normal" system restart?

Edited January 5Jan 5 by Tyrus

24 minutes ago, Tyrus said:

I updated my parity disc to an 8TB drive and used the old parity drive as a second hdd(sdb) in the array. I followed the official instructions HERE

That link discusses a lot of things so it isn't clear what exactly you did.

Do you mean you did parity swap?

23 minutes ago, trurl said:

That link discusses a lot of things so it isn't clear what exactly you did.

Do you mean you did parity swap?

Yes, exactly! Sorry I haven't specified it further.

If you had parity errors after doing parity swap you must have made a mistake somewhere.

Do you still have the original data disk from before the parity swap?

21 hours ago, trurl said:

Do you still have the original data disk from before the parity swap?

Yes, the original Data-Disc from the "old" array is, sdc(4tb). sdb(4tb) was the old parity disc. sdb is the one that is now pre-cleared. And the new parity disc is sde(8tb)

As far as my knowledge goes, the data on sdb is lost, isn't it? Luckily it's not thaaat bad. All the important stuff is on "sdc" and the stuff that was copied on sdb can mostly be redownloaded. If I am not missing some crucial files, that i copied on the NAS at the time, and forgot about...

Edited January 6Jan 6 by Tyrus

You can mount the original data disk with Unassigned Devices and copy its data to the array.

Alternatively, you could New Config the original disk back into the array and rebuild parity.

I don't understand how that would work.

My old array was sdc as data and sdb as parity. Everything was fine with that.

Than I swapped the parity(sdb) with a new one(sde) and used the old parity(sdb) as an additional data disc on the array.

My current array is sdb + sdc = data drives and sde as parity.
This array had over 50 million parity errors and when I fixed them, it looks like I killed all the data on (sdb). So I am not sure where the parity information should come from, to restore the data. Or am I missing something?

2 minutes ago, Tyrus said:

Than I swapped the parity(sdb) with a new one(sde) and used the old parity(sdb) as an additional data disc on the array.

This would normally be done as two separate steps. Did you do it some other way (e.g used the New Config tool).

Can you mount the original data disk as an Unassigned Device?

3 minutes ago, itimpi said:

This would normally be done as two separate steps. Did you do it some other way (e.g used the New Config tool).

I followed the parity swap instruction but probably messed something up. It was a while ago(in november) so I don't remember the details anymore... The array was working fine without errors or emulation. But something wasn't right with the new parity drive.

2 minutes ago, trurl said:

Can you mount the original data disk as an Unassigned Device?

I can. But what should I do afterwards?

Edited January 6Jan 6 by Tyrus

Try to mount the original disk as an unassigned device and see if you can read its data.

1 minute ago, trurl said:

Try to mount the original disk as an unassigned device and see if you can read its data.

It works but the data on the original disk was luckily never a problem. The problem is only with the new drive that I added to the array and the data that was on it.

Post new diagnostics and tell me which disk is the Unassigned.