dlandon

I've updated UD to handle NFS remote mounts on servers that do not accept 'server://share' for the source. This has been this way in UD since I took it over many years ago. I'm surprised that it has taken this long to surface. I don't know why the 'server://share' format was chosen, but it seems to be a problem with some servers and in my testing I didn't find any issues with the single '/'. Any existing NFS remote mounts will continue to work. You don't need to make any changes. They will show a source of 'server://share'. They will mount and work fine. You will notice that when you create a new NFS share the source will now be 'server:/share' and not 'server://share'.

Update UD and try again. You'll need to recreate the NFS share. You should notice now the source will be 'server:/share' and not 'server://share' when you create the remote shares.

Ok. I see the issue. I'll do some testing. The issue is the // after the IP address. Strange this has not come up before this.

Try this: mount -t nfs 192.168.1.225://MejoServerNFS /mnt/user/MeJoServerTv/MeJoQnap I'd really like to figure this one out.

Will it mount without the port command or the proto command? UD does not specify either. It may be one or both need to be added to the mount command.

Can you show your terminal mount commands? I don't understand why UD won't mount them.

The first mount is a permission issue as you noted. I don't know enough about NFS mounts to offer any help on how to fix that. Others here can help. The second issue doesn't make any sense. If you selected the server and share from the list, it shouldn't fail on not found. Check and see that the spelling and case is correct. Is the server IP address correct for this share? Is the server IP address static?

Add the nfs remote shares in ud by searching the server, make a selection, then search the shares and make a selection. Don't enter anything manually. I think you're entering it wrong.

Don't mount anything at /mnt/user/. Why are you trying to mount the NFS share in a UD script? Mount the NFS share with UD as a remote share and then refer to it in your script. UD will mount it at /mnt/disks//MeJoServerTv/MeJoQnap1.

Are those devices connected through a USB hub?

UD is seeing those devices: Jan 25 08:11:28 Tower unassigned.devices: Mounting 'Auto Mount' Devices... Jan 25 08:11:28 Tower unassigned.devices: Disk with serial 'Transcend_16GB_15H2VE3EAPUM8OBL', mountpoint 'UNRAIDVM02' is not set to auto mount and will not be mounted. Jan 25 08:11:28 Tower unassigned.devices: Disk with serial 'DataTraveler_2.0_001A4D5F25DFC290595BF646', mountpoint 'UNRAIDVM01' is not set to auto mount and will not be mounted. I have no idea why they are not showing in the UD webpage. Nothing has changed in the UD webpage display lately that would affect that.

Looks to be a repository issue. I have no control over the repository.

Not really. I'd like to see the diagnostics after you deleted the UD configurations and re-installed the plugin. There are reasons I ask for things. If I have to ask twice, it only slows down the efforts to help with your issue.

I believe sda is your Unraid flash device. Please post another diagnostics.

Remove the UD plugin, delete the /flash/config/plugins/unassigned.devices folder and then re-install UD. All your unassigned devices should then show in UD. Be sure to switch on the "Pass Through" for the devices that you pass through to VMs.

Diagnostics, not a syslog.

Post diagnostics.

Neither. Post diagnostics.

No. It looks to be a network issue. It might be the GitHub repository for the UD plugin. Try again.

That's not the UD plugin. That's the standard Unraid unassigned devices page.

The reason auto mount default was changed is a problem in the following scenario: Install a new drive and pass through the drive to a VM or Docker. If UD defaults to auto mount on and you did not specifically set it in UD to not auto mount, UD would mount the drive on reboot and corrupt the file system. You can't have a disk passed to a VM or Docker and also have it mounted by UD. I added the pass through switch so you can designate the disk as passed through and UD will not try to mount it and the mount button is disabled so you don't accidentally mount the disk.

If you navigate to the UD page and the auto mount is set like you want, there is nothing else to do. If you never changed any settings for the drive, the auto mount will default to off now, instead of on. The status will be reflected in the setting of the switch. Just set it how you want.

It used to default to on when a new drive was introduced. It now defaults to off. If you already set it manually, then there is nothing to do.

There is a new version of UD available. The changes are: Remove ext4 format. Ext4 is not a format used in Unraid and is available in UD for file transfer purposes. It is not recommended to use an ext4 disk for Unraid purposes such as VMs or Dockers. Ext4 disks can still be mounted. The 'Auto Mount' switch now defaults to off for physical disk devices. This might affect existing disks you have that are still using the default setting. Just go to UD and set the 'Auto Mount' switch on for any physical disks you want auto mounted. Add a 'Pass Through' switch. Set this switch to on for any disks you are passing through to a VM or Docker. When this switch is set, UD will not allow a manual mount and will not attempt to auto mount the disk even if 'Auto Mount' is turned on. UD will not monitor the disk temperature. Anyone passing through a disk to a VM or Docker should go to UD and set the 'Pass Through' switch on. With this switch set on, UD will not allow mounting the disk. It is known that mounting a passed through disk with UD will corrupt the file system on the disk.

If this is the situation you have, it makes sense. For some reason I was under the impression that you were using the disk for the VM image, and not as a pass through disk to a VM. The reason this happened is that a new disk found by UD defaults the 'Auto Mount' on. I will look into making a change to this.