Thanks to all of you who have replied. I tried all sort of things but the
machine still hangs...
Here`s my original question followed by the answers:
>Hello,
>After a Kernel rebuild (in single user mode), after I move the new kernel
to >/vmunix and I issue the command "shutdown -r now", I get a message
telling me >that the system is going down and the computer freezes. I tried
with the HALT >command instead, and then a "b"oot and this works. What is
the problem ?
>I use and AlphaServer 2100RM with a VGA card. I'm running DU3.2D
====================================================================
sjenkins_at_iastate.edu:
Typically shutdown wants to write to /var/adm/utmp, which is often in
/usr on a separate partition, so it's quite possible that in single-user
mode you don't have /usr mounted, so shutdown hangs. At least, I've
noticed that happen to me before..
======================================================================
Sheila Hollenbaugh <shollen_at_valhalla.cs.wright.edu>:
In some versions of DU, if you are running LAT the system will hang
going down. Try doing "latcp -h" right before the reboot to see if
this helps.
======================================================================
From: alan_at_nabeth.cxo.dec.com:
This may be a bug specific to V3.2D, so check the CSC
to be sure. If it is there is bound to be a patch by
now.
I have seen a similar symtom on older systems because
the system tries to dismount all the file systems too
early in the shutdown. Since I often reboot a system
remotely and have processes open on NFS file systems
the NFS file system can't be unmounted and the shutdown
hangs. Halt works because it does a bit more work when
cleaning up the system. The reboot command will also
work much like halt, saving you the "boot" step.
=======================================================================
I have had the same problem from time to time under ULTRIX.
If you leave it then it will come good. If you are more impatient (as I am)
then you can run sync a couple of times to write everything to disk, then
unmount all unecessary drives (or you can do it the other way around).
When you run one of these commands - the response will probably be quite
slow. This will indicate that this is the command that is causing shutdown a
problem. I usually find a remote machine has been mounted and the connection
has been lost for whatever reason - thus the shutdown command can't stop the
mount command cleanly.
Don't use halt unless you need to - you risk corrupting your partitions
because the buffers in memory may not have been written to disk.
Bruce Whittaker.
Received on Sun May 12 1996 - 02:29:22 NZST