CodeThief

So I've kind of worked around this by adding a static DNS record on my router to resolve to the correct internal IP, but I'd really like to fix this properly if anyone knows how to force it to update the record on unraid.net

Hi, I recently switched routers and am now using a different IP address range (192.168.1.0/24 --> 192.168.88.0/24). I've updated the IP on my Unraid server and that's fine, but I can't get it to update the guid.unraid.net DNS record for HTTPS access. The update DNS button under the Management Access settings page says there's nothing to update, but that's not correct. I've checked the DNS cache on my router and it looks like the unraid record only has a TTL of 1 minute and I've watched it disappear and reappear with the old IP address every time so I know it's not a caching problem (at least inside of my network!). Is there a way to force the update manually from the commandline? Thanks!

This sounds helpful?

Some sort of CPU scheduling perhaps? Have you got the CPU cores pinned?

Sure, but these settings specifically are in the dynamix folder. The others are all obviously named and in the /config folder but these ones weren't obvious so I thought I'd call them out for others in the future. Thanks for your assistance and suggestions!

Fixed it! I created a new Unraid USB stick to compare the contents and found the only obvious thing that was different was that I was missing a "dynamix" folder under /config/plugins. I had a file called "dynamix", but not a folder; something must have gotten corrupted somehow. Anyway, I deleted the file, copied the folder over and everything is working as expected again. So the server image and the notification settings are all stored in the /config/plugins/dynamix folder for anyone who stumbles across this in the future

It took 37 seconds to stop my array when it had it's normal idle load running on it. The docker timeout is 10 seconds and the VM manager one is 60 seconds. I'm not clear on how this relates to my array stopping though? Aren't the docker containers and VMs shut down first, then the array stopped?

Great info, thanks. I'll do some more digging...

Does anyone know the location of the configuration files that get written to when you change notification or server image settings? I'd like to check for permissions issues etc. Also, is there any sort of debug logging I can enable? Nothing appears in the syslog when I try these failing procedures.

I'm also intrigued by this. Has anyone done this successfully? Is it actually usable? Is it just a constant struggle of problems and annoying performance issues?

I'm using Chrome v92. It was working using exactly the same browser the day before though... I don't have any Adblocker plugins for anything. I'll check on Edge Chromium also... EDIT: Same on Edge Chromium I've also noticed that my array gets parity checked every time I boot which I guess is also leaning towards a flash drive problem if Unraid isn't writing that it's completed one.

As far as I'm aware, yes I am. My motherboard has black and blue ports and I'm plugged into a black one. EDIT: I've just checked in the manual and the black ports are USB2. The blue ones are USB 3.1.

Diagnostics attached server-diagnostics-20210902-1143.zip

Hi all, I'm running Unraid v6.9.2 and am having some odd issues with saving settings via the WebUI. I had an issue yesterday where Unraid suddenly reported that my flash drive (a Sandisk 2GB stick) was set as read-only. I shut down the server, stuck the drive into a Windows PC and it reported it as damaged; Windows dutifully repaired the drive (and chkdsk reports no problems), but since then I haven't been able to save some specific settings - the screen just refreshes and the changes are gone again. The things it won't save that I've found so far are: The image of the server in the dashboard on the top-left (this changed by itself after repairing the drive). Notification settings including filling in the Agent config for Telegram I'm able to successfully add more Docker containers and the config for those saves OK so I'm guessing the problem lies with my USB stick somewhere. When I plugged it into my Windows PC I checked in DISKPART if the disk or volume was read-only and both reported they weren't. I'm also not seeing any further errors from Unraid about writing to the drive, so I'm not sure what's going on. I only purchased Unraid less than 48 hours ago using this stick, so I'm not keen on trying another stick and using up my 12 month license change in the first 2 days! I'm struggling to upload my diagnostics .zip from this PC, so I'll upload it in the next post from another device... Any ideas? Thanks!