dlandon

Does it work if you format it with UD?

Try deleting the /flash/config/plugins/unassigned.devoces-plus/ folder and try to install again.

Post your diagnostics zip file.

Why are you wanting to preclear Nvme drives?

Be sure to set the correct volume to be mounted in the disk device settings.

Ok, well I asked for your diagnostics because I wanted to see what version of Unraid and UD you were running, not because I don't believe you. If you are running pre 6.9, UD handles the spin down and doesn't respect SMART test activity. On 6.9 and 6.10 it shouldn't be a problem because Unraid is managing spin down on UD disks.

Post your diagnostocs zip file.

The CIFS errors are very difficult to decipher because the error code seems to depend on the particular remote share server. The best I can tell is you are getting a permissions error. This can be from: Windows PC folder not being shared. Windows PC folder not being shared with the specified user credentials. Windows PC credentials don't match the UD credentials. Try not to use special characters. UD struggles with them. What you can try is to setup the share again (you don't need to delete the prevous one). Tell UD to search for servers. Enter your credentials. Tell UD to search for the shares. If the shares list, you have things set up right. If not, there is an issue with sharing/permissions. If that works, save it. It will overwrite the previous settings and it should mount. I've seen where a WIndows PC will update and folders being shared will be set not to share.

The disk log routine was changed in 6.10 so it fails because UD is still using the 6.9 disk log routine. This is fixed in the next release of UD.

This should be in the ud thread.

Turn on the "Basic View" switch to select to the "Advanced View". Then click on "Force Update". It will load a fresh Docker Image. See if that doesn't fix the issue.

Install UD+ if you need to manage partition removal and/or clearing of dsks. You can't preclear a disk if it has any partitions.

Install the Unassigned Devices (UD) plugin first. The UD Preclear is an add on to the UD plugin.

Your situation is confusing. The first remote server "MACBROOKPRO-1850" is offline because the disk ball and the "Unmount" button are grayed out. It was mounted then went offline. When UD shows this state, the remote server is not responding to a ping. Maybe, because it is disconnected from the LAN? The second remote server "PRODUCER-HELENS" is online and is ready to mount. Please post your diagnostics zip file and explain which remote share you are talking about.

Yes, it will remain intact if you preserve the share contents.

Changes can occur with new versions of Unraid because of updates in the Linux Kernel.

You are using a Realtek r8169 NIC. The Realtek NIC card driver has been a constant headache in Linux, and I'm wondering if that is causing your issues. I'm not a NIC expert, so I can't offer anything to try to see if that is the problem. I do have some suggestions on your network setup: Your servers should have static IP addresses. You should specify a gateway IP address. Probably your router. You have several FCP issues you should solve: Jun 25 13:11:02 Reveille root: Fix Common Problems Version 2022.05.30 Jun 25 13:11:02 Reveille root: Fix Common Problems: Error: Unable to communicate with GitHub.com Jun 25 13:11:03 Reveille root: Fix Common Problems: Warning: Docker application Jellyfin-AMD-Intel-Nvidia has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option I think the unable to communicate with GitHub.com is related to your UD issues.

The mount command is timing out. This is because the remote server cannot be reached. Go to a command line and ping the remote server using the IP address. If that doesn't work, you'll need to try to find the cause - network issue, bad network cable, NIC problem on one of the servers.

Be sure to set php to 7.4 in the xml template. 10.10 does not run on 7.2.

The auto update is the container applying security and other updates to Ubuntu upon startup. It is done because many users expose it to the Internet. Why do you say it keeps happening? It only happens when the container is started, and any previous updates are kept so it doesn't have to update again.

ownCloud is not updated in the Docker container. You'll need to update manually. The procedure is in the second post. Don't do an auto update, it will fail.

What version of Unraid are you using? The powerdown script was deprecated many years ago and is not recommended or necessary.

Linux does not see any partitions on the disk. How was the disk originally formatted? If you want to use it with UD, you'll need to clear it off and format it with UD.

Ok. Here's the deal. Using sec=ntlm is no longer supported because it has been removed from the Linux Kernel: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=76a3c92ec9e0668e4cd0e9ff1782eb68f61a179c I removed the sec=ntlm when mounting SMB 1.0 because it generated an error. The error you are seeing now is because the Epson printer only supports ntlm and Unraid doesn't. There's nothing I can do to get around this.

Fixed in the next release. If the Unraid settings are spin down on a timer, that will apply to UD devices as well. You cannot set spin down per UD device.