Crazywatermelon

Yes the issue is TestDisk is writing the partition as ~ 2MB. Its an 8 TB disk so a full scan is going to take much longer but I think I'll run that and see if TestDisk pulls up any other partitions.

Tesdisk sees the partition and I can write the partition to the disk but its still showing with the same error. Unassigned disk also won't mount it. I'll see if theres anything else I can think of and if not go through recovery options.

Parity isn't valid since I was doing an array shrink. Any options to try to repair the partition?

I'm working on shrinking my array as I recently got larger capacity drives. I followed the guide for performing the shrink and after performing a new config and verifying the drives were assigned correctly I went to start the array and got that error message on one of the disks that was working previously. I've gone through and started the array in maintenance mode and run a disk check on the drive but that didn't resolve the issue. Any ideas on what I can do to resolve the issue or should I just start running through recovery options?

Thank you. One small note performing the saveconfig did not for whatever reason save the config in a location that persists through boot but I was able to back up the config to another location and use targetctl restore to restore it. Minor hiccup nothing major. Thank you again.

I setup an iSCSI target, created a fileIO volume and get everything setup however after reboot all the settings were wiped out. The FileIO still exists, is there a way to re-map it to the iSCSI target?