I purchased a new drive this week and went to install it in my system. Didn't think much of the array disk count at the time. But while that disk was clearing i realized a number of data folders were missing from my shares.

I then realized my array was a 12tb drive short. It was appearing in Unassigned drives, but couldn't be mounted and has an assignment of Dev2.

All while this was happening an 8tb drive disappeared, then reappeared and started a data rebuild on it. Which seems to be successful.

So my new 12tb finished data clear, but didn't trigger a data rebuild for the "missing" 12tb thats in Unassigned drives.

If I try to add the Unassigned device to the array it says it'll format it and either start a rebuild or parity check, which is scary as hell because it looks like 3 years worth of data are on that drive.

How can I gain access to see what is on the drive, or be confident the content exists in parity? My last parity check was 6/2, before the rebuild that happened the past 24 hours. Am I screwed?

Please post the diagnostics.

8 hours ago, JorgeB said:

Please post the diagnostics.

diagnostics-20250704-2312.zip
Alright there is the whole set of logs.

During my continued research, I believe the file system is corrupt, so it has been running xfs_repair all night. Bad Super Block so its looking for the secondary, which I guess is going to take a while. What are the odds it finds a secondary super block?

No filesystem is being detected on disks 14 and 15, with the array stopped, post the output from blkid

Disk 14 is the 8tb the rebuilt yesterday and has not been formatted

Disk 15 is a brand new 12TB that has yet to be formatted

I am after disk sdn, it just completed, but failed, a xfs_repair because it could not find a super block.

b1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="E0D9-DA1E" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="37dc8abd-01"

/dev/loop1: BLOCK_SIZE="131072" TYPE="squashfs"

/dev/sdf1: UUID="c504829a-9def-46b1-8b57-56c9b2e487c8" UUID_SUB="a1b86c0a-241d-4ae3-99dc-c77c2a5d05f9" BLOCK_SIZE="4096" TYPE="btrfs"

/dev/sdd1: UUID="c504829a-9def-46b1-8b57-56c9b2e487c8" UUID_SUB="1192802c-2398-463b-9126-ac67bbd58829" BLOCK_SIZE="4096" TYPE="btrfs"

/dev/loop0: BLOCK_SIZE="131072" TYPE="squashfs"

/dev/sde1: BLOCK_SIZE="512" UUID="69EF280A7AC9528D" TYPE="ntfs" PARTUUID="a86fb5e4-01"

/dev/sdm1: UUID="abba103d-13a9-4174-b480-032c5f5ab876" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="92e37d91-ba78-496c-9166-d36fc3bd82be"

/dev/md9p1: UUID="f02938a7-be13-442b-a619-4fbfd6df3e46" BLOCK_SIZE="512" TYPE="xfs"

/dev/md15p1: UUID="fb2614db-c80a-42f2-9913-46ca9bb200fc" BLOCK_SIZE="512" TYPE="xfs"

/dev/md2p1: UUID="48d45bd1-43ca-4b06-bf61-621fefeb8c10" BLOCK_SIZE="512" TYPE="xfs"

/dev/md5p1: UUID="bf6fd98d-649c-4eb6-939a-e95dafcda214" BLOCK_SIZE="512" TYPE="xfs"

/dev/md11p1: UUID="80c2c9f7-c43e-4289-a477-472dc095a045" BLOCK_SIZE="512" TYPE="xfs"

/dev/md8p1: UUID="5ccae6a1-0b49-4c8e-ae72-fbed351c02b1" BLOCK_SIZE="512" TYPE="xfs"

/dev/md14p1: UUID="9d929547-9638-40c1-ba8f-56ca414e225a" BLOCK_SIZE="512" TYPE="xfs"

/dev/md1p1: UUID="7f7c8472-216c-46f6-b71b-88e491e52043" BLOCK_SIZE="512" TYPE="xfs"

/dev/md4p1: UUID="159d6407-70fc-46b7-8372-b38326f0e005" BLOCK_SIZE="512" TYPE="xfs"

/dev/md10p1: UUID="0ae23449-14b0-401f-80bc-733c22c02e6b" BLOCK_SIZE="512" TYPE="xfs"

/dev/md7p1: UUID="79379f82-6aa2-4585-8050-5a23a04a9679" BLOCK_SIZE="512" TYPE="xfs"

/dev/md13p1: UUID="62d648d5-4ea4-4dab-9f28-d20d10c18b2e" BLOCK_SIZE="512" TYPE="xfs"

/dev/md3p1: UUID="04b3635e-aa0c-4026-8ffd-4beaedb62c89" BLOCK_SIZE="512" TYPE="xfs"

/dev/md6p1: UUID="187d1d2e-b309-4c06-a242-801b4cf14c4c" BLOCK_SIZE="512" TYPE="xfs"

/dev/md12p1: UUID="96406c7d-3444-4959-8e76-348b23687b00" BLOCK_SIZE="512" TYPE="xfs"

/dev/sdn1: PARTUUID="9d02f38d-d036-49f9-ab1c-f3e4fe049991"

The last one, sdn1 is the one I'm trying to get into and recover.

13 hours ago, mrmagoo_83 said:

Disk 14 is the 8tb the rebuilt yesterday and has not been formatted

Which filesystem was this disk?

XFS

16 hours ago, mrmagoo_83 said:

I am after disk sdn, it just completed, but failed, a xfs_repair because it could not find a super block.

Did you try to run the repair from the GUI or the command line? If the command line what was the exact command you used?

With the array stopped, post the output from wipefs /dev/sdr1

Despite the name, this won't wipe anything as written

Sorry, I was traveling for work the past few days.

I executed "wipefs /dev/sdn1" from the terminal but it does nothing, no errors, nothing, just returns to the next line.

I ran "xfs_repair -v /dev/sdn" & xfs_repair -v /dev/sdn1" from the terminal window, both failed to find a super block.

1 minute ago, mrmagoo_83 said:

I executed "wipefs /dev/sdn1" from the terminal but it does nothing, no errors, nothing, just returns to the next line.

That confirms there's no filesystem signature on that disk, not sure what happened, but it was likely before now, probably during the repalcement, if you have the syslog that covers that, post it.

Does that mean the filesystem was erased or corrupted?

I posed the whole diagnostics zip file early in the thread, does that have the right log you need?

Edited July 9, 2025Jul 9 by mrmagoo_83

36 minutes ago, mrmagoo_83 said:

Does that mean the filesystem was erased or corrupted?

Something like that, more on the erased side.

36 minutes ago, mrmagoo_83 said:

I posed the whole diagnostics zip file early in the thread, does that have the right log you need?

Those don't cover disk14 rebuild.

Well...I'm an idiot.

So sdn has no filesystem because its the brand new drive. Sitting here with it in an external docking station I glanced over and saw the damn manufacturing date...5/2025 SOB!

So I went looking for the 'other' 12 TB drive, SN M4B, it had been added to the array, but never drove a rebuild, so not real sure what is the status of it.

Luckily I have a data recovery software tool, and it is currently running to pull whatever data I can from it, so far it is recovering a lot, probably not everything, but some is better than nothing. I originally thought I'd only lost 3 years worth of pictures/videos of the family, but it turns out there was data from numerous years on that drive. So even if I can't get them all back, I'm happy to get what I can.

After this, I'm going to duplicate the drive onto another newer drive I have, just as a backup.

I am then going to put it back in and bring the array online and see if it will rebuild the full drive, or if something else is wrong and it only rebuilds a portion, or at all.

I am open to additional safety backup suggestions. I am thinking about an NVME drive to store critical docs and files on as a redundancy, just in case. Figure out how to have Unraid push new data to it weekly or something. I am willing to pay extra money to keep these files safe, so I'll figure something out. I used to have a backup to a 4TB external, but I forget what and how that was working and if it was a 1:1 backup.

Hopefully I get lucky and Unraid rebuilds the drive like nothing happened, but normally I'm not lucky.