February 14, 20251 yr I am also having this issue when I try to move 1 certain folder called Applications. This is where most of my Docker container settings are. I have stopped my Docker containers, and the Docker vDisk is stored on my cache drive, not one of my array drives. This is the last folder of my reiserfs drive I started with back in 2015. Everything else is moved. The drive only shows 37.2GB used, and any of my other array drives have more than plenty of space for this. It will get through the planning, then when I move to the Transfer tab, it spins for a while. Only if I refresh the page do I see this error. I left it for 8 hours at one point and saw no updates. I'm on 2024.12.23a and Unraid 6.12.13
February 14, 20251 yr Author 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 🤷♂️ 😀 Edited February 14, 20251 yr by jbrodriguez
February 14, 20251 yr Interestingly enough, when I did the dry run first, then did the move this error did not occur. I also selected every folder inside the Applications instead of the Applications folder itself. But it occurred twice when I selected the Applications folder itself and just did the move without a dry run.
February 20, 20251 yr On 2/10/2025 at 9:21 PM, 012315 said: I've moved a 8TB btrfs disk to a 8TB encrypted zfs disk. The original disk was at 95% with about 500GB left I left the plugin to its thing. I come back to a completely full zfs drive and the old drive with still ~2TB on it. Logs show: I: 2025/02/09 14:24:20 core.go:817: monitor:transfer:(/mnt/disk1/hmedia/bits/movie.mkv) I: 2025/02/09 14:34:21 core.go:817: monitor:transfer:(/mnt/disk1/hmedia/bits/movie.mkv) W: 2025/02/09 14:35:26 shell.go:50: flag:(rsync: [receiver] write failed on "/mnt/disk4/hmedia/bits/movie.mkv": No space left on device (28) ) W: 2025/02/09 14:35:26 shell.go:50: flag:(rsync: [receiver] chown "/mnt/disk4/hmedia/bits/moviename/.moviename.mkv.uIE0if" failed: No space left on device (28) ) W: 2025/02/09 14:35:26 shell.go:50: flag:(rsync: [receiver] rename "/mnt/disk4/hmedia/bits/movienameH265-SiGMA/.movienameH265-SiGMA.mkv.uIE0if" -> "hmedia/bits/moviename.mkv": No space left on device (28) ) W: 2025/02/09 14:35:26 shell.go:50: flag:(rsync error: error in file IO (code 11) at receiver.c(380) [receiver=3.3.0] ) W: 2025/02/09 14:35:26 core.go:748: command:end:error(exit status 13) I: 2025/02/09 14:35:26 core.go:752: command:retcode(0):exitcode(13) I: 2025/02/09 14:35:26 core.go:1009: Command Finished I: 2025/02/09 14:35:26 core.go:1022: Current progress: 90.41% done ~ 3h48m7s left (50.82 MB/s) W: 2025/02/09 14:35:26 core.go:941: skipping:deletion:(rsync command was flagged):(/mnt/disk4/hmedia/bits) I: 2025/02/09 14:35:26 core.go:695: Command Started: (src: /mnt/disk1) rsync -avPR -X "hdata-a/DriveE" "/mnt/disk4/" W: 2025/02/09 14:35:26 shell.go:50: flag:(rsync: [generator] failed to set times on "/mnt/disk4/hdata-a": No space left on device (28) ) W: 2025/02/09 14:35:27 core.go:748: command:end:error(exit status 13) I: 2025/02/09 14:35:27 core.go:752: command:retcode(0):exitcode(13) I: 2025/02/09 14:35:27 core.go:1009: Command Finished I: 2025/02/09 14:35:27 core.go:1022: Current progress: 93.02% done ~ 2h41m18s left (52.29 MB/s) W: 2025/02/09 14:35:27 core.go:941: skipping:deletion:(rsync command was flagged):(/mnt/disk4/hdata-a/DriveE) I: 2025/02/09 14:35:27 core.go:695: Command Started: (src: /mnt/disk1) rsync -avPR -X "hmedia/PLEX" "/mnt/disk4/" W: 2025/02/09 14:35:27 shell.go:50: flag:(rsync: [generator] recv_generator: mkdir "/mnt/disk4/hmedia/PLEX" failed: No space left on device (28) ) W: 2025/02/09 14:35:27 shell.go:50: flag:(*** Skipping any contents from this failed directory *** and it goes on for the other folders like that since it ran out before. -> So I guess there is some zfs overhead or so and I should've set 2 disks as the copy target. I thought it would certaily fit. Anyways, what the best way to start over / continue where i left off to ensure no data loss? How should I proceed here?
February 22, 20251 yr Author On 2/20/2025 at 12:49 PM, 012315 said: How should I proceed here? 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 ?
February 22, 20251 yr Author 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
February 26, 20251 yr On 2/22/2025 at 11:59 PM, jbrodriguez said: 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 ? sure, are there any duplicate files now? pressing the "rmsrc" or similar would be a bad idea right? If this wipes the only copy of the files there should be a little warning or so.
February 26, 20251 yr Author 1 hour ago, 012315 said: pressing the "rmsrc" or similar would be a bad idea right? 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
February 26, 20251 yr Can someone explaine, what this plugin is doing? I selected two files to move, but only one was moved... is this normal?
February 27, 20251 yr 18 hours ago, jbrodriguez said: 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 Alright, thanks. Would there be duplicate files if the move/copy fails mid program, as it did on my end?
February 28, 20251 yr I'm in the process of moving my array to a new pool running ZFS - Is there a way to run multiple unbalance operations at the same time - There's plenty of disk IO capacity so I don't expect that is an issue, but I have 12 array data drives and it's going to take forever doing them one at a time. Or should I just manually run the rsync commands the plan generates and have them work behind the scenes?
March 16, 20251 yr I have some duplicates across disks (only show up once on usershare). Detailed description of my issue below. does unbalanced allow to fix this?
March 31, 20251 yr I'm moving urbackup backups that got stuck on my cache drive off to my array using unbalanced. (unRAID 7.0.1) It's not clearing out the folders entirely. I'm moving subfolders of a share a few at a time otherwise it can't seem to complete a plan. When it's "done" moving a group of subfolders the original folder is still there and *most* of the content is moved. The folder remains with a `.symlink_Content` file still in it. Any idea what's going on here? source folder after already moving/scattering: UPDATE: Got all major files moved via unBALANCE, mover handled the rest. Edited April 3, 20251 yr by NeoMatrixJR
April 13, 20251 yr I seem to be having problems with unbalanced and ZFS. I moved all my disks to ZFS one by one. I did move the majority of the data around with unbalanced. If you have ZFS Master installed you can see that some top level folders on my disks that were moved by unbalanced are not properly set up in ZFS on that disk. They are missing from the output of the command "zfs list" as well. It looks like unbalanced does not create the top level folders in zfs as unraid is expecting it. Mover seems to do that fine. If a top level folder was present on the destination disk before unbalance move was started, everything seems fine. If unbalance needs to create the top level folder, then the folder does not show up properly in ZFS Master. Here is a screenshot showing the problem: everything on disk8 and the folder data on disk7 was moved there by unbalanced. Any ideas on how to fix this beside evacuating data each disk with issues by using mover?
April 16, 20251 yr I have been using this plugin for quite some time, it has been really useful. But now I have been having an issue with it for some time, where I'm not able to start this plugin. No reinstalling doesn't help. This was in the log when trying to enable unbalanced server; Apr 16 00:00:00 Server ool www[3497639]: /usr/local/emhttp/plugins/unbalanced/scripts/start Apr 16 00:00:00 Server sSMTP[3498136]: Creating SSL connection to host Apr 16 00:00:00 Server sSMTP[3498136]: SSL connection using TLS_AES_256_GCM_SHA384 Apr 16 00:00:00 Server sSMTP[3498136]: Authorization failed (535 5.7.8 https://support.google.com/mail/?p=BadCredentials a640c23a62f3a-acb3ce5dbaesm177589766b.85 - gsmtp) unbalanced v2025.02.22 Unraid 7.0.1 Any ideas how to make it functioning again
April 24, 20251 yr I don't know what I've done wrong but I had a version from 2021 installed. Just uninstalled that plugin and reinstalled and holy cow it has changed. Don't be like me people! Check the dates on your plugins!
April 24, 20251 yr 1 minute ago, pinion said: Check the dates on your plugins! Install Fix Common Problems and it will check for you.
April 24, 20251 yr 2 minutes ago, trurl said: Install Fix Common Problems and it will check for you. I have that installed. You have to run it for it to work though. I'm just a terrible server maintainer!
April 24, 20251 yr 2 minutes ago, pinion said: You have to run it for it to work though Just let it run daily
April 26, 20251 yr Does this plugin have the ability to divide up subfolders automatically when using the scatter function? If I select a top-level folder called "media" that's 1.15tb in size, none of the folders within are selected. If I instead select all of the folders within, then they are each counted as a separate item to be allocated. This has been a major drawback of this plugin for years. If I select a higher level of a directory tree, I expect all levels within to be selected as well. I want the deepest subfolders to be treated as individual items to allocate to other disks. EDIT: A simple setting in the settings page called "Treat all subdirectories as individual items" would be amazing. Edited April 26, 20251 yr by JohnnyGrey Adding material.
May 17, 20251 yr I just booted my server up from some downtime and going through the motions this plugin was marked as not available and it was recommended to delete it. I am wondering why it was removed in the first place; does anyone know?
May 17, 20251 yr 3 hours ago, the_frapster said: I am wondering why it was removed in the first place; does anyone know? Are you sure you are talking about "unbalanceD" ? there was an "unbalance" before (without the "D" at the end), this was not compatible with recent UNRAID versions and has been dropped. The replacement was called "unbalanced", there was no automatic update, you have to deinstall the old one and then get the new one.
May 18, 20251 yr Author On 4/26/2025 at 12:17 PM, JohnnyGrey said: EDIT: A simple setting in the settings page called "Treat all subdirectories as individual items" would be amazing. probably not a bad idea, would need some sort of depth setting too
May 23, 20251 yr On 5/16/2025 at 10:44 PM, the_frapster said:I just booted my server up from some downtime and going through the motions this plugin was marked as not available and it was recommended to delete it. I am wondering why it was removed in the first place; does anyone know?I had this same issue also on the date you posted this. But it wasn't only for unbalanced. Several of my plugins on the plugin page were displaying this error.Thought it was strange and may be a temp github problem or something so i did nothing immediately. Checking the next day and all was fine once again.
May 24, 20251 yr 3 hours ago, wirenut said:I had this same issue also on the date you posted this. But it wasn't only for unbalanced. Several of my plugins on the plugin page were displaying this error.Thought it was strange and may be a temp github problem or something so i did nothing immediately. Checking the next day and all was fine once again.There was a spurious issue with at least one of the Dynamix plugins in and around then where it did get marked as blacklisted, uninstall it. This was due to a spurious GitHub issue, and the reason why it happened on the GH issue has been addressed.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.