jbrodriguez

it uses rsync underneath, iirc rsync does that by default move works by doing rsync, then running "rm *" on the source, there has been some discussion about this, "--remove-source-files" could probably work, but would need to take a look, i don't remember if that works at a file level or at the command level, in any case it would be a departure from current logic

hey, hmm you can check /var/log/unbalanced.log, but im guessing it might be a ui error if you're on chrome, can you click on the menu View -> Developer -> Javascript Console ? it may show an error there, can you post a screenshot ?

ill add an issue to look into this

released 2026.05.17 implements a time window to calculate speed (and remaining time) this uses the last ~90 seconds to calculate speed (instead of the previous fixed 60 samples), should prevent some integer overflow that could have been happening

that would be a balanced move, but this is something built in into Unraid, with the allocationg logic (high water, etc) many ppl here prefer to fill up disks, rather than having data scattered to serve as sort of "read-only/archives", there are some threads on the matter what's unusual is what you mention about filling the first drive then failing, if you have the logs related to the error, i could take a look finally, even though "balancing" disks is currently not supported, one of my goals is to have pluggable algorithms/logic, to move/copy files around: one of these algorithms could be to balance disks, versus the default one: fill one disk, then the next and so on. not there yet tho, hopefully sometime this year

released 2026.05.03 improve login/logout user experience additional hardening of different surfaces (some shell invocations, websocket auth, rsync execution paths, .env permissions and logging) wanted to land these changes, before the last (bigger) one in the security category

small update 2026.05.02a rsync flags hardening (rejects some flags that prevent normal unbalanced operation) small adjustment to replay logic (to avoid altering history)

released 2026.05.02 hardening of file-touching commands (no longer shelling out, guarding paths, use golang primitives) drive operations through plan ids rather than client supplied operation details, to prevent potential injection of unsafe paths or transfer instructions this release is about improving the plugin's security envelope, i actually never heard of a security incident, still better safe than sorry there's one or two additional security related changes, but i won't throw another update for the next week or so, in case any of any issues

released 2026.04.25a migrated encryption algorithm to argon (vs previous bcrypt) this makes password length limitless, for practical purposes im maxing it out at 256

released 2026.04.25 (whoa, its been more than a year since the last upgrade) added auth support (local, backed by a disk file) this should improve security a bit, will potentially look into ssl certs down the road pls report any issues you find the happy path would be stop unbalanced enable auth start unbalanced on first access to the page, it will request you to set the password access from other browsers will ask for username/password you can logout from the unbalanced ui (top right)

IMPORTANT NOTICE Effective June 1st 2026, ControlR will be removed from the App Store and Google Play; it will be no longer available for purchase. Read the full note at https://jbrio.net/posts/sunset-controlr/

IMPORTANT NOTICE Effective June 1st 2026, ControlR will be removed from the App Store and Google Play; it will be no longer available for purchase. Read the full note at https://jbrio.net/posts/sunset-controlr/

thanks for the report, glad you sorted it out ! with the advent of unraid api, a lot of new players have entered the scene, as it's now a lot easier to develop for unraid im still on the fence on implementing the unraid api, there are so many things going on in the tech space right now, innovations happen weekly, not even monthly, much less yearly will post any news here, on the unraid forum.

hmm crazy numbers, it would seem like an integer overflow, dont remember seeing something like this before tho ... i assume that's on a healthy drive right ? can you check the logs (/var/logs/unbalance.log) when it happens, do they show anything meaningful ?

could kill unbalance process on the command line, not ideal but should work