ailliano

Server is on same subnet unraid 172.18.108.10 and Synology at 172.18.108.100, I tried with automatic search and IP option, shares load fine with both choices.

Hello I'm unable to mount my Synology 918+ share via SMB3/2 to my unraid, I've tried mounting it with IP only, local DNS name, changed password to have no special characters, it will still not mount. Any help is appreciated. *NFS works fine. *The same share works fine on windows or mac, so UD is the only one that can't mount it. May 1 17:42:24 Loki kernel: CIFS: Attempting to mount \\172.18.108.100\Unraid May 1 17:42:34 Loki unassigned.devices: Warning: shell_exec(/sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,credentials='/tmp/unassigned.devices/credentials_Unraid' '//172.18.108.100/Unraid' '/mnt/remotes/172.18.108.100_Unraid' 2>&1) took longer than 10s! May 1 17:42:34 Loki kernel: CIFS: VFS: \\172.18.108.100 Send error in SessSetup = -512 May 1 17:42:34 Loki kernel: CIFS: VFS: cifs_mount failed w/return code = -512 May 1 17:42:34 Loki unassigned.devices: SMB default protocol mount failed: 'command timed out'. May 1 17:42:34 Loki unassigned.devices: Mount SMB share '//172.18.108.100/Unraid' using SMB 3.1.1 protocol. May 1 17:42:34 Loki unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.1.1,credentials='/tmp/unassigned.devices/credentials_Unraid' '//172.18.108.100/Unraid' '/mnt/remotes/172.18.108.100_Unraid' May 1 17:42:34 Loki kernel: CIFS: Attempting to mount \\172.18.108.100\Unraid May 1 17:42:44 Loki kernel: CIFS: VFS: \\172.18.108.100 Send error in SessSetup = -512 May 1 17:42:44 Loki kernel: CIFS: VFS: cifs_mount failed w/return code = -512 May 1 17:42:44 Loki unassigned.devices: Warning: shell_exec(/sbin/mount -t cifs -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.1.1,credentials='/tmp/unassigned.devices/credentials_Unraid' '//172.18.108.100/Unraid' '/mnt/remotes/172.18.108.100_Unraid' 2>&1) took longer than 10s! May 1 17:42:44 Loki unassigned.devices: SMB 3.1.1 mount failed: 'command timed out'. May 1 17:42:44 Loki unassigned.devices: Mount SMB share '//172.18.108.100/Unraid' using SMB 3.0 protocol. May 1 17:42:44 Loki unassigned.devices: Mount SMB command: /sbin/mount -t cifs -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.0,credentials='/tmp/unassigned.devices/credentials_Unraid' '//172.18.108.100/Unraid' '/mnt/remotes/172.18.108.100_Unraid' May 1 17:42:44 Loki kernel: CIFS: Attempting to mount \\172.18.108.100\Unraid May 1 17:42:54 Loki kernel: CIFS: VFS: \\172.18.108.100 Send error in SessSetup = -512 May 1 17:42:54 Loki kernel: CIFS: VFS: cifs_mount failed w/return code = -512 May 1 17:42:54 Loki unassigned.devices: Warning: shell_exec(/sbin/mount -t cifs -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=3.0,credentials='/tmp/unassigned.devices/credentials_Unraid' '//172.18.108.100/Unraid' '/mnt/remotes/172.18.108.100_Unraid' 2>&1) took longer than 10s! May 1 17:42:54 Loki unassigned.devices: SMB 3.0 mount failed: 'command timed out'. May 1 17:42:54 Loki unassigned.devices: Mount SMB share '//172.18.108.100/Unraid' using SMB 2.0 protocol. May 1 17:42:54 Loki unassigned.devices: Mount SMB command: /sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=2.0,credentials='/tmp/unassigned.devices/credentials_Unraid' '//172.18.108.100/Unraid' '/mnt/remotes/172.18.108.100_Unraid' May 1 17:42:54 Loki kernel: CIFS: Attempting to mount \\172.18.108.100\Unraid May 1 17:43:04 Loki kernel: CIFS: VFS: \\172.18.108.100 Send error in SessSetup = -512 May 1 17:43:04 Loki kernel: CIFS: VFS: cifs_mount failed w/return code = -512 May 1 17:43:04 Loki unassigned.devices: Warning: shell_exec(/sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=2.0,credentials='/tmp/unassigned.devices/credentials_Unraid' '//172.18.108.100/Unraid' '/mnt/remotes/172.18.108.100_Unraid' 2>&1) took longer than 10s! May 1 17:43:04 Loki unassigned.devices: SMB 2.0 mount failed: 'command timed out'. May 1 17:43:04 Loki unassigned.devices: Mount SMB share '//172.18.108.100/Unraid' using SMB 1.0 protocol. May 1 17:43:04 Loki unassigned.devices: Mount SMB command: /sbin/mount -t 'cifs' -o rw,noserverino,nounix,iocharset=utf8,file_mode=0777,dir_mode=0777,uid=99,gid=100,vers=1.0,credentials='/tmp/unassigned.devices/credentials_Unraid' '//172.18.108.100/Unraid' '/mnt/remotes/172.18.108.100_Unraid' May 1 17:43:04 Loki kernel: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers May 1 17:43:04 Loki kernel: May 1 17:43:04 Loki kernel: CIFS: VFS: Use of the less secure dialect vers=1.0 is not recommended unless required for access to very old servers May 1 17:43:04 Loki kernel: CIFS: Attempting to mount \\172.18.108.100\Unraid May 1 17:43:04 Loki kernel: CIFS: VFS: cifs_mount failed w/return code = -95 May 1 17:43:04 Loki unassigned.devices: SMB 1.0 mount failed: 'mount error(95): Operation not supported Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) '

