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


Recommended Posts

28 minutes ago, dlandon said:

 

I see the issue.  You are using the smb-extra.conf edit to create a rootshare:

#unassigned_devices_start
#Unassigned devices share includes
   include = /tmp/unassigned.devices/smb-settings.conf
#unassigned_devices_end
[rootshare] 
   path = /mnt/user 
   comment = 
   browseable = yes 
   valid users = sittingmongoose
   write list = sittingmongoose
   vfs objects =

 

Do the following:

  • Remove the rootshare entry in your smb-extra.conf file.
  • Create the rootshare using UD with a unique name - not 'rootshare'.
  • Reboot to clear up a lot of strange stuff I see.  This will remount your NFS share with NFSv4 that will clear up your NFS issues.  Your nfs mount was mounted before the 2022.04.11c update.

I can't help you with the 'custom' aproach you're using for a rootshare.

I can try all that and report back.  Thank you

Link to comment
3 hours ago, dlandon said:

 

I see the issue.  You are using the smb-extra.conf edit to create a rootshare:

#unassigned_devices_start
#Unassigned devices share includes
   include = /tmp/unassigned.devices/smb-settings.conf
#unassigned_devices_end
[rootshare] 
   path = /mnt/user 
   comment = 
   browseable = yes 
   valid users = sittingmongoose
   write list = sittingmongoose
   vfs objects =

 

Do the following:

  • Remove the rootshare entry in your smb-extra.conf file.
  • Create the rootshare using UD with a unique name - not 'rootshare'.
  • Reboot to clear up a lot of strange stuff I see.  This will remount your NFS share with NFSv4 that will clear up your NFS issues.  Your nfs mount was mounted before the 2022.04.11c update.

I can't help you with the 'custom' aproach you're using for a rootshare.

Are you not able to access appdata through your rootshare?  I dont see it in my rootshares.  Also I attached my diagnostics to make sure everything looks better than before.

Edit: It seems the one can see the others appdata, but the other one can not.  Is there a way to control this?

 

9900k-diagnostics-20220412-2105.zip

Edited by sittingmongoose
Link to comment

So still getting all these weird errors in my log.  I attached my diag again.

Apr 13 00:26:51 9900K kernel: CIFS: VFS: \\NAS1\user-pool.nas1megashare Close unmatched open for MID:335382
Apr 13 00:27:54 9900K kernel: CIFS: VFS: \\NAS1\user-pool.nas1megashare Close unmatched open for MID:343600
Apr 13 00:28:25 9900K kernel: CIFS: VFS: \\NAS1\user-pool.nas1megashare Close unmatched open for MID:346564
Apr 13 00:28:57 9900K kernel: CIFS: VFS: \\NAS1\user-pool.nas1megashare Close unmatched open for MID:349543
Apr 13 00:30:32 9900K kernel: CIFS: VFS: \\NAS1\user-pool.nas1megashare Close unmatched open for MID:358330
Apr 13 00:31:03 9900K kernel: CIFS: VFS: \\NAS1\user-pool.nas1megashare Close unma9900k-diagnostics-20220413-0031.ziptched open for MID:361262

Link to comment
6 hours ago, sittingmongoose said:

So still getting all these weird errors in my log.  I attached my diag again.

 

You need to fix this:

Apr 12 21:00:00 9900K root: Fix Common Problems Version 2022.03.29
Apr 12 21:00:00 9900K root: Fix Common Problems: Error: Same share (downloads) exists in a different case
Apr 12 21:00:00 9900K root: Fix Common Problems: Error: Same share (Downloads) exists in a different case

 

You seem to be having network issues:

Apr 12 23:26:36 9900K unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/NAS1_Media2' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s!

This is UD trying to get the size, free, and used information from the remote server.

 

Your remote server dropped off-line and you unmounted the remotes share:

