Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

One way to make 'hidden' SMB shares reappear Network
At my work, we have a large number of SMB shares, and for some reason they stop showing up on desktops sometimes. If you look for them in Terminal, they are mounted, but they are not in the Finder anywhere. If this happens, here's one way to get them back.
  • Launch Terminal and type cd /Volumes
  • Type ls to list the directory's contents, and find the volume name in the list.
  • Type open volumename, where volumename is the name as shown in the prior output.
A new Finder window will open with the root contents of the volume you chose, and the icon will then appear in the Finder window and on the desktop (if you have network volumes showing on your desktop).
    •    
  • Currently 1.80 / 5
  You rated: 2 / 5 (5 votes cast)
 
[12,255 views]  

One way to make 'hidden' SMB shares reappear | 10 comments | Create New Account
Click here to return to the 'One way to make 'hidden' SMB shares reappear' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
One way to make 'hidden' SMB shares reappear
Authored by: ataraxia on Aug 14, '07 07:52:08AM
Have you tried just doing disktool -r? That's supposed to make Finder refresh its list of attached volumes.

[ Reply to This | # ]
One way to make 'hidden' SMB shares reappear
Authored by: mlinde on Aug 14, '07 11:18:36AM

I tried the suggestion mentioned in the first comment - and it didn't work. It would have been nice too, as it is a simpler solution.



[ Reply to This | # ]
One way to make 'hidden' SMB shares reappear
Authored by: fds on Aug 14, '07 11:32:41AM

Another thing to try in this case may be to go to Finder Preferences and turn "Show these items on the Desktop: - Connected servers" off then back on again.



[ Reply to This | # ]
One way to make 'hidden' SMB shares reappear
Authored by: pfernandes on Aug 14, '07 01:44:01PM

These disappearing SMB shares is driving me crazy. This is something recent as I have been using samba shares for a long time.
An easier way that has been working for me (most of the times) is using the go to folder Command+Shift+G and change to folder /Volumes
Normally Finder will just refresh and show up the missing mounted smb shares.
Another odd and related thing happening to me is having smb shares show up on their own!



[ Reply to This | # ]
One way to make 'hidden' SMB shares reappear
Authored by: pfernandes on Aug 14, '07 01:46:55PM

By appearing on their own I mean. They are not mounted and out of Finder's recreation they suddenly show up as if they were!



[ Reply to This | # ]
One way to make 'hidden' SMB shares reappear
Authored by: peertimo on Aug 14, '07 11:56:01PM

I have mistakenly removed, but not unmounted, a drive from the side of the Finder, and have always found it again in the Computer view. Give it a try.



[ Reply to This | # ]
One way to make 'hidden' SMB shares reappear
Authored by: mm2270 on Aug 15, '07 06:58:26AM
How interesting this would be posted today, when just yesterday I ran across something similar involving AFP shares.

We had an issue that would pop up from time to time that was bugging us here at work, where an AFP share would have difficulty mounting. Usually an error stating it couldn't mount the volume or something similar would pop up.
Afterwards, we noticed that mounting this volume would result in the volume showing up as "share_name-1". This would cause issues when using certain applications, like Capture One, which uses absolute paths. The links to session files would end up broken when using Capture One on any Mac having this share-1 issue.

I discovered by poking around in the terminal that the system apparently created some invisible temp directory in the location /Volumes that would stay there, even after reboots, and had the name of the share. Because of this the OS had no choice but to append the -1 to the end of the name of the actual share when it mounted in the Finder.

The fix was to actually do an rm -R on the offending file. Before doing this, I completely disconnected the affected Mac from the network, just to be sure it wasn't reading some actual network share. Even with it disconnected, it would show in /Volumes, so it was definitely a local file. After removing it, the actual AFP share would then show up with its proper name.

I know this hint is based on a slightly different issue, but it seems somehow related to how Mac OS X is mounting shares. Must be some kind of bug in how Tiger mounts volumes that causes this issue, and the one this hint is about.

[ Reply to This | # ]
One way to make 'hidden' SMB shares reappear
Authored by: JimMueller on Aug 16, '07 01:28:55PM

You are the only other person I have seen mention the sharename-1 behaviour, and I have searched many online resources and asked about it several times with no acknowledgment. We get it in a different situation - if another user on the FUS-enabled Mac has a share on another mac mounted, then when you mount the same share it appears with a -1 after the sharename. Not much of a problem except they both appear in the sidebar in the Finder and file open/save dialogue. Aliases to folders and files on this share often get confused and sometimes cannot find the file or open the folder with nothing appearing in it.
Not really pertinent to this discussion, but I was happy to see it happened to someone else too.



[ Reply to This | # ]
One way to make 'hidden' SMB shares reappear
Authored by: seede on Sep 10, '07 11:31:41PM

I have had exactly the same mentioned problem with /Volumes directory having these phantom links with -1 after them. I haven't tried to reproduce the problem but it is not unique to mm2270's situation



[ Reply to This | # ]
One way to make 'hidden' SMB shares reappear
Authored by: cellocgw on Sep 14, '07 09:41:06AM

This same mess happened to me today. Thank goodness for the answers in this thread. I also noticed that "umount" would not remove the volume from /Volumes. "rm -rf" succeeded. (this is for a network volume that the Finder didn't see, even though Terminal sessions did).



[ Reply to This | # ]