To manually balance my array's drives, I used Dynamix File Explorer's move tool to group some TV series folders, in a share that straddles two disks, into the least filled one. The UI let me choose the destination folder (a newly created one), and once launched I could see the progress in the File Explorer and the drives' activity in the main window, its speed being as expected.

But when checking the result I saw that it had hardly created some subdirectories and moved a few files. 95% of the material is just gone.

The only thing I can think that could be an issue is that I had Krusader open in another webbrowser tab (I tipically have it so). Could that be a factor?

I'm on Unraid 7.3.1.

(Is there any procedure to have Unraid check the Array's drives and shares for inconsistencies that might let me try to rescue that material? It's not that crucial and could have it around in some old HDDs, but…)

Please post the diagnostics and also a screenshot showing the copy paths used.

54 minutes ago, JorgeB said:

Please post the diagnostics and also a screenshot showing the copy paths used.

Thank you for your assistance. The destination folder was created before the move operation (the origin one no longer exists, so, I've recreated it). The ones in the destination hardly hold one or two files instead of the complete seasons they ought to.

(I don't use the cache pool for staging, so, typically file transfers go directly to the Array)

nas-diagnostics-20260627-2243.zip

Edited June 28Jun 28 by MetricTonto

Never heard of a problem like that using the built-in file manager. Difficult to see how it happened as source files should not be removed until destination file has successfully been created.

Having said that your syslog is full of hundreds of messages of the form:

Jun 27 13:26:15 NAS nginx: 2026/06/27 13:26:15 [alert] 13542#13542: worker process 160061 exited on signal 6

Jun 27 13:26:15 NAS nginx: 2026/06/27 13:26:15 [alert] 13542#13542: worker process 160121 exited on signal 6

Jun 27 13:26:16 NAS nginx: 2026/06/27 13:26:16 [alert] 13542#13542: worker process 160122 exited on signal 6

Jun 27 13:26:17 NAS nginx: 2026/06/27 13:26:17 [alert] 13542#13542: worker process 160129 exited on signal 6

which I assume must relate to the issue you saw, but I am not sure how.

I see. Thanks for taking the time to investigate and highlight that. I guess I could produce some tests (get some TV episode file, duplicate it to a quantity enough to pass for a multi-season collection, try again, and monitor the process).

(Previous balancing adventures used the Unbalanced tool. I'll limit myself to it fornow)

I'm unable to reproduce, see if you can repro the issue (using test data) with a couple of the folders with the same or similar names as you had before.

5 hours ago, MetricTonto said:

(I don't use the cache pool for staging, so, typically file transfers go directly to the Array)

Cache wouldn't be involved in this anyway since the destination is an array disk. Caching only applies to user shares.

21 hours ago, trurl said:

Cache wouldn't be involved in this anyway since the destination is an array disk. Caching only applies to user shares.

You are right. I was grasping at straws.

(Possibly unrelated, but who knows: the WebGUI, both locally and remotely, started to show enormous lag. I've rebooted and things seem normal now)