Apr 12 23:26:40 9900K kernel: traps: lsof[14699] general protection fault ip:1547eb08968e sp:45eaefe5b0939e40 error:0 in libc-2.33.so[1547eb070000+15e000]
Apr 12 23:26:56 9900K kernel: CIFS: Server share \\NAS1\user.nas1megashare deleted.
Apr 12 23:27:23 9900K rpc.mountd[12829]: v4.0 client detached: 0xac8459dd62561e47 from "192.168.50.118:1002"
Apr 12 23:28:59 9900K kernel: CIFS: VFS: \\NAS1\user.nas1megashare BAD_NETWORK_NAME: \\NAS1\user.nas1megashare
Apr 12 23:28:59 9900K kernel: CIFS: reconnect tcon failed rc = -2
Apr 12 23:29:01 9900K kernel: CIFS: VFS: \\NAS1\user.nas1megashare BAD_NETWORK_NAME: \\NAS1\user.nas1megashare
### [PREVIOUS LINE REPEATED 11 TIMES] ###
Apr 12 23:29:19 9900K unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/NAS1_Media2' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s!
Apr 12 23:29:21 9900K kernel: CIFS: VFS: \\NAS1\user.nas1megashare BAD_NETWORK_NAME: \\NAS1\user.nas1megashare
Apr 12 23:29:21 9900K unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/NAS1_Media2' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s!
Apr 12 23:29:23 9900K kernel: CIFS: VFS: \\NAS1\user.nas1megashare BAD_NETWORK_NAME: \\NAS1\user.nas1megashare
Apr 12 23:29:24 9900K unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/NAS1_Media2' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s!
Apr 12 23:29:25 9900K kernel: CIFS: VFS: \\NAS1\user.nas1megashare BAD_NETWORK_NAME: \\NAS1\user.nas1megashare
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Apr 12 23:29:28 9900K unassigned.devices: Removing Remote SMB/NFS share '//9900K/mnt/user0/'...
Apr 12 23:29:28 9900K unassigned.devices: Unmounting Remote SMB/NFS Share '//9900K/mnt/user0/'...
Apr 12 23:29:28 9900K unassigned.devices: Synching file system on '/mnt/rootshare/user.9900kmegashare'.
Apr 12 23:29:28 9900K unassigned.devices: Unmount cmd: /sbin/umount '/mnt/rootshare/user.9900kmegashare' 2>&1
Apr 12 23:29:28 9900K unassigned.devices: Successfully unmounted 'user.9900kmegashare'
Apr 12 23:29:28 9900K unassigned.devices: Removing SMB share 'user.9900kmegashare'
Apr 12 23:29:29 9900K unassigned.devices: Removing Remote SMB/NFS share '//NAS1/user.nas1megashare'...
Apr 12 23:29:29 9900K unassigned.devices: Unmounting Remote SMB/NFS Share '//NAS1/user.nas1megashare'...
Apr 12 23:29:29 9900K unassigned.devices: Synching file system on '/mnt/remotes/NAS1_user.nas1megashare'.
Apr 12 23:29:29 9900K unassigned.devices: Unmount cmd: /sbin/umount -t cifs '//NAS1/user.nas1megashare' 2>&1
Apr 12 23:29:29 9900K unassigned.devices: Successfully unmounted 'user.nas1megashare'
Apr 12 23:29:29 9900K unassigned.devices: Removing SMB share 'NAS1_user.nas1megashare'
Apr 12 23:29:32 9900K unassigned.devices: Removing Remote SMB/NFS share 'NAS1:/mnt/user/Media2'...
Apr 12 23:29:32 9900K unassigned.devices: Unmounting Remote SMB/NFS Share 'NAS1:/mnt/user/Media2'...
Apr 12 23:29:32 9900K unassigned.devices: Synching file system on '/mnt/remotes/NAS1_Media2'.
Apr 12 23:30:02 9900K kernel: nfs: server NAS1 not responding, timed out
Apr 12 23:30:02 9900K kernel: nfs: server NAS1 not responding, still trying
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Apr 12 23:30:08 9900K kernel: nfs: server NAS1 OK
Apr 12 23:30:08 9900K kernel: NFS: state manager: check lease failed on NFSv4 server NAS1 with error 13
Apr 12 23:30:08 9900K kernel: nfs: server NAS1 OK

 

Are you using Jumbo Frames anywhere on your network?

Link to comment
4 hours ago, dlandon said:

 

You need to fix this:

Apr 12 21:00:00 9900K root: Fix Common Problems Version 2022.03.29
Apr 12 21:00:00 9900K root: Fix Common Problems: Error: Same share (downloads) exists in a different case
Apr 12 21:00:00 9900K root: Fix Common Problems: Error: Same share (Downloads) exists in a different case

 

You seem to be having network issues:

Apr 12 23:26:36 9900K unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/NAS1_Media2' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s!

This is UD trying to get the size, free, and used information from the remote server.

 

Your remote server dropped off-line and you unmounted the remotes share:

