Frank1940

It is an option in the actual plugin:

Interest find! If, on the Edit page/tab, you switch from Basic View to Advance View, you get these additional settings. I did test and, with these settings I can get directories with 777 permissions and files with 666 permissions. (I checked to add the write permission of 'Others' for both File and Directory.) Looks like a simple solution. But I still think that the out-of-box permissions should be 777 and 666. Then if the user requires something different, they can make the changes required using these Advanced View Settings. Demo of results: @zapbranagann, Looking really good from my perspective!!!

A few years ago, this was how Unraid behaved. It used nobody as the owner of everything on the array. Then something changed (at least in Samba) and, if you were logged in as a Share Access user with valid Share Access credentials, any file you created, you ended up as owner. From my previous research into how Unraid SMB works, I found out that all Share Access users are automatically members of the users Group. Thus they always have access via the Group using group permissions regardless of who the owner is. What I can''t remember at this point (I getting older and my memory is not as good as It once was) is if nobody is also a member of the users group. (IF I remember correctly, a Share Access login with a bad user name is automatically logged is using the guest account and I think is assigned as nobody.) As a matter of information, you might want to google nobody Linux and read how this user name came about. it was an semi-hack to fix/solve a problem many years ago. The New Permissions Tool has to change the owner to some user (assuming that the owner name is a problem to be addressed) and nobody is a convenient, harmless one that is ready to use.

Mental Neutral on my part. As soon as I realized I had to enter the URL, everything make sense! OK--- I just made a couple of quick tests and I observed this: The standard Unraid permissions for directories are 777 and for files are 666. I did not do a lot of testing but it is possible that there may be some issues when people are accessing using 'Public' permissions. Unraid security setup and permissions are a bit funky and I would strongly suggest that you conform to their standard. (I can not remember for sure if 'nobody' is a member of the 'users' group. Next item— Look at these two directories: The directory names should indicate how they were created. Notice the one created by your plugin has 'nobody' as the owner whereas the one created using a standard Unraid Share has my SMB login name– user –as the owner. Notice that it also has the stand Unraid permissions. The owner of 'nobody' is not a real issue in this case but it can mask some access issues with the 'other' permissions. (I rue the day when I decided on using 'user' as my SMB login. It is not a problem in day-to-day usage but complicates things when I composing a reply on the forum! 🫤)

This type of 'adding' a drive will trigger a preclear clear operation. If I remember correctly, the proeclear clear operation will happen and then you will format the drive as XFS. (Formatting only sets up the File structure, it does not 'clear' the reminder of the drive by writing zeros to all of the unused bytes. That's why formatting takes about one minute while clearing takes about two hours per TB.) Here: EDIT: And check this first before committing to the format:

By the way, this link (in both Firefox and Chrome) takes to a listing of the code and does not trigger the download for the actual .plg file. If you want wider participation, change the link to provide the actual install file needed.

Just make sure that 'Life' will allow you some extra time to deal with any issues or bugs that a wider release might reveal...

Because for hard drives, the attributes are virtually standard for all manufacturers and models. Over the years, it has been found that those few attributes are the ones which indicate drives that are more likely to fail. They might not be failing now but one should keep a closer eye on them. From what I see, I would say that drive is fine to reuse. I would not bother preclearing it. Depending on how you insert the drive, Unraid might have to preclear it but it will not take any longer that way then if you do it prior. (If your drive had had some non zero critical attributes, I– personally –would have precleared it to verify that it was stable and not likely to be a problem in the near future.)

Any idea when this might occur? (Many of us are reluctant to install plugins that are not in the App Store...)

@Zass, we need those diagnostics when the problem is present...

You have to find the process that is causing the problem. You can disable the Docker and see if you can stop the array then. You can manually stop any VM's and check again. If neither of those tests don't allow stopping, then you can try booting in the 'SAFE' mode which disables all plugins. Finding the problem process is a tedious procedure of elimination.

Now for what to you may be the big reveal. If the array does not stop, you can never have a clean shutdown. When that 'Shudown down timer' expires, Unraid will then force-ably shut the system down resulting in an unclean shutdown and require a parity rebuilt on startup.

I think you may misunderstand the purpose of that setting. If the array is not stopped by that point, UnraID WILL FORCE a shutdown and that will result in an unclean shutdown. You should time the time required to stop the array from the button on the MAIN tab to determine how long it takes to stop your array. If it never stops, you can never do a clean shutdown and you have to find what it preventing stopping the array.

There is this setting: You should manually check to see that you can shutdown the array. If you can't, you may have a Docker container or VM that will not release a disk.

You have to use a valid login to the remote server. (i.e., the same user name and password that you normally used when you logged into that server for the share that you are mounting.)

One thing that I see is the you have not clicked on the 'MOUNT' button. Do that and see if the other server mounts on your Unraid server. When that happens, you should see something like this: Left-click where I have circled. IT should show something like this: This is the built-in File Manager for Unraid. We are interested in seeing the owner and permissions on the directories and files. (You are seeing a Share from my first Unraid server which is mounted on my second Unraid server.)

Try pinging the server. To do this, type 'command prompt' in the search window on the Windows Task Bar. Typical below: Of course, use your own server_name and/or IP_Address

One thing to try. Connect up a monitor and keyboard to the server and get the Diagnostics file saved. Upload that file in a new post in this thread/topic. Another thing to try is to try to shut the server down and restart it. You can try for a clean shutdown by a quick push of the power button. (A long push-- > 5 sec --will force an unclean shutdown that will force a parity check on restart. So you might want to wait to do that...)

Yes. Before you do anything to upgrade your system, get the smart report on this drive. Look at the parameters that Unraid uses to evaluate drives. To see this list. MAIN >>>> Array Devices >>> Parity >>> Parity Settings and look for this: Attribute = 199 is not really important and it indicates a cable failure, not a disk problem, 99.99% of the time. Any value other than zero for the others, you should investigate further. First step would be a run a preclear cycle on it and see what the results are. (Any additional failure, I would be cautious about using the drive.) Otherwise, I would not run a preclear cycle on it.

Sorry, I am not a Linux Client Samba expert. You will have to either wait for someone else to read this thread or open a new thread and ask for instructions on how to 'auto- mount' SMB shares. Have you inquired on the support site or documentation for the Linux distribution that you are using? (I can't believe that you are the only one who wants to be able to to this...) A new thread might be a better option than waiting for a reply in a thread that basically is about NFS problems.

You might actually find it easier to install Samba and set up SMB on your Linux client.

Try umask=000 The permissions need to be drwxrwxrwx and -rw-rw-rw- for things to work right as Unraid is setup. I believe that the recommended permissions for security purposes by the Linux security Gurus is now 755 and 644. These recommendations have made their way into many Linux distributions recently.

There are a number of strange things going on in your Syslog. I wish that someone with a good knowledge of reading syslogs would have a good look at it...

I got that from this syslog entry: Jan 8 16:36:11 TerraFirma kernel: r8169 0000:02:00.0 eth0: jumbo features [frames: 9194 bytes, tx checksumming: ko]

You seem to have Jumbo frames enabled. This has given problems in the past. Suggest returning to the default. (MTU = 1500)