Temporary NFS mount keep being mounted while server is powered off

Question

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!
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.

Answer 1

Please read this whole message before doing anything.
This procedure is a diagnostic test. It won’t solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
Third-party system modifications are a common cause of usability problems. By a “system modification,” I mean software that affects the operation of other software — potentially for the worse. The following procedure will help identify which such modifications you've installed. Don’t be alarmed by the complexity of these instructions — they’re easy to carry out and won’t change anything on your Mac. 
These steps are to be taken while booted in “normal” mode, not in safe mode. If you’re now running in safe mode, reboot as usual before continuing. 
Below are instructions to enter some UNIX shell commands. The commands are harmless, but they must be entered exactly as given in order to work. If you have doubts about the safety of the procedure suggested here, search this site for other discussions in which it’s been followed without any report of ill effects. 
Some of the commands will line-wrap or scroll in your browser, but each one is really just a single line, all of which must be selected. You can accomplish this easily by triple-clicking anywhere in the line. The whole line will highlight, and you can then either copy or drag it. The headings “Step 1” and so on are not part of the commands. 
Note: If you have more than one user account, Step 2 must be taken as an administrator. Ordinarily that would be the user created automatically when you booted the system for the first time. The other steps should be taken as the user who has the problem, if different. Most personal Macs have only one user, and in that case this paragraph doesn’t apply. 
Launch the Terminal application in any of the following ways: 
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.) 
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens. 
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid. 
When you launch Terminal, a text window will open with a line already in it, ending either in a dollar sign (“$”) or a percent sign (“%”). If you get the percent sign, enter “sh” and press return. You should then get a new line ending in a dollar sign. 
Step 1 
Triple-click the line of text below to select it:
kextstat -kl | awk '!/com\.apple/{printf "%s %s\n", $6, $7}' 
Copy (command-C) the selected text to the Clipboard. Then click anywhere in the Terminal window and paste (command-V). Post the lines of output (if any) that appear below what you just entered. You can do that by copy-and-paste as well. Omit the final line ending in “$”. No typing is involved in this step.
Step 2 
Repeat with this line:
sudo launchctl list | sed 1d | awk '!/0x|com\.(apple|openssh|vix)|edu\.mit|org\.(amavis|apache|cups|isc|ntp|postfix|x)/{print $3}' 
This time you'll be prompted for your login password, which you do have to type. It won't be displayed when you type it. Type it carefully and then press return. You may get a one-time warning not to screw up. You don't need to post the warning. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator. 
Note: If you don’t have a login password, you’ll need to set one before taking this step. If that’s not possible, skip to the next step. 
Step 3
launchctl list | sed 1d | awk '!/0x|com\.apple|edu\.mit|org\.(x|openbsd)/{print $3}' 
Step 4
ls -1A /e*/mach* {,/}L*/{Ad,Compon,Ex,Fram,In,Keyb,La,Mail/Bu,P*P,Priv,Qu,Scripti,Servi,Spo,Sta}* L*/Fonts 2> /dev/null  
Important: If you formerly synchronized with a MobileMe account, your me.com email address may appear in the output of the above command. If so, anonymize it before posting. 
Step 5
osascript -e 'tell application "System Events" to get name of every login item' 2> /dev/null 
Remember, steps 1-5 are all copy-and-paste — no typing, except your password. Also remember to post the output. 
You can then quit Terminal.