so i not sure if its requested.. but for the next release of Unraid

id like to see a status of Mover

 

like any Copy  Move.  windows does.. also  if Mover crashed..  no one will know..  like windows has "Not Responding"  

 

as i moving 2tb  off my Lancahce      its been like 24 hours  and  2.9 million files   but nothing has moved

 

dont even know if its running all i see is some mb/s  accessing the pool..  but i have no idea if is working where it is in the at 2.9  million files

if its locked up    like i had btrfs  that crashed  i posted..    and you'd never know it crashed..  till you report the diagnostic..  but even unraid doesnt report a crash of the btrfs   of the array  when  it was doing the pool...  so     be nice a current running lo of

time elapsed    time left    current move..

 

as like i cant tell  same with that btrfs  that crashed making a pool  wouldnt know till. the array was never mounting

 

 

Edited December 15, 20214 yr by comet424

Yes, and there's a PR request already existing for changing the UI to show this.

ah ok..  my bad then.. figured  id ask just incase 🙂

 

what does PR means?   previous request?

1 minute ago, comet424 said:

what does PR means? 

Pull requst in Github https://github.com/limetech/webgui/pulls

ah ok..  should i re post my comment then in the github too?

 

 

learn something new everyday... 🙂

 

4 minutes ago, comet424 said:

ah ok..  should i re post my comment then in the github too?

 

 

learn something new everyday... 🙂

 

My PR is already there on Github, its awaiting inclusion by Limetech. You will only be ab!e to raise an issue, but there is already code to provide mover status,

 

 

Edited December 15, 20214 yr by SimonF

ah ok..  and that was back in 2016 and they werent ever to make it work eh..  

i read that page talked about a navigation button  but i dont have a naviagation  button to see some log....

so ill just probably run  krusader if nothing happens by tomorrow...  

Here is the PR request for this coming in future release , there is an nice example screen shot

https://github.com/limetech/webgui/pull/1042

its beautiful I would love to add that now! i have been trying to move a 214GB plex appdata folder from my ZFS 4 drive zpool to the array trying to get it on my newly formatted SSD in ZFS) for over 13 hours its moving sooo slowly

i need to see the status I have dozens of messages coming in why my plex is down...it litterally not showing in the logs that its moving

I see trickles of data on Disk1 and the ZFS cache-pool here and there but it is taking forever....the initial appdata move of over 500GB from BTRF to array took 4 hours

What's happened with this? It's a basic feature that, while not required often, would make a tremendous difference when it's needed.

I am currently in the trial of this and I must say, for a paid OS this seems like a basic feature that should be included. Is there any more info on this? Seems this has been asked for since 2015 and it still hasn't been added.

1. its probably not simple to have a reliable number to provide in general

2. its getting more and more complex with multiple share moving files from one pool to the Array or the other way around What to show then ?

3. and more importantly, I think that 95% of people run their mover on a server downtime and don't care much. For me it runs while I am sleeping, so it take the time it needs.

All this put together, probably make a high effort low reward task and probably for a low percentage of the userbase.

I don't believe its hard, nor overly complex... but the mover binary is closed source, and that's where the changes really need to happen to make front end progress visualisation easy.

Pretty much impossible to predict file operation durations, probably even more so in the unraid mover situation where many different file sizes and storage devices may be involved and concurrent operations are highly likely. Time-wise all you'd get is something fluctuating so much it'd be useless, but yeah overall progress would be nice to see even if it doesn't mean that much.

Edited September 2, 2025Sep 2 by Kilrah

I don't even need a estimated time, just seeing the progress like the log shows would do wonders. Even showing an estimated time would be great even if it fluctuates. In my current situation the mover is a black box and I am completely in the dark to see if its actually working or not. I have been waiting 2 days for my cache to unload and I have no idea if the mover is even still working.

After stopping it one time in fear that it stalled. I restarted it remotely using the terminal which actually provided some verbosity which helped TONS, as I could see the total files needing to be moved as well as the file number in that queue. Here's the problem - I had to sleep the computer I started this command from and upon waking it no longer had access to this terminal session so I lost the ability to see. I am doing an initial onboard of data, so some 900,000 files need to be transferred and the progress was agonizingly slow. From what I have read, this is normal and a consequence of the xfs format's convenience. To add to the frustration, my GUI stopped working both on the localhost / remotely which made me even more weary. I eventually diagnosed this as nginx crashing and restarted the process, however I'm not sure of why or when it crashed as I do not see anything in the log about it.

In hindsight I should have hooked up a monitor, mouse and keyboard to the host machine and launched the terminal command from there so I wouldn't have run into this issue, but as it stands I am at a crossroads. Do I keep waiting hoping it is still working or do I stop and start it again going this route instead? Either decision I make eats into my trial time.

12 hours ago, D3K17 said:

Here's the problem - I had to sleep the computer I started this command from and upon waking it no longer had access to this terminal session so I lost the ability to see. I am doing an initial onboard of data, so some 900,000 files need to be transferred and the progress was agonizingly slow.

For this issue, take a look at the Tmux plugin which will keep the terminal session running and allow you to rejoin later.
https://forums.unraid.net/topic/183427-plugin-tmux-terminal-manager-ttm/

We have a Test, Trying, Requests, Thread in older Versions from @SimonF : https://forums.unraid.net/topic/51179-mover-bar-or-information/

https://github.com/unraid/webgui/pull/1042/commits/a91f1d52a61fb35eae3fc0d5829b8d9f7b906b7f

Edited September 7, 2025Sep 7 by Revan335

Quite likely that PR won't get merged due to the conflicts. Hopefully a new one will get issued at some point.