Filter
Top Products
144 Chapter 7
Recovering from failures
System panics
Step 4. If the system does not reboot by itself, reboot the computer by issuing the
reset command in the console window or do_reset command at the
ksh-shell window. For more information about rebooting the system see
“Rebooting the system” on page 146.
If the problem reappears, it might be necessary to have the problem fixed
by Hewlett-Packard service personnel.
File system problem
If the panic message indicates a problem with one of the file systems,
reboot the system and run the file system checker fsck to check and
correct the problem. Follow all directions that fsck displays. Especially
when the root file system (the one with the / directory) has problems, it is
important to use the -n option to the reboot command, right after fsck
completes. fsck is normally run automatically at boot time. See
“Rebooting the system” on page 146.
LAN communication problem
Use the following procedure if the panic messages indicate a problem
with LAN communication:
Step 1. Check LAN cable and media access unit (MAU) connections.
Step 2. Ensure that all vampire taps are tightly connected to their respective
cables.
Step 3. Ensure that the LAN is properly terminated. Each end of the LAN cable
must have a 50-ohm terminator attached. Do not connect the system
directly to the end of a LAN cable.
If the problem reappears or if the hardware failure appears to be
associated with a LAN card or an internal component of the V-Class
server, it might be necessary to have the problem fixed by Hewlett-
Packard service personnel.