You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Temporary NFS mount keep being mounted while server is powered off

I was doing some performance testing using different file protocols (NFS, SMB mainly).


The last test was with NFS, I mounted on the command line the nfs exported directory, did my test, forgot about the moment and shutdown the NFS server. Since then OS X is bugging me every 2 minutes with a popup (which has the focus!) which states "There was a problem connecting to the server 192.168.1.250". The mount is not visible via 'df' so I decided to reboot the machine... But even after rebooting it, the popup keep on poping up!


User uploaded file


The setup was: OS X 10.8 as NFS client; FreeBSD 9.1 as NFS server (in a virtual machine hosted by a Linux machine on the same network). The command was:


mount -t nfs 192.168.1.250:/mnt/test ~/mnt/


I restarted the FreeBSD VM, suddenly the NFS export was mounted, this time as /Volumes/test. I unmounted it this time using:


sudo umount /Volumes/test


It did work successfully. I shutdown and deleted my VM, and some hours later the popup reappeared!!


How to get rid of it? Or more explicitely where is the configuration file where the mount is still explicitely present?

(it is not in /etc/fstab, nor /etc/auto_master) I did a huge grep using the IP address on the disk, and I got only log errors in /var/log.

MacBook Pro with Retina display, OS X Mountain Lion (10.8.2)

Posted on Feb 12, 2013 8:59 AM

Reply
39 replies

Feb 23, 2013 2:57 PM in response to Huygens-25

One more thing!


Regarding Safe Mode, I have 2 things I want to mention, but mainly that I perhaps have the problem in safe mode too!


First, I did not have a working network in safe mode (and I do not manage to make it work, even when set manually!). I thought it was "expected" in safe mode but I have found out that it should work.


Second, I did see once the error message in safe mode. I was trying to make the network work, tried DHCP (as it is configured in normal mode) then manual, then DHCP only for the IP, etc. without luck. I then decided to reboot in normal mode, and during the brief moment after the OS X desk disappear and you see a grey background which you guess is the shutting down mode, I briefly see appeared the popup message that the NFS server was not reachable.


Maybe, I was not seeing the popup because network is not properly working in safe mode...

Feb 25, 2013 1:44 PM in response to Linc Davis

I have check the file, I don't see the NFS share.


The file is a binary plist. If I open it with Xcode, I do not see the destination volume but rather its UID only. The same apply if I convert this binary plist to an XML one.

However, an hexdump clearly show the AFP destination for time machine (i.e. the hostname and share of the Time Machien volume).

Is this normal that I can see it in the binary but not in the XML?


That's 36 hours since I deactivated TM and since no more popup. I have just reactivated it and will wait to see if it comes back. Though that might take a couple of days as I will use little my Mac tomorrow and the day after.

Feb 25, 2013 3:53 PM in response to Huygens-25

If the warnings come back, then it will be clear that you've triggered an obscure bug. I don't know where the link to the share could be hiding. In undocumented CoreStorage metadata, perhaps? What I would do in your place is to start a new TM backup on another drive. You should do that anyway, as one backup is not enough. Put the old drive aside for a while. If the problem doesn't recur, erase the drive and start over. I don't have a better idea.

Feb 25, 2013 11:19 PM in response to Linc Davis

This morning I quickly logged in to see if one of the automated TM backup triggered the message, but nothing.

I will try to reboot also and do some more testing tomorrow, but you are probably right, I have hit an obscure difficult to reproduce bug.


I will start a new backup, why not. However, I am using a NAS (2 mirrored disks) so I will simply create a new image for it. I also do have Crashplan with a Cloud plan, so I think I don't need another drive yet ;-)

But I will move to and keep the previous image on a DAS for awhile still, if I need back some historical data.


Anyway thank you very much Linc. If I don't post anymore it is because there is nothing weird happening and it is back as usual.

It is sad that I cannot change the "This post solve my problem" to another post, in a way your advice to stop TM did work in the end :-)

Mar 30, 2013 3:33 AM in response to Huygens-25

That is now a bit over than a month without the problem. Well almost...


Today, a bit more than 30 days later, I got for the first time again the infamous popup message. But after a reboot it is now gone again. The weirdest bug since Windows 98 plug and pray magic!


Anyway, today I was just trying to set up my step parents network and WiFi. They have 2 routers, one in the basement (the "modem router") and one in the living room. The WiFi signal from the basement is too weak, so they have plugged another router to it and put it in the living room. I just setup proper WiFi encryption, changed the router default admin password and switch the living room router to AP mode to avoid the double firewall problem (when using apps like Skype).

Once the living room router was set to AP mode and restarted, my Mac greeted us with the infamous popup less than a minute later! Then I lost "internet" connectivity: I could still reach device in the current network, but could not reach any internet service! However all other devices in the same network performed properly. A reboot of my Mac solved the problem this time.

But this bug is still around and driving me kind of mad (in the sense that it puzzle me, not that it gets on my nerve).


I don't expect any help here, but just writing down my experience until this bug shows a proper causality behaviour!

May 31, 2013 6:30 AM in response to Huygens-25

I guess this is simply the new OS X (aka Mountain Lion) which is that much crap!


I do have a NAS at home with AFP shares. During my last weekend away from home, my Mac bugged me the full weekend with a similar popup message that it cannot connect to the NAS!!! Of course, I was not home, I was on a different network! Crazy!


I could accept that the OS would try to connect to the share and display a warning that a network share is not present. However, I found clearly crap that the OS tries repeatedly to do so and notifies me every 60 sec of the failed attempt with a focused, on top of everything, popup dialog. Even ads popup on Internet are not that much intrusive/annoying!

Temporary NFS mount keep being mounted while server is powered off

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.