max.prime

It turns out my flash drive went into read-only mode. Replacing it has fixed almost all of the problems, but some are still persisting. I think I should be able to work out the rest on my own, but if I have any difficulties with anything outstanding I'll make a new thread. Thanks for all of your help!

Correct: building a new container does not add it to the user templates. I will try a new flash drive and see if that does anything.

I just tried this. I deleted a container, but after clicking "add container" the template was not listed under "user-templates". I had many familiar templates available but not the one I had just deleted, which was one of the ones that was missing an "edit" button. Edit: something I have noticed is that the containers that are missing an "edit" button and have this issue of not showing up in the templates, are new containers, ever since I started having this issue about a month ago. Part of me feels like this is a permissions issue since it seems like there are just so many settings throughout my system that do not get applied. I check a box, hit apply, and the box is unchecked. Being unable to turn off Docker is one example of many. Another example: I cannot edit any scripts in User Scripts. Saving does nothing -- when I re-open the script my edits are unchanged.

Yes. There are several containers that have a missing edit button. To change any setting I have to delete the container and reinstall it.

Sorry for the late response. I just nuked the Docker image and reinstalled containers. Unfortunately, I am still having significant problems. All of the problems above are still present. Any help would be greatly appreciated. Note: while reinstalling some containers, a couple did not show up under Previous Apps, even though I am 100% sure they were installed previously. Once installed, those containers are not editable: clicking them gives access to WebUI but not the edit button. Edit: my guess is that this doesn't have to do with Docker config, since it seems to affect many things outside the scope of Docker.

Hi there, Over the past few weeks I have been dealing with growing issues on my Unraid machine... it seems like there is a ghost. Some of the problems include: unable to access docker containers through tailscale (although tailscale seems to work on other machines just fine) unable to change tailscale settings in a container -- after clicking apply, the old config persists, even after resetting some containers do not include the "edit" button, so to make changes I have to remove and re-install sometimes when clicking edit on one container, another containers settings are loaded I cannot delete scripts in User Scripts unbalanced will not load there are some containers that simply do not work for me... perhaps this is user error, but a container like overseerr/seerr shouldn't be that hard to set up, and I have done so many times before. docker does not turn off. In settings, if I turn it off, after clicking apply the page refreshes and the toggle is still on. I will admit that I haven't tried much beyond fiddling with container settings, launching Fix Common Problems, and rebooting. Some things that may or may not have led to this: I used this guide to install ohmyzsh, but got an error mounting the image (mkdir -p /tmp/root mount -o loop /boot/root.img /tmp/root) I installed a new cache drive and tried to migrate the contents of the old sata ssd to the new nvme. But at some point unbalanced stopped launching so there are a few files still on the old drive, despite its share settings pointing to the new drive. Any help would be appreciated! uma-diagnostics-20260217-0905.zip

Yesterday I had a power outage while I happened to have my UPS disconnected. When I turned my server back on, Unraid did not recognize my parity disk - it was as if it was disconnected. I didn't notice this until a this morning, well after I had spun up the array. While I didn't make any major changes to the filesystem, I reckon that logs were generated and several automated tasks wrote to the array. When I noticed the parity drive wasn't online, I rebooted, and there it was as an unassigned disk. When I assigned it as the parity drive it was as if it was a new disk (there was a blue dot) and is now writing a parity sync. I'm not sure how concerned I should be. It kind of defeats the purpose of a parity drive. I've attached a SMART report (post power outage) of the parity disk, along with and diagnostics, and previous syslog (after the power outage). logs.zip

I had trouble logging into Flood-UI with qbittorrent but that's because I had turned off authentication. When I turned it back on, I still couldn't log in, but restarting qbit did the trick.