I am unsure how long this has been an issue. I have tried stopping all my dockers and rebooting. I do not have mover tuning installed. My storage direction for Cache -> Array is configured the way I want it. I am unsure what to do next other than a fresh install. I am attaching my diagnostics for support, mover logging was enabled.

smokebox-diagnostics-20250811-2052.zip

trying to use unbalance first will report back if still having issues

As my mover has been running on my system for days (and I have little to no data on it). It is preventing my stopping the array. Advice on how to proceed would be appreciated.

Should I reboot in safe mode .. will that stop the mover? Is it safe reboot with the mover active?

tower-diagnostics-20250811-1848.zip

I've included this in case it helps.

1 hour ago, ethyr2000 said:

As my mover has been running on my system for days (and I have little to no data on it). It is preventing my stopping the array. Advice on how to proceed would be appreciated.

You might want to start your own thread

Just so there's a record. I rebooted in safe mode. Downgraded to 7.1.2. I'm currently going through checks on the system. As I had no data, this seems to have been fine.

5 hours ago, Supershocker said:

My storage direction for Cache -> Array is configured the way I want it. I am unsure what to do next other than a fresh install.

What is the share name(s) you are trying to move?

5 hours ago, ethyr2000 said:

As my mover has been running on my system for days

Please start your own thread; it can get confusing trying to help multiple users in the same one.

I came here looking for a solution too

not running any mover addon or mod (mover tuner etc)

not torrenting from my server at all that can cause constant access to the files. (i do have a Syncthing instance running comparing the download folder and my seedbox) - but as the issue happens in my download and my media (plex) folders i dont think that is the cause

files and directory goto download folders, mover will copy the folder and smaller files to the drive (.info files screenshots etc) but the actual video files remain cache only.

logs show "has 1 dangling link(s)" just like OP's logs

so have been using MC to manually move the files from cache to the drive its put the folders on.

not here to try and take over thread, i think i have same issue as OP

just been moving manually every few days to keep my cache drive clear

