Hello, first time poster. I originally asked on the Discord server but was directed to post here with the diagnostics info. Not sure how much info I should include in this body so I'll take it from the top. I have a brand new Unraid server, so there is no data on any of the disks. Both drives are brand new, tested perfectly good in crystaldisk before I put them in the server, and did not have any errors when I tested them with the SMART extended self test tool. As troubleshooting 101 I replaced the sata cables for the hard drive and uplugged and replugged everything in just to try and rule out a hardware issue.

Went to run xfs repair after putting the array in maintenance mood and only got this

Phase 1 - find and verify superblock...
bad primary superblock - bad magic number !!!

attempting to find secondary superblock...
warning: device is not properly aligned /dev/md1p1
..Sorry, could not find valid secondary superblock
Exiting now.

Tried reading around for similiar issues. Went to the CLI and ran

xfs_repair -L /dev/sdb

Phase 1 - find and verify superblock...

bad primary superblock - bad magic number !!!

attempting to find secondary superblock...

with it infinitely printing . after, I assume indicating its searching through the data. Anyhow it doesn't seem to work.

Thank you in advance for your help.

brunhild-diagnostics-20260529-2238.zip

15 minutes ago, Draxis said:

xfs_repair -L /dev/sdb

That is the wrong command. For a disk not in the array, you must specify the partition, such as /dev/sdb1. But, for a disk in the array, you must specify the md device, such as /dev/md1p1, or you will invalidate parity. Better to use the webUI, it will use the correct command.

What do you get from command line with this?

fdisk -l /dev/sdb

Start the array in normal (not maintenance) mode and post new diagnostics.

Apologies, I'm not sure how to run those commands in the WebUI. For right now ran the command in the CLI and got thebrunhild-diagnostics-20260529-2324.zip following:

Disk /dev/sdb: 10.91 TiB, 12000138625024 bytes, 23437770752 sectors

Disk model: ST12000NT001-3MD

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: gpt

Disk identifier: 3D1C1F05-062A-42FA-8C46-B03907040601

Device Start End Sectors Size Type

/dev/sdb1 34 32767 32734 16M Microsoft reserved

Partition 1 does not start on physical sector boundary.

Heres the new diagnostic data.

Thank you again for the help.

Click on the disk name "Disk1" or whatever the problematic disk is and there will be a repair button. Yours will say "Repair" instead of check

As a quick update since there was some back and forth on the Discord:

Tried running xfs_repair -n /dev/md1p1

It produces the same result of the XFS repair tool from the WebGUI
Phase 1 - find and verify superblock...

bad primary superblock - bad magic number !!!

attempting to find secondary superblock...

warning: device is not properly aligned /dev/md1p1

..Sorry, could not find valid secondary superblock

Exiting now.

Then tried "wipefs /dev/md1p1" but it just produces a blank line

40 minutes ago, Draxis said:

Then tried "wipefs /dev/md1p1" but it just produces a blank line

That means there's no filesystem on that sector.

3 hours ago, Draxis said:

/dev/sdb1 34 32767 32734 16M Microsoft reserved

This partition is too small for Unraid to format it.

If there's no data, you can just reformat it, but I would need to erase it first, Tools - New Config - Keep All - Apply

Then back on main, all disks should have a blue icon. Click on disk1 and "ERASE", then start the array and reformat it (a new parity sync will start)

Thank you! The drive was reformatted correctly this time. Wish I knew what caused it t fail the first time, but hey, if it's working it's working!