dlandon

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.

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

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?

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?

There are two root share choices: The "User and Pool Shares" choice should include your appdata. Your log looks a lot cleaner.

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.

Your log is being spammed with myunraid.net messages. It's very hard to see anything relevant. @ljm42 can you take a look at this. I still see NFSv3 being mounted: Apr 11 17:01:43 9900K unassigned.devices: Mount NFS command: /sbin/mount -t 'nfs' -o rw,noacl 'NAS1:/mnt/user/Media2' '/mnt/remotes/NAS1_Media2' The behaviour you are experiencing is what happens with NFSv3. For NFSv4, the 'nfs' will be 'nfs4' in the mount command.

No, just post diagnostics.

There was at least one version of UD that had a bug that showed 'Array' when it shouldn't. Updating UD fixed that bug.

The only change was to respect the NFS version setting in the UD Settings. Just switch that to NFSv3 and it will mount them the same as before the change. This really surprises me though, because NFSv3 is known to cause the issues you are describing.

You won't be able to do anything until you clear the 'Array' status. Reboot and it should clear up. Those disks were probably not unmounted before being removed, or they were part of the array and fell out of the array.

Ok, that shows that there are no deleted files being logged. Show the output of this command: cat /var/log/samba/log.smbd This will show if any logging is done at all.

I found a bug in UD that was preventing NFSv4 from working. That's why I thought you were only using NFSv3. I just released a fix. I suggested this fix because I wanted to be sure there was no interraction between the nfs and cifs mounts. I totally get it, but I can't explain the log entries you are getting. There is very little information available about this log message except it has something to do with an interrupted system call. You might check to be sure your network is not having any issues. Are you using /mnt/remotes/ or the SMB share to transfer data?

I'm having a little trouble understanding why you are cross mounting root shares, but for starters you need to be using NFSv4 and not NFSv3. The mount comand in your log is for NVSv3. Apr 11 17:01:43 9900K unassigned.devices: Mount NFS command: /sbin/mount -t 'nfs' -o rw,noacl 'NAS1:/mnt/user/Media2' '/mnt/remotes/NAS1_Media2' Set NFSv4 in the UD Settings, then unmount and remount your NFS shares.

Post your diagnostics.

Show the output of this command: cat /var/log/samba/log.smbd | grep unlink

Your USB disconnected and Linux assigned a new designation thinking it is a new disk. The UD update did not have anything to do with the issue. UD does not take over any disks. Unraid did not see it as the flash drive so it ended up as Unassigned and UD then shows it.

If I recall, changing the mount point on the primary pool device will change them all.

Did you see my suggestion about removing all the historical information for the devices? Enter the disk label as the mount point. A pool of devices is where all the disks have the same label and the same UUID. Because UD isn't pool aware, you have to trick it into finding the pool.

It probably works, but you should not assume [global]. Add the [global] tag ahead of your settings.

Did you copy your old configuration to the new disk?

I'm not sure of your sequence of events, but probably. Look in the log after your unmount attempts and see if it's because the mounts are busy.

In order to support legacy devices using SMB2 and connecting to Unraid shares. the implementation of these security settings will have to be configurable. Because of the desire to get 6.10 released, it is being held up for now. For the time being, you can put those settings with a [global] tag in smb-extra.conf.

No.

Try a blank the mount point and it should pick up the default pool label. If that doesn't work, remove all the pool devices and delete each one in Historical devices. Then re-install them. Edit: The mount point has to be the disk label on the pool devices.