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

Having an issue with the History Tab this morning.  I tried moving the unbalanced.hist file to unbalanced.hist.old - no difference.  Other tabs seem to work fine.  I am moving data off of a parity emulated drive that took a crap on me, using rsync directly for time being so I can have some history to know what I still need to transfer (basically up arrow console history to review what commands I have run already).

 

I'm seeing the same issue with 2024.12.22 where the History tab throws the application error page. It's also occurring with Settings > Reserved Space.

For me, I see it when an unbalanced run completes. Appears to be successful, yet this error pops up upon completion.

looking into the history/settings > reserved issue

 

Came to report same error

should be fixed in 2024.12.23, let me know otherwise

 

thanks for the reports !!!

Just updated....now I can't find it in Settings? 😅

CTRL+F5 without success

 

Settings/unbalanced is empty

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

I am unable to stop the transfer process using 2024.12.23a. The red Stop button fades but the process continues.

 

PS: Okay I refreshed the unbalance page and tried again and this time it stopped as should.

Edited December 24, 20241 yr by interwebtech
fixed itself

This plug-in is a life saver. I am on the last 12TB disk of the original 11 ReiserFS formatted drives (18 total). Been thinking about updating for years but always put it off as a massive hassle I would rather avoid. Finally jumped in when I read that 2025 is the year ReiserFS is being dropped from the kernel.

Took me a minute (close to 2.5 days per drive) to get it done but now its almost over and I am ready to put this behind me. If you haven't already, send Juan a donation to acknowledge how useful his add-ons are especially this one at this time ;).

Happy holidays Juan!

Edited December 28, 20241 yr by interwebtech

I ran into a problem where Unbalanced didn't delete/remove the source file/folders.  Since I don't know anything else to do, I naturally retried moving the folders again, multiple time.  Now I'm left with duplicates scattered among a lot of drives.  I didn't start to notice this problem until I noticed my drives filling up faster than I before I started.

 

Is there an easy and programmatic method to cleanup the scattered duplicates?

15 hours ago, Jaybau said:

Is there an easy and programmatic method to cleanup the scattered duplicates?

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

Am I using scatter wrong? I want to move 14TB from disk 9 to all other disks in my array that have 51TB free, but the logs say that there is not enough space on the target disks. Is there something that I am missing? Thank you!

Try deselecting the parent folders and expanding them so you can select the individual folders underneath.  I believe it is looking for one drive with enough space for the entire parent folder, and that's too much data for any of your drives.  But ignoring the parent folder will give it smaller child folders to work with.  I bet it works just fine once you do that.  Although you might also want to check into the issues it lists.  Probably need to go into unRAID's Tools, New Permissions, and in the right-hand drop-down menu select All and then hit start.  Once that finishes, go back to the unbalanced page and reload it so it re-reads file info.  I've seen persistent issues that no longer exist if I don't reload.

Edited January 13, 20251 yr by _Shorty

Hi, is it normal that the MOVE command leaves empty folders behind on original disk?

It does for me, but what I do is run the move again without making any changes. Sometimes do it twice, but all the folders eventually get deleted. So if you do a Scatter, when it finishes, select the Scatter tab again and do Next, Next, etc. to accept the same settings that were there before. 

Hi all, I have emptied the disk and nothing shows up when I re-run unbalance, but I still have a parent directory showing from the main screen. Is it safe to delete this directory before zeroing the disk and which is the best way to do this ?

Thanks in advance.

Nic

 

On 1/18/2025 at 8:06 PM, mklecka said:

Hi, is it normal that the MOVE command leaves empty folders behind on original disk?

it could leave behind folders that had issues when moving

also, top level (shares) folders are not moved

8 hours ago, Fence said:

nothing shows up when I re-run unbalance

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 ?)

25 minutes ago, jbrodriguez said:

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 ?)

During the initial scatter operation I selected all the available folders then hit move.

 

After this I rebooted unraid and opened unbalance to check if anything was left behind, there were a few empty folders so I repeated the operation as suggested in the video from spaceinvaderone.

 

Now if I run unbalance it shows nothing to move from the disk but if I go to the main page on unraid there is still a parent directory as shown in the screenshot with 0 bytes and lots of empty folders.

 

I want to zero the disk as I am shrinking my array and I want to know if it is safe to delete these folders and also the safest way to do so. Thanks JB

 

Correct me if I am wrong but the act of zeroing the drive will eliminate all folders (overwrite w/zeros) anyway. Same with converting and formatting.

4 hours ago, Fence said:

shrinking my array

Safest and simplest (also safer because simpler) way to shrink is to use the "normal" method, which rebuilds parity instead of relying on manual, multi-step process of clearing a disk while it's still in the array.

 

https://docs.unraid.net/unraid-os/manual/storage-management/#removing-data-disks

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?

Edited February 10, 20251 yr by 012315

On 12/23/2024 at 7:41 AM, sentient-russ said:

Having an issue with the History Tab this morning.  I tried moving the unbalanced.hist file to unbalanced.hist.old - no difference.  Other tabs seem to work fine.  I am moving data off of a parity emulated drive that took a crap on me, using rsync directly for time being so I can have some history to know what I still need to transfer (basically up arrow console history to review what commands I have run already).

 

 

I am having this same, or very similar, issue on v2024.12.23a when trying to use Gather. When it happens the UI is completely crashed and I have to stop/restart the plugin before I can interact with it again. 

 

Edited February 13, 20251 yr by WalkerJ