xamindar

Yes, each time I receive an email that says "unRAID is being shut down".

I have my settings configured to power down only if ups power is down to 5% or 2 minutes left and STILL it powers down 5 minutes or so into a power outage. I need my storage to be the LAST thing to power down, not the first. Does it just not work properly? I just set all the following to 0 now to see if that prevents it from powering down: Battery level to initiate shutdown (%): 0 Runtime left to initiate shutdown (minutes): 0 Time on battery before shutdown (seconds): 0 I would like it to act as configured though. Anyone use this and have any pointers? (UPS Settings) The dashboard currently says %46 and 25 minutes remaining at the time of posting this. So it should not have powered off yet. EDIT: It just powered off again with all these setting at 0. This is ridiculous.

i can not get this radarr to rename any of my movies? What's the deal? Is it broken? I have rename turned on, even have rename folders turned on but no dice. It will go through and pop up little messages saying is it organizing/renaming but it never does anything.

I just installed it but it shows I need a license to test it. How do I get around this? This is looking at the webui.

Nope, still set to host. No worries though. I actually tried that jellyfin after and really like that a lot more. Think I might just stop using plex....unless they have a %50 off sale on the plexpass any time soon lol.

The webui on this docker does not work. At least with the default settings it does not. Anyone else have this issue?

I'm surprised no one has an answer to this issue. I guess not that many use ssh on unraid. This is a problem with only unraid and I am also searching for a solution. Ignore the guy above who is fixated on putty. That will not resolve this issue witch is an unraid terminal issue only. It is server side.

This is the exact problem I have when I ssh into unraid from a screen session on another machine. I do not use or even have installed the screen version in nerdpack. Any idea how to fix this for unraid in general? Just type the following in the terminal to fix it. "export TERM=xterm"

Try it and find out. It will probably work just fine. I'm thinking of trying it myself just to have a "backup" folder I can send snapshots from my other systems to (using send/receive).

Interesting because I logged in yesterday and it was the same it has always been for the past year. I triggered a build just as I had always done, then later in the day I kept getting Server error 503 and nothing would come up. I log in again today and everything was in this new layout and I could not find any place to trigger a build. My github was no longer linked to my account. I had to re-link it, then create new repos for each docker on github (I had them all under one repository before but didn't see how to use it this way again). And then when I finally found how to trigger a build I found I had to select a build location? Weird.

I just logged into the docker website and found that it has been completely changed. It lost my github link (had to re-link) and apparently all my build settings too. There was a link at the top to switch back to "classic ui" but that is hilariously not the classic ui that I was used to. Are they complete idiots? Or are they messing with us? Oh well, it looks like I will have to set up my builds all over again.

Recent versions of syncthing use an outside relay service to break through NAT without the need to port forward. My understanding is this is slower though.

Btrfs has some really nice features, but most are not utilized by unraid. Really, at this time the only reason to use btrfs on unraid is for the scrub capability. Scrub will read all data and verify checksums which will tell you whether you have any bit rot or not. But keep in mind btrfs is fairly untested in certain edge cases as it is a new filesystem. It has been known to fail quite spectacularly in certain situations. (All my disks are btrfs)

Looks like your docker image was forced read-only due to errors. When you restarted the docker service it was likely remounted read-write again and "fixed" your issue. I would either run a btrfs check on the docker image, or just recreate it from scratch to make sure it doesn't still have issues (it probably does).

The syncthing docker has been updated to include the discovery and relay servers. They are disabled by default to ensure the syncthing docker remains a standard syncthing instance as before. To enable them, see the environment variables under the advanced section. While this docker should auto-update just fine, you will probably need to delete it and re-install it in order to make use of the new options from the template. Just make a note (or screenshot) of the "Update container" page with your current settings, delete the container, then re-install it with your same settings/mount mappings in addition to any use of the new features. Syncthing will continue to work as before as long as it has access to the same config folder and data locations.