kimdu

To close this, I had no issues anymore at all. Solution was one of the two things in my last post.

After one day after upgrading to 6.12.6 my server crashed... But after doing the following things everything is running fine: 1. Unistalled all unassigned plugins and reinstalled them (was a hint from here: Link 2. Follow the instructions for the "new" way to fix mtacvlan call traces introduced with 6,12,4 Maybe just number two did the trick. I will come back again when a little bit more time has passed. Hopefully to say everything is still fine. Sorry for using the forum as my personal mind map / notebook thing

Happened two times since my last update. I limited every Docker Container I have to in total 34 GB of RAM. Should be no problem I think. I also upgraded to Unraid 6.12.6 finally from 6.11.5. Hopefully this helps. I will check it in the next two weeks and update here.

Not enough RAM is definitely not the issue here. I have 64GB installed and the server does not use more than about 25% on average at the moment. But I honestly never thought of fragmentation. Ok, I will start with limiting RAM for docker containers. Some already are limited, the latest ones I installed are not. Since the issue happens only once a month or so, my next update after trying your suggestions might be not in the near future

Hi everyone, since a few month my Unraid server starts showing the error: "Out Of Memory errors detected on your server" out of nowhere every month or so. Reboot fixes it but seems not to be a fix. I'm not sure where to look in the diagnostics files. Could you please support me in finding the problem? Thanks in advance! Newest Diagnostics are attached homeserver-diagnostics-20231112-1601.zip

Here's what I tried: reboot unraid server delete remote share and try to recreate The final solution was simple and a little bit strange: The vm hosting the share I want to mount uses mullvad vpn cli-client. I thought to activate split-tunneling should be enough, but unfortunately unraid is only connect to the share when the vpn is disconnected. Without vpn everything works fine. I will check whether split-tunneling is editable within the mullvad client to get to work with and without active vpn tunnel. Thank you for your time and keep up the great work!

It definitly is, unraid is able to load the share I want to connect to. I chossed the share from the drop down menue. Both machines are on the same network. And as mentioned, other windows pcs on the same network are able to connect to this smb share without a problem. Are there any tests I can do, to get more information from unraid?

To start with positiv things, your plugin is one of my favorites. I use it as long as I'm running my unraid server. But unfortunately I have an issue and I don't know what happened. Since the last update of the plugin, I can't mount my smb share from one of my unraid linux vms. The smb share is mountable with my windows machines wihtout a problem. Here ist the log output with the errors: Oct 19 16:45:46 HomeServer unassigned.devices: Mount SMB share '//192.168.178.205/Down-01' using SMB3 protocol. Oct 19 16:45:46 HomeServer unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.0,credentials='/tmp/unassigned.devices/credentials_Down-01' '//192.168.178.205/Down-01' '/mnt/disks/192.168.178.205_Down-01' Oct 19 16:45:56 HomeServer kernel: CIFS VFS: cifs_mount failed w/return code = -512 Oct 19 16:45:56 HomeServer unassigned.devices: Error: shell_exec(/sbin/mount -t cifs -o rw,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.0,credentials='/tmp/unassigned.devices/credentials_Down-01' '//192.168.178.205/Down-01' '/mnt/disks/192.168.178.205_Down-01' 2>&1) took longer than 10s! Oct 19 16:45:56 HomeServer unassigned.devices: SMB3 mount failed: command timed out. Oct 19 16:45:56 HomeServer unassigned.devices: Mount SMB share '//192.168.178.205/Down-01' using SMB2 protocol. Oct 19 16:45:56 HomeServer unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=2.0,credentials='/tmp/unassigned.devices/credentials_Down-01' '//192.168.178.205/Down-01' '/mnt/disks/192.168.178.205_Down-01' Oct 19 16:46:06 HomeServer kernel: CIFS VFS: cifs_mount failed w/return code = -512 Oct 19 16:46:06 HomeServer unassigned.devices: Error: shell_exec(/sbin/mount -t cifs -o rw,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=2.0,credentials='/tmp/unassigned.devices/credentials_Down-01' '//192.168.178.205/Down-01' '/mnt/disks/192.168.178.205_Down-01' 2>&1) took longer than 10s! Oct 19 16:46:06 HomeServer unassigned.devices: SMB2 mount failed: command timed out. Oct 19 16:46:06 HomeServer unassigned.devices: Mount SMB share '//192.168.178.205/Down-01' using SMB1 protocol. Oct 19 16:46:06 HomeServer unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=1.0,credentials='/tmp/unassigned.devices/credentials_Down-01' '//192.168.178.205/Down-01' '/mnt/disks/192.168.178.205_Down-01' Oct 19 16:46:16 HomeServer kernel: CIFS VFS: cifs_mount failed w/return code = -512 Oct 19 16:46:16 HomeServer unassigned.devices: Error: shell_exec(/sbin/mount -t cifs -o rw,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=1.0,credentials='/tmp/unassigned.devices/credentials_Down-01' '//192.168.178.205/Down-01' '/mnt/disks/192.168.178.205_Down-01' 2>&1) took longer than 10s! Oct 19 16:46:16 HomeServer unassigned.devices: SMB1 mount failed: command timed out. Oct 19 16:46:16 HomeServer unassigned.devices: Mount of '//192.168.178.205/Down-01' failed. Error message: 'command timed out'. Hope you can help me to sort this out.