Apr 12 23:26:40 9900K kernel: traps: lsof[14699] general protection fault ip:1547eb08968e sp:45eaefe5b0939e40 error:0 in libc-2.33.so[1547eb070000+15e000]
Apr 12 23:26:56 9900K kernel: CIFS: Server share \\NAS1\user.nas1megashare deleted.
Apr 12 23:27:23 9900K rpc.mountd[12829]: v4.0 client detached: 0xac8459dd62561e47 from "192.168.50.118:1002"
Apr 12 23:28:59 9900K kernel: CIFS: VFS: \\NAS1\user.nas1megashare BAD_NETWORK_NAME: \\NAS1\user.nas1megashare
Apr 12 23:28:59 9900K kernel: CIFS: reconnect tcon failed rc = -2
Apr 12 23:29:01 9900K kernel: CIFS: VFS: \\NAS1\user.nas1megashare BAD_NETWORK_NAME: \\NAS1\user.nas1megashare
### [PREVIOUS LINE REPEATED 11 TIMES] ###
Apr 12 23:29:19 9900K unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/NAS1_Media2' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s!
Apr 12 23:29:21 9900K kernel: CIFS: VFS: \\NAS1\user.nas1megashare BAD_NETWORK_NAME: \\NAS1\user.nas1megashare
Apr 12 23:29:21 9900K unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/NAS1_Media2' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s!
Apr 12 23:29:23 9900K kernel: CIFS: VFS: \\NAS1\user.nas1megashare BAD_NETWORK_NAME: \\NAS1\user.nas1megashare
Apr 12 23:29:24 9900K unassigned.devices: Error: shell_exec(/bin/df '/mnt/remotes/NAS1_Media2' --output=size,used,avail | /bin/grep -v '1K-blocks' 2>/dev/null) took longer than 5s!
Apr 12 23:29:25 9900K kernel: CIFS: VFS: \\NAS1\user.nas1megashare BAD_NETWORK_NAME: \\NAS1\user.nas1megashare
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Apr 12 23:29:28 9900K unassigned.devices: Removing Remote SMB/NFS share '//9900K/mnt/user0/'...
Apr 12 23:29:28 9900K unassigned.devices: Unmounting Remote SMB/NFS Share '//9900K/mnt/user0/'...
Apr 12 23:29:28 9900K unassigned.devices: Synching file system on '/mnt/rootshare/user.9900kmegashare'.
Apr 12 23:29:28 9900K unassigned.devices: Unmount cmd: /sbin/umount '/mnt/rootshare/user.9900kmegashare' 2>&1
Apr 12 23:29:28 9900K unassigned.devices: Successfully unmounted 'user.9900kmegashare'
Apr 12 23:29:28 9900K unassigned.devices: Removing SMB share 'user.9900kmegashare'
Apr 12 23:29:29 9900K unassigned.devices: Removing Remote SMB/NFS share '//NAS1/user.nas1megashare'...
Apr 12 23:29:29 9900K unassigned.devices: Unmounting Remote SMB/NFS Share '//NAS1/user.nas1megashare'...
Apr 12 23:29:29 9900K unassigned.devices: Synching file system on '/mnt/remotes/NAS1_user.nas1megashare'.
Apr 12 23:29:29 9900K unassigned.devices: Unmount cmd: /sbin/umount -t cifs '//NAS1/user.nas1megashare' 2>&1
Apr 12 23:29:29 9900K unassigned.devices: Successfully unmounted 'user.nas1megashare'
Apr 12 23:29:29 9900K unassigned.devices: Removing SMB share 'NAS1_user.nas1megashare'
Apr 12 23:29:32 9900K unassigned.devices: Removing Remote SMB/NFS share 'NAS1:/mnt/user/Media2'...
Apr 12 23:29:32 9900K unassigned.devices: Unmounting Remote SMB/NFS Share 'NAS1:/mnt/user/Media2'...
Apr 12 23:29:32 9900K unassigned.devices: Synching file system on '/mnt/remotes/NAS1_Media2'.
Apr 12 23:30:02 9900K kernel: nfs: server NAS1 not responding, timed out
Apr 12 23:30:02 9900K kernel: nfs: server NAS1 not responding, still trying
### [PREVIOUS LINE REPEATED 1 TIMES] ###
Apr 12 23:30:08 9900K kernel: nfs: server NAS1 OK
Apr 12 23:30:08 9900K kernel: NFS: state manager: check lease failed on NFSv4 server NAS1 with error 13
Apr 12 23:30:08 9900K kernel: nfs: server NAS1 OK

 

Are you using Jumbo Frames anywhere on your network?

Ok, so I had Jumbo frames on.  I turned that off.  I also deleted the Downloads share(I wasnt using it anyway).  I rebooted both servers.  I am still seeing the errors.  I attached my diagnostics again.  BTW, I want to thank you for sifting through all my issues.  You have helped me figure out a lot of other issues I have been having, so I appreciate that.

 

Apr 13 11:23:16 9900K kernel: CIFS: VFS: \\NAS1\user-pool.nas1megashare Close unmatched open for MID:773600
Apr 13 11:23:48 9900K kernel: CIFS: VFS: \\NAS1\user-pool.nas1megashare Close unmatched open for MID:776748

 

Edit: I also attached my second server which has the same errors.  This one might be easier to look at because it has a lot less stuff on it.

 

9900k-diagnostics-20220413-1122.zip

nas1-diagnostics-20220413-1139.zip

Edited by sittingmongoose
Link to comment

Hello,

 

I rebooted my server yesterday and when the system came back up one of my drives that I auto mount in Unassigned Devices showed up as completely blank with no files and no partition. It also has a red x that says clear next to it and shows as an 8TB disk but has no usable space.

 

