dlandon

It's a quirk with nvme drives that I have yet to figure out. You should not have to do that to get them to work.

Show a screen shot of the issue. Type ctrl-shift-j to bring up the Java Script console and see if there are any errors. Try another Browser.

Click on the double arrows icon (arrows in a circle) to get udev to refresh the drives and you should then be able to mount the drives.

Yes.

This is a brief guide on some best practices to set up NFS on Unraid. There are some special considerations on Unraid because of the mover operation. If NFS is not configured correctly, you can end up with stale file handles. This isn't a bug in Unraid, it's the way Unraid operates. When you need to connect to a remote share, the best way is to use the Unassigned Devices (UD) plugin to mount and manage the remote shares. UD is optimized to deal with NFS mounts in a robust fashion. It is not recommended to mount remote shares with fstab entries on Unraid. The following are some recommendations when setting up NFS: Set up your Unraid shares for Private access and limit access by entering rules. In Unraid, set the rules to: *(async,no_subtree_check,rw,sec=sys,insecure,anongid=100,anonuid=99,no_root_squash) you may want to adjust a little for your situation - like a specific IP address/range, or root_squash. On the client side use these mount parameters: hard,timeo=50,retrans=5,relatime,rsize=1048576,wsize=1048576. When accessing Unraid shares with NFS on 7.0.0, there are some adjustments you can make on Unraid to overcome some NFS issues: Unraid uses shfs that is the file aggregation driver on Array disks. There is an open file limit that might need adjustment if you have a large amount of NFS activity. This can be adjusted in Settings->Global Share Settings. Increase the "Number of fuse File Descriptors" if you have trouble with NFS starting and/or shfs crashes and shares are no longer available. The other setting is the number of threads available to NFS. If you have a lot of NFS file activity, increasing the number of threads for NFS can help with NFS operation. Go to Settings->NFS and increase the number of threads from the default of 8. It is rcommended that you use the Unassigned Devices Plugin (UD) to manage remote NFS shares. If you use fstab, you have to be sure to set up the mount parameters correctly to maintain a robust connection. UD is optimized to manage the remote connection for robustness, and when the Unraid array is started and stopped.

If you click on the setting text, you'll see the help text. This is true for all of the Unraid settings pages. You can also click the 'Help' icon in the upper right and it will display all the help text.

Update File Activity.

Post diagnostics.

Thank you, it was a hunch I had about the vfs objects. Now to find a solution that doesn't break SMB on Macs.

Can you turn off Macos Interoperability and see if it makes a difference? I'm wanting to be sure the Mac vfs objects aren't interferring with the Recycle Bin.

I see that you have Macos interoperability enabled. Are you deleting files on a Mac?

Any suggestions on how I can reproduce your issue? Post diagnostics so I can look at testparm output.

Verify the Recycle Bin is running. Shares only show in the Recycle Bin when files are deleted on that share. Also keep in mind that the Share Recycle Bin status is updated every 5 minutes. You'll see the deleted files in the log immediately, but the Shares won't show the deleted file for up to 5 minutes.

That generally happens when there is an error on the page. Do this: Hit ctrl-shift-j and see if there are Java Script errors. If so, post a screen shot. Go to Tools->PHP Settings and view the PHP log and see if there are PHP Errors/Warnings. Show any errors/warnings in the log.

No, it shouldn't. It defaults to 40960. Blank the line (remove the (null)), then enter a value at least double the default value.

This is known and will be fixed in the next update of 7.0.

There are new settings in Unraid 7.0 that may help this: Go to Settings->Global Share Settings and increase the "Number of fuse File Descriptors:". I would start by doubling the default. Go to Settings->NFS and increase the "Number of Threads:" from the default of 8. These two things will probably help.

Fixed in next release.

It's working for me. When you are testing, be sure to create a file that is not zero length. Any file that is zero length will be ignored and not put in the Recycle Bin. Post diagnostics.

All you have to do is select 'Array' and save the changes. In an earlier version of Unraid, the 'Cache' pool was presumed to be there, but in 7.0.0, a verification was added to check the Secondary Pool. This situation was ignored is earlier versions of Unraid but now generates an error.

This is a bit off the wall, but when this happens, go to the UD Settings page and click on the "Remote Servers" tab and enter a Windows client name or IP address and click "Test". UD does several tests that might show what the problem might be. If the IP address works and not the name, there is a name lookup issue. Also try the Unraid server you are on (yes, you are testing yourself) and see if anything shows out of that. I appreciate your frustration and the assumption it is Unraid because it happens on an Unraid update, but keep in mind we are subject to the following things that change that we have no control over: Linux Kernel changes. Samba changes and security updates. Windows security updates. Nothing like this showed up in either internal, beta, or rc testing. If we can reproduce the issue, we can work on a resolution. If we cannot make it happen, it's pretty much a trial and error approach so we can find what affects it. Do we like to do it this way? No, but it's the best we can do until we can reproduce it or seek out a proper resolution. If you don't have the patience for this approach, feel free to do what you have done - downgrade and wait it out.

If you have "NetBIOS" enabled, disable it. It is not necessary anymore for Windows clients and may be causing issues.

Post diagnostics.

A fix is in the next release.