dlandon

What we are talking about is a pool in ud, which would not be a part of the array. It would just be another ud device, but pooled.

The only issue that has come up is in the duplicate share names check recently added to UD that won't mount devices with duplicate names. There is a setting that can be turned off so UD won't check for duplicate UD names. Can someone post a link on how to do this using the cli? I'm considering adding the ability to create pools to UD.

Your disk is 5 years old. Neither of those errors are necessarily a sign of a bad disk. I wouldn't do anything but keep an eye on it. You'll get notifications when disk errors occur and can take appropriate action then.

Post a UD screen shot and your diagnostics.

You have a mapping problem. Notice the size of the disk is 1MB. That's not your disk. It looks like you mapped /mnt/disks/. Post a screen shot of your mappings.

Looks to be a bug in UD. I'll issue an update tomorrow to fix it.

UD thinks the disk is an array disk that has disconnected and reconnected with a different device designation. What is the history of this device? Always been a UD device? Post your diagnostics.

The devX designation is assigned by Unraid to the UD device similar to naming a pool device. You can't mount it directly.

This is a common problem with NFS. Your best bet is to upgrade to Unraid 6.10rc2, set to mount NFSv4 in UD settings and then mount your remote shares.

I'm not clear on what you are trying to do. When a disk is physically passed through to a VM, you don't want UD to mount it so you mark it as passed through so UD won't touch the disk. The VM will then mount the physical disk and use it. If you are trying to have UD mount the disk and have the VM use it, you would have UD auto mount it and share it with samba. Then use /mnt/disks/mountpoint to access it, or access it at //tower/mountpoint depending on the VMs use case. You don't want UD and your VM mounting the physical disk at the same time. You will corrupt the file system.

A check was recently added to UD to detect this situation. The issue is the drive has a 'sdo' designation and not a 'Dev X' designation under 'Device'. Unraid is not detecting the drive as unassigned. When UD sees this situation, it marks the disk as 'Array' assuming that the disk was an array disk and has been dropped from the array and then assigned a new sdX designation. It would be unwise to have UD do anything with the disk if it truly was an array disk. Obviously, the disk is a portable disk and I doubt you'd have that in the array. Try this: - Remove the preclear plugin. It receives udev events and might be interfering. - Click on the double arrow icon on the UD page. This will cause udev to rescan the disks and will initiate an Unraid hot plug event. I also see some disk errors: Dec 10 11:14:58 unRyzend ntfs-3g[11194]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Dec 10 11:14:58 unRyzend ntfs-3g[11194]: Failed to read vcn 0x4: Input/output error Dec 10 11:14:58 unRyzend ntfs-3g[11194]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Dec 10 11:14:58 unRyzend ntfs-3g[11194]: Failed to read vcn 0x4: Input/output error Dec 10 11:14:58 unRyzend ntfs-3g[11194]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Dec 10 11:14:58 unRyzend ntfs-3g[11194]: Failed to read vcn 0x4: Input/output error Dec 10 11:14:58 unRyzend ntfs-3g[11194]: ntfs_attr_pread_i: ntfs_pread failed: Input/output error Dec 10 11:14:58 unRyzend ntfs-3g[11194]: Failed to read vcn 0x4: Input/output error Dec 10 11:14:58 unRyzend kernel: Buffer I/O error on dev sdb1, logical block 109934, async page read The interesting thing is that the errors are on sdb. Because they are ntfs errors, I assume it's your USB disk. If that's the case your USB disk has two device designations - sdb and sdo? When I look at your smart reports, I don't see a sdb disk. Did you have the USB drive plugged in when you rebooted last? Because of the sdb device, I suspect yes. Is there a chance you rebooted your server and the USB disk auto mounted, then you removed it without unmounting and then reconnected it? If you are still having issues, unmount the USB disk and reboot. Then re-install it and see if Unraid assigns a 'Dev X' designation. If none of that works, move this discussion to the unassigned devices forum and we'll go through some debugging steps.

Why do you say the change UUID didn't work? Look in the log and it will tell you if it was successful.

This shouldn't show up unless Unraid doesn't see the disk as unassigned which means it's assigned to the array or pool. It should not be happening to you. Give me a screen shot of the array disks and UD disks.

This implies that you have a UD device mount point (share name) the same as one in Unraid. This is not a good idea and will potentially cause a conflict if you share the UD device. You need to change the mount point on the UD device.

For those of you with pools in UD, go to the UD Settings and set "Check Unassigned Devices Share Names?" to 'No'. UD will not check for duplicate UD share names.

Update to the latest UD release 2021.12.09 and see if the issues is solved. If not, post diagnostics and share_names.json once more.

Is there a way for UD to detect that disks are in a pool?

Pool disks would have the same mount point?

What use case do you have where you need UD devices mounted with the array stopped?

Post the contents of the file /var/state/unassigned.devices/share_names.json.

Please post diagnostics.

I don't understand how the pool thing works. I know there is a scheme to trick UD into doing this. Can you give e a link to how pool the disks? Both devices in the pool have the same mount point? What mount point are you changing? Why can't you change the mount point with the GUI?

Please do the following: Update to the latest UD (2021.12.08). Try to mount the device again. Post diagnostics and the contents of the file /var/state/unassigned.devices/share_names.json. I've added some information to the log message about the duplicate share name to help find this issue.

For those of you with a loss of GUI on 6.9, update to the latest release - 2021.12.08.