.Did I lose all of my data? Is there a way to repair the file system? Not sure what caused this.

 

Any help would be appreciated. Thanks.

 

 

Screen Shot 2022-04-13 at 1.25.36 PM.png

Link to comment
2 hours ago, sittingmongoose said:

Ok, so I had Jumbo frames on.  I turned that off.  I also deleted the Downloads share(I wasnt using it anyway).  I rebooted both servers.

 

You have another FCP error:

Apr 13 08:29:07 Nas1 root: Fix Common Problems: Error: Reserved user share user

Please take a few minutes and fix all the issues FCP is reporting.

 

Your mounts are interleaved and not sequential:

Apr 13 08:21:30 Nas1 unassigned.devices: Mounting Remote Share '//9900K/user-pool.9900kmegashare'...
Apr 13 08:21:30 Nas1 unassigned.devices: Mount SMB share '//9900K/user-pool.9900kmegashare' using SMB default protocol.
Apr 13 08:21:30 Nas1 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.9900kmegashare' '//9900K/user-pool.9900kmegashare' '/mnt/remotes/9900K_user-pool.9900kmegashare'
Apr 13 08:21:30 Nas1 kernel: CIFS: Attempting to mount \\9900K\user-pool.9900kmegashare
Apr 13 08:21:33 Nas1 unassigned.devices: Mounting Remote Share '9900K:/mnt/user/Media'...
Apr 13 08:21:33 Nas1 unassigned.devices: Mount NFS command: /sbin/mount -t 'nfs4' -o rw,noacl '9900K:/mnt/user/Media' '/mnt/remotes/9900K_Media'
Apr 13 08:21:34 Nas1 unassigned.devices: Successfully mounted '9900K:/mnt/user/Media' on '/mnt/remotes/9900K_Media/'.
Apr 13 08:21:34 Nas1 unassigned.devices: Adding SMB share '9900K_Media'.
Apr 13 08:21:34 Nas1 rpc.mountd[9639]: No host name given with /mnt/user/appdata (ro,async,wdelay,hide,nocrossmnt,secure,root_squash,no_all_squash,no_subtree_check,secure_locks,acl,no_pnfs,fsid=102,anonuid=65534,anongid=65534,sec=sys,ro,secure,root_squash,no_all_squash), suggest *(ro,async,wdelay,hide,nocrossmnt,secure,root_squash,no_all_squash,no_subtree_check,secure_locks,acl,no_pnfs,fsid=102,anonuid=65534,anongid=65534,sec=sys,ro,secure,root_squash,no_all_squash) to avoid warning
Apr 13 08:21:34 Nas1 rpc.mountd[9639]: v4.0 client attached: 0xba88df6e6256bfc4 from "192.168.50.119:964"
Apr 13 08:21:35 Nas1 kernel: CIFS: VFS: cifs_mount failed w/return code = -112
Apr 13 08:21:35 Nas1 unassigned.devices: SMB default protocol mount failed: 'mount error: Server abruptly closed the connection. This can happen if the server does not support the SMB version you are trying to use. The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0. mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) '.
Apr 13 08:21:35 Nas1 unassigned.devices: Mount SMB share '//9900K/user-pool.9900kmegashare' using SMB 3.1.1 protocol.
Apr 13 08:21:35 Nas1 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_user-pool.9900kmegashare' '//9900K/user-pool.9900kmegashare' '/mnt/remotes/9900K_user-pool.9900kmegashare'
Apr 13 08:21:35 Nas1 kernel: CIFS: Attempting to mount \\9900K\user-pool.9900kmegashare
Apr 13 08:21:35 Nas1 unassigned.devices: Successfully mounted '//9900K/user-pool.9900kmegashare' on '/mnt/remotes/9900K_user-pool.9900kmegashare/'.
Apr 13 08:21:35 Nas1 unassigned.devices: Adding SMB share '9900K_user-pool.9900kmegashare'.

Your 'user-pool.9900kmegashare' did not complete mounting before the '9900K_Media' began mounting.  That's not how the UD Auto Mounts work.  They mount in seqence.

 

You should have 'Auto Mount' set for the devices you want mounted at array start and not do anything else to start UD devices.  Are you running a script somewhere that tries to mount UD devices?  Are you mounting your old rootshare in fstab?

Link to comment
1 minute ago, theGrok said:

Hello,

 

I rebooted my server yesterday and when the system came back up one of my drives that I auto mount in Unassigned Devices showed up as completely blank with no files and no partition. It also has a red x that says clear next to it and shows as an 8TB disk but has no usable space.

 

.Did I lose all of my data? Is there a way to repair the file system? Not sure what caused this.

 

Any help would be appreciated. Thanks.

 

 

Screen Shot 2022-04-13 at 1.25.36 PM.png

