Hi friends,

 

Today i found some errors in unraid that I couldn't find any info on. Any information on what would have triggered these?

 

 

I don't see any disk full errors on the dash, cache pool has utilization warning but that's about all that stands out.

 

 

 Also, I'm not sure if this following issue has anything to do with what my question is about, but adding it in just in case.

 

I found this because I had some issues today getting into my unraid dash. I was unable to get into the webgui on my main desktop or via phone. SSH was not working either. Entering root and password just refreshed the page a and wouldn't progress to the next page after auth. I suspect possibly related to these lines from the syslog which seem to have been ongoing for a couple days:

Oct 19 09:54:01 Jonsbo winbindd[8840]: [2024/10/19 09:54:01.233397,  0] ../../source3/winbindd/winbindd_samr.c:71(open_internal_samr_conn)
Oct 19 09:54:01 Jonsbo winbindd[8840]:   open_internal_samr_conn: Could not connect to samr pipe: NT_STATUS_CONNECTION_DISCONNECTED
Oct 19 09:55:01 Jonsbo winbindd[8840]: [2024/10/19 09:55:01.298789,  0] ../../source3/winbindd/winbindd_samr.c:71(open_internal_samr_conn)
Oct 19 09:55:01 Jonsbo winbindd[8840]:   open_internal_samr_conn: Could not connect to samr pipe: NT_STATUS_CONNECTION_DISCONNECTED
Oct 19 09:56:01 Jonsbo winbindd[8840]: [2024/10/19 09:56:01.368957,  0] ../../source3/winbindd/winbindd_samr.c:71(open_internal_samr_conn)
Oct 19 09:56:01 Jonsbo winbindd[8840]:   open_internal_samr_conn: Could not connect to samr pipe: NT_STATUS_CONNECTION_DISCONNECTED

 

After a few tries eventually from private browser session it let me log in on my phone, login from desktop then worked fine as well. Maybe this was because I had logged into the server gui a few days ago and kept the window open and active in a tab for that whole time, so possibly closing the old session and starting a new one fixed this maybe?

 

Appreciate any guidance anyone may have.

 

Thanks

 

Diagnostics attached: jonsbo-diagnostics-20241019-1027.zip

this sounds like a mover issues.

under share settings what is the mover options for the disk that is getting full?

per diagnostics. you using unraid beta 3

per redit for a fix:

 

Edit your go file at: /boot/config/go and add:

rm /usr/local/sbin/move

ln -s /usr/libexec/unraid/move /usr/local/sbin/move

and run mover after a reboot

 

Thanks @bmartino1

 

Yeah it's unraid beta 7. I didn't want to raise it as a bug in the beta 7 board, figuring it's possibly a general or maybe user error issue (still learning unraid ).

 

I've got 2 shares at the moment that are Cache > Array

1. Nextcloud share

2. Data share (setup per trash guides with cache pool)

 

None of the shares or drives were showing full at the time. Maybe the cache was getting close to being full around that time but at the time of posting, cache utilisation was around 76%. Mover tuning plugin is set to schedule mover run when utilisation reaches 80% moving down to 50% utilisation of the pool

 

Mover settings below:

 

 

- Note have since changed to trigger mover after utilisation is oer75%

 

 

Mover has run overnight and brought utilisation down to 50%

 

 

I don't see the same errors in the recent sys logs. Regardless I've added those 2 lines to the go file and done a reboot and manually triggered mover from the gui per your suggestion.

 

I've attached the latest diagnostic since the reboot in case this is of any interest.

jonsbo-diagnostics-20241024-1525.zip

@zdonkDid you conclude on the Mover being the cause of your error messages? I've struggled with exactly the same thing and could not find the source of it until I realized that the errors always happen within the maintenance window of Plex. With Plex container shut down it all goes away. I have to dig into what Plex is really doing and maybe tweak some of the settings.

I don't strictly know what the issue was. Could have been mover issues, maybe a session timeout as I had logged in and running in browser on my desktop overnight, or maybe something to do with unraid 7 beta, never really pinpointed what was going on. 

It sort of fixed itself after I managed to log back in. 

 

I implemented the changes suggested @bmartino1, hasn't recurred since then. But not sure if that's thanks to the mover settings I added or something else. Has been running rock solid ever since, no other issues manifested

Edited December 12, 20241 yr by zdonk

the mover commands are hit-and-miss. As there are 2 move plugin tuners.

 

I've had others use that command (mutiple forum post and a pull form redit for a floating workaround solution...) with the plugin installed and it worked. I've had others disable mover settings and remove the plugin and use unriads default mover application and it worked. It really depends on settings you set as there was a recent user who had to install the plugin again to remove a setting then uninstall to fix a issues when mover was called...

Its at least worth a test/try inf you are having mover issue.

Thanks makes sense

Has been running fine so haven't really needed to touch anything in mover tuner plugin. Fwitw this is the version of plugin I have installed 

 

Hope some of this info is of help @vhw