January 4, 20215 yr I have a folder in my share which is not visible through Windows Explorer. However, I am able to access it by name. Share where the folder is, opened in Windows Explorer. Folder "kovalevylta-1" is missing. It never has, I just copied the data to the share recently. The folder is accessed by typing the name in address bar: Also, the files are visible from Unraid's terminal. Hidden items are also made visible in Windows Explorer. What might be the reason behind this problem and solution to make that folder visible. tower-diagnostics-20210104-1928.zip Edited January 6, 20215 yr by Ahalm Solved
January 4, 20215 yr Community Expert First open the teminal on the GUI and give us a screen shot of the following command: ls -al /mnt/user0 Then add the directory with the problem to the command and give us that screen shot. (Note, you can scrub out the file/directory names -- except for the one with the problem-- but leave the permissions!) Next look at the permissions for the folders in Windows Explorer and make sure that somehow something has not made them 'Hidden'. (Right-click on directory/folder and select Properties from dropdown list.)
January 5, 20215 yr Author I have no /mnt/user0 folder. I have no cache drive set, which might be the reason. I've included below outputs from /mnt/user instead. That folder is indeed seen in Windows Explorer as hidden. That hidden checkbox isn't active so chancing it there isn't possible. (File sizes below are inaccurate, I didn't wait for calculation.)
January 5, 20215 yr Community Expert 33 minutes ago, Ahalm said: That folder is indeed seen in Windows Explorer as hidden. That hidden checkbox isn't active so chancing it there isn't possible. (File sizes below are inaccurate, I didn't wait for calculation.) I would guess that is being shown that way because of the state of its parent directory/folder (and the parent is actually being hidden by Windows). Do some checking and googling about this condition. I am no expert on setting up any non-standard attributes on the Windows file system because it usually (in my limited expiration) leads to trouble in the future!
January 6, 20215 yr Author I found a solution. The reason behind is still mystery (despite trying to search answer, found lot new information anyway), but there was quite simple workaround. I just moved all items in problematic folder to new folder, removed the problematic folder and then renamed the new folder back to the original name. So simple, that I wonder why I hadn't thought this before. Thank you for your assistance anyway.
Archived
This topic is now archived and is closed to further replies.