Unmount it and click on the blue check mark to run a file system check.  See if that fixes it.

Link to comment
9 minutes ago, dlandon said:

 

You have another FCP error:

Apr 13 08:29:07 Nas1 root: Fix Common Problems: Error: Reserved user share user

Please take a few minutes and fix all the issues FCP is reporting.

 

Your mounts are interleaved and not sequential:

Apr 13 08:21:30 Nas1 unassigned.devices: Mounting Remote Share '//9900K/user-pool.9900kmegashare'...
Apr 13 08:21:30 Nas1 unassigned.devices: Mount SMB share '//9900K/user-pool.9900kmegashare' using SMB default protocol.
Apr 13 08:21:30 Nas1 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.9900kmegashare' '//9900K/user-pool.9900kmegashare' '/mnt/remotes/9900K_user-pool.9900kmegashare'
Apr 13 08:21:30 Nas1 kernel: CIFS: Attempting to mount \\9900K\user-pool.9900kmegashare
Apr 13 08:21:33 Nas1 unassigned.devices: Mounting Remote Share '9900K:/mnt/user/Media'...
Apr 13 08:21:33 Nas1 unassigned.devices: Mount NFS command: /sbin/mount -t 'nfs4' -o rw,noacl '9900K:/mnt/user/Media' '/mnt/remotes/9900K_Media'
Apr 13 08:21:34 Nas1 unassigned.devices: Successfully mounted '9900K:/mnt/user/Media' on '/mnt/remotes/9900K_Media/'.
Apr 13 08:21:34 Nas1 unassigned.devices: Adding SMB share '9900K_Media'.
Apr 13 08:21:34 Nas1 rpc.mountd[9639]: No host name given with /mnt/user/appdata (ro,async,wdelay,hide,nocrossmnt,secure,root_squash,no_all_squash,no_subtree_check,secure_locks,acl,no_pnfs,fsid=102,anonuid=65534,anongid=65534,sec=sys,ro,secure,root_squash,no_all_squash), suggest *(ro,async,wdelay,hide,nocrossmnt,secure,root_squash,no_all_squash,no_subtree_check,secure_locks,acl,no_pnfs,fsid=102,anonuid=65534,anongid=65534,sec=sys,ro,secure,root_squash,no_all_squash) to avoid warning
Apr 13 08:21:34 Nas1 rpc.mountd[9639]: v4.0 client attached: 0xba88df6e6256bfc4 from "192.168.50.119:964"
Apr 13 08:21:35 Nas1 kernel: CIFS: VFS: cifs_mount failed w/return code = -112
Apr 13 08:21:35 Nas1 unassigned.devices: SMB default protocol mount failed: 'mount error: Server abruptly closed the connection. This can happen if the server does not support the SMB version you are trying to use. The default SMB version recently changed from SMB1 to SMB2.1 and above. Try mounting with vers=1.0. mount error(112): Host is down Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) '.
Apr 13 08:21:35 Nas1 unassigned.devices: Mount SMB share '//9900K/user-pool.9900kmegashare' using SMB 3.1.1 protocol.
Apr 13 08:21:35 Nas1 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_user-pool.9900kmegashare' '//9900K/user-pool.9900kmegashare' '/mnt/remotes/9900K_user-pool.9900kmegashare'
Apr 13 08:21:35 Nas1 kernel: CIFS: Attempting to mount \\9900K\user-pool.9900kmegashare
Apr 13 08:21:35 Nas1 unassigned.devices: Successfully mounted '//9900K/user-pool.9900kmegashare' on '/mnt/remotes/9900K_user-pool.9900kmegashare/'.
Apr 13 08:21:35 Nas1 unassigned.devices: Adding SMB share '9900K_user-pool.9900kmegashare'.

Your 'user-pool.9900kmegashare' did not complete mounting before the '9900K_Media' began mounting.  That's not how the UD Auto Mounts work.  The mount in seqence.

 

Yoou should have 'Auto Mount' for the devices you want mounted at array start and not do anything else to start UD devices.  Are you running a script somewhere that tries to mount UD devices?  Are you mounting your old rootshare in fstab?

I do not have anything set to mount them.  I just have the set to auto mount through unassigned devices.  After I rebooted though, they didn’t auto mount.  So I clicked mount.

 

As for the FCP issue.  I am terrified to touch it.  It says I have an extra User share, but I never made one.  I looked and it seems like that is where all my shares are?  And my other server looks the same but that one isn’t flagged by FCP?  
 

I’m afraid to mess with it though for fear of blowing my Nas up.  Granted I don’t have much on that nas except media, but still.  I am not good with file systems in linux at all.  I would be more than happy to offer a small bounty to someone if they want to hold my hand through fixing it.

Link to comment
4 hours ago, dlandon said:

Unmount it and click on the blue check mark to run a file system check.  See if that fixes it.

