Excessively long shut down times

[McLovin]

that is an upstream bug from Ubuntu, I have installed all level 3 updates, and one of them fixes this, you may want to give that a try. If that doesn't help, there is a hack that works, but it is a dirty hack, so give the level 3 updates a first.

Just so you know, level 3 updates are generally safe, i have never seen issues with them.

[kwisher]

that is an upstream bug from Ubuntu, I have installed all level 3 updates, and one of them fixes this, you may want to give that a try. If that doesn't help, there is a hack that works, but it is a dirty hack, so give the level 3 updates a first.

Just so you know, level 3 updates are generally safe, i have never seen issues with them.

I am experiencing slow shutdowns also. This condition only shows up after I add mount commands in my fstab file for samba shares. Mint-5 did not have this problem. The message I see is as follows:

Code: Select all

acpid: exiting

[1667.040027] CIFS VFS:SERVER NOT RESPONDING
[1667.040072] CIFS VFS:NO RESPONSE FOR CMD 50 MID 2177

[nelamvr6]

When I first installed Felicia on my Dell I had problems with hanging on shutdown. I use the nosplash option so I was able to see that the problems had something to do with alsa shutting down.

I did some digging and discovered a fix, putting ifconfig wlan0 down at the beginning of stop in: /etc/init.d/alsa-utils.

Then I ran the updates and there was an update modifying that same file.

And so I guess what I'm saying is there appears to have been a bug in the alsa-utils file which has been addressed by an update.

[kwisher]

Is this considered a bug? If so, is there an official post for bug fixes for Mint-6 final?

[kwisher]

An update for everybody-

I installed all the level 3 updates and have not had a problem since.

Updating does not solve the problem I posted about. So is this a bug? Where can I report it?

[kwisher]

I would appreciate some feedback from the Mint team on this issue. This is a showstopper for me to upgrade to Mint-6.

Thanks.

[kwisher]

BUMP

[McLovin]

On a samba share I really don't know, I have never tried to automount a samba share, only an nfs share. Is the samba share on your system, or a remote one?

[kwisher]

On a samba share I really don't know, I have never tried to automount a samba share, only an nfs share. Is the samba share on your system, or a remote one?

It is on a different system on my local network. This works fine in previous versions of Mint. I did notice it when I tried Mint-5 KDE but it is not present in Mint-5 Gnome.

[McLovin]

so, the remote drive is on a windows system, right? I am asking because if it is on a linux system, you should really use NFS, its alot faster, and native.

[kwisher]

so, the remote drive is on a windows system, right? I am asking because if it is on a linux system, you should really use NFS, its alot faster, and native.

The server is a Mint-5 system. I have to use samba because I have a mixture of Linux & Windows machines.

[McLovin]

thats fine, but you do not need to mount samba shares in another linux distro, if you are doing linux to linux use nfs, it is much better for that purpose, you do not need to use samba on the host machine, only the server. I use samba on my server, as i have windows installed on one of my partitions, but in linux i use all nfs, so my server is running nfs, and samba, but my linux hosts are running only nfs. there are alot of great tutorials on how to set-up nfs so that your network, (nfs) shares automount on boot, and your shares also automount on windows with samba. if you need more help, I can help you out, as this is how my server is configured, just let me know.

[kwisher]

thats fine, but you do not need to mount samba shares in another linux distro, if you are doing linux to linux use nfs, it is much better for that purpose, you do not need to use samba on the host machine, only the server. I use samba on my server, as i have windows installed on one of my partitions, but in linux i use all nfs, so my server is running nfs, and samba, but my linux hosts are running only nfs. there are alot of great tutorials on how to set-up nfs so that your network, (nfs) shares automount on boot, and your shares also automount on windows with samba. if you need more help, I can help you out, as this is how my server is configured, just let me know.

The point is that Mint-6 or Ubuntu has broken something that worked in the previous release. In fact I have been using Samba on my network in this manner since my first Linux install of Fedora-4 years ago. I wanted to bring this issue to the Mint team and was hoping for an explanation of the problem. If NFS is my only option then I will pursue it.

[kwisher]

Any comment from the developers would be appreciated.

Thanks

[kwisher]

After digging around on the Ubuntu forum I believe I have found the solution to this problem. The thread is here:
http://ubuntuforums.org/showthread.php?t=293513

I guess it boils down to a blame game between the init dev's and the samba dev's at Debian. The cifs driver does not unmount the samba shares before the network shuts down. To fix the problem enter the following commands from a terminal as root:

Code: Select all

ln -s /etc/init.d/umountnfs.sh /etc/rc0.d/K15umountnfs.sh
ln -s /etc/init.d/umountnfs.sh /etc/rc6.d/K15umountnfs.sh

Hope this helps.

[tawan]

Just booted Felicia and I have noticed that it takes a long time to shut down my system..

From the time I click "Shut Down," watch the splash screen and another blank screen with a blinking cursor in the top left; until my computer is completely off it's been 2 minutes. Just seems like a long time to shut down doesn't it?

Is it a Felicia thing, or is it just me?

BTW, I've updated all level 2 updates available and I am currently trying to install proprietary video card drivers.

Solution from here:

Code: Select all

gksudo gedit /etc/init.d/alsa-utils

The file opens in Gedit and around the line 353 you'll find the instruction "stop)". Below this instruction you should add these two instructions:

ifconfig wlan0 down
ifconfig eth0 down

So, the file should be this way:

stop)
ifconfig wlan0 down
ifconfig eth0 down
EXITSTATUS=0

---

That fixed the problem for me and others.

...