Pierry

Yeah, I used my USB dock to work on the drive on my main computer. Now I understand what messed up the layout. At this point, I opted for backing up the data on an external HDD, create the array and let the parity build. Will simply copy the data back on it later. Still bugs me that I'm not sure what bogged the drives in the first place. Not sure what lesson I can take from this then. Thanks for your help!

So, I was able to recover the partition using Testdisk. Now the drive is showing up correctly in unraid, but anytime I try to use it in the Array, I'm met with the following error: Unmountable: Unsuported partition layout. I can mount the drive using "Unassigned Devices" and even access every single file on it. Am I doing something wrong here?

OK, thanks a lot. I will look into recovering the data with the 3rd party tools. At this point, I had already given up hope but was still interested to know what caused this. Was is it me unassigning the drives with the new config? Or might've it been some SW hiccup? Just really wanted to know to avoid the same mistake in the future.

sce1: /dev/sce1: No such file or directory /dev/sce1: No such file or directory fatal error -- couldn't initialize XFS library Should I use sdc instead? (tag of the disk in Unraid webGUI) xfs_repair on sde1 I've been running for hours now, apparently still searching with nothing but dots on the screen: Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... .found candidate secondary superblock... unable to verify superblock, continuing... ................................................................................................................................................................................................................................................

blkid output below: /dev/sda1: LABEL_FATBOOT="UNRAID" LABEL="UNRAID" UUID="272B-4CE1" BLOCK_SIZE="512" TYPE="vfat" /dev/loop1: TYPE="squashfs" /dev/sdb1: UUID="6bc7b2ff-7774-451e-b640-196e1bfe6053" BLOCK_SIZE="512" TYPE="xfs" /dev/loop0: TYPE="squashfs" /dev/sdd1: PARTUUID="f7a58234-43f7-43d7-acd2-9ab3d443f9b4"

Hi, I'm pretty much new to Unraid, so please bear with me. I was migrating from my OMV setup that used 2x 2TB drives in snapRAID. For the migration, and also to use as a parity drive later, I got an additional 4TB drive. Following some pointers from the internet, I was able to get all the data I had from the primary 2TB drive to the 4TB drive, which was now formatted in the compatible xfs. After that, I used the unbalance plugin to put all the data from the 4TB drive to one of the 2TB drives. All drives were in the same array and formatted in xfs at this point. All went fine. I wanted to unassign the 4TB drive to put it as the parity drive for the 2TB drives, but this is where things went wrong. In order to be able to reassign the drives, I used the "New Config" tool which probably caused the issues I'm now having. After assigning the drives into the array, with the 4TB being now the parity drive, I was met with the error msg "Unmountable: Unsupported or no File System" next to the both 2TB drives. Now, is everything lost at this point? I tried xfs_repair -vn as well as btrfs check on both the drives with no success. btrfs check /dev/md1p1: Opening filesystem to check... No valid Btrfs found on /dev/md1p1 ERROR: cannot open file system btrfs check /dev/md2p1: btrfs check /dev/md2p1 Opening filesystem to check... No valid Btrfs found on /dev/md2p1 ERROR: cannot open file system Diagnostics attached. Thanks in advance for any help. esprimo-p757-diagnostics-20231119-0015.zip