I am not able to unmount it. When I click the unmount, the button turns grey and I see a spinning wheel and then The unmount button appears again in orange.

 

Oddly enough  here is the log from the disk nothing new since last night and it seems to say the disk was already mounted and it could not mount it. Is there a way to force unmount and then maybe it will work?

 

Apr 12 21:52:08 Medserver kernel: sd 8:0:1:0: [sdj] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
Apr 12 21:52:08 Medserver kernel: sd 8:0:1:0: [sdj] 4096-byte physical blocks
Apr 12 21:52:08 Medserver kernel: sd 8:0:1:0: [sdj] Write Protect is off
Apr 12 21:52:08 Medserver kernel: sd 8:0:1:0: [sdj] Mode Sense: 7f 00 10 08
Apr 12 21:52:08 Medserver kernel: sd 8:0:1:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA
Apr 12 21:52:08 Medserver kernel: sdj: sdj1
Apr 12 21:52:08 Medserver kernel: sd 8:0:1:0: [sdj] Attached SCSI disk
Apr 12 21:53:11 Medserver emhttpd: HGST_HDN728080ALE604_R6GSBU2Y (sdj) 512 15628053168
Apr 12 21:53:11 Medserver emhttpd: read SMART /dev/sdj
Apr 12 21:53:21 Medserver unassigned.devices: Adding partition 'sdj1'...
Apr 12 21:53:21 Medserver unassigned.devices: Mounting partition 'sdj1' at mountpoint '/mnt/disks/seed'...
Apr 12 21:53:21 Medserver unassigned.devices: Partition 'sdj1' is already mounted.
Apr 12 22:53:19 Medserver emhttpd: spinning down /dev/sdj

 

A few other things I noticed:

when I shutdown all services and stopped the array, and all disks unmounted, the folder /mnt/seed still existed and was not removed. I set the "bad" disk to not automount and I erased the /mnt/seed folder and restarted the server. The disk mounted anyways in it's bad state even though the auto mount option was turned off. There was nothing in the system log about attempting to mount the disk either. Also the permissions of the mount were set by root and were different than the other ones set by UA. 

 

 

Screen Shot 2022-04-13 at 6.24.13 PM.png

Edited by theGrok
add more information
Link to comment
12 minutes ago, sittingmongoose said:

As for the FCP issue.  I am terrified to touch it.  It says I have an extra User share, but I never made one.  I looked and it seems like that is where all my shares are?  And my other server looks the same but that one isn’t flagged by FCP?  

You may have something referencing /mnt/user/ for it's storage, instead of /mnt/user/sharename.

 

You still have some network issues.  Your 'Auto Mounts' failed because the remote server was not on-line.  Make sure Jumbo Frames are turned off on all your network devices if you aren't going to use Jumbo Frames.  Jumbo Frames require some sophisticated work to get working properly.

Link to comment
3 hours ago, dlandon said:

You may have something referencing /mnt/user/ for it's storage, instead of /mnt/user/sharename.

 

You still have some network issues.  Your 'Auto Mounts' failed because the remote server was not on-line.  Make sure Jumbo Frames are turned off on all your network devices if you aren't going to use Jumbo Frames.  Jumbo Frames require some sophisticated work to get working properly.

I do have krusader referencing it…but I do in my other server too.   I’ll try changing that and seeing if that stops FCP.  
 

Do the auto mounts keep trying?  So for example if I reboot my server and nas at the same time, the nas boots faster.  Once the server comes back, they should both eventually reconnect right?

 

I am running ubiquiti equipment.  Jumbo was on for both my dream machine and switch.  I turned both off.

 

Edit: Took /mnt/user/ out of my krusader template.  It didnt fix FCP.  All of my dockers are using /mnt/user/appdata/ is that a problem?  Thats how my other server is and its not complaining.  I only have two dockers on my Nas, syncthing and krusader.  Syncthing doesnt have user called out except for the appdata folder.

 

I also restarted my network equipment and did a reboot of both servers.  The nas which comes back first did not automount to the server.  But the server when it came back second did automount to the Nas.  Is this expected behavior?  Posting diags for both again.

nas1-diagnostics-20220413-1721.zip 9900k-diagnostics-20220413-1725.zip

Edited by sittingmongoose
Link to comment
4 hours ago, theGrok said:

I am not able to unmount it. When I click the unmount, the button turns grey and I see a spinning wheel and then The unmount button appears again in orange.

 

Oddly enough  here is the log from the disk nothing new since last night and it seems to say the disk was already mounted and it could not mount it. Is there a way to force unmount and then maybe it will work?

 

