dlandon

Some CSS changes in UD may have caused this. I would suggest: Try another browser. Clear your browser cache. Upgrade to 6.12. And see if it clears up.

We have identified and corrected the issue with NFS Daemon not stopping properly. This fix will be in the 7.0 rc2 release and will be backported to 6.12. Please retest with this release and see if the issue is corrected. This is interesting. I will look into this further.

Follow this procedure: Update UD and UD Preclear. Reboot. This insures there are no mounts that show in 'df'. Remove partitions from the disks to be precleared. Preclear the disks.

I see an issue with a disk that has a partition but no file system. I'll work on sorting that out.

This is extremely confusing for the following reasons: Preclear should never allow preclearing a disk with a partition. In your case, none of the partitions have a file system. This may be a bug in preclear. I will investigate. Preclear should never try to preclear a disk that is mounted. How did these disks get mounted? Dev 2 is showing disks /dev/sdk twice with one preclearing and the other with the 'Mount' button grayed out. I don't know how this could happen.

It looks like those disks are mounted with UD. That's why you can't preclear them. Please show a screen shot of the UD page showing those two disks. If you use the preclear page to start a preclear, show a screen shot of that page. You shouldn't be able to start a preclear on mounted disks.

If that is disk /dev/sdj, it appears to have cleared.

Don't preclear an SSD, it's not necessary or recommended.

Post the complete preclear log. It's on the preclear page. Hover over the icons in the upper right of the page to find it.

You have no array disks assigned and because of a potential bug, preclear thinks the disk is part of the array. I'm looking at making a fix for this situation.

The check icon is whan a filesystem check can be performed . The "1" indocates partition 1. The log icon will be active when a log is available to view. The pencil indicates you can click on the mountpoint text to change the mountpoint.

Provide more information. Post the Unraid logs and the log from preclear.

Update just posted. The 'retrans=' parameter is not available in 6.12 and earlier versions of Unraid because Samba does not support it.

An update is coming in the next hour to fix this.

It's an issue in the newest UD release. I'll have an update to fix this soon.

Today's release of UD: Allows for the use of special characrers in passwords. You shouldn't have to make any changes to update your passwords. The UD update is backwards compatible to existing passwords. If a password does appear to be failing after the update, re-enter the password. i.e. Add a Remote Share back with the password re-entered. There are differences now in how passwords are stored with special characters. The 'Cancel' button on some dialogs was not the rightmost button. The Unraid standard is for the rightmost button to be 'Cancel'. Adjust some NFS and CIFS mount options for robustness to better deal with network and remote server issues. No functionality should be affected.

The first line is at the drive level, the second line is at the partition level. If the drive had several partitions, you'd see partition size, used, and free for the partitions and the drive line would show all partitions size, used, and free. Also things like temperature apply to the disk, and not the partition.

Yes, the refresh icon. Is it not two arrows pointing to each other is a circle? Show screen shot of what you are seeing. I don't understand what you are asking.

Sometimes nvme drives have this problem after formatting. Click on the double arrow icon on the upper right of the UD page and force udev to refresh the disk information. It should then enable the mount button.

Yes. I'll leave it for now, but it won't be updated.

The next release of UD will have an update to the password handling so special characters will work.

I'm working on a change to the UD password handling so special characters can be used.

This is what is causing your issues: Dec 12 18:08:35 BusyBee kernel: NFS: server NEO.LOCAL error: fileid changed Dec 12 18:08:35 BusyBee kernel: fsid 0:105: expected fileid 0x90200023f1474bb, got 0xad000000017aa6 Dec 12 18:08:35 BusyBee kernel: NFS: server NEO.LOCAL error: fileid changed Dec 12 18:08:35 BusyBee kernel: fsid 0:105: expected fileid 0x90100000e3d07e3, got 0xad000000017aa4 Dec 12 18:08:35 BusyBee kernel: NFS: server NEO.LOCAL error: fileid changed Dec 12 18:08:35 BusyBee kernel: fsid 0:105: expected fileid 0x90100038ba83239, got 0xad000000017aa2 Try by fixing these problems: Dec 12 18:10:04 BusyBee root: Fix Common Problems: Warning: Docker application binhex-readarr has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option Dec 12 18:10:04 BusyBee root: Fix Common Problems: Warning: Docker application Radarr has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option Dec 12 18:10:04 BusyBee root: Fix Common Problems: Warning: Docker application Sonarr has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option Dec 12 18:10:04 BusyBee root: Fix Common Problems: Warning: Docker application tdarr has volumes being passed that are mounted by Unassigned Devices, but they are not mounted with the slave option

The log messages strongly indicate a credential issue: STATUS_LOGON_FAILURE (0xc000006d): This status code explicitly states that the login attempt failed due to invalid credentials (username or password). cifs_mount failed w/return code = -13: The error code -13 corresponds to EACCES (Permission Denied), which is often seen when the provided credentials do not have sufficient rights or are incorrect. Check your credentials. Don't use special characters in the user name or password.

Post Unraid diagnostics and go to a command line and enter 'ud_diagnostics' then post the /flash/logs/ud_diagnostics.zip file.