I always had this setup and has been working great, single 2.5G nic + vlans, Docker network as IPvlan. Putting it here if anyone having issue or similar setup.

Dec 9 13:14:33 Loki nginx: 2022/12/09 13:14:33 [alert] 10725#10725: worker process 48882 exited on signal 6 Dec 9 13:14:35 Loki nginx: 2022/12/09 13:14:35 [alert] 10725#10725: worker process 37448 exited on signal 6 Dec 9 13:14:37 Loki nginx: 2022/12/09 13:14:37 [alert] 10725#10725: worker process 37786 exited on signal 6 Dec 9 13:16:21 Loki nginx: 2022/12/09 13:16:21 [alert] 10725#10725: worker process 37896 exited on signal 6 Dec 9 13:18:05 Loki nginx: 2022/12/09 13:18:05 [alert] 10725#10725: worker process 45966 exited on signal 6 Dec 9 13:18:07 Loki nginx: 2022/12/09 13:18:07 [alert] 10725#10725: worker process 53045 exited on signal 6 Dec 9 13:18:08 Loki nginx: 2022/12/09 13:18:08 [alert] 10725#10725: worker process 53116 exited on signal 6 Dec 9 13:19:52 Loki nginx: 2022/12/09 13:19:52 [alert] 10725#10725: worker process 53260 exited on signal 6 Dec 9 13:21:36 Loki nginx: 2022/12/09 13:21:36 [alert] 10725#10725: worker process 60328 exited on signal 6 Dec 9 13:23:20 Loki nginx: 2022/12/09 13:23:20 [alert] 10725#10725: worker process 67409 exited on signal 6 Dec 9 13:25:04 Loki nginx: 2022/12/09 13:25:04 [alert] 10725#10725: worker process 831 exited on signal 6 Dec 9 13:25:06 Loki nginx: 2022/12/09 13:25:06 [alert] 10725#10725: worker process 7872 exited on signal 6 Dec 9 13:25:07 Loki nginx: 2022/12/09 13:25:07 [alert] 10725#10725: worker process 7966 exited on signal 6 Dec 9 13:25:09 Loki nginx: 2022/12/09 13:25:09 [alert] 10725#10725: worker process 8090 exited on signal 6 Dec 9 13:25:11 Loki nginx: 2022/12/09 13:25:11 [alert] 10725#10725: worker process 8203 exited on signal 6 Dec 9 13:25:12 Loki nginx: 2022/12/09 13:25:12 [alert] 10725#10725: worker process 8512 exited on signal 6 Dec 9 13:25:13 Loki nginx: 2022/12/09 13:25:13 [alert] 10725#10725: worker process 8514 exited on signal 6 Dec 9 13:26:59 Loki nginx: 2022/12/09 13:26:59 [alert] 10725#10725: worker process 8562 exited on signal 6 Dec 9 13:27:01 Loki nginx: 2022/12/09 13:27:01 [alert] 10725#10725: worker process 15566 exited on signal 6 Dec 9 13:39:19 Loki nginx: 2022/12/09 13:39:19 [alert] 10725#10725: worker process 15743 exited on signal 6 Dec 9 13:39:22 Loki nginx: 2022/12/09 13:39:22 [alert] 10725#10725: worker process 63701 exited on signal 6 Dec 9 13:41:05 Loki nginx: 2022/12/09 13:41:05 [alert] 10725#10725: worker process 63856 exited on signal 6 Dec 9 13:42:49 Loki nginx: 2022/12/09 13:42:49 [alert] 10725#10725: worker process 70729 exited on signal 6 Dec 9 13:44:33 Loki nginx: 2022/12/09 13:44:33 [alert] 10725#10725: worker process 4074 exited on signal 6 Dec 9 13:44:36 Loki nginx: 2022/12/09 13:44:36 [alert] 10725#10725: worker process 11193 exited on signal 6 Dec 9 13:44:37 Loki nginx: 2022/12/09 13:44:37 [alert] 10725#10725: worker process 11374 exited on signal 6 Dec 9 13:46:19 Loki nginx: 2022/12/09 13:46:19 [alert] 10725#10725: worker process 11396 exited on signal 6 Dec 9 13:46:21 Loki nginx: 2022/12/09 13:46:21 [alert] 10725#10725: worker process 18037 exited on signal 6 Dec 9 13:48:03 Loki nginx: 2022/12/09 13:48:03 [alert] 10725#10725: worker process 18299 exited on signal 6 Dec 9 13:49:47 Loki nginx: 2022/12/09 13:49:47 [alert] 10725#10725: worker process 25053 exited on signal 6 Dec 9 13:51:32 Loki nginx: 2022/12/09 13:51:32 [alert] 10725#10725: worker process 32646 exited on signal 6 Dec 9 13:51:34 Loki nginx: 2022/12/09 13:51:34 [alert] 10725#10725: worker process 40098 exited on signal 6 Dec 9 13:53:17 Loki nginx: 2022/12/09 13:53:17 [alert] 10725#10725: worker process 40152 exited on signal 6 Dec 9 13:53:19 Loki nginx: 2022/12/09 13:53:19 [alert] 10725#10725: worker process 48136 exited on signal 6 Dec 9 13:55:01 Loki nginx: 2022/12/09 13:55:01 [alert] 10725#10725: worker process 48215 exited on signal 6 Dec 9 13:55:03 Loki nginx: 2022/12/09 13:55:03 [alert] 10725#10725: worker process 55234 exited on signal 6 Dec 9 13:56:46 Loki nginx: 2022/12/09 13:56:46 [alert] 10725#10725: worker process 55395 exited on signal 6 Dec 9 13:56:47 Loki nginx: 2022/12/09 13:56:47 [alert] 10725#10725: worker process 62061 exited on signal 6 Dec 9 13:56:49 Loki nginx: 2022/12/09 13:56:49 [alert] 10725#10725: worker process 62324 exited on signal 6 Dec 9 13:56:51 Loki nginx: 2022/12/09 13:56:51 [alert] 10725#10725: worker process 62373 exited on signal 6 Dec 9 13:56:51 Loki nginx: 2022/12/09 13:56:51 [alert] 10725#10725: worker process 62418 exited on signal 6 Dec 9 13:58:36 Loki nginx: 2022/12/09 13:58:36 [alert] 10725#10725: worker process 62422 exited on signal 6 Dec 9 14:38:36 Loki nginx: 2022/12/09 14:38:36 [alert] 10725#10725: worker process 69305 exited on signal 6 Dec 9 14:38:38 Loki nginx: 2022/12/09 14:38:38 [alert] 10725#10725: worker process 8957 exited on signal 6 Dec 9 14:38:39 Loki nginx: 2022/12/09 14:38:39 [alert] 10725#10725: worker process 9105 exited on signal 6 Dec 9 14:38:40 Loki nginx: 2022/12/09 14:38:40 [alert] 10725#10725: worker process 9159 exited on signal 6 Dec 9 14:38:41 Loki nginx: 2022/12/09 14:38:41 [alert] 10725#10725: worker process 9183 exited on signal 6 Dec 9 14:38:42 Loki nginx: 2022/12/09 14:38:42 [alert] 10725#10725: worker process 9208 exited on signal 6 Dec 9 14:38:43 Loki nginx: 2022/12/09 14:38:43 [alert] 10725#10725: worker process 9280 exited on signal 6 Dec 9 14:38:45 Loki nginx: 2022/12/09 14:38:45 [alert] 10725#10725: worker process 9332 exited on signal 6 Getting spammed with these in the log and eventually only way to recover is with nginx restart or server reboot, all tabs are closed nothing trying to go to the gui, logs are not very helpful.

