April 12, 201610 yr I had a share/folder on my cache drive that I didnt think I needed shared any more, so I set SMB share off. I figure I can get to the folder via the cache share already, so to avoid confussion I wanted to hide it by stopping the share. All dockers accessed it via /mnt/cache/appdata so having an appdata share was not really needed. however, upon doing so, all my shares when with it. I still see my folders on the drives and the share config files, so not sure what happened. I have stopped the array and started it, but no luck. the only thing I have not tried is a reboot, but I am not sure if that is needed. I an certainly a bit nervous as things have been rock solid for year and now the last week I have been dealing with issues. first my cache drive appeared to go read only taking my containers with it. and now upong replacing the drive and getting things back up, I have now lost all my shares. Data appears ok, but still. what give. I am hoping this is an easy fix.
April 12, 201610 yr Author Apr 11 23:32:53 Tower php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'start' 'Beets' Apr 11 23:32:53 Tower kernel: device veth9a603a0 entered promiscuous mode Apr 11 23:32:53 Tower kernel: docker0: port 4(veth9a603a0) entered forwarding state Apr 11 23:32:53 Tower kernel: docker0: port 4(veth9a603a0) entered forwarding state Apr 11 23:32:53 Tower avahi-daemon[23433]: Withdrawing workstation service for veth44442f9. Apr 11 23:32:53 Tower kernel: docker0: port 4(veth9a603a0) entered disabled state Apr 11 23:32:53 Tower kernel: eth0: renamed from veth44442f9 Apr 11 23:32:53 Tower kernel: docker0: port 4(veth9a603a0) entered forwarding state Apr 11 23:32:53 Tower kernel: docker0: port 4(veth9a603a0) entered forwarding state Apr 11 23:32:53 Tower kernel: veth44442f9: renamed from eth0 Apr 11 23:32:53 Tower kernel: docker0: port 4(veth9a603a0) entered disabled state Apr 11 23:32:53 Tower kernel: docker0: port 4(veth9a603a0) entered disabled state Apr 11 23:32:53 Tower avahi-daemon[23433]: Withdrawing workstation service for veth44442f9. Apr 11 23:32:53 Tower avahi-daemon[23433]: Withdrawing workstation service for veth9a603a0. Apr 11 23:32:53 Tower kernel: device veth9a603a0 left promiscuous mode Apr 11 23:32:53 Tower kernel: docker0: port 4(veth9a603a0) entered disabled state Apr 11 23:32:53 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Documents Transport endpoint is not connected Apr 11 23:32:53 Tower emhttp: get_filesystem_status: statfs: /mnt/user/ISOs Transport endpoint is not connected Apr 11 23:32:53 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Music Transport endpoint is not connected Apr 11 23:32:53 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Pictures Transport endpoint is not connected Apr 11 23:32:53 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Software Transport endpoint is not connected Apr 11 23:32:53 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Video Transport endpoint is not connected Apr 11 23:32:53 Tower emhttp: get_filesystem_status: statfs: /mnt/user/appdata Transport endpoint is not connected Apr 11 23:32:55 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Documents Transport endpoint is not connected Apr 11 23:32:55 Tower emhttp: get_filesystem_status: statfs: /mnt/user/ISOs Transport endpoint is not connected Apr 11 23:32:55 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Music Transport endpoint is not connected Apr 11 23:32:55 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Pictures Transport endpoint is not connected Apr 11 23:32:55 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Software Transport endpoint is not connected Apr 11 23:32:55 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Video Transport endpoint is not connected Apr 11 23:32:55 Tower emhttp: get_filesystem_status: statfs: /mnt/user/appdata Transport endpoint is not connected Apr 11 23:32:58 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Documents Transport endpoint is not connected Apr 11 23:32:58 Tower emhttp: get_filesystem_status: statfs: /mnt/user/ISOs Transport endpoint is not connected Apr 11 23:32:58 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Music Transport endpoint is not connected Apr 11 23:32:58 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Pictures Transport endpoint is not connected Apr 11 23:32:58 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Software Transport endpoint is not connected Apr 11 23:32:58 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Video Transport endpoint is not connected Apr 11 23:32:58 Tower emhttp: get_filesystem_status: statfs: /mnt/user/appdata Transport endpoint is not connected Apr 11 23:33:01 Tower crond[2496]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Apr 11 23:33:09 Tower emhttp: shcmd (224): :>/etc/samba/smb-shares.conf Apr 11 23:33:09 Tower emhttp: shcmd (225): cp /etc/exports- /etc/exports Apr 11 23:33:09 Tower avahi-daemon[23433]: Files changed, reloading. Apr 11 23:33:09 Tower emhttp: Restart SMB... Apr 11 23:33:09 Tower emhttp: shcmd (226): killall -HUP smbd Apr 11 23:33:09 Tower emhttp: shcmd (227): smbcontrol smbd close-share 'appdata' Apr 11 23:33:09 Tower emhttp: shcmd (228): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service Apr 11 23:33:09 Tower avahi-daemon[23433]: Files changed, reloading. Apr 11 23:33:09 Tower avahi-daemon[23433]: Service group file /services/smb.service changed, reloading. Apr 11 23:33:09 Tower emhttp: shcmd (229): pidof rpc.mountd &> /dev/null Apr 11 23:33:09 Tower emhttp: Restart NFS... Apr 11 23:33:09 Tower emhttp: shcmd (230): exportfs -ra |& logger Apr 11 23:33:09 Tower emhttp: shcmd (231): /etc/rc.d/rc.atalk status Apr 11 23:33:10 Tower avahi-daemon[23433]: Service "Tower" (/services/smb.service) successfully established. Apr 11 23:34:01 Tower crond[2496]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Apr 11 23:35:01 Tower crond[2496]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Apr 11 23:35:50 Tower php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'start' 'Beets' Apr 11 23:35:50 Tower kernel: device veth17705c5 entered promiscuous mode Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered forwarding state Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered forwarding state Apr 11 23:35:50 Tower avahi-daemon[23433]: Withdrawing workstation service for veth0a7411e. Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered disabled state Apr 11 23:35:50 Tower kernel: eth0: renamed from veth0a7411e Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered forwarding state Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered forwarding state Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered disabled state Apr 11 23:35:50 Tower kernel: veth0a7411e: renamed from eth0 Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered forwarding state Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered forwarding state Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered disabled state Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered disabled state Apr 11 23:35:50 Tower avahi-daemon[23433]: Withdrawing workstation service for veth0a7411e. Apr 11 23:35:50 Tower avahi-daemon[23433]: Withdrawing workstation service for veth17705c5. Apr 11 23:35:50 Tower kernel: device veth17705c5 left promiscuous mode Apr 11 23:35:50 Tower kernel: docker0: port 4(veth17705c5) entered disabled state Apr 11 23:35:56 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker logs --tail=350 -f Beets Apr 11 23:36:01 Tower crond[2496]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Apr 11 23:36:31 Tower php: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker 'start' 'Beets' Apr 11 23:36:31 Tower kernel: device veth3218716 entered promiscuous mode Apr 11 23:36:31 Tower kernel: docker0: port 4(veth3218716) entered forwarding state Apr 11 23:36:31 Tower kernel: docker0: port 4(veth3218716) entered forwarding state Apr 11 23:36:31 Tower avahi-daemon[23433]: Withdrawing workstation service for veth4987bee. Apr 11 23:36:31 Tower kernel: docker0: port 4(veth3218716) entered disabled state Apr 11 23:36:31 Tower kernel: eth0: renamed from veth4987bee Apr 11 23:36:31 Tower kernel: docker0: port 4(veth3218716) entered forwarding state Apr 11 23:36:31 Tower kernel: docker0: port 4(veth3218716) entered forwarding state Apr 11 23:36:31 Tower kernel: docker0: port 4(veth3218716) entered disabled state Apr 11 23:36:31 Tower kernel: veth4987bee: renamed from eth0 Apr 11 23:36:31 Tower kernel: docker0: port 4(veth3218716) entered disabled state Apr 11 23:36:31 Tower avahi-daemon[23433]: Withdrawing workstation service for veth4987bee. Apr 11 23:36:31 Tower avahi-daemon[23433]: Withdrawing workstation service for veth3218716. Apr 11 23:36:31 Tower kernel: device veth3218716 left promiscuous mode Apr 11 23:36:31 Tower kernel: docker0: port 4(veth3218716) entered disabled state Apr 11 23:36:34 Tower emhttp: cmd: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker logs --tail=350 -f Beets Apr 11 23:36:52 Tower kernel: device vethc50a332 entered promiscuous mode Apr 11 23:36:52 Tower kernel: docker0: port 4(vethc50a332) entered forwarding state Apr 11 23:36:52 Tower kernel: docker0: port 4(vethc50a332) entered forwarding state Apr 11 23:36:52 Tower avahi-daemon[23433]: Withdrawing workstation service for veth9c048c9. Apr 11 23:36:52 Tower kernel: docker0: port 4(vethc50a332) entered disabled state Apr 11 23:36:52 Tower kernel: eth0: renamed from veth9c048c9 Apr 11 23:36:52 Tower kernel: veth9c048c9: renamed from eth0 Apr 11 23:36:52 Tower kernel: docker0: port 4(vethc50a332) entered forwarding state Apr 11 23:36:52 Tower kernel: docker0: port 4(vethc50a332) entered forwarding state Apr 11 23:36:52 Tower kernel: docker0: port 4(vethc50a332) entered disabled state Apr 11 23:36:52 Tower kernel: docker0: port 4(vethc50a332) entered disabled state Apr 11 23:36:52 Tower avahi-daemon[23433]: Withdrawing workstation service for veth9c048c9. Apr 11 23:36:52 Tower avahi-daemon[23433]: Withdrawing workstation service for vethc50a332. Apr 11 23:36:52 Tower kernel: device vethc50a332 left promiscuous mode Apr 11 23:36:52 Tower kernel: docker0: port 4(vethc50a332) entered disabled state Apr 11 23:37:01 Tower crond[2496]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null Apr 11 23:37:14 Tower kernel: mdcmd (108): nocheck Apr 11 23:37:14 Tower kernel: md: nocheck_array: check not active Apr 11 23:37:14 Tower cache_dirs: Stopping cache_dirs process 24473
April 12, 201610 yr Community Expert It is not at all clear from your description exactly what you did? I would suggest that you post the diagnostics file (Tools->Diagnostics) so that we can see more information on how things are currently set up on your system.
April 12, 201610 yr Author It is not at all clear from your description exactly what you did? I would suggest that you post the diagnostics file (Tools->Diagnostics) so that we can see more information on how things are currently set up on your system. I had a share, appdata, set to cache drive only. under smb security I selected export, no, clicked apply thats all i did and it took all my shares with it tower-diagnostics-20160412-0542.zip
April 12, 201610 yr Community Expert It is not at all clear from your description exactly what you did? I would suggest that you post the diagnostics file (Tools->Diagnostics) so that we can see more information on how things are currently set up on your system. I had a share, appdata, set to cache drive only. under smb security I selected export, no, clicked apply thats all i did and it took all my shares with it do you know if you can see the shares on the network? I am asking as it recently seems that many people encounter shares not showing up in the GUI even though they are otherwise working fine. The cause in virtually all such cases seems to be an adblocker installed in the browser that interferes with the GUI, and the solution is then to whitelist the unRAID server in the adblocker. I will look through the diagnostics files to see if I can spot anything else amiss.
April 12, 201610 yr Author No, I see cache, flash and all my disks only Sent from my Nexus 6P using Tapatalk
April 12, 201610 yr Author It might also be worth noting that all of my share config files still exist, so it's puzzling as to why they would not be there. Is it worth trying a reboot? Sent from my Nexus 6P using Tapatalk
April 12, 201610 yr Author Global Share Settings? Shares Enabled? enable disk shares: yes enable user shares: yes
April 12, 201610 yr Community Expert It might also be worth noting that all of my share config files still exist, so it's puzzling as to why they would not be there. Is it worth trying a reboot? Definitely worth a reboot.
April 12, 201610 yr Author OK, I will try. I was holding off nervous that it could blow up all my data... Since there are no shares, I was thinking it might try deleting everything... Sent from my Nexus 6P using Tapatalk
April 12, 201610 yr Community Expert OK, I will try. I was holding off nervous that it could blow up all my data... Since there are no shares, I was thinking it might try deleting everything... Sent from my Nexus 6P using Tapatalk if anything the opposite is likely to happen. On boot, the User Share system is constructed from all the top level folders on each drive. If there is not a .cfg file for a particular share then default settings are applied.
April 12, 201610 yr Author Sweet, that seems to have worked. So, maybe I was being stupid. Can I not have a folder on my cache drive that is not shared? Or would it just need to be hidden? I ask because that explains why after rebooting I have a share for appdata again under /mnt/user/"appdata" Or, instead of smb share setting being no, make it yes, hidden? I mean I don't need it to be a share at all, but whatever. My goal was to simply have it as a folder on my cache drive only and not share it. If I wanted to access it, I could get to it via my cache drive. Sent from my Nexus 6P using Tapatalk
April 12, 201610 yr Community Expert Sweet, that seems to have worked. So, maybe I was being stupid. Can I not have a folder on my cache drive that is not shared? Or would it just need to be hidden? I ask because that explains why after rebooting I have a share for appdata again under /mnt/user/"appdata" Or, instead of smb share setting being no, make it yes, hidden? I mean I don't need it to be a share at all, but whatever. My goal was to simply have it as a folder on my cache drive only and not share it. If I wanted to access it, I could get to it via my cache drive. Yes - you can hide the share from the network by setting the SMB setting to No. However this will not remove it from the list of shares shown on the GUI Shares tab.
April 12, 201610 yr Community Expert ... Can I not have a folder on my cache drive that is not shared? Or would it just need to be hidden? I ask because that explains why after rebooting I have a share for appdata again under /mnt/user/"appdata" Or, instead of smb share setting being no, make it yes, hidden? I mean I don't need it to be a share at all, but whatever. My goal was to simply have it as a folder on my cache drive only and not share it. If I wanted to access it, I could get to it via my cache drive... Not just your cache drive. As itimpi already said, any top level folder on any drive is a user share. Whether you can access that share over the network is up to you.
April 12, 201610 yr Author I wasn't worried about seeing it in the gui, just trying not to confuse myself with it in 2 places. Sent from my Nexus 6P using Tapatalk
April 17, 201610 yr Author @itimpi I wanted to point you to a new thread I started which is a little more precise to my issue as it happened again... https://lime-technology.com/forum/index.php?topic=48473.0
Archived
This topic is now archived and is closed to further replies.