dlandon

Screen shot?

Agreed. It will be a support issue. We're looking at options.

Cick the red 'X' on the serial number line to clear the preclear partition, then the 'Format' button will show and you can format the disk.

Enable the UD destructive mode in Settings->Unassigned Devices and then use the clear disk (click on red 'X') by the serial number. That will clear the disk of all partitions.

Ah, it's the old reboot fix. Funny how that clears up a lot of stuff sometimes. We re looking at the options. The /mnt/user/share should work. I'll leave this open and see if we can implement a fix for this. You could then test it.

UD will not recognize a linux_raid_member format, so reformatting it would be necessary. Why don't you look at formatting it in UD and then passing it through to the VM?

Why are you mounting like this: main/longhorn-backups 14T 130G 14T 1% /mnt/main/longhorn-backups That will be a problem. Your dummy share is at /mnt/cache/: cache/dummyshare 1.7T 128K 1.7T 1% /mnt/cache/dummyshare So your should be able to access it.

No worries. This is the kind of feedback we need to understand how people use Unraid and what issues they have. I'll leave this open until we have some sort of resolution. Sorry, too many conversations going on about the same subject.

The device is mounted at /mnt/nvme. Why? UD shouldn't mount it if it is already mounted somewhere else. It will cause corruption of the disk if UD does manage to mount it.

We are looknig at some options.

The trailing "/" is needed for the symlink. Using /mnt/user/, doesn't help if the docker container doesn't add a trainling "/" to the share folder like this /mnt/user/symlink/ to reference the folder.

Settings only show if the disk has a valid partition with a recognized file system. What file system did you format on the partition? UD won't be able to mount the disk, even if passed through is turned off. Linux does not recognize the file system.

I only gave you that UD mount as an example of what works. My example is the same as yours, with the exception that my share on a XFS formatted cache disk, and I use the server name instead of the IP address in the mount command. Maybe one of those affects the mount in your case. Please post your diagnostics so I can have a better look.

Did you use UD to create and manage the shares? Post diagnostics.

Yes, and it works for me. root@BackupServer:~# ls -la /mnt/cache/ total 4 drwxrwxrwx 5 nobody users 50 May 18 17:47 ./ drwxr-xr-x 13 root root 260 May 19 10:45 ../ drwxrwxrwx 3 nobody users 4096 May 11 04:40 Syslogs/ drwxrwxrwx 3 nobody users 32 Apr 4 13:42 Unraid/ drwxrwxrwx 7 nobody users 105 Apr 28 18:40 appdata/ And the UD mount to mount the share: May 19 10:49:04 MediaServer unassigned.devices: Mounting Remote Share 'BACKUPSERVER:/mnt/cache/Syslogs'... May 19 10:49:04 MediaServer unassigned.devices: Mount NFS command: /sbin/mount -t 'nfs4' -o rw,noacl 'BACKUPSERVER:/mnt/cache/Syslogs/' '/mnt/remotes/BACKUPSERVER_Syslogs'

The dockers are assuming that the symlinks are files and not directories. The option is to not to set up exculsive shares and map the share directly in cases where it is needed. For example, I have my appdata mapped directly to /mnt/cache/appdata/ and not /mnt/user/appdata/. This in effect provides the same operation as exclusive share access at /mnt/user/appdata/ symlinked to /mnt/cache/appdata/. The whole idea behind exclusive shares is to get around the /mnt/user/ file handling so access is faster and the user doesn't have to be concerned with the direct share mapping. You don't have to use it.

I did a little experiment and to mount the NFS share, you need to mount /mnt/cache/dummyshare/ and not /mnt/user/dummyshare/.

The only difference will be that the /mnt/user/share for an exclusive share will be a symlink. If you don't include the trailing "/", the mapping of /mnt/user/share will appear to be a file and not a directory. If you use /mnt/user/share/ it will be treated as a directory.

Show the output of this command: ls -la /mnt/user/.

I just ran a test and it worked for me. Your path needs to be the actual share path. The exclusive share may not be in /mnt/user/. For example you have this as an exclusive share on a pool. Your mapping should be '/mnt/pool/longhorn-backups/.

You need to put a trailing "/" on your paths.

Try putting a trailing slash on the mount directory: /mnt/user/longhorn-backups/.

Can you also post the preclear logs? I've made a change so the divide by zero will not happen, but we need to find out why there is no available space. Something is clobbering the rootfs. Do the following: Post the output of the 'ls -la /' command. Reboot in safe mode. Post the results of the 'df /' command. If the command shows expected results, you'll need to find out which plugin, VM, or Docker Container is messing with rootfs. You may have a misconfigured path.

Post diagnostics. The script needs to be modified to at least handle this situation a bit better. I'll work on that.

Looks like UD sees a partition on the device. Enable destructive mode and clear the disk (red 'X') next to the serial number.