Apr 12 21:52:08 Medserver kernel: sd 8:0:1:0: [sdj] 15628053168 512-byte logical blocks: (8.00 TB/7.28 TiB)
Apr 12 21:52:08 Medserver kernel: sd 8:0:1:0: [sdj] 4096-byte physical blocks
Apr 12 21:52:08 Medserver kernel: sd 8:0:1:0: [sdj] Write Protect is off
Apr 12 21:52:08 Medserver kernel: sd 8:0:1:0: [sdj] Mode Sense: 7f 00 10 08
Apr 12 21:52:08 Medserver kernel: sd 8:0:1:0: [sdj] Write cache: enabled, read cache: enabled, supports DPO and FUA
Apr 12 21:52:08 Medserver kernel: sdj: sdj1
Apr 12 21:52:08 Medserver kernel: sd 8:0:1:0: [sdj] Attached SCSI disk
Apr 12 21:53:11 Medserver emhttpd: HGST_HDN728080ALE604_R6GSBU2Y (sdj) 512 15628053168
Apr 12 21:53:11 Medserver emhttpd: read SMART /dev/sdj
Apr 12 21:53:21 Medserver unassigned.devices: Adding partition 'sdj1'...
Apr 12 21:53:21 Medserver unassigned.devices: Mounting partition 'sdj1' at mountpoint '/mnt/disks/seed'...
Apr 12 21:53:21 Medserver unassigned.devices: Partition 'sdj1' is already mounted.
Apr 12 22:53:19 Medserver emhttpd: spinning down /dev/sdj

Post your diagnostics.

Link to comment
18 minutes ago, theGrok said:

medserver-diagnostics-20220413-1831.zip 167.24 kB · 1 download

 

Here are the diagnostics. I also updated my post above Original Post with a little bit more information. Thank you!

 

Your disk was unmounted by ntfs-3g:

Apr 13 18:16:16 Medserver unassigned.devices: Adding partition 'sda1'...
Apr 13 18:16:16 Medserver unassigned.devices: Mounting partition 'sda1' at mountpoint '/mnt/disks/flashbackup'...
Apr 13 18:16:16 Medserver unassigned.devices: Mount drive command: /sbin/mount -t 'ntfs' -o rw,noatime,nodiratime,nodev,nosuid,nls=utf8,umask=000 '/dev/sda1' '/mnt/disks/flashbackup'
Apr 13 18:16:17 Medserver ntfs-3g[24979]: Version 2017.3.23 integrated FUSE 27
Apr 13 18:16:17 Medserver ntfs-3g[24979]: Mounted /dev/sda1 (Read-Write, label "", NTFS 3.1)
Apr 13 18:16:17 Medserver ntfs-3g[24979]: Cmdline options: rw,noatime,nodiratime,nodev,nosuid,nls=utf8,umask=000
Apr 13 18:16:17 Medserver ntfs-3g[24979]: Mount options: rw,nodiratime,nodev,nosuid,nls=utf8,allow_other,nonempty,noatime,default_permissions,fsname=/dev/sda1,blkdev,blksize=4096
Apr 13 18:16:17 Medserver ntfs-3g[24979]: Global ownership and permissions enforced, configuration type 1
Apr 13 18:16:17 Medserver ntfs-3g[24979]: Unmounting /dev/sda1 ()

 

Put the disk in a PC and see if there are any issues with the disk.  Do a file system check.  I see nothing in the log that indicates why it unmounted.

 

You'll need to reboot before you put the disk back in the server.  UD still thinks the disk is mounted.

Link to comment
18 minutes ago, dlandon said:

 

Your disk was unmounted by ntfs-3g:

Apr 13 18:16:16 Medserver unassigned.devices: Adding partition 'sda1'...
Apr 13 18:16:16 Medserver unassigned.devices: Mounting partition 'sda1' at mountpoint '/mnt/disks/flashbackup'...
Apr 13 18:16:16 Medserver unassigned.devices: Mount drive command: /sbin/mount -t 'ntfs' -o rw,noatime,nodiratime,nodev,nosuid,nls=utf8,umask=000 '/dev/sda1' '/mnt/disks/flashbackup'
Apr 13 18:16:17 Medserver ntfs-3g[24979]: Version 2017.3.23 integrated FUSE 27
Apr 13 18:16:17 Medserver ntfs-3g[24979]: Mounted /dev/sda1 (Read-Write, label "", NTFS 3.1)
Apr 13 18:16:17 Medserver ntfs-3g[24979]: Cmdline options: rw,noatime,nodiratime,nodev,nosuid,nls=utf8,umask=000
Apr 13 18:16:17 Medserver ntfs-3g[24979]: Mount options: rw,nodiratime,nodev,nosuid,nls=utf8,allow_other,nonempty,noatime,default_permissions,fsname=/dev/sda1,blkdev,blksize=4096
Apr 13 18:16:17 Medserver ntfs-3g[24979]: Global ownership and permissions enforced, configuration type 1
Apr 13 18:16:17 Medserver ntfs-3g[24979]: Unmounting /dev/sda1 ()

 