hoping for a solution (i thought maybe its a permissions issue on the files? - no idea, also 7.1.4

Thank you all 🫶

17 minutes ago, radfx said:

logs show "has 1 dangling link(s)"

See if this applies to you and also to the OP @Supershocker :

https://forums.unraid.net/topic/192352-mover-not-moving-files-from-cache-to-array/#findComment-1571982

1 hour ago, JorgeB said:

See if this applies to you and also to the OP @Supershocker :

https://forums.unraid.net/topic/192352-mover-not-moving-files-from-cache-to-array/#findComment-1571982

Hi JorgeB, thank you for the link, and i can see how having some apps pointing to the cache folders directly can break things but i was very careful when i get all this up in 2018 to use /mnt/usr folders.

The setup was download to downloads /mnt/user/downloads thats is setup for Array -> Cache (this folder is synced with a seedbox via Syncthing and it just downloaded locally

then the local sync is complete, radarr grabs them and moves them to the /mnt/user/media/ folders that are also set for Cache-> Array, i did this so if i imported a large series of LINUX IOS's it would do it quickly. then overnight move them quietly to the array

so new LINUX IOS's being accessed by a few people as they are new and just downloaded would be off the cache and not spinning discs up.

I do see that my Sonarr has hardlinks enabled, but this setup has been working for years and the mnt/user/downloads movement has the same issues before sonarr touches anything..

say there is a file structure like this:

<linux folder>

new linux.iso

new linux.pdf

new linux.jpg

The folder <linux folder> is copied onto the array (in this instance, mnt/user/disk4/downloads) along with the pdf and jpg (the the smaller files removed from cache as expected), but the larger file remains throwing up errors in the logs.

So maybe my setup worked before unraid 7 and id need to change something, but I am not sure what as i cannot see anything pointing directly to the cache or a specific disk.

Thank you for the help, sorry im dumb and this is the best explanation i can give

9 minutes ago, radfx said:

I do see that my Sonarr has hardlinks enabled, but this setup has been working for years

There was a recent change in the mover regarding behavior with hard links since Unraid 7.0.0, because the old behavior caused some users to break the hard links and endup with multiple copies of the same file. This would happen if you have files crosslinked on the different shares and then run the mover for both.

There are some use cases when the old behavior could be preferable. Let me discuss this with LT to see if something can be done.

29 minutes ago, radfx said:

The setup was download to downloads /mnt/user/downloads thats is setup for Array -> Cache (this folder is synced with a seedbox via Syncthing and it just downloaded locally

then the local sync is complete, radarr grabs them and moves them to the /mnt/user/media/ folders that are also set for Cache-> Array

Though note, that with your use case, it's precisely the one that would end up with multiple copies of the same file; the hard link would be broken, and the files would be moved individually and duplicated.

2 minutes ago, JorgeB said:

Though note, that with your use case, it's precisely the one that would end up with multiple copies of the same file; the hard link would be broken, and the files would be moved individually and duplicated.

I have just manually moved and cleared out my downloads folder for the temp files and the sonarr files, so now running the mover instantly says ok finished.

i copied a 8gb file from my network to my downloads share (which is cache>array) after the copy, it was on mnt/cache/downloads only as expected.

ran the mover and a few mins later, the file was fully moved to mnt/disk4/downloads without issue..

so only thing i can think of here is the syncthing is causing the files to be locked like some people have with active torrents or has some weird permission issues? before sonarr with its hardlinks even touches anything, this is what I am seeing.

and im not seeing duplicates (exept the folder), its like it copied the folder and moved the smaller files (like the .info and screenshot.jpg's etc but left the .mkv files with errors)

thank you again for your help!

while all this isnt life ending, i had it working for ages and only really noticed my cache drive filling up and this is why :D

but copying my own file via the network thats large (8gb) and set the mover, went without issue.

3 minutes ago, radfx said:

i copied a 8gb file from my network to my downloads share (which is cache>array) after the copy, it was on mnt/cache/downloads only as expected.

ran the mover and a few mins later, the file was fully moved to mnt/disk4/downloads without issue..

That should always work correcly, the issue is if you have hard links across different shares, example:

A file is initially downloaded to /mnt/cache/downloads

Then you or an app creates a hard link to /mnt/cache/media

With the old mover, if both shares are set to cache=yes, it would move first one of those files and unlink it, then move the other one to the other share, so in the end, you would have the same file duplicated across two shares. The new mover does not allow this, and that's when you see the "has 1 dangling link" error.

Now there's a possible use case where the old behavior was desired, for example:

A file is initially downloaded to /mnt/cache/downloads but this share is set to cache=only, for temporary seeding for example

Then you or an app creates a hard link to /mnt/cache/media

With previous releases, the mover would run and the file from media would be moved to the array, the one in download would later be deleted manually by the user, so it would never duplicate a file in the array. With the new mover behavior, this file would fail to move.

21 minutes ago, JorgeB said:

That should always work correcly, the issue is if you have hard links across different shares, example:

A file is initially downloaded to /mnt/cache/downloads

Then you or an app creates a hard link to /mnt/cache/media

This is the odd part, mine doesnt change folders like that

forget for a moment I have sonarr doing anything.

I have syncthing downloading from a remote server to /mnt/user/downloads

because i have Unraid setup for this share to be Cache-> array, the file ends up existing on /mnt/cache/downloads

then at 3AM , unraid does its move and picks what drive to put it on (my largest now is disk4 so it supposed to move to mnt/disk4/downloads but thats all unraid behind the scenes, (which is exactly what happened when i copied my 8gb test file earlier)

(sorry its nearly 4am here now and im probably not thinking straight)

unless because sonarr touches those downloaded files and hardlinks them to then move to a media folder and rename/organise and as that point the originally downloaded files have been hardlinked and causing the issues.

i have turned off hardlinks in sonarr and will try some experiments with sonarr shut down to see if just pulling the file via syncthing blocks the mover..

thank you again for your help i really appreciate it!

Most users, I would say, are configuring their "downloads" is under a single share lets call it "data"

Files downloaded would go to /mnt/user/data/downloads/... and would then be hardlinked to /mnt/user/data/media/... when mover runs using the updated mover, both of these files are moved to the same disk that way they only occupy 1 file copy worth of space.

So after mover ran, you'd be left with /mnt/disk4/data/downloads/,,, and a hardlink in /mnt/disk4/data/media/...

7 minutes ago, MowMdown said:

Most users, I would say, are configuring their "downloads" is under a single share lets call it "data"

Files downloaded would go to /mnt/user/data/downloads/... and would then be hardlinked to /mnt/user/data/media/... when mover runs using the updated mover, both of these files are moved to the same disk that way they only occupy 1 file copy worth of space.

So after mover ran, you'd be left with /mnt/disk4/data/downloads/,,, and a hardlink in /mnt/disk4/data/media/...

I think my issue is wrapping my brain around the mapping

Sure I have a download folder then a media/tv show folder but I leave the original files in download and what I thought was happening is the RR app was copying from downloads into the media (while both still exiting on the cache drive) renaming them to make plex happy and then 3am rolls around and everything gets moved to the respective spinning disk homes

But if the RR app was touching the original downloaded file then make a hard link from that then renaming etc to the other folder it seems it was breaking the new mover.

I turned off all hardlink options from the RR apps and some new .. LINUX ISO’s were downloaded.

They were sorted imported etc as normal. I ran mover and it was happy, no errors.

So end result. Turning off all my hardlink options in my RR’s solved it

Hope this may help OP and thank you all for your help

It didn’t click for me because I have the apps linked to the same folder all going to and looking at mnt/user/downloads and didn’t have it mapped as anything else but the RR’s do copy them to a new folder to rename etc. I thought leaving the originals untouched

It’s 4:30am , I think it’s working. A million internet points to you all 😁