Frank1940

Try rebooting the Windows Client as that worked for me.

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: https://www.samba.org/samba/history/ 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.

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!

I had a similiar problem, rebooted the client computer (Windows 10) and I got immediate access to the server.

Was this the problem? IF not post up the diagnostics.

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.

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.

I really don't think so based on the experience of the other users. As I recall from the discussions at the time, the script was written to run on the physical disks. (In fact, it was intended to be run only once when the server was upgraded from version 5.X to version 6.X as-- I believe ---, root was the owner and possibly even the group name in version 4 and version 5.)

I wanted to see the permissions on the shares and the directory--- /user/ ---as these have been involved in several cases of access difficulties in the past couple of weeks. The symptoms were always that the an upgrade from 6.9.x to 6.10.x would result the loss of access and a rollback would 'fix' things...

Please post up the results of the following command: ls -al /mnt/user

Open the GUI terminal Window (the >_ icon on the right of the toolbar). Type type the following command ping 8.8.8.8 A Control-C will stop it. If that works, try this command: ping cnn.com IF these two both work, you have full Internet access from your server. Try the install again. (It is not summons that these servers will be down.)

If you look at the screen shot for my hexbin-krusader Docker, you will find a support link in the dropdown menu. I don't see one in yours. If you installed it from the APPS tab, there should be a support link in the listing for the version you are using. Ask there about where the Krusader GUI is. If you don't find the answer, you could consider switching to the Docker that I am using...

I am going to post up a screenshot of the Krusader Docker to show how to launch its GUI. You left-click on the icon to open this menu. Hope this helps!

I don't understand what the use case was in the first place. It appeared that the question was regarding hard disks (most likely found on the Array) and ssd's (most likely in a cache situation). user0 will only show those files on the array which is probably all of the hard disks in most systems. As far as the ssd's go, a disk mount setup of the cache (or cache pool) is possible for them. The OP will have to get his head around how to integrate all these storage points into one cohesive storage system. As I said, I admit that I don't have a clue as to why the OP is wanting this separation...

Look at the directory /mnt and you will see a user and a user0 directory. user0 has only the files/directories that are on the actual parity-protected array. (user0 was scheduled to be deprecated but there are a few people who found it useful...) user has all of the files on the array plus those that are on the cache. It is the one that is normally used. Just be sure you understand what is going on if you are going to use user0.