PDA

View Full Version : Won't reboot 9 out of 10 times...



muzicman0
Mar 12th 2009, 01:46 AM
90% of the time, a reboot or restart hangs before a complete shutdown on 9.04...any ideas on what to try?

mm0

Rog131
Mar 12th 2009, 09:38 AM
Do you get error messages ?


Something to try: Take the splash (usplash) off

1) Backup your /boot/grub/menu.lst
2) Edit your /boot/grub/menu.lst

Alt+F2 and kdesudo kate /boot/grub/menu.lst

There should be something like:

title Ubuntu jaunty (development branch), kernel 2.6.28-9-generic
uuid 63f41b2a-9ea8-449a-b723-e5233ac92896
kernel /boot/vmlinuz-2.6.28-9-generic root=UUID=63f41b2a-9ea8-449a-b723-e5233ac92896 ro quiet splash
initrd /boot/initrd.img-2.6.28-9-generic

remove "splash" from the kernel line. Save and exit kate.

After this Kubuntu should start and shutdown without splashscreens and you should see the warnings and errors.


A possible workaround: use an external shutdown utility. I have been using kshutdown, it is in the repositories.

Package: kshutdown

an advanced shut down utility for KDE

It has 4 main commands:

- Shut Down (logout and halt the system),
- Reboot (logout and reboot the system),
- Lock Screen (lock the screen using a screen saver),
- Logout (end the session and logout the user).

It features time and delay options, command line support, wizard, and sounds.

> KShutdown (http://kshutdown.sourceforge.net/) home
> KShutdown (http://www.kde-apps.org/content/show.php/KShutdown?content=9754) kde-apps

muzicman0
Mar 15th 2009, 05:11 PM
OK, so I disables the splash...

It is failing to kill all remaining processes, and the last thing I see before it halts is Mount: / is busy

Anything else I can try to isolate the problem?

mm0

flarson
Mar 15th 2009, 06:24 PM
That is an interesting line "/ is busy". The init system should get through that eventually but depending on what the problem is it might take a while. Do you have some disks mounted via smbfs? This looks like there is a mount that is stopping / from unmounting. This seems to be happening to a lot of people. I wonder if it could be from filesystems that are accessed through dolphin?

muzicman0
Mar 15th 2009, 06:37 PM
yes, i do have some samba shares mounted...is there a workaround?

flarson
Mar 15th 2009, 06:39 PM
I don't know, but identifying the problem would certainly help. Try manually unmounting the shares and see if it will reliably reboot. If it does we may be able to figure something out.

utkjamie
Apr 18th 2009, 05:09 AM
Any luck with this? I have yet to have a successful Jaunty reboot.

flarson
Apr 18th 2009, 04:22 PM
I have a laptop that I installed from the Alpha 6 CD which has not been rebooting either, while a desktop installed from a Beta nightly does reboot just fine.

With the laptop it would stop KDM and go to a black screen, blink a cursor a few times and then nothing. At that point CTL-ALT-DEL would cause it to print one line about stopping md devices (software raid, of which I have none) and it would then reboot.

I just now edited /boot/grub/menu.lst and removed quiet and splash from the default options and ran sudo update-grub. Now I see the normal boot messages, but also it shuts down properly, whether I use a GUI or command line.

flarson
Apr 18th 2009, 09:29 PM
I have done a little experimenting and digging and have come up with a few things. Although I am sure I don't entirely understand them yet my Sony Vaio (Core2 Duo, 64 bit) now reboots and shuts down reliably.

I first removed the quiet and splash options so I could see what was happening and the first thing I see is a message from iwlagn ( Intel wireless AGN adapter) that it is in deep sleep followed by a register dump and then it stops. But sometimes I get to where I see "Will now reboot" or "Will now halt" which come from thelast scripts to run when entering runlevel 6 or 0 respectively, for reboot or halt.

Looking at that I find that it ends up calling either reboot or halt with a -d option that is not supported in the Kubuntu version of this command. It is also calling it, at least sometimes, with -i (shutdown network interfaces) which linux does anyway. So I removed those option from the reboot script and it worked, but it would still not halt. So I removed those options from the halt script and it works also.

Meanwhile, on my desktop Pentium D, with no wireless, the same scripts work just fine and always has.

muzicman0
Apr 19th 2009, 12:10 AM
I ended up going 32 bit install, and it works good now...