Athelstan

Well, moving everything off the cache in safe mode by mounting it in read only mode to a disk in the array worked. Ran a full memtest (passed) and restarted the system with auto start array turned off and removed the cache disks, erased the cache, then built a new one and it worked fine. Copied everything back and found everything was owned by root:root (docker permissions was totally borked because of this). At least that is fixable and a much better place to be than where I was. I've seen some other people (including the one I posted above and possibly DingusKahn) with the same issue. I'm questioning if going to ZFS to get compression on my cache was such a good idea (don't get me wrong, performance and compression are great) but only time will tell. I guess if it happens again I'll roll it back to XFS. This was no fun, haha.

This is what I found that seems to apply to me I think.

I was lucky enough to catch an error this time when it tried to mount the disks to start the array as I was tinkering with it. This is on the monitor directly connected to it while in Safe Mode and I tried to start the array with my two cache disks (mirrored) were attempting to mount as well. VERIFY3(size <= rt->rt_space) failed (281442900086784 <= 1880903680) PANIC at range_tree.c:436:range_tree_remove_impl()

So, I've done some more digging. It seems the ZFS cache pool is the culprit. It won't start the array with the either disk from the cache pool assigned. If I unassign both cache drives, turn off docker and vms, and start the array, it comes up fine. So, at this point, I'll need someone to point me in the right direction, LOL. I went to ZFS for the compression feature, but I'm at a disadvantage on what to do to troubleshoot why it won't start. Diagnostics will not complete if I try to start the array with the ZFS cache pool a part of it.

Long story short, Woke up this morning and noticed my Unraid server was pingable, but unresponsive. No GUI, no shares responding, nor response from keyboard/monitor also plugged up to it. Did a hard reset. Now it's stuck at "Array Starting - Mounting Disks." After an hour, I started a diagnostics to bring here for help, but it also has been stuck for the last hour and not completing. Looking for some next steps on direction to go to get it back up. Thanks in advance!

Well, I followed up this post with a post on the r/Unraid on Reddit about the issue. I had someone reply that said doing a full server reboot fixed their issues (they had it happen more than once, apparently). I had already rebooted the server twice, but I thought why not. Third server reboot fixed my issue. No idea what the issue was or why it even existed unless it was an app update that went south somewhere recently.

I'm on Unraid 6.9.2 using DelugeVPN-binhex. Deluge says it's running 2.1.0. Today, I noticed my torrents were sitting idle. All at 0% download as they were automatically added within 8 hours of each other. No changes had been made in months other than updates. I currently had/have nothing seeded. I get them from a public indexer (nyaa.si). Space isn't an issue (10TB of space to play with). I've checked and double-checked the config. I've made sure the VPN (PIA) is connecting and getting a valid and correct IP for the remote locale. Port Forwarding is turned on. I deleted the docker and redownloaded using the same template. Same result. I tried manually adding trackers to one of the torrents that was stuck and the same result....although it did acknowledge 4 seeds, it just sat there at 0 percent. Paused and restarted, remove torrents and added manually. It's very weird. One of those downloads has like 400 seeds and 1300 leachers currently. It's not from a lack of supply. Any thoughts anyone? Any help would be appreciated. Thanks!

You are my hero. Thank you good sir for your time and education! This corrected my issue.

I also see this now in my Dockers.

Power outage hit me and lasted a good 26 hours. I wasn't here to power anything down nor did I know about the power outage so my UPS died (it lasts 12 hours). I get home and power everything back up...then the trouble starts. Plex and TDarr don't start. I try to manually start and I get the above error. Well, first I did say "gave Bad Executive error" not because the issue is fixed, but more so because I attempted to make a change in the settings because I had a theory I knew what the issue might be. That failed when I clicked apply...okay fine. But I discovered in it failing it deleted the Binhex-Plex docker from existence. I got to take the blame here because this happened to me when I was originally setting everything up and had to go back and redo all my settings. I spent a lot of time on that and I'd rather not do it again as it took quite a while to remember and guess at everything I did before to make sure it was the same again. I realize the folder in my appdata and everything is still there, but now I have a two fold issue. 1. How do I figure out what all custom settings I have without just working through all the variables I could have setup. I'd rather not fight this battle if I don't have to. Yes, I realize after the 1st time it happened I should have taken notes or a screenshot, but this feels way to finicky to make a simple mistake and find it gone when it tries to compile/setup after a change is made to find it all gone forever. 2. Getting my settings back is one thing...the next is what caused it. I have a theory it was me pointing my transcodes to /tmp (I got 128GB of RAM so a 64 GB space feels like plenty here) and something weird happened after boot. I think this because only two applications use /tmp to do work in and that's Plex and Tdarr. Tdarr is doing the same error when it tries to start (nothing in the logs, I checked), but I don't DARE touch it because if it deletes and I can't retrieve the settings...I'm going back to Windows Server, haha. So, if I can get number 1 taken care of, it'll be a huge plus (seeing my old settings again and praying they aren't gone forever). Edit: #2 has been fixed. My Nvidia driver deleted itself somehow...those two containers both used my GTX 1650. Fixing that issue fixed #2..so, now all I really need is how to get my settings back prior to it's "self deletion".