I've had this issue once or twice in the last 2 months, but just upgraded to Unraid 7.1.4 and it's happened again after around 7-8 hours or so of the upgrade. No idea whats causing it.

Everything works fine, then for no reason i goto access a share on windows which fails, check unraid's dashboard and notice there are no shares being exported. Reboot brings it all back.

Anonymized diagnostics attached - Can anyone shed some light on it?

mediaserver-diagnostics-20250812-0037.zip

Aug 11 21:09:15 MediaServer shfs: shfs: ../lib/fuse.c:1402: unlink_node: Assertion `node->nlookup > 1' failed.

It's this issue:

https://forums.unraid.net/bug-reports/stable-releases/683-shfs-error-results-in-lost-mntuser-r939/

Some workarounds discussed there, mostly disable NFS if not needed or you can change everything to SMB, can also be caused by Tdarr if you use that.

Thanks JorgeB .

This is not good.

I don't use Tdarr, But i do use NFS - For more responsive file transfers to both my MAC's and for ALL my media shares to my mediacenters.

Why would this have ramped up after my move to 7.1.4 from 7.0.1? Server i now unusable, happening with a few hours of reboots.

I've also noticed that mover is not moving files off the cache to the array, related?

1 hour ago, thestraycat said:

I've also noticed that mover is not moving files off the cache to the array, related?

That should be unrelated. Enable mover logging, run the mover, post new diags and the names of the shares(s) you expect to be moved.

Will do. I'll post them this evening. Thanks for the help - It's appreciated.

@JorgeB Here you go.

So mover seems to be ignoring the "TVSeries" user share when runner mover automatically and manually. Even though I have a test file downloaded to the cache ready to move.

All other folders that are set to cache > array work as expected. for eg. "TVseries4K", "Documentarys" etc. All move fine.

Permissions look the same between a known good folder (TVSeries4K) and the problematic folder (TVSeries) that refuses to move.

Both shares look identical in Unraid UI > Shares.

"TVSeries" User Share.

"TVSeries4K" User Share.

Diagnostics captured after running the mover manually with fresh files in the cache folder "TVSeries" that are ready be moved to the user share "TVSeries"

Interestingly, i've noticed that the files that mover should be moving to the array on the cache are already showing up on the array. So there showing both places at once. (cache + array)

When i delete the test file from the array, the copy on the cache dissapears

When i delete the test file from the cache, the copy on the array dissapears.

Its like there symlinked instead of the file being "moved" from cache to Array which would be the expected behaviour.

Is there any state file i can delete for the mover at all? All i see in the syslog is "Mover started - Moved finished"

mediaserver-diagnostics (after running mover)-20250814-0042.zip

Edited August 13, 2025Aug 13 by thestraycat

Looks like a case issue; post the output from ls -l /boot/config/shares/T*

You might be onto something there. The configuration file references "TVseries" (with NO capital S for series.)

My share shows as "TVSeries" (WITH a capital S for series.)

Obviously this path is referenced as "TVSeries" throughout a lot of services. Can i just stop the array and rename this .cfg file to "TVSeries" (wit the capital S) and restart the array?

Edited August 15, 2025Aug 15 by thestraycat

3 minutes ago, thestraycat said:

Can i just stop the array and rename this .cfg file to "TVSeries" (wit the capital S) and restart the array

That should work. With current releases of Unraid it is important that the capitalisation of the share .cfg files is identical to the actual folders on the drives.

Thanks for confirming - I'll try it now. I wonder why it hasn't updated the .cfg file when the share name was tweaked? Old share in use at the time no doubt via an openfile or container?

Edited August 15, 2025Aug 15 by thestraycat

Yup thats fixed the mover issue. (TVseries.cfg > TVSeries.cfg)

I'm now testing to see if the user shares dissapearing issue is resolved but wont know for a week or so.

Thanks @JorgeB and @itimpi for the timely assistance.

Edited August 15, 2025Aug 15 by thestraycat