Can you provide a link to this theme I love it. Thank you

Hi all I've been using this command for past year and never had issues , I see this script/guide includes cache and other things involved, can someone explain what it does ? #!/bin/bash #mounts cloud storage to unraid rclone mount --max-read-ahead 1024k --allow-other --uid 99 --gid 100 --umask 002 --allow-non-empty -vv --tpslimit=10 plex: /mnt/user/data/media/gdrive/ I have no permission issues or disconnects and api bans, but will gladly take suggestions for improving it

correct I really care about ipmitools lol since my Dell will start screaming without manual fan controls

that link has barely anything (https://slackware.pkgs.org/15.0/slackware-x86_64/)

Can we just grab these and install on 6.11 ?

Thank you for fast reply ! I updated the plugin to the new replacement and rebooted the server, will monitor and see what happens, If the remote server is the issue I'm not sure what's going on, it's a DS918 connected to a switch on same network and never has any problems, I'm not sure what can cause the NAS to stop communicating with unraid and cause shares issues, any suggestions ?

Thanks for the reply, I edited my original post. loki-diagnostics-20220518-1234.zip

loki-diagnostics-20220518-1234.zipHi all, my first time asking for support so not sure I'm in the right thread, I've been having issue with a SMB mount to my nas, I switched to NFS and was good for a while however it now started again. All of my shares are showing 0 bytes and I can't navigate to them as they are disconnected, I included a screeshot and what the log is freaking out about. May 18 11:57:49 Loki unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/plexmedia' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s! May 18 11:57:49 Loki unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/plexmedia' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s! May 18 11:57:54 Loki unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/plexmedia2' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s! May 18 11:57:54 Loki unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/plexmedia2' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s! May 18 11:58:01 Loki kernel: traps: lsof[1259] general protection fault ip:15532da576ae sp:58c4db2936431bf error:0 in libc-2.33.so[15532da3e000+15e000]

that's what I did and it's working, but drives me crazy why /mnt/user/downloads is not the same

yes

I mapped everything to /mnt/docker/downloads, and of course everything is going to the correct cache now even though /mnt/user/downloads should point there.

looks like you are forcing it to go to disk22 where I have it as /mnt/user/downloads which is picking the wrong disk at the end.

this might be my only option at this point, another option is to wipe nzbget and qbit, remove the download share as well and start fresh, something is stuck.

path on both is /mnt/user/downloads

i wrote a test file in /mnt/user/downloads and sure enough ends up in /mnt/cache/downloads, not /mnt/cache/downloads, so it's not even a docker issue, somehow unraid thinks that downloads is a different location that is mapped to.

same with qbittorrent...not sure why these 2 keep writing in the wrong cache

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='nzbget' --net='bridge' -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Loki" -e HOST_CONTAINERNAME="nzbget" -e 'PUID'='99' -e 'PGID'='100' -e ' DOCKER_MODS'='ghcr.io/gilbn/theme.park:nzbget' -e 'TP_THEME'='aquamarine' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:6789]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/nzbget-icon.png' -p '6789:6789/tcp' -v '/mnt/user/downloads/':'/downloads':'rw' -v '/mnt/user/appdata/nzbget':'/config':'rw' 'linuxserver/nzbget' The command finished successfully!

I deleted everything in downloads and started the containers one at the time, seems like upon starting nzbget writes in cache

could it be the name of the cache ? why is only cache showing full name and other 2 are --------- covered ?

not that I know of... I read thru all the docker mappings and nothing showing /mnt/cache/downloads , any way to check what's using what ?

I force updated the 2 containers and both docker run show they are mapped to mnt/user/downloads, which is not on Cache