dlandon

Start by posting your diagnostics.

On the UI, click on the 'Boot' device label and then the "Syslinux Configuration" tab. Romove any instances of this text "root=sda" you see, save it, and then reboot. You should be able to preclear without memory issues.

Start with a fresh diagnostics.

Post diagnostics.

You shouldn't get duplicates because Unraid doesn't allow that. The issue was with file listings, not with files not getting written or getting corrupted. File handling was not an issue. Do a transfer and only copy missing files to save time if you can. Be sure to upgrade to 6.12.10-rc.1 first. It does not have the problem.

The best we can tell is that this problem manifests itself in files and folders not showing up in a remote mount in any listings on the mount. Depending on the application accessing the mount and the actions taken by the applicaton when files and folders don't show, the results can be very weird. For example, you transfer a file to a remote share and the application doesn't find the file causiung the application to act on a file not found. The files and folders seem to physically be there, but don't show in listings on the share. At this point, we can't say for sure whether or not your files and folders are actually there short of upgrading to 6.12.10-rc.1 and looking through directories, or initiating your file transfers again just to be sure.

It's not a design issue; it's a technical limitation. The Root Share is mounted as bind mount and exclusive shares are not available because the bind mount does not allow symlinks.

Please update to 6.12.10-rc.1. It should fix this issue. It's available on "Next".

This issue is in 6.12.9, but there was a change made that will be in 6.12.8 to enable client negotiation of 4.X. Boot in 6.12.8 and see if this helps your situation.

I think you are running into an issue with 6.12.9 where a changed setting in nfsmounts is causing problems. It is to be solved in 6.12.10 due out soon.

Who is the client? From the client that I assumed was Unraid.

We need more information to be able to help. Post diagnostics.

When i click on it, it sits on the Unraid wave and appears to be hung.

Go to Settings->CA Settings and it will turn itself off.

Artificial Intelligence. If you aren't using it, do. It will do wonders for your coding. You can get a free ChatGPT account.

Just as a clarificaton. When AI is asked about which approach is better, the response is: "It depends on the size of the file /var/log/file.activity.log and the frequency of the script execution. If the file is relatively small and the script is not executed frequently, directly grepping the file would likely be more efficient and result in lower disk I/O. This is because reading the file directly with grep avoids the overhead of piping the output of cat into grep. However, if the file is large or the script is executed frequently, it may be more efficient to use a combination of cat and grep as you have done, especially if you're only interested in specific lines matching a pattern. This can help avoid repeatedly scanning the entire file with grep, potentially reducing overall disk I/O." The line of code in question is executed for every disk device and the log can get large (it is limited to 20,000 lines though), so based on the AI response, it appears the " useless use of cat" may not be useless after all. Maybe before criticizing the code, you need to understand it better?

Fixed.

There's a problem. GIve me a minute to fix.

Update released.

I have a fix for this. I just haven't released it yet. Different styles. If you think you can do a better job, you are free to fork this project and do it yourself.

Yes. Fix: Apply a patch to revert an NFS setting causing "protocol not supported" issue.

I found an issue with NFS that is resolved with the latest release of UD that I believe will solve the NFS mounting issue.

NFS does not use credentials. It uses Linux permissions. There is an issue with UD and 6.12.9 Unraid. Update UD and see if you can get your NFS shares to mount.

it's a known problem and an Unraid update will be available soon to fix this.

Either one, but the "Auto" settng is best so UD will negotiate the server version.