I added a brand new drive to the array and now it's giving "Unmountable: wrong or no file system". I've tried starting the array in maintenance mode and running the Check on Drive 5 (the new drive) and it just writes infinite "." over and over again.

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

attempting to find secondary superblock...
............................................

Steps:

1) Shutdown the array.

2) Added new drive to the chassis.

3) Started up the server.

4) Stopped the array.

5) Added the new drive to the array.

6) Started the array.

• new drive showed in blue status and the filesystem was "auto" for some reason.

7) waited 25+ hours for the parity drives to recalculate.

• after the recalc was done, the drive showed up with the "Unmountable: wrong or no file system".

At this point I stopped the array and changed disk 5 from a filesystem type of "auto" to "xfs". I started up the array, but it gave the same error. So, I ran the Check Filesystem Status starting at around 12:30 am and when I got up at 6:30 am, it was still running with the dots. At this point I rebooted the system, but it's still showing the drive with the wrong or no filesystem error.

I've run dumpe2fs on the drive and it gives the following info:

dumpe2fs 1.47.2 (1-Jan-2025)
dumpe2fs: Bad magic number in super-block while trying to open /dev/sdc
Couldn't find valid filesystem superblock.
/dev/sdc contains a xfs file system

So it knows it's xfs, but I just cannot get past the bad magic number issue.

vault25-diagnostics-20250713-0649.zip

Edited July 13, 2025Jul 13 by smeep2k4
Note that I fixed it.

I missed the format step. Stopped the array, removed the disk from the array, started the array, stopped the array, added the disk, put a check in the Format checkbox and restarted. It's rebuilding the drive, but I don't know what it's rebuilding since it was messed up.

If you formatted the disk it's rebuilding an empty disk.