CIFS VFS no response for cmd 50 using Ubuntu 9.10 Karmic Koala

[solbot]

I was also having a problem with the Shutdown / Reboot sequence taking ages due to using WiFi, WPA2 and mounting SMB shares.
I wasted about 4 hours digging around before I finally realised that the solution involved Upstart.

1. Open a terminal and enter:

sudo gedit /etc/init/network-manager.conf

2. Just below the description line add the following:

pre-stop script
   /etc/init.d/umountnfs.sh
end script

3. Save the script and attempt a restart.

I don't know if this will work for everyone, or even what version of Upstart you need for it to work, but it cuts my shutdown time from about 2 mins to about 30 seconds.

Note: This has been working for me about 90% of the time.
Occasionally though I see that the script ends prematurely due to the TERM signal and I end up with the 2 minute wait again.
I've added the following to the /etc/init/network-manager.conf file:

pre-stop script
   trap "Caught TERM Signal" TERM
   /etc/init.d/umountnfs.sh
   trap - TERM
end script

Not sure if it works, but I haven't seen the TERM error yet.

[bi0hazard]

Yup, this worked for me! Thx!

[^_Pepe_^]

Yessssssssssssssss!

You rock!!



Thank you so much!

[MrEgg]

This worked for me too! Thanks!!

[roalt]

Have the same problem, but adding the script doesn't help. Look like the script is not executed when I do a shutdown. Any ideas?

[solbot]

What version of Ubuntu are you using?

[slackware_user]

All of this is related to mounting samba/cifs shares via fstab and using networkmanager to manage the wireless connections. It is still possible to use nautilus mounts. You can find them by issuing cat /etc/mtab and finding the hidden mount points for the shares. The system can then umount them and shutdown is fine.

But it is much nicer to have them mounted in a normal, consistent location!

There had been a workaround prior to my latest upgrade to 9.10. Now the old fix, to rename the sysv rcX.d umountnfs shutdown scripts to K00umountnfs.sh, no longer works. Something to do with upstart?

This pre-stop script thing sounded reasonable, but no cigar.

The funny thing is that all of this nonsense would take 2 mins to fix in slackware. So far, my experience with ubuntu is that it is very easy to get almost working, but very hard to get finally right.

I think my best bet, before finally blowing ubuntu away and going back to slack, is to try to bypass network-manager and configure the interface via /etc/network/interfaces. (This is so the interface will stay connected long enough to allow the umount). So far, I have not been able to accomplish this, or even to get the interface (ath5k netgear wg511T) to connect via ifconfig and iwconfig commands that I know work with this interface in a slackware box. Maybe uninstall networkmanager and try again?

This is starting to try my patience.

[roalt]

What version of Ubuntu are you using?

As the topic says: Karmic 9.10

Just like @slackware_user says: I also had a similiar solution for pre-Karmic Ubuntu to do the unmounting, but this does not work anymore as no /etc/rc*.d/K scripts are used any more by Upstart.

I do not understand why a mainstrean release like Ubuntu cannot handle the automatic mounting of shares on a server in combination with wireless/Network manager.

[solbot]

I don't understand why it won't either but I'll keep trying to come up with solutions until either I get it working perfectly or the devs fix the problem.

To Slackware_User, it's true you could do this pretty quickly with Slackware. You could do it with Gentoo or Fedora fairly rapidly too, but if we keep doing the same old thing all the time then eventually we'll fall behind and MS will win.

The Network Manager makes it almost as easy for new users to set up their networking as in Windows, and that's a good thing.

The bad part of it, for us that actually know how to edit things like fstab to mount shares, is when we try something that used to work but now doesn't.

It's basically a trade off between ease of use and power.
Upstart is such a massive change from the old SysV init scripts that I'm suprised there haven't been more glitches like this.

Anyway, I'll see if I can think of an alternate solution to your problem and get back to you.

[a3101]

Doesn't work for me either.. Ubuntu, fits for all.. yeah right...

ver 9.10,My file looks like this:

# network-manager - network connection manager
#
# The Network Manager daemon manages the system's network connections,
# automatically switching between the best available.

description    "network connection manager"

pre-stop script
   /etc/init.d/umountnfs.sh
   trap - TERM
end script

start on (local-filesystems
      and started dbus)
stop on stopping dbus

expect fork
respawn

exec NetworkManager