10 minutes ago, dlandon said:

It's not UD.  The remote shares unmounted fine.  It's the dockers taking a long time to stop:

Mar 27 12:19:06 Apollo root: stopping dockerd ...
Mar 27 12:19:07 Apollo root: ... Waiting to die.
Mar 27 12:19:08 Apollo root: ... Waiting to die.
Mar 27 12:19:09 Apollo root: ... Waiting to die.
Mar 27 12:19:10 Apollo root: ... Waiting to die.
Mar 27 12:19:11 Apollo root: ... Waiting to die.
Mar 27 12:19:12 Apollo emhttpd: shcmd (94): umount --lazy /var/lib/docker
Mar 27 12:19:12 Apollo unassigned.devices: Unmounting All Devices...
Mar 27 12:21:02 Apollo sshd[1168]: Connection from 192.168.2.35 port 17590 on 192.168.2.40 port 22 rdomain ""
Mar 27 12:21:02 Apollo sshd[29211]: Connection closed by 192.168.2.35 port 17480
Mar 27 12:21:02 Apollo sshd[29211]: Close session: user root from 192.168.2.35 port 17480 id 0
Mar 27 12:21:02 Apollo sshd[29211]: pam_unix(sshd:session): session closed for user root
Mar 27 12:21:02 Apollo sshd[29211]: Transferred: sent 154472, received 4672 bytes
Mar 27 12:21:02 Apollo sshd[29211]: Closing connection to 192.168.2.35 port 17480
Mar 27 12:21:02 Apollo elogind-daemon[1528]: Removed session c4.
Mar 27 12:21:02 Apollo sshd[1170]: Connection from 192.168.2.35 port 17591 on 192.168.2.40 port 22 rdomain ""
Mar 27 12:21:02 Apollo sshd[1172]: Connection from 192.168.2.35 port 17592 on 192.168.2.40 port 22 rdomain ""
Mar 27 12:21:02 Apollo sshd[1168]: Postponed keyboard-interactive for root from 192.168.2.35 port 17590 ssh2 [preauth]
Mar 27 12:21:02 Apollo sshd[1168]: Postponed keyboard-interactive/pam for root from 192.168.2.35 port 17590 ssh2 [preauth]
Mar 27 12:21:02 Apollo sshd[1168]: Accepted keyboard-interactive/pam for root from 192.168.2.35 port 17590 ssh2
Mar 27 12:21:02 Apollo sshd[1168]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Mar 27 12:21:02 Apollo elogind-daemon[1528]: New session c5 of user root.
Mar 27 12:21:02 Apollo sshd[1170]: Postponed keyboard-interactive for root from 192.168.2.35 port 17591 ssh2 [preauth]
Mar 27 12:21:02 Apollo sshd[1170]: Postponed keyboard-interactive/pam for root from 192.168.2.35 port 17591 ssh2 [preauth]
Mar 27 12:21:02 Apollo sshd[1170]: Accepted keyboard-interactive/pam for root from 192.168.2.35 port 17591 ssh2
Mar 27 12:21:02 Apollo sshd[1170]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Mar 27 12:21:03 Apollo elogind-daemon[1528]: New session c6 of user root.
Mar 27 12:21:03 Apollo sshd[1172]: Postponed keyboard-interactive for root from 192.168.2.35 port 17592 ssh2 [preauth]
Mar 27 12:21:03 Apollo sshd[1172]: Postponed keyboard-interactive/pam for root from 192.168.2.35 port 17592 ssh2 [preauth]
Mar 27 12:21:03 Apollo sshd[1172]: Accepted keyboard-interactive/pam for root from 192.168.2.35 port 17592 ssh2
Mar 27 12:21:03 Apollo sshd[1172]: pam_unix(sshd:session): session opened for user root(uid=0) by (uid=0)
Mar 27 12:21:03 Apollo elogind-daemon[1528]: New session c7 of user root.
Mar 27 12:21:03 Apollo sshd[1168]: Starting session: subsystem 'sftp' for root from 192.168.2.35 port 17590 id 0
Mar 27 12:21:03 Apollo sshd[1170]: Starting session: subsystem 'sftp' for root from 192.168.2.35 port 17591 id 0
Mar 27 12:21:03 Apollo sshd[1172]: Starting session: subsystem 'sftp' for root from 192.168.2.35 port 17592 id 0
Mar 27 12:21:03 Apollo sshd[1172]: Connection closed by 192.168.2.35 port 17592
Mar 27 12:21:03 Apollo sshd[1172]: Close session: user root from 192.168.2.35 port 17592 id 0
Mar 27 12:21:03 Apollo sshd[1172]: pam_unix(sshd:session): session closed for user root
Mar 27 12:21:03 Apollo sshd[1172]: Transferred: sent 3656, received 3232 bytes
Mar 27 12:21:03 Apollo sshd[1172]: Closing connection to 192.168.2.35 port 17592
Mar 27 12:21:03 Apollo elogind-daemon[1528]: Removed session c7.
Mar 27 12:21:03 Apollo sshd[1170]: Connection closed by 192.168.2.35 port 17591
Mar 27 12:21:03 Apollo sshd[1170]: Close session: user root from 192.168.2.35 port 17591 id 0
Mar 27 12:21:03 Apollo sshd[1170]: pam_unix(sshd:session): session closed for user root
Mar 27 12:21:03 Apollo sshd[1170]: Transferred: sent 3656, received 3232 bytes
Mar 27 12:21:03 Apollo sshd[1170]: Closing connection to 192.168.2.35 port 17591
Mar 27 12:21:03 Apollo elogind-daemon[1528]: Removed session c6.
Mar 27 12:21:51 Apollo kernel: CIFS: VFS: \\10.0.0.2 has not responded in 180 seconds. Reconnecting...
Mar 27 12:21:51 Apollo kernel: CIFS: VFS: \\10.0.0.2\Dropbox Close cancelled mid failed rc:-11
Mar 27 12:21:51 Apollo kernel: CIFS: VFS: \\10.0.0.2\Dropbox Close cancelled mid failed rc:-11
Mar 27 12:21:51 Apollo kernel: CIFS: VFS: \\10.0.0.2\Dropbox Close cancelled mid failed rc:-11
Mar 27 12:22:22 Apollo unassigned.devices: Unmounting Remote SMB/NFS Share '//10.0.0.2/Dropbox'...
Mar 27 12:22:22 Apollo unassigned.devices: Unmount cmd: /sbin/umount -t cifs -f '/mnt/remotes/Dropbox' 2>&1
Mar 27 12:22:22 Apollo unassigned.devices: Successfully unmounted '//10.0.0.2/Dropbox'
Mar 27 12:22:43 Apollo unassigned.devices: Unmounting Remote SMB/NFS Share '//10.0.0.2/Dropbox/Pictures'...
Mar 27 12:22:43 Apollo unassigned.devices: Unmount cmd: /sbin/umount -t cifs -f '/mnt/remotes/Pictures' 2>&1
Mar 27 12:22:43 Apollo unassigned.devices: Successfully unmounted '//10.0.0.2/Dropbox/Pictures'

