2.
From the siconsole, select the server.
■
If the system fails to respond, go to step 3.
■
If the system takes you to the server OS console, issue the command:
bt
active
, so you can view the display.
■
If you are still at the siconsole, select
q
, press
Return
, and then perform the
following steps:
1.
Connect directly to the MMB as manager using ssh.
2.
If the connection succeeds, you are taken to the server OS console, where
you issue the command:
bt active
3.
If the connection fails, continue to step 4.
3.
Connect to the system with a serial null modem cable, and perform the following
steps:
See
if you need details.
1.
Login as manager or you will get the Linux prompt, not the server OS.
If you use root, use
ssc localhost
.
2.
Issue the command:
bt active
4.
If you are still unable to get to the server OS, perform the following steps:
1.
Check to make sure that the Bali CLI is booting successfully.
2.
Log in through the serial cable connection.
3.
Tail
/var/opt/mercury-main/logs/dblog
4.
Search the log for the entry
MFB.ini not found run nas-preconfig
.
■
If the entry is present, the system has been
unconfigured
by either running
the
unconfig
script or removing the node from a cluster.
■
If the entry is not present, monitor the
dblog
during the boot cycle to see
where it fails.
Warning:
If the server is still unresponsive, do not pull the plug. Instead,
see the next step. The reboot time varies from system to system. The
reboot can take up to 20 minutes, because a dump is compiled during
the reset process.
5.
Check the green LED on the front panel of the server for the server status.
Restarting an unresponsive server
Chapter 6: Rebooting, shutting down, and powering
off
Hitachi NAS Platform and Hitachi
Unified
Storage Series 4000 Hardware Reference
83