January 24, 20206 yr I have had an error flag up by Fix Common Problems "Fix Common Problems: Error: Same share (System) exists in a different case" I can see that I have a "system" folder on disk 1 that has two folders in it docker (with a docker.img file in it) and libvirt (with a libvirt.img file in it) What is this folder doing here? What can I do to sort out the problem?
January 24, 20206 yr Community Expert You need to use the Linux tools on this problem. First open up a Terminal in the GUI. (It is the >_ icon on the toolbar.) Now type the following command: ls -al /mnt/user You will get a list of all the user shares. You are looking for the ones that are named system or System or systeM or some other combination of capital and small letters that spell "system". Now, here is what the problem is. Linux assumes that all of these are different directories/folders. Windows won't even allow you to create a folder named Text if text already exists! SMB works using Windows rules but it is running on top of a Linux based file system. So there is a conundrum of what to do when there is a situation when Linux file system has two directories (or files) with with identical names except for the capitalization. Apparently what happens is that SMB passes on the first one it finds when scanning the file system. Most people find the issue when files and folders are missing or randomly appear and disappear. Now, how does the problem come up. It usually happens when a Docker or Plugin is being configured. If the user enters 'system' when he intends the file to be stored in his existing share 'System'. When the Docker (or plugin) goes to store a new file, it looks for the directory 'system'. If it does not find it, it creates it and stores the file in that directory. Edited January 24, 20206 yr by Frank1940
January 24, 20206 yr Community Expert Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post.
January 25, 20206 yr Author Diagnostics attached. I have a "system" folder on disk 1 that has two folders in it docker (with a docker.img file in it) and libvirt (with a libvirt.img file in it) but also the main "System" folder/share tower-diagnostics-20200125-1046.zip
January 25, 20206 yr Community Expert The lower case one 'system' with the contents you mentioned is the default created by Unraid if Docker and VMs are enabled! What do you have in the 'System' one as knowing its contents might give a clue as to how it got created.
February 27, 20206 yr I am getting this same error. What I have done is create a symlink from one share to another. Would there be another way to accomplish this
February 27, 20206 yr Community Expert 2 minutes ago, sgt_spike said: I am getting this same error. What I have done is create a symlink from one share to another. Would there be another way to accomplish this Go to Tools - Diagnostics and attach the complete diagnostics zip file to your NEXT post. Since the OP hasn't visited this thread for a while I guess you can have it.
February 27, 20206 yr Diagnostics attached. I just noticed this error today. I created the symlink to gain access to one share from another. tower-diagnostics-20200227-1119.zip
February 27, 20206 yr Community Expert Feb 26 04:40:01 Tower root: Fix Common Problems: Error: Same share (html) exists in a different case Feb 26 04:40:01 Tower root: Fix Common Problems: Error: Same share (HTML) exists in a different case The lower case version doesn't appear in the diagnostics, but that may just be an artifact of the symlink. The correct fix for this would be to only have one of these folders with all of their contents combined, and to figure out what you did to create the other one. Accidentally creating another user share with different case is a common result of using incorrect case in a docker mapping.
February 27, 20206 yr 1 hour ago, trurl said: Feb 26 04:40:01 Tower root: Fix Common Problems: Error: Same share (html) exists in a different case Feb 26 04:40:01 Tower root: Fix Common Problems: Error: Same share (HTML) exists in a different case The lower case version doesn't appear in the diagnostics, but that may just be an artifact of the symlink. The correct fix for this would be to only have one of these folders with all of their contents combined, and to figure out what you did to create the other one. Accidentally creating another user share with different case is a common result of using incorrect case in a docker mapping. No worries....I just deleted the symlink. I thought I was using it but I guess I went another direction to solve my problem. No more errors! Edited February 27, 20206 yr by sgt_spike
Archived
This topic is now archived and is closed to further replies.