I think your shutdown timer is set properly to handle this.

Ok that makes sense. I appreciate your help. Sorry for bothering you. 😊

24 minutes ago, dlandon said:

The mount points you are trying to mount remotely are not Unraid shares and you are setting the export rules manually for those shares.  This is an Unraid share entry in the exports file:

"/mnt/user/isos" -fsid=105,async,no_subtree_check *(rw,sec=sys,insecure,anongid=100,anonuid=99,all_squash)

I suggest you take a look at this entry and compare to your entries and see if changes are needed.  I suspect a permissions issue that UD is having trouble with.  Check if 'all_squash' makes a difference.

 

As a test, share a normal Unraid share with NFS and try to mount that and see how it goes.

 

I fully understand that you can mount those with other systems.  The issue is that the UD NFS client is probably more restrictive about permissions.

Little confused these nfs shares are not from unraid but a debian distro running on a pi.

I dont want to mount any Unraid Shares.

34 minutes ago, DuzAwe said:

Little confused these nfs shares are not from unraid but a debian distro running on a pi.

I dont want to mount any Unraid Shares.

Ok.  But if you want Unraid to mount them, you'll probably need to add all or part of this to the rules:

anongid=100,anonuid=99,all_squash

 

3 hours ago, dlandon said:

Ok.  But if you want Unraid to mount them, you'll probably need to add all or part of this to the rules:

