I had this same problem but all I needed to do was remove "Shut Down via gdm." from the halt option. Since doing this ubuntu shuts down or reboots without any problems and seems to be a permanent fix to my problem. I have tried re adding "Shut Down via gdm." to the halt option to see what happens and the system shutsdown as its meant to. So what does "Shut Down via gdm." do?
I can add to this bunch. Hardy shutdown gets fixed if I set a static IP for the box, which I always do (eventually).
When first installed, I set a static IP like I always do and never had a shutdown problem (I had a static IP). I reinstalled Hardy for another reason AND HAD THE SHUTDOWN PROBLEM. Eventually I set a static IP and viola!... the shutdown problem is history.
Obviously, all these bandaids have a root cause. This is just MY bandaid.
Expert Opinions $5 Shutup $10
I too had this shut down problem on my Acer 4152 Laptop....
post #13 solved my problem.....
Well the solution stated in Post #13 does work, but the problem as others have pointed out is that it needs to be done everytime u restart or halt the system, and thatz buggy. I felt that there must be some problem with the reboot and shutdown scripts and did play around with them a bit and it soved the problem. But I am not a linux expert so cant tell why it works. Any this is what I did.
In /etc/init.d there is a file by the name reboot which is the script for rebooting the system..........well thatz what I feel......if itz wrong plz do correct me.........There is a line of code in it
reboot -d -f -i which seems to be the problem maker..........
for those of you who have the problem with the network not stopping correctly due to which the system does not reboot or halt I suggest remove the last part of the line -i which tries to iteratively stop the network devices. That should solve most of the problem.
Another solution that works on system is to change that line of code with
/sbin/shutdown -r now
well and a funny thing about the reboot command is that in its man page there is no description about the command modifier -d which points to something buggy in its coding ?????
Last edited by girishsasikumar; May 11th, 2008 at 08:28 AM.
Thank you very much. I haven't had problems with rebooting, only shutting down (no idea why), so in the file /etc/init.d/halt I changed the line
toCode:halt -d -f -i $poweroff $hddown
and my computer shut down for the first time in a week (or two, or whatever). It's rather amazing, and it's *buntu generic.Code:halt -d -f $poweroff $hddown
cant wait to give it a try, thanks for the infos and heads up
Fascinating. I suspect reboot option "-i" in the scripts is on top of what I'm seeing, too.
I first discover if I have a mounted windows share I get the slow shutdown. This is a share in /mnt, cifs via a mount command (not the Nautilus stuff). Just a umount prevents the slow shutdown.
Next, I discover as long as NetManager is not set to this "Roaming Mode" (whatever the heck that is) then all is well again, too. Even set straight DHCP or STATIC IP is ok - only "Roaming" gets the slow shutdown.
The terminal message during slow shutdown:
[ ***.****] CIFS VFS: server not responding
[ ***.****] CIFS VFS: No response for cmd 50 mid 11 (or 9)
More things I see:
I'd like to understand more before hacking at /etc/init.d scripts. BUT...
Man page says on the reboot -i option: "On Linux, this is unnecessary as the kernel will do this anyway." Hmmm...
And YES... why doesn't the packaged man page for reboot NOT cover -d? Is this just some sloppy packaging?
Expert Opinions $5 Shutup $10