jbrodriguez

Thanks for the reply d2dyno. I recently removed from the code a flag that I had deprecated a long time ago, but it looks like it's still present in users' config file. Try either one of these: - edit /boot/config/plugins/unbalance/unbalance.conf, remove the line that starts with notifyCalc - remove /boot/config/plugins/unbalance/unbalance.conf altogether, but you'll lose any custom settings. Then try to stop/start the plugin from the webUI. Let me know if that works.

Upgraded to 6.7.0 and unbalance is running normally. root@lucy:~# uname -a Linux lucy 4.19.41-Unraid #1 SMP Wed May 8 14:23:25 PDT 2019 x86_64 Intel(R) Core(TM) i5-3570K CPU @ 3.40GHz GenuineIntel GNU/Linux root@lucy:~# ps aux | grep unbalance nobody 4808 0.0 0.3 107864 10324 ? Sl 10:06 0:00 /usr/local/emhttp/plugins/unbalance/unbalance -port 6237 root 5199 0.0 0.0 3908 2228 pts/0 S+ 10:10 0:00 grep unbalance So, for those having issues, try this on the command line killall unbalance /usr/local/emhttp/plugins/unbalance/unbalance -port 6237 This is to check the output. Post the result.

Oh hadn't read the last post. Maybe an issue with 6.7.0 ? Strange, I'll upgrade my test server today and check.

Can you reinstall the plugin ? I think the plugin has a bug when Unraid upgrades major (and minor) versions, I think. Let me know.

The speed is impacted by a read/write on the same array (since every rsync command goes through parity), whereas writing from another workstation (or similar) doesn't have the same penalty, so you can even reach wire speeds (with a cache drive). Another source of slow down could be disk health. Even if SMART reports are fine, the drive could still be slow. Check this docker

I could check for mover, but other dockers would be difficult.

That's the purpose of the `rmsrc` button. The app can't automate that because it has to be a user decision.

You were actually running `basically` the same command twice. The app copied the folder, but the underlying rsync failed to set some file's date/time. The rsync command you ran should have shown the same warnings for the same file(s).

Currently, no. Move, right now, is: copy, check the folder actually exists on the target, delete the source. Verify is a VERY expensive operation, since it compares checksums of each file on the source and the target. You can do it with unbalance, by doing a COPY, then going to the History screen and clicking on the Validate button.

So, I also want to thank all of you making donations. I can't find a way to thank individually, so ... this is my thanks ! 🙌

Hi, thanks for the suggestion and the kind words ! You have a point, the disappearing warning is something I can change easily. I also need to say that, the warning is basically a tally. Imagine this path: /mnt/disk1/tvshows/Billions/Season 01/Episode 1.mkv Well, turns out each component (Billions, Season 01, Episode1.mkv) may have wrong permissions. Each component is counted and that's what you see in the summary. You can fix it by running the docker safe permissions script. There's a path worth considering for the plugin: - You could localize/restrict the docker safe script to just /mnt/disk1/tvshows/Billions (and descend recursively). The script would need a minor adjustment, but it's doable and would use a lot less time, than going through the whole disk. In any case, what I'm trying to say is that in its current incarnation, the warning `pop-up` is mostly a heads up to run the docker safe permissions script. You won't gather too much more info out of it.

It's unBALANCE (for now). As soon as it finds a enough space, it will use it. What you're asking for is something like the built-in share allocation does.

That is true.

Also, some time in the past week, this thread went past 100k views ... a far cry from CA, dynamix, preclear, unassigned devices, et al., but ... it still counts for something ! 🙌 🙌

I just noticed something 👀

Are you running the latest app version? (4.9.0) I think I need to update the plugin as well but the app and the plugin are independent.

I don't know why I hadn't heard about this docker before. I noticed an immediate write speed bump (with turbo write), after replacing a drive that was on the outs. Very nice docker !

v4.9.0 is available on the App Store / Play Store ! This release includes the following fixes: - Fix stop array issue - Fix issue with dockers not appearing

Is your SSL set to auto or yes ? If not, use port 80 (or whatever http port you set up).

Ok, I'll pm you

Yes, that's strange. I tested against rc7 when it came out and the app works (currently running rc7 on my test server). Did you change anything when it stopped working ? SSL settings ? Added any docker or such ? If it's none of the above, would you remove and reinstall the app, just to check ? Let me know how it goes and we take it from there.

Yes, there's some issue in 'reverse proxy on the Unraid server' scenarios. Can't quite figure it out yet though.

Could not have said it better myself 😁 👍 I have an update pending, I added elapsed time and some other stuff. Can't quite remember why I haven't published it yet 🤷🏼‍♂️

Is it possible you're running 6.7.0-rc5 ? This version supports ONLY 6.7.0-rc6, as well as past stables. There are differences between rc's and since they're short-lived, doesn't make sense to support each one.

I remember reading somewhere/sometime that limetech have plans for user logins. I'll wait for that implementation 😁 👍