dlandon

ownCloud is not updated in the Docker container. You'll need to update manually. The procedure is in the second post. Don't do an auto update, it will fail.

What version of Unraid are you using? The powerdown script was deprecated many years ago and is not recommended or necessary.

Linux does not see any partitions on the disk. How was the disk originally formatted? If you want to use it with UD, you'll need to clear it off and format it with UD.

Ok. Here's the deal. Using sec=ntlm is no longer supported because it has been removed from the Linux Kernel: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=76a3c92ec9e0668e4cd0e9ff1782eb68f61a179c I removed the sec=ntlm when mounting SMB 1.0 because it generated an error. The error you are seeing now is because the Epson printer only supports ntlm and Unraid doesn't. There's nothing I can do to get around this.

Fixed in the next release. If the Unraid settings are spin down on a timer, that will apply to UD devices as well. You cannot set spin down per UD device.

Which icon are you clicking on? That error doesn't make any sense to me. Are you talking about the short log in the black screen? The UD device log is more like the syslog display, and not the short log. UD devices are supposed to follow the same rules as the Array disks. It does. If the icons are active, the tool tip will show when you hover your mouse over the icon.

The error 22 is a pretty generic error that is not very specific. SMB 1.0 is an old/insecure version and WIndows is trying to phase it out. It's not Unraid trying to get rid of SMB 1.0, it's changes being made to samba. I don't understand what has changed in the latest version of samba. I'll keep trying to find a solution, but it's getting harder when changes are made to samba and I don't know what they are.

Try using the IP address instead of the server name.

It looks like you are mounting a memory card in an Epson Printer. Is there a firmware update for the printer? On one of your previous posts it looks like the printer was responding to the SMB version 2.0 mount. Now it's not. It is failing on SMB 1.0. SMB 1.0 is an older insecire protocol. Can the printer use SMB 2.0?

Not true. Enabling the plugin monitors activity for the Array. The 'Enable for Cache and Pool Disks?' adds monitoring for any Cache and Pool disks. Leave it off and only Array disks are monitored. The plugin excludes the 'appdata' and 'syslog' shares automatically. I should add 'system' to those though so the docker and VM images get excluded. I'll fix this in the next release. If you do a non traditional mapping of appdata, syslog, and system shares, the file activity plugin will monitor those.

Separate them how? What is your use case for a feature such as this?

Be sure to use passwords without special characters.

Your latest log shows a login faikure: Jun 20 18:34:24 9900K unassigned.devices: Mount SMB share '//NAS1/user-pool.nas1megashare' using SMB default protocol. Jun 20 18:34:24 9900K 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,credentials='/tmp/unassigned.devices/credentials_user-pool.nas1megashare' '//NAS1/user-pool.nas1megashare' '/mnt/remotes/NAS1_user-pool.nas1megashare' Jun 20 18:34:24 9900K kernel: CIFS: Attempting to mount \\NAS1\user-pool.nas1megashare Jun 20 18:34:24 9900K kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE Jun 20 18:34:24 9900K kernel: CIFS: VFS: \\NAS1 Send error in SessSetup = -13 Jun 20 18:34:24 9900K kernel: CIFS: VFS: cifs_mount failed w/return code = -13 Check your credentials.

Post your current diagnostics zip file. Just posting log snippets isn't helpful.

You don't use the root password to mount remote shares, even the root share.

Verify the credentials.

Your root share is having a problem: un 20 10:16:59 9900K unassigned.devices: Mount SMB share '//NAS1/user-pool.nas1megashare' using SMB default protocol. Jun 20 10:16:59 9900K 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,credentials='/tmp/unassigned.devices/credentials_user-pool.nas1megashare' '//NAS1/user-pool.nas1megashare' '/mnt/remotes/NAS1_user-pool.nas1megashare' Jun 20 10:16:59 9900K kernel: CIFS: Attempting to mount \\NAS1\user-pool.nas1megashare Jun 20 10:16:59 9900K kernel: CIFS: VFS: BAD_NETWORK_NAME: \\NAS1\user-pool.nas1megashare Jun 20 10:16:59 9900K kernel: CIFS: VFS: cifs_mount failed w/return code = -2 Jun 20 10:16:59 9900K unassigned.devices: SMB default protocol mount failed: 'mount error(2): No such file or directory Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) '. Maybe you need to remove the remote share on the 9900K it and reconfigure it? My guess is the mount point changed on nas1.

Looks to be a security issue. Not credentials, but the remote server probably doesn't support the CIFS security. I'll need you to post your diagnostics zip so I take a closer look.

That doesn't make any sense. The SMB Security settings only work once a device is mounted. How did the change allow you to see it? What did you see?

Just removed and re-installed it on my test server. Worked fine. It's something with your server. Flash problem? Ram memory problem?

Check the SMB Security settings in UD settings. There has been a change in SMB sharing. 'No' used to share public, but now doesn't share at all. The 'Public' setting is used to share public.

No. How am I supposed to even guess when all you tell me is it hangs. You already checked the preclear log, so if it doesn't tell you anything I have no idea.

Kinda hard to help you without it.

Check the UD SMB Security settings. There was a change in the latest release. The 'No' setting now turns off the SMB sharing instad of sharing public. The 'Public' setting is the new setting that shares public and does what the 'No' setting used to do.

Yes, you can't have an Unraid share and a UD share with the same name. UD checks when a device is mounted and won't mount if there is a duplicate name. There are also some reserved names that are checked along with checking other UD names.