Unassigned Devices - Managing Disk Drives and Remote Shares Outside of The Unraid Array


Recommended Posts

54 minutes ago, sittingmongoose said:

Jun 20 14:24:04 9900K kernel: CIFS: VFS: \\NAS1 Send error in SessSetup = -13
Jun 20 14:24:04 9900K kernel: CIFS: VFS: cifs_mount failed w/return code = -13

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.

Link to comment
7 minutes ago, dlandon said:

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.

Here you go.  9900K is the server trying to access the Nas1.  The other way around works though.

 

 

9900k-diagnostics-20220620-1528.zip nas1-diagnostics-20220620-1529.zip

Link to comment
14 minutes ago, sittingmongoose said:

Here you go.  9900K is the server trying to access the Nas1.  The other way around works though.

 

 

9900k-diagnostics-20220620-1528.zip 289.47 kB · 0 downloads nas1-diagnostics-20220620-1529.zip 133.67 kB · 0 downloads

 

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.

Link to comment
14 minutes ago, dlandon said:

 

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.

Just tried that.  No longer gettings errors on the Nas, but my server still wont mount it.  Saying this in the log.

 

un 20 16:03:15 9900K unassigned.devices: Removing configuration '//NAS1/user-pool.nas1megashare'.
Jun 20 16:03:34 9900K flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Jun 20 16:04:37 9900K avahi-dnsconfd[22338]: read(): EOF
Jun 20 16:04:44 9900K unassigned.devices: Mounting Remote Share '//NAS1/user-pool.nas1megashare'...
Jun 20 16:04:44 9900K unassigned.devices: Mount SMB share '//NAS1/user-pool.nas1megashare' using SMB default protocol.
Jun 20 16:04:44 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 16:04:44 9900K kernel: CIFS: Attempting to mount \\NAS1\user-pool.nas1megashare
Jun 20 16:04:44 9900K kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun 20 16:04:44 9900K kernel: CIFS: VFS: \\NAS1 Send error in SessSetup = -13
Jun 20 16:04:44 9900K kernel: CIFS: VFS: cifs_mount failed w/return code = -13
Jun 20 16:05:08 9900K kernel: CIFS: VFS: \\NAS1\Media2 Close interrupted close
Jun 20 16:05:08 9900K kernel: CIFS: VFS: \\NAS1\Media2 Close cancelled mid failed rc:-9

Link to comment
20 minutes ago, sittingmongoose said:

Just tried that.  No longer gettings errors on the Nas, but my server still wont mount it.  Saying this in the log.

 

un 20 16:03:15 9900K unassigned.devices: Removing configuration '//NAS1/user-pool.nas1megashare'.
Jun 20 16:03:34 9900K flash_backup: adding task: /usr/local/emhttp/plugins/dynamix.my.servers/scripts/UpdateFlashBackup update
Jun 20 16:04:37 9900K avahi-dnsconfd[22338]: read(): EOF
Jun 20 16:04:44 9900K unassigned.devices: Mounting Remote Share '//NAS1/user-pool.nas1megashare'...
Jun 20 16:04:44 9900K unassigned.devices: Mount SMB share '//NAS1/user-pool.nas1megashare' using SMB default protocol.
Jun 20 16:04:44 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 16:04:44 9900K kernel: CIFS: Attempting to mount \\NAS1\user-pool.nas1megashare
Jun 20 16:04:44 9900K kernel: CIFS: Status code returned 0xc000006d STATUS_LOGON_FAILURE
Jun 20 16:04:44 9900K kernel: CIFS: VFS: \\NAS1 Send error in SessSetup = -13
Jun 20 16:04:44 9900K kernel: CIFS: VFS: cifs_mount failed w/return code = -13
Jun 20 16:05:08 9900K kernel: CIFS: VFS: \\NAS1\Media2 Close interrupted close
Jun 20 16:05:08 9900K kernel: CIFS: VFS: \\NAS1\Media2 Close cancelled mid failed rc:-9

Verify the credentials.

Link to comment
16 minutes ago, dlandon said:

Verify the credentials.

I triple checked it and even changed my user password and root password.  root doesnt work at all.  Readded it and now im getting this error instead.

 

