dlandon

I've applied a fix for this. I'll refresh today's release once I see if anyone else comes up with additional devices. For the time being, just ignore it.

Update to today's release of UD, delete your NFS remote shares and then re-add them using the server name. Click on the 'Search for Servers' button and choose the server you want.

New release of UD: Pool devices are now handled better by UD. Pool devices must all have the same mount point in UD and any of the pool device's 'Mount' button will mount the pool. When mounted the primary device has an active 'Unmount' button. Secondary devices are marked 'Pool'. The primary device is used to umnount the pool. Pooled devices unassigned from Unraid Pools can be mounted by UD. The UD check for mount point duplicates now works even with Pool Devices. The setting to not check UD devices for duplicates has been removed. It is no longer necessary. Ability to save a blank mount point. This removes the UD mount point setting and can be helpful with a disk pool device that has a UD historical mount point. Pooled devices will use the disk label (common to all pooled devices) as the mount point. Fix for CIFS mounts on Windows computers that sometimes won't mount because of local name resolution. It is recommended to have SMBv1 disabled on all Windows computers and NetBIOS disabled on your Unraid server. Fix for disks showing in sdX order. They were sometimes out of order. SMB/NFS, ISO, and historical devices are now sorted in alphabetic order. Applied a fix that should show SCSI disks in UD with the dynamix.scsi.device plugin installed. UD now excludes CD and DVD disks, and accepts all other devices. This was changed from including only sd, hd, and nvme devices. I have no way to test though, so I don't know if this works. Feedback would be appreciated. If you see a device in UD that should not be there, let me know as I may need to exclude it. SMB and NFS server lookups display all servers now by name and not IP address. It is best to use the server name and not the IP address. If the IP address of a server is not static, it can change causing remote mounts to fail. Some minor GUI changes. With the changes in resolving local servers and the lookup of servers now showing server names and not IP addresses, there should be no need for using IP addresses for remote shares, especially NFS shares. I recommend updating all remote shares to use the server name and not the IP address.

What is that IP address - 172.27.9.90? That can't be your LAN?

I guess I was wrong. You do have an issue with this drive. There is no work around to your drive disconnecting, except to fix it. It it's a USB drive, try another UB port. Post diagnostics so we can see what is causing the disconnect.

It doesn't indicate a problem with your system, it's just a situation that UD does not handle well.

Jan 1 22:26:26 Tower unassigned.devices: Mount NFS command: /sbin/mount -t 'nfs4' -o rw,noacl '172.27.9.90:/mnt/Skywalker/Nikki' '/mnt/remotes/172.27.9.90_Nikki' Jan 1 22:26:26 Tower unassigned.devices: NFS mount failed: 'mount: /mnt/remotes/172.27.9.90_Nikki: unknown filesystem type 'nfs4'. '. Jan 1 22:26:31 Tower unassigned.devices: Mounting Remote SMB/NFS Share '172.27.9.90:/mnt/Skywalker/Nikki'... Jan 1 22:26:31 Tower unassigned.devices: Mount NFS command: /sbin/mount -t 'nfs4' -o rw,noacl '172.27.9.90:/mnt/Skywalker/Nikki' '/mnt/remotes/172.27.9.90_Nikki' You need 6.10 or better to mount nfs shares with NFSv4. Go to UD settings and set NFS version to use NFSv3 and your shares will mount.

I've made a fix for this in the next release of UD.

Right, now you'll need to format it.

Post another diagnostics.

It probably doesn't have a file system. Post a screen shot of the disk with all the details on that disk on UD.

You have multiple issues: Dec 31 09:43:02 Tower unassigned.devices: Cannot 'Auto Mount' Remote Shares. Network not available! The network was not available on startup so remote shares could not be auto mounted. Dec 31 09:45:31 Tower unassigned.devices: Error: Device '172.27.9.81:/mnt/Skywalker/Nikki' mount point '172.27.9.81_Nikki' - name is reserved, used in the array or by an unassigned device. Dec 31 09:45:31 Tower unassigned.devices: Remote SMB/NFS '172.27.9.81:/mnt/Skywalker/Nikki' cannot be mounted. You have another UD device with the same name. Dec 31 09:54:14 Tower unassigned.devices: Error: Device '172.27.9.81:/mnt/Skywalker/bkup' mount point '172.27.9.81_bkup' - name is reserved, used in the array or by an unassigned device. Dec 31 09:54:14 Tower unassigned.devices: Remote SMB/NFS '172.27.9.81:/mnt/Skywalker/bkup' cannot be mounted. Dec 31 09:54:16 Tower unassigned.devices: Error: Device '172.27.9.81:/mnt/Skywalker/bkup' mount point '172.27.9.81_bkup' - name is reserved, used in the array or by an unassigned device. Dec 31 09:54:16 Tower unassigned.devices: Remote SMB/NFS '172.27.9.81:/mnt/Skywalker/bkup' cannot be mounted. This one looks to be duplicated in UD. I'd remove all the NFS remote shares and re-enter them.

I wouldn't recommend doing that. UD adds additional things to the share configuration such as the recycle bin if that plugin is installed, and some entries to deal with case sensitive names, and Mac OS interoperability. It's also very easy to mess up samba shares when making manual entries. A cleaner approach would be to partition the disk with multiple partitions on a PC. When you put the disk back in Unraid, you then set each partition mount point for the share name you want, and you'll have multiple shares on one disk with all the extra things UD handles. Down side is each share is limited by the partition size for the shares. If you need more share control than that, use Unraid shares.

1) No. One disk - one share. 2) Yes.

Post the contents of the '/var/state/unassigned.devices/unasigned.devices.ini' file.

Debug logging won't help in this situation and it just clogs the syslog with messages.

You also need to go to the UD settings and set 'Debug Log Level' to 'None'. You are generating excessive log messages. This setting should only be used when requested for debugging.

Disk was not unmounted cleanly: Dec 29 14:11:38 Kyles-Lab mount.exfat: volume was not unmounted cleanly Dec 29 14:11:38 Kyles-Lab unassigned.devices: Mount of 'sdc1' failed: 'FUSE exfat 1.3.0 WARN: volume was not unmounted cleanly. fuse: mountpoint is not empty fuse: if you are sure this is safe, use the 'nonempty' mount option ' Take it to a PC and mount it, then unmount it cleanly.

Post your diagnostics.

Start by posting your diagnostics zip.

Yes, your devices are showing zero size. Dec 26 22:42:46 Tower emhttpd: device /dev/sdh has size zero Dec 26 22:42:46 Tower emhttpd: device /dev/sdg has size zero Dec 26 22:42:46 Tower emhttpd: device /dev/sdf has size zero Dec 26 22:42:46 Tower emhttpd: device /dev/sdi has size zero Dec 26 22:42:47 Tower emhttpd: device /dev/sdh has size zero What's the story on these devices? Can you give a screen shot?

Can someone with scsi attached disks with the dynamix.scsi.devices plugin installed give me the output of: ls /dev/ I think I see what might be happening with scsi disks not being recognized by UD.

This is a known issue in UD. The dynamix.scsi.devices plugin changes the disks from ata to scsi. UD should be handling this properly, but apparently something has broken it. I can't fix it until I can get some hardware to test scsi attached disks as I don't have scsi disks. The only fix for the moment is to remove the dynamix.scsi.devices plugin.

I plan on a release after the Holidays. I'm working on some issues I want resolved by the next release.

Thanks. I'd like to get this solved.