January 3, 201610 yr Hi, I am unable to see the directories and files that I have created under samba. For example, I have a user share called "Backup". In that folder, there is nothing in it. If I look under the disk itself, it displays the shares files and folders. I have already tried rebooting the computer twice. This all occurred after a hard reboot. Here are visuals of what I am talking about: Viewing the user share "Backup": Viewing the disk: This only is a problem under samba NOT NFS. When I view the user shares on NFS, then all the files and folders are there. I can also see the files and folders under /mnt/user/backup when i am in terminal or etc... I have attached my syslog and diagnostic view for reference. Here is my smb-shares.log path = /boot comment = unRAID Sever OS boot device browseable = yes # Public public = yes writeable = yes map archive = no map system = no map hidden = no map readonly = yes create mask = 0777 directory mask = 0777 [disk1] path = /mnt/disk1 comment = browseable = yes # Public public = yes writeable = yes [disk2] path = /mnt/disk2 comment = browseable = yes # Public public = yes writeable = yes [disk3] path = /mnt/disk3 comment = browseable = yes # Public public = yes writeable = yes [disk4] path = /mnt/disk4 comment = browseable = yes # Public public = yes writeable = yes [disk5] path = /mnt/disk5 comment = browseable = yes # Public public = yes writeable = yes [disk6] path = /mnt/disk6 comment = browseable = yes # Public public = yes writeable = yes [disk7] path = /mnt/disk7 comment = browseable = yes # Public public = yes writeable = yes [disk8] path = /mnt/disk8 comment = browseable = yes # Public public = yes writeable = yes [disk9] path = /mnt/disk9 comment = browseable = yes # Public public = yes writeable = yes [backup] path = /mnt/user/Backup comment = browseable = yes # Public public = yes writeable = yes [shares] path = /mnt/user/Shares comment = browseable = yes # Public public = yes writeable = yes [appdata] path = /mnt/user/appdata comment = browseable = yes # Public public = yes writeable = yes [backup] path = /mnt/user/backup comment = browseable = yes # Public public = yes writeable = yes [disk5] path = /mnt/user/disk5 comment = browseable = yes # Public public = yes writeable = yes [lost+found] path = /mnt/user/lost+found comment = browseable = yes # Public public = yes writeable = yes [mariadb] path = /mnt/user/mariadb comment = browseable = yes # Public public = yes writeable = yes [shares] path = /mnt/user/shares comment = browseable = yes # Public public = yes writeable = yes Thank you for any help. Aaron
January 3, 201610 yr Community Expert I see two shares--- One named "backup" and the other "Backup" Try adding a "1" (e.g., "backup1") to the end of one of them and report back what happens. Weird things have been know to happen when file the only difference between two file names is capitalization!
January 3, 201610 yr I see two shares--- One named "backup" and the other "Backup" Try adding a "1" (e.g., "backup1") to the end of one of them and report back what happens. Weird things have been know to happen when file the only difference between two file names is capitalization! Because Linux is case sensitive whereas Windows is not. (and you manually created the folders)
January 3, 201610 yr Author Dang, I knew that was the problem, but I thought Android was case sensitive like Linux. I have two kindle fire tvs, and they were experiencing the same issue so I thought it wasn't the issue. Thank you all for the help!
Archived
This topic is now archived and is closed to further replies.