jbrodriguez

Good ! Well, sort of good Yes, that message has been a thorn in the ControlR plugin shoes It seems to manifest itself when a reverse proxy is present on the server. Could that be your case ? I have tried to replicate it without success, thus the no-solution at the moment.

Hi, by any chance, are you running 6.8.x ?

Hi, thanks for the reports about unbalance not working on 6.8.x, fortunately there's the 'start from the command line' workaround. I had to install my workstation from scratch yesterday and with work and all, I'm rebuilding my dev environment piece by piece, hopefully by next weekend I'll have looked into this issue. Thanks for the heads up @Squid, I'll start by checking that isNumber. RGauld, I think what's happening is that when you started it from the webui, it redirected you to the secure port (6238) behind the scenes, for the time being, you have to point it to the appropriate port manually

I guess what you're thinking about is a 'scatter/balance' functionality. There are many opinions here on the forums stating the you should fill a disk and leave it alone (sort of an archival disk). Not sure if that applies to your case, but it's worth considering.

Hi, thanks for the kind words ! You sort of can do this right now. Select the parent, then unselect the ones you don't want being selected. Does that help ?

Hi, yes, you need the ControlR plugin. More info on the FAQ: https://www.apertoire.com/faq/controlr

There used to be an issue with btrfs, it was reporting a wrong disk size. If that hasn't been solved, I suspect that might be the issue here.

Hi, unbalance works at disk level, not share level Having said that, it will use the disk with the most free space first, then work its way down the other disks.

That is impossible !!! 🤣 To be honest, I have no clue, I guess you already uninstalled/installed the plugin. I also assume that everything else works on your server right ? Out of ideas 🤷🏼‍♂️

Hi, can you try running it from the command line, to make sure it works ? /usr/local/emhttp/plugins/unbalance/unbalance -port 6237

v2019.09.07 (5.6.0) is available ! This is a minor release with some new features and some optimizations. Changes: - Add elapsed time to transfer screen - Fix unbalance logo container background color - Add contrast to drop down in history screen - Decrease binary size - Compress server output - Modify UI version format - Add notice about exclusive access in the UI

Hi, you can go to the History tab, click on the "chevron down" to the right and check if the operation had any command with issues.

I haven't really thought about it, not sure this is something I'd like to do.

unbalance moves folders in blocks, if you try to move a whole share, it's possible that the whole size (across disks) exceeds the remaining free space of a single disk. Try moving subfolders off of the main share and such, it should help

Hi, I'm very busy lately ... About a "balance" mode, it's not in my plans, as that is sort of the basic functionality of Unraid, with Mover. About automation, it's currently not possible. It can be done, but needs some work on it, which I'm currently unable to allocate.

Thanks for your comments, jpotrz ! There's a docker (diskover), that among other things, finds duplicates

yes

Your issue will be that once the copy is finished, the data will exist in both the target and the source disk. You'll need to remove data from the source disk manually (please note I'm referring to disks, not user shares). Move is implemented by a copy then delete, to protect your source data in case the copy fails for whatever reason. This is normal behaviour.

It should move all files/sub-folders that fit into the target disks you choose. If some files/folders don't fit, it won't move them and send an email informing about this (if you have notifications on). Not sure what you attached, but that's not the log file.

I haven't published any changes to the plugin in a while, so I lean towards some change in your environment/browser ? Did you install any chrome extension lately ? Disabled javascript ? Changed SSL settings in Unraid ? Try looking in Chrome Dev Tools console for any possible errors.

Hi, I'm not really sure what the issue might have been. If you want to send the log (/boot/logs/unbalance.log), I'll take a look at it.

Yes, I got a couple of replies. I always appreciate more test data.

Weird. I'll do some tests.

Thanks for the report, I'll check the code.

You don't need to create the history file. It's (re)created if not present. It seems to me like a bug ... can you open DevTools in your browser (Tools > Web Developer > Web Console in Firefox, View > Developer > Javascript Console in Chrome) and check for any errors (red messages) ? Send a screenshot of the console if you want.