MSOBadger

Same thing happened to me. Theme Engine plugin stopped working yesterday and I couldn't get anything to re-apply. Ended up removing and reinstalling the plugin after reading the above posts and that finally resolved it for me as well. (Thankfully I was just using a theme.park theme so re-configuring it after the reinstall was a two second thing.)

THANK you! That indeed looks to have done the trick. Mild heart attack averted.

A quick bit of info on my basic setup - I have one nvme pool set up to house all of my appdata and system files, a separate nvme pool for my VMs, and a third single drive setup for my generic write cache. Fix Common Problems detected that some of my appdata files were not being stored on the "nvme_docker" pool that I have setup for appdata, but rather on my separate generic cache drive (which used to be my sole cache drive/pool). In moving things around in an attempt to correct this, I think I somehow accidentally deleted the mnt/user/ directory. My Shares tab is now completely empty. I can still see all of the files when I browse to the "nvme_docker" pool in the Main tab, but the shares are gone. Is there any way to easily restore this? I have a backup of my USB from this morning (from just prior to updating to 6.12.2), is restoring to that USB backup the way to go here?

Thank you @JorgeB! That did the trick. Much appreciated!

I was updating one of my docker containers this morning and received an error in the middle of the update process. Unfortunately, I didn't record what that error said - I believe it was a connection refused error of some sort. Since closing the update window, I've been receiving an error that the "Docker Service failed to start" and all of my containers are down. At the bottom of the Dockers tab page, there are several error messages: Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 682 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 866 Warning: stream_socket_client(): unable to connect to unix:///var/run/docker.sock (Connection refused) in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 682 Couldn't create socket: [111] Connection refused Warning: Invalid argument supplied for foreach() in /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php on line 932 I tried stopping and restarting the Docker service, but that hasn't resolved things. (When I change the "Enable Docker" setting to "No" and save the change, the "Status" flag in the top right corner never changes from "Running", so I'm not sure that it's ever actually trying to fully restart. The Docker tab does go away though, so maybe it is.) Perhaps something in the update process for the container I was updating corrupted my Docker file? I've attached my diagnostics logs. Any help would be greatly appreciated! vulcan-diagnostics-20220521-0636.zip

Excellent. Thank you again for all of the support! Much appreciated!

Ahh... Ok, that explains it then. I always use the rootshare when transferring files from my "downloads" share into their destination shares as it ensures all of the traffic remains local rather than going across the network from the origin server share to my device and then back to the server destination share. Thank you! Is there a better way of doing this that will keep the traffic local but respect the share settings? I'm pretty green on Linux so I generally access everything via SMB via my Windows devices.

The data is generally coming from the "downloads" share - manual cut/paste via a remote rootshare accessed from my laptop. I am also seeing this issue with the "movies", "wrestling" and "videos" shares (there might have been others but those are the ones I recall for sure).

Here are my diagnostic logs. Thank you! vulcan-diagnostics-20220411-1207.zip

THANK YOU! Yep, I'm sure that's it. I had that set at "Automatically split any directory as required". I assume this should instead be set to "Manual" then?

I'm running Unraid 6.9.2 and have been having an issue with the "Include Disk(s)" setting seemingly not properly restricting the disks that files in my shares are saving to. I have each one of my shares set to use specific disks to limit which disks get spun up for certain tasks. I've noticed however that files from these shares are ending up on disks not specified in each share's respective "Include Disk(s)" setting. For example, I have my "tv" share (which contains all of my TV episode media files) set to include disks 13 and 14. However I just found "tv" share folders with files (files relatively recently added) on disks 8, 9, and 10. So I'm using unBalance to move them all over to 13 and 14. I've found similar issues with numerous other shares. (It's not a space issue, as the specified disk groups for each share do have free space on them.) I should also note that I am not using the "Exclude Disk(s)" setting, just the Include. Has anyone else experienced this? Is there something else I need to do, settings-wise, to make this restriction work?

First, a huge heartfelt thank you for this awesome utility. I'm trying to clean up my share data so that each share is no longer scattered across numerous drives (so that "movies", for example, is limited to 3 drives and unraid only has to spin those drives up when movies are being accessed). I'm running into a hurdle using the Gather function however; when I get to the screen to select the Target drives to gather the share data on to, only a few drives are showing up (and they don't happen to be the drives that I want to target). I'm guessing I'm probably just missing something simple. I've disabled all of my dockers and VMs so nothing should be accessing drives. I've tried spinning up all the drives before hand as well. I have been able to work around this by slowly piecemealing the transfer by using Scatter to move share data disk-by-disk, but that's obviously a much more manual process. Any ideas? Thanks in advance!

THANK YOU @ghost82!! That did the trick! I was able to mount the image and get all the files backed up off of it. You are a god-send! Now to get to work on setting things back up. Thanks again!

Here's the output -

This was my problem, lol. I was pointing RealVNC to the VM's IP rather than the server host. After pointing it to the server's IP I was able to remote in and run gparted and expand the primary Windows partition. After that, I was able to boot into Windows again on the primary vdisk and the OS virtual disk now shows the full expanded size. Thanks for the help there. It looks like I'm not out of the woods yet though. With the partition resized, I went back and fired up the original instance of the VM (i.e. the one that has the second vdisk setup (i.e. my data disk for this VM), and I ended up right back in the instant-pause cycle. After some messing around, I discovered that the VM boots just fine with just the primary vdisk, but as soon as the second is added it pauses on boot. I made a copy of this vdisk2 file and tossed it on my Windows laptop and tried to mount the disk there and received a "the disk image file is corrupted" error. I've never tried mounting a vdisk that Unraid created like this before... should that work if the vdisk is working properly (meaning this vdisk2 is actually corrupted)? Or is it normal to be unable to mount a vdisk in Windows in this manner? Assuming that the vdisk is actually corrupted... is there any way to restore the data?