Put the disk in a PC and see if there are any issues with the disk.  Do a file system check.  I see nothing in the log that indicates why it unmounted.

 

You'll need to reboot before you put the disk back in the server.  UD still thinks the disk is mounted.

 

Hi, So I could not unmount it despite pushing the unmount button. However when I stopped the array it unmounted and I was able to run a file system check and I am happy to report that it looks like it fixed it. What a relief!  Thank you so much for you help!

Link to comment

Since the update 2 hours ago, I have been receiving this on my test bench upon clean install

 

None of my default network settings or other attributes were changed. This is *almost* certainly attributed to the new pull

 

plugin: installing: https://raw.githubusercontent.com/dlandon/unassigned.devices/master/unassigned.devices.plg
plugin: downloading https://raw.githubusercontent.com/dlandon/unassigned.devices/master/unassigned.devices.plg
plugin: downloading: https://raw.githubusercontent.com/dlandon/unassigned.devices/master/unassigned.devices.plg ... done

Warning: simplexml_load_file(): /tmp/plugins/unassigned.devices.plg:5: parser error : xmlParseEntityDecl: entity version not terminated in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): /tmp/plugins/unassigned.devices.plg:5: parser error : xmlParseEntityDecl: entity version not terminated in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): /tmp/plugins/unassigned.devices.plg:5: parser error : xmlParseEntityDecl: entity version not terminated in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): /tmp/plugins/unassigned.devices.plg:5: parser error : xmlParseEntityDecl: entity version not terminated in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212
plugin: XML file doesn't exist or xml parse error

 

Link to comment
11 minutes ago, erlipton said:

Since the update 2 hours ago, I have been receiving this on my test bench upon clean install

 

None of my default network settings or other attributes were changed. This is *almost* certainly attributed to the new pull

 

plugin: installing: https://raw.githubusercontent.com/dlandon/unassigned.devices/master/unassigned.devices.plg
plugin: downloading https://raw.githubusercontent.com/dlandon/unassigned.devices/master/unassigned.devices.plg
plugin: downloading: https://raw.githubusercontent.com/dlandon/unassigned.devices/master/unassigned.devices.plg ... done

Warning: simplexml_load_file(): /tmp/plugins/unassigned.devices.plg:5: parser error : xmlParseEntityDecl: entity version not terminated in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): /tmp/plugins/unassigned.devices.plg:5: parser error : xmlParseEntityDecl: entity version not terminated in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): /tmp/plugins/unassigned.devices.plg:5: parser error : xmlParseEntityDecl: entity version not terminated in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): /tmp/plugins/unassigned.devices.plg:5: parser error : xmlParseEntityDecl: entity version not terminated in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212

Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 212
plugin: XML file doesn't exist or xml parse error

 

Just fixed this.  Try again.

Link to comment

May I issue a feature request here?

 

There's a "Disable Unmount Button" for disks - but not for remote SMB shares. Would it be possible to add this option?

 

I'm using "/usr/local/sbin/rc.unassigned mount/unmount" within User Scripts during Array Start/Stop. This option would help not to hit Unmount by accident.

 

Link to comment
1 hour ago, hawihoney said:

May I issue a feature request here?

 

There's a "Disable Unmount Button" for disks - but not for remote SMB shares. Would it be possible to add this option?

 

I'm using "/usr/local/sbin/rc.unassigned mount/unmount" within User Scripts during Array Start/Stop. This option would help not to hit Unmount by accident.

 

Will be in the next release.

  • Thanks 1
Link to comment
26 minutes ago, sittingmongoose said:

Could you include an option to try to reconnect I mounted shares if they are set to auto mount?  Maybe try again after 5,10,15 minutes?

 

The best way to handle this is with a User Script.  Enter the following commands in a User Script set to run "At First Array Start Only".

# Wait for 10 minutes
sleep 600

# Auto mount all UD remote shares
/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned mount autoshares

If the shares are already mounted, UD will not attempt to mount them again.

  • Like 2
Link to comment
1 hour ago, dlandon said:

 

The best way to handle this is with a User Script.  Enter the following commands in a User Script set to run "At First Array Start Only".

# Wait for 10 minutes
sleep 600

# Auto mount all UD remote shares
/usr/local/emhttp/plugins/unassigned.devices/scripts/rc.unassigned mount autoshares

If the shares are already mounted, UD will not attempt to mount them again.

This is exactly what I needed thank you.

 

So is there any hope to fix the error im getting every minute?

 

Apr 14 13:23:58 Nas1 kernel: CIFS: VFS: \\9900K\user-pool.9900kmegashare Close unmatched open for MID:9803351

 

I only get it on the smb connected rootshares between the two unraid servers.  I use rootshare because I manage them frequently through krusader.  

 

Maybe a solution would be to use nfs?  Is there a way to mount the rootshares through NFS? 

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.