• Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by Frank1940

  1. Let me be by saying that I am not a Linux Guru. I often say I know enough to make me really dangerous. I did a bit of googling before I wrote this to verify some of my presumptions. But let's start from this premise that @limetech intends that all of the files on the array should have the following permissions: -rw-rw-rw- 1 root root 0 Sep 29 09:07 test.txt (I created this file from the command line using the touch command so the owner and group are 'root'.) and directories should have the following permissions: drwxrwxrwx 9 nobody users 4096 Jul 9 2020 appdata/ A umask of 002 would remove the write permission from the 'others' category for both new directories and files. Similarly, a umask of 022 would remove write permissions for 'group' and 'others' category for all new files and directories. I will now make another assumption that this umask setting is for files/directories that are to be written to the Unraid array. I will make a further assumption that LimeTech really wants all files written to the array to have the 666 permissions for file and 777 permissions for directories. Using this line of reasoning, the umask for files to be written to the Unraid array by a Docker Container should be 000.
  2. Looks like an interesting approach to the problem, I know that on my Private shares that the 'owner' ends up being the Unraid share access user rather than 'nobody'. While I have not encountered any problems to date, I can see where it might in the future. (The 'group' is still 'users' which is good.) The only issue I see with this approach is that it only addresses those files which are generated through SMB. Files/Directories being added to the server via Linux Dockers are also a problem. Many of them have to make provision similiar owner/user/permission settings but apparently not all Dockers are strictly developed to be used in the Unraid environment but in a larger Unix environment and their default values are not always compatible with Unraid. I hope some other folks ( @limetech, @dlandon, @Geoff Bland, @bonienl, @JorgeB ) will jump in and add their two cents in a discussion about your suggestions.
  3. EDIT: Changed to a quote as I copied and pasted it from another web page. Not sure about the chmod command. One should consult the man page for more details on this command.
  4. Looking at what you have posted up is confusing at this point. I am going to post what should be the permissions for directories for SMB to work correctly. Notice that all of the directories from /mnt/user down the tree have to have 777 permissions. (The last listing a actually a file. this is indicated by the fact that the first character is a '-'. For a directory, it will be a 'd'.) You can run the Docker Safe New Permission tool to fix this. You can also use the New Permissions tool but you have to exclude the 'appdata' and 'CommunityApplicationsAppdataBackup' shares as these shares often have different owners, groups and permissions assigned to them! Neither of these tools will fix the directories in /mnt/user so this has to be done manually.
  5. Have you tried the support thread for the Plex app?
  6. This problem is going to be difficult to handle in this thread. I have one more suggestion: Try setting the shares to 'Public' and see if that works. I suspect that your devices are being logged onto the server with guest account privileges. IF that does not solve the problem, create a thread in the General Support section of the forum.
  7. Not a problem on the server that is (believed to be) the Local Master. However, it was on the Testbed server. In fact, nmbd never run the Media server while there periods where it run every few seconds on the Testbed server. Not sure what is going on...
  8. @bonienl, I am using the Dynamix Local Master plugin and the name of the Local Master no longer appears as shown below: This server is (/should be) the Local Master. I could show the same condition on my second server but that would be redundant as that page would be the same. I believe this problem start about the time that I removed the last visages of SMBv1 support from my SMB configuration. I will point out that ScottiesTech LANscaner v2.02 utility also fails to identify the current Local Master. I also observed that the last update to this plugin was on June 20, 2020. I am wondering if this plugin is still being supported and might receive an update anytime soon.
  9. Open up the Credential Manager and delete all of the Windows Credentials associated with your server. Then download the PDF file in the first post of this thread: Set up a login to your Unraid server for the user that you created on the user using the instructions in the section called "Setting Up the Unraid Server and the Windows 10 Client".
  10. Another option to to have a look at flat cat5/6 cable. This stuff is much easier to temporarily run through living spaces as its flat profile means it can run under carpet without creating a massive bulge.
  11. Welcome to the wonderful world of Samba! Seven plus years back this was often the case. (In those days, I often said that fixing Samba issues was more witchcraft than science.) One thing to check is to see if your Windows server and PC's received an update in the past twenty-four hours.
  12. With all discussion of SMB, it might be useful to provide one tool to have a look at what parameters are actually being used by the Unraid SMB server. You can find these listed by typing the following command: testparm The following is a screen capture of the result of the gobal section: Following this section are the results of all of your shares.
  13. Should not be an issue as Window 7 support SMB 2.1 as shown here: And this:
  14. Might you be confusing this parameter to "server max protocol" I believe the current default for "server min protocol" is "SMB2_02".
  15. @craigr, you might want to consider using NFS but I am not sure if devices that old have a version of NFS that still works today (due to security issues) but it would be worth a try. I can feel your pain. I had three Netgear NTV-550 media players (only support SMBv1) that I retired earlier this year. (The removal of SMBv1 was an forgone given...) I went with mini/micro PC's running KODI. The prices for these boxes that will work start at about $150US. I added to that a mini wireless keyboard (~$22US) to use as a remote.
  16. Another way is to open the flash drive in Windows Explorer and go to the /config/plugins/NerdPack folder/directory. Now open the NerdPack.cfg file with a text editor (Notepad will work) and search/find "yes" for the packages that you have selected to be installed.
  17. As a note to other folks who encounter this problem of permissions being wrong inside of a share. Either the 'New Permissions" or "Docker Safe New Perms: tool should fix this problem as it does basically the same thing as @tTownTom's chmod command. (IF you use the 'New Permissions" be sure to select only the share affected as that will shorten the time require to the process to finish.)
  18. On what directory/directories? Could you provide us with the exact command that you use? (I am suspecting that we will be seeing a lot more of these types of issues...)
  19. Try rebooting the Windows Client as that worked for me.
  20. The permissions on this screen are what we would expect them to be. So the problem is not there. In Unraid 6.9.2, the samba version is 4.12.14 In Unraid 6.11.0, the samba version is 4.17.0 I leave it to you to figure out what has changed. (I am a volunteer and I don't intend to devout that much time to such a task...) You will have to start here: Don't really recommend that course of action... You should be starting by googling using such terms as--- Android, smb, problems ---and see what you find. As a complete aside, why is it necessary for you do file management on your Smartphone? Why don't you try 'cutting' the file and 'move' it to 'Trash'? How old is that Smartphone and what version of Android is it running? Is your carrier even updating it still? I would be investigate these types of questions as the problem appears to be on the Android side of the equation.
  21. You can run either of the scripts and see if it will fix the problem. Prior to this recent outbreak of access issues, that was the first step. And it worked often far more often than not! (To be be fair, it was not always the solution to the what was causing the problem but it fixed the damage caused by the problem temporarily. Then an investigation would have to pursued to find and correct the application that was generating files with the wrong permissions/owner/group and fix that issue.) Understand that this is the first instance of the problem with an Android device that we have heard of. So what the problem is, nobody knows at this point. (In fact, you have not even told us what version of Android your device is using.) No one knows where we should be focusing. You were asked about the information on the /mnt/user/ mount point because we have found that it was the permissions at the point were wrong on the server and when corrected, that fixed the problem for Windows 10/11 computer access. Obviously, the proper permissions should be verified and set up on the server before we start looking elsewhere for a solution!
  22. I had a similiar problem, rebooted the client computer (Windows 10) and I got immediate access to the server.
  23. Was this the problem? IF not post up the diagnostics.
  24. It is still in the current releases (haven't check version 6.11.0 yet). You can find it Tools >>> New Permissions (It was revised when a problem was found that it would reset things in the appdata share and to add some additional functionality to it You can read about this if you just open up the tool. Note that it only works on Disks and Shares. You can verify this by looking at the options of what can be selected to to worked on. Specifically, it does NOT list that it will modify the /user/ 'device'!) Docker Safe New Permissions was developed for use in the interval when the New Permissions script was causing problems. Both scripts do basically the same thing. The problem with Windows access was caused by the wrong permissions on the /user/ device! At this point, we don't know what the cause of the problem is Android Devices. Hopefully, it is a permission error! I don't where either of permission fixing scripts are located in the Unraid file system. I am sure that they are scripts because no good Unix/Linux programmer would use anything like a C++ program when a Shell script will do the job! (Unix was build on the concept that the shell language would be the backbone for most system utilities!) If you want to see what a shell script looks like, download the first Preclear script from the first post in this thread: JoeL. Preclear Script Don't try and run this script as there are some commands in it that are not in the current versions of Linux.
  25. One more thing, I believe the permissions are wrong in version 6.9.X but for some reason, it works. (Samba was upgraded between the two versions and there were a lot of CVEs that were addressed in the updated samba version used in the ver 6.10.X. One of those security updates could be the reason for the problem as the permissions are definitely wrong on 6.9.X!) Why do I say that? The vast majority of people make the upgrade from 6.9.X to 6.10.X without any problems. Only a few people have the problem. When they revert back to 6.9.X, the problem is gone. If they upgrade again, the problem comes back. So it appears that the permission error in 6.10.X is an inherited set of permissions from the 6.9.X installation. To date, no one has identified what is changing these permissions but it reasonable to suspect that some Docker container or Plugin is the culprit.