jbrodriguez

hi, yea, current logic doesn't fully support pools. i want to migrate to use unraid api which should support pools (just looking into it right now)

mm that's odd, when did it change for you ? should work normally it works for me, although i use wireguard directly, tailscale should be the same since it uses wireguard internally as well

it depends and is up to you, the plugin defers the decision, since it requires manual intervention, the user may have the best context in the matter if it was a no space left issue, i wouldnt delete the source

added some logging in 2025.02.22, if the crash happens again, pls go to view > developer > console (in chrome), to check the error and potentially figure out what's causing it

hi, the plugin doesn't delete the source until the target has been moved, so you can try again, select a smaller set of files perhaps ?

pushed a fix for the issue with the docker operations, will be available in 6.9.5 (whenever apple & google complete their review process)

pushed a fix for the issue with the docker operations, will be available in 6.9.5 (whenever apple & google complete their review process)

will take a look

thanks @bmartino1! im still a bit confused though, i don't remember cache drives being part of parity (also mentioned in the docs, https://docs.unraid.net/legacy/FAQ/cache-disk/#overview) i know pools are different in Unraid 7, just not sure how to move forward also, i dont remember this happening when i added a cache drive on a 6.x system a while back maybe the dialog isn't picking up that i want to format a cache drive, not an array drive ? the wording "Create an empty file system on the disks shown as Unmountable discarding all data currently on the disks and update parity to reflect this" is what makes me doubt

hey, i just installed an nvme in order to use it for jellyfin (docker), it's set as a pool device, only now that i try to format it, it's telling me it will update parity i dont really want it to affect parity, what should i do ? also, i have a docker setup pointing to hard drives docker is it ok to just point it to the cache drive once working (ony one docker there which i can delete without issues)

fixed the issue with the icon to open docker's web ui in 6.9.4

fixed an issue with the icon to open docker's web ui in 6.9.4

hmm, strange that it seems to have surfaced only now, hopefully by this weekend i have my dev environment set up again, will probably add some logging, although unbalanced doesn't have any error telemetry, so will need to wait for the app update, wait for the error to happen again and post logs 🤷‍♂️ 😀

im looking into the issue of the webui link, need to restore my dev env

hi, did you recently upgrade to Unraid 7 ? i wonder if something changed in the latest betas (i tested up to the rc's)

not sure what you mean with nothing shows up note that unbalanced won't delete top level folders, as these are Unraid shares (perhaps with some exceptions ?)

it could leave behind folders that had issues when moving also, top level (shares) folders are not moved

thanks for the report, the app worked through the rcs, maybe something changed in the final code ill look into it

odd, it worked with the rc's ... will look into it

hi, are you connecting via ssl ? if that's the case, make sure to connect using the lets encrypt certificate endpoint more info here https://www.apertoire.com/faq/controlr#cant-connect

you do have the operation history, which shows where the files/folders were copied to, you could "copy" the rsync commands and change them to a remove command on the target disks

right, i had an unhandled build error, pushed 2024.12.23a to fix it

should be fixed in 2024.12.23, let me know otherwise thanks for the reports !!!

looking into the history/settings > reserved issue

released unbalanced 2024.12.22, which restores the select all checkbox on scatter operation (i missed it too 😀)