Oh geez, where do I start in this mess? I was going to fly to my offsite backup location and sometimes I bring a hard drive that houses large files (since my offsite backup location's internet speeds are abysmal for large file sizes). In preparation for getting my files, I accidentally removed my parity drive for my array instead of my Unassigned Drive which caused unRAID to freak out and disable one of my parity drives. Due to me being in a quick rush, I looked up how to fix the issue and was told about "New Config" and that I was supposed to select "All" not knowing that it would reset my config for my Cache Pool Drives too. Not wanting to make things worse I left it as is and decided to turn to the forms for help. I currently have 2 Cache Pools (technically 3). I have one setup for App-dom-sys (Appdata, Domains, and System files) and another strictly acting as a cache pool for my Array. My last SSD is just for VMs. While I don't care about losing data in the Cache and VM pool as those are recoverable, my Appdata, Domain, and System files I would like to retain them and not sure what's the best way to go about it. I feel to make things worse, my App-dom-sys drives are in BTRFS, while my Cache is in ZFS, and my VM is in XFS which I feel might make things worse, and for some reason, unRAID wants to default them to Auto. Anyways, I have attached a screenshot of my cache drive layout and my diagnostics files, any help would be greatly appreciated. 

 

systemupsilon-diagnostics-20241023-0953.zip

As long as the devices are correctly assigned, you just need to start the array, leave the fs set to auto for all, and Unraid will import any existing pools.

Thanks for the help/information! Looks like everything is intact and just rebuilding the parity now (which I will take over potential data loss). Thanks again!