Jun 20 16:41:32 9900K kernel: CIFS: Attempting to mount \\NAS1\
Jun 20 16:41:32 9900K kernel: FS-Cache: Duplicate cookie detected
Jun 20 16:41:32 9900K kernel: FS-Cache: O-cookie c=00000003 [p=00000002 fl=222 nc=1 na=1]
Jun 20 16:41:32 9900K kernel: FS-Cache: O-cookie d=0000000056862e88{CIFS.server} n=000000001e27faf6
Jun 20 16:41:32 9900K kernel: FS-Cache: O-key=[8] '020001bdc0a83276'
Jun 20 16:41:32 9900K kernel: FS-Cache: N-cookie c=00000010 [p=00000002 fl=2 nc=0 na=1]
Jun 20 16:41:32 9900K kernel: FS-Cache: N-cookie d=0000000056862e88{CIFS.server} n=000000004ea6a98f
Jun 20 16:41:32 9900K kernel: FS-Cache: N-key=[8] '020001bdc0a83276'
Jun 20 16:41:32 9900K kernel: CIFS: VFS: cifs_mount failed w/return code = -6
Jun 20 16:41:32 9900K unassigned.devices: SMB 1.0 mount failed: 'Retrying with upper case share name mount error(6): No such device or address Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) '.

Link to comment
1 hour ago, sittingmongoose said:

Yea, I just tried it to see if it would work.  I’m having this issue with my regular user account. Which is working for my other shares and my other server.

 

But for some reason not this rootshare.

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

Link to comment
32 minutes ago, sittingmongoose said:

 

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.

Link to comment
17 minutes ago, dlandon said:

 

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.

I did, 4 times.  I changed the passwords twice.  Is there a security setting that might be causing it?  Or a different password?  I have root and my user.  I’m using the user and I changed the password for user a few times and tried readding the share.  Same issue.

Link to comment
11 hours ago, dlandon said:

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.

 

I found the culprit. I was using the older gfjardin preclear plugin. I removed that and installed your UD preclear plugin. It is running the clear now. One thing I noticed: both, Preview Progress and Preclear Disk Log complain:

 

Preview Progress (continuous repetition): tput: unknown terminal "screen"

Preclear Disk Log (continuous repetition): Jun 21 02:41:34 preclear_disk_redacted: tput: unknown terminal "screen"

 

I installed screen manually via the nerd pack and stopped and resumed the preclear. Now the Previe Progress and Preclear Disk Log work as expected.

 

Not sure why screen wasn't installed by the plugin, though.

 

 

Edited by b0m541
Link to comment
On 6/18/2022 at 6:22 PM, dlandon said:

Fixed in the next release.

I updated the plugin to 2022.06.19 but I'm still getting errors unfortunately. Here's what I tried so far:

1. Restarted the unraid server and reinstalled the plugin

2. Changed the password (I'm using a very simple password)

3. Disabled authentication

Any other suggestion I can do to check on my end? Thank you.

947138963_Screenshot2022-06-21175610.png.6da336faa5e3abb42d6603233d99d1c3.png

 

tower-diagnostics-20220621-1754.zip

Link to comment
25 minutes ago, skylake said:

I updated the plugin to 2022.06.19 but I'm still getting errors unfortunately. Here's what I tried so far:

1. Restarted the unraid server and reinstalled the plugin

2. Changed the password (I'm using a very simple password)

3. Disabled authentication

Any other suggestion I can do to check on my end? Thank you.

947138963_Screenshot2022-06-21175610.png.6da336faa5e3abb42d6603233d99d1c3.png

 

tower-diagnostics-20220621-1754.zip 95.79 kB · 1 download

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?

Link to comment
7 minutes ago, dlandon said:

Try using the IP address instead of the server name.

The printer has the latest firmware and I believe it only uses SMB 1.0. 

 

I tried to mount the share using the IP address, but I am getting the same error. I guess unraid is trying to get rid of devices that use SMB 1.0. :(

Link to comment
38 minutes ago, skylake said:

The printer has the latest firmware and I believe it only uses SMB 1.0. 

 

I tried to mount the share using the IP address, but I am getting the same error. I guess unraid is trying to get rid of devices that use SMB 1.0. :(

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.

Link to comment
21 hours ago, skylake said:

I updated the plugin to 2022.06.19 but I'm still getting errors unfortunately. Here's what I tried so far:

1. Restarted the unraid server and reinstalled the plugin

2. Changed the password (I'm using a very simple password)

3. Disabled authentication

Any other suggestion I can do to check on my end? Thank you.

947138963_Screenshot2022-06-21175610.png.6da336faa5e3abb42d6603233d99d1c3.png

 

tower-diagnostics-20220621-1754.zip 95.79 kB · 1 download

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.

Link to comment

I looked through a bit above and didn't see a similar problem:

 

I have been using my internal docking bay (with hot swap enabled on the Sata controller) to clone and resize various drives over the past few days, but I've run into a snag...

 

If I plug any drive in it mounts on it's own and appears to have the same structure as the last one I used but if I try to look at the OS partition with Krusader it shows up as empty.

 

I'm assuming a reboot will fix it, and I am due to install some hardware tonight, but I'd love to know if there was a way to reset Unassigned Devices without a reboot.

 

jupiter-diagnostics-20220622-1900.zip

Link to comment
3 hours ago, dlandon said:

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.

No worries, all is good. Thanks for trying though. :D

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.