anongid=100,anonuid=99,all_squash

 

Still no joy. I got it working with samba.

hey guys , am new to unraid ,,

ive been using unassigned devices and working fine so far but there's a small issue where some files not shown in the mount drive tho its already there ( synology )

any clue would be appreciated

5 minutes ago, drahmed86 said:

hey guys , am new to unraid ,,

ive been using unassigned devices and working fine so far but there's a small issue where some files not shown in the mount drive tho its already there ( synology )

any clue would be appreciated

There is an issue with CIFS mounts (remote shares) in 6.12.9 that causes this issue.  For the moment downgrade to 6.12.8 until we come up with a solution.  Since this appears to be related to Samba (CIFS mounts) or the Kernel, it will have to be fixed with an Unraid release.  I haven't been able to address the issue with anything related to how UD mounts remote shares.

13 minutes ago, dlandon said:

There is an issue with CIFS mounts (remote shares) in 6.12.9 that causes this issue.  For the moment downgrade to 6.12.8 until we come up with a solution.  Since this appears to be related to Samba (CIFS mounts) or the Kernel, it will have to be fixed with an Unraid release.  I haven't been able to address the issue with anything related to how UD mounts remote shares.

ya actually saved my day,ty

I'm using this plugin to mount a Hetzner Storage Box via NFS on my Unraid machine as an offsite borg backup. This mostly works fine, but I'm experiencing an issue where fairly frequently Hetzner will perform maintenance (or something akin) and the NFS connection is broken - and not automatically re-established. This causes my regular borg backup to break indefinitely until I unmount/remount the share and restart the borgmatic container.

 

Hetzner have recommended mounting the share with autofs, which should resolve the problem. Is there a way to do this via this plugin?

 

If not, would a suitable alternative be to spin up a small VM that mounts the share via autofs, which then re-exposes it via NFS/Samba?

2 hours ago, ryanskidmore said:

Hetzner have recommended mounting the share with autofs, which should resolve the problem. Is there a way to do this via this plugin?

UD is not able to accomodate this.  You should look into setting up an fstab where you can specify the autofs.

I've been using Unraid and this plugin for years, but recently I've upgraded to the latest version and the new Unraid version. I have been getting some weird issues..

 

I use Radarr and Sonarr for movies and tv shows, All my movies or tv shows are stored on my NAS drive.

So the other day I was getting messages saying the movie or TV show file was deleted from Radarr and Sonarr. Checked the radar/Sonarr and it says the file is missing. So then I checked the movie/TV show on my NAS and the file is there.

 

Next, I go to Unassigned device click on my SMB share and then click on one of the movies/TV shows it says is missing and the mkv file is not there.

 

File exists on my NAS

Nas drive mounted into unraid with unassigned devices not seeing the file.

11 minutes ago, Dialatech2303 said:

I have been getting some weird issues..

Downgrade back to 6.12.8, there's a known issue about remote SMB mounts in 6.12.9.

 

 

7 minutes ago, Kilrah said:

Downgrade back to 6.12.8, there's a known issue about remote SMB mounts in 6.12.9.

 

 

 

 

Great thank you for the quick reply

dev1 and Dev 2?? Is this in Unraid or in unassigned devices? 

I put in a new (second) Nvme drive today and it shows up in my UX. I can format it, but after doing so, Mount is greyed out. Not sure how to move forward.

5 hours ago, rickeames said:

Not sure how to move forward.

Try clicking on the double arrows in the upper right of the UD page. It should initiate udev to refresh the disk status.

Thank you -- that was the ticket.

Anyone having issues with remote NFS shares not mounting because of the "protocol not supported" problem, update UD and is a patch will be applied to overecome an issue with an NFS setting we enabled that causes this issue.  UD reverts that setting so these errors do not occur.  It isn't an issue with Unraid to Unraid connections with NFS, it seems to only affect other server devices that don't behave the same way as Unraid.

Can anyone advise what user is used when making remote file shares in NFS?  Struggling to get a rpi share up and running. 
 

thanks 

Hello,

 

I encounter strange problem after update Unraid to 6.12.9. Some files in SMB mount are not visible to Unraid.

I have docker container with Emby and mounted remote share from Synology NAS (SMB). This remote share with video files mapped to Emby container. Everything worked great until update to 6.12.9. During scanning a Emby Library a got info that some video files was removed and also deleted from Emby database (about 600-800 files). I checked on remote share on Unraid and indeed this files is missing but on Synology files are still ok. I don't know why this files are no visible to Unraid.

 

After downgrade to 6.12.8 everything is ok. What can I do or check?

it's a known problem and an Unraid update will be available soon to fix this.

After I did update to 6.12.9, I started to have a problem, after 20min in after boot, one core does max out and RAM starting to grow until 100% and locks up the system.

 

After many tries, and after safemode test, it happon only with plugins enabled and I dont even need array started or disks plugged in. 

 

Thanks to plugin EnchantedSyslog I did get this when the cpu started maxed out after 20min, Did google the code, find a old post that did send me here, anyone seen this before?

 

Mar 31 22:28:23 Lucifer smbd[18713]: [2024/03/31 22:28:23.488637,  0] ../../lib/param/loadparm.c:1959(lpcfg_do_service_parameter)
Mar 31 22:28:23 Lucifer smbd[18713]:   Global parameter server multi channel support found in service section!
Mar 31 22:28:23 Lucifer smbd[18713]: [2024/03/31 22:28:23.488693,  0] ../../lib/param/loadparm.c:1959(lpcfg_do_service_parameter)
Mar 31 22:28:23 Lucifer smbd[18713]:   Global parameter interfaces found in service section!
Mar 31 22:32:28 Lucifer smbd[30672]: [2024/03/31 22:32:28.185601,  0] ../../lib/param/loadparm.c:1959(lpcfg_do_service_parameter)
Mar 31 22:32:28 Lucifer smbd[30672]:   Global parameter server multi channel support found in service section!
Mar 31 22:32:28 Lucifer smbd[30672]: [2024/03/31 22:32:28.185625,  0] ../../lib/param/loadparm.c:1959(lpcfg_do_service_parameter)
Mar 31 22:32:28 Lucifer smbd[30672]:   Global parameter interfaces found in service section!
Mar 31 22:34:27 Lucifer smbd[4476]: [2024/03/31 22:34:27.956301,  0] ../../lib/param/loadparm.c:1959(lpcfg_do_service_parameter)
Mar 31 22:34:27 Lucifer smbd[4476]:   Global parameter server multi channel support found in service section!
Mar 31 22:34:27 Lucifer smbd[4476]: [2024/03/31 22:34:27.956324,  0] ../../lib/param/loadparm.c:1959(lpcfg_do_service_parameter)
Mar 31 22:34:27 Lucifer smbd[4476]:   Global parameter interfaces found in service section!

 

 

The old post:

Quote

I have been troubleshooting this, and after I removed UNASSIGNED DEVICES these syslog entries stopped.

https://forums.unraid.net/topic/121797-syslog-being-filled/

 

My post about the problem:

https://forums.unraid.net/topic/160025-ram-problem-after-os-update/

 

 

 

EDIT:

Did resolve it! Was something in my SMB Extra.

https://forums.unraid.net/topic/160025-ram-problem-after-os-update/?do=findComment&comment=1397328

 

Edited March 31, 20242 yr by ChillZwix

4 hours ago, firedog said:

Can anyone advise what user is used when making remote file shares in NFS?  Struggling to get a rpi share up and running. 
 

thanks 

NFS does not use credentials.  It uses Linux permissions.  There is an issue with UD and 6.12.9 Unraid.  Update UD and see if you can get your NFS shares to mount.

On 3/27/2024 at 4:45 PM, DuzAwe said:

Still no joy. I got it working with samba.

I found an issue with NFS that is resolved with the latest release of UD that I believe will solve the NFS mounting issue.

6 hours ago, dlandon said:

I found an issue with NFS that is resolved with the latest release of UD that I believe will solve the NFS mounting issue.

Is it possible that you forget to list the fixes?

5 hours ago, saber1 said:

Is it possible that you forget to list the fixes?

Yes.

 

Fix: Apply a patch to revert an NFS setting causing "protocol not supported" issue.