naturalblaze

Thanks for the advise, I had forgotten that I could disable the array from auto-starting in the disk.cfg file. Here is what I did to backup and recover my system.oh 
Purchased: Western Digital 12TB External Hard Drive (I plan to start doing some backups of my critical files, photos, etc. to this weekly) ikuai SATA to USB 3.0 Dual Hard Drive Dock UGREEN M.2 NVMe SSD Enclosure Pulled my Pool/Cache drives and the Array disks from my unRaid server. I used the the HDD Dock and the SSD Enclosure to rsync the critical files I needed from each of the drives.  I'm already running PopOS on my laptop so no special programs needed it was able to mount the xfs and btrfs file systems without any problem.  Created a backup of my UnRaid USB Flash Drive.  I edited /config/disk.cfg to startArray="no". Re-installed everything and tried to boot my system but it never came up so I had to hook a monitor and keyboard to my system (I normally run it headless). There was a "VFS: Cannot open root device" error message so I just recreated flash using the USB Creator and just copied over the config folder from my backup after rec-creating the flash drive.   This time the system booted correctly, I was able to start the array, and everything looked good.  As previously stated all system, Docker, and VM files are stored on my Cache so they were not affected.  I did loose some data as my total array size did go down but was mainly just some missing seasons of Plex TV shows or old DVR recordings which I can get back if needed.  I did a Parity check just to validate everything was good on the parity disks. My system is now back to full functionality! While this was a pretty unique situation where I was the point of failure an not anything on UnRaid side. I do plan to utilize the 12TB external to do some weekly backups of some of the critical docs, photos, etc. just in case.