So I need help with fixing my array, I just swapped out an older 4TB with a new 10TB drive. I installed the new disk started the server and selected the new drive in place of the 4TB. I then started the array and started the data rebuild process, of which it took about 19 hours. Once that process finished the new 10TB drive has the triangle warning “device contents emulated” next to disk3, and where the size, used, and free data amounts are it reads “unmountable: unsupported or no file system”   
I've tried restarting the system, and putting it in maintenance mode checking the disk file system at which point all it comes back with is “phase 1 - fine and verify superblocks…

bad primary super block - bad magic number !!!

attempting to find secondary super block…

…………………………………………………………

-exit”

 

will preforming a data rebuild solve this problem? Do I need to reformat the drive and then redo the data rebuild? Am I able to put the old 4TB drive back in it place and the array work so then I could move all the drive contents and remove the drive from the array, with no data loss, and then just add the 10TB instead of replacing the old drive? I’m worried about the data loss, of course, because the 4TB drive had about 3.4TB of data on there. 

Please post the diagnostics, also, what command did you use to check filesystem?

I used this guide for checking the file system.  

nas-diagnostics-20250119-1240.zip

Did you use the GUI or the CLI to make the check? Do you still have the old disk intact? Also post the output from

blkid

 

I tried both ways, the GUI is what gave me the results I posted and the other way didn't give me any results after following that guide.  The old 4TB drive is still in the server and I haven't done anything to it except remove it from the array when I replaced it. There is nothing wrong with it I just needed to upgrade the capacity. I was planning on using that drive in my daily computer after this was done. 

 

blkid results:

 

root@NAS:~# blkid
/dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="2736-60C3" BLOCK_SIZE="512" TYPE="vfat"
/dev/loop1: TYPE="squashfs"
/dev/sdf1: UUID="64a7f191-f265-4242-9bf0-c07bcaa2e311" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="095b5cb7-8345-4b1a-8ca7-91a6f55efcc5"
/dev/sdd1: UUID="93498264-d36c-454f-9d74-99b984cace74" UUID_SUB="1d896179-03c5-4f71-83da-9923e5b94344" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/md2p1: UUID="e5bcd7d6-a8e4-4cf9-8a31-58ca62624e50" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdm1: UUID="e5bcd7d6-a8e4-4cf9-8a31-58ca62624e50" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="5c8ba4cc-bbbd-472b-9304-70554d29703d"
/dev/md5p1: UUID="64a7f191-f265-4242-9bf0-c07bcaa2e311" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdk1: UUID="f65f4644-b03c-4884-bf47-9cdc3282e678" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="52400893-d633-47aa-b805-3daf18e21534"
/dev/md8p1: UUID="25093a6c-9045-42bc-98c9-6786acc3d1c7" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdi1: UUID="434aaf96-1d08-4537-abd4-90aa238f487d" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="89c18bed-ca11-48aa-9a67-c3adc4c69fa8"
/dev/md1p1: UUID="f65f4644-b03c-4884-bf47-9cdc3282e678" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdg1: UUID="ab4389ac-58b8-4206-8e61-01f5743ad977" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="71506686-5c8d-4105-8597-70dec0be3877"
/dev/md4p1: UUID="ad00211d-58b4-4ef9-a81b-4a954feaeb84" BLOCK_SIZE="512" TYPE="xfs"
/dev/loop0: TYPE="squashfs"
/dev/sde1: UUID="93498264-d36c-454f-9d74-99b984cace74" UUID_SUB="82c3f90a-d175-4712-ba71-c0579eb66fb8" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/md7p1: UUID="ecfa4354-b405-47b3-a860-eef0a7cc160b" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdn1: UUID="25093a6c-9045-42bc-98c9-6786acc3d1c7" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="ab8a8f92-e239-4184-9658-6fec441473d4"
/dev/sdc1: UUID="ad00211d-58b4-4ef9-a81b-4a954feaeb84" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="0039760a-2cd3-4393-b057-a6e57aeb9c17"
/dev/sdl1: UUID="93498264-d36c-454f-9d74-99b984cace74" UUID_SUB="268a5d8a-6870-45b6-91a8-2de285730784" BLOCK_SIZE="4096" TYPE="btrfs"
/dev/sdj1: UUID="ecfa4354-b405-47b3-a860-eef0a7cc160b" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="10472f14-fbf3-4815-94ac-4e08de21d99a"
/dev/md6p1: UUID="434aaf96-1d08-4537-abd4-90aa238f487d" BLOCK_SIZE="512" TYPE="xfs"
/dev/sdb1: PARTUUID="2be1165b-d581-44cd-85fa-5a7f8a75fa2b"
/dev/sdh1: PARTUUID="74ea5709-bbc5-477e-a486-7464954de4ec"

8 hours ago, RTC1929 said:

/dev/sdg1: UUID="ab4389ac-58b8-4206-8e61-01f5743ad977" BLOCK_SIZE="512" TYPE="xfs" PARTUUID="71506686-5c8d-4105-8597-70dec0be3877"

I assume this is the old disk? If yes, mount it with UD, if the data looks fine copy to the new array disk.

I'm not sure which drive is which, but I've mounted the old drive with UD, and the data is still on it and I'm able to access it from my computer. Am I correct in saying that I can transfer the data to my computer, then reformat the new 10TB in the array with the file system issue, (wiping that drive in the process) then just transfer everything back to the array? Would that cause any other problems down the road if I were to do that? Is there a better way to do that process? What causes a file system error like that in the first place? This is the 5th drive I've replaced in this manor and the first time this problem happened. 

23 minutes ago, RTC1929 said:

Am I correct in saying that I can transfer the data to my computer,

You don't need to transfer to your computer, you can just transfer from UD to the array.