b. Log in through the serial cable connection.
c. Tail
/var/opt/mercury-main/logs/dblog
.
d. 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 by 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 process 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.
6. If the green LED is flashing 5 times per second, plug in the serial cable.
■
If the terminal screen is generating output, let the process complete.
■
If the terminal screen is blank, press the Reset button.
Note: Pulling the power cord from the server is not recommended.
Do not pull the power cord unless it is absolutely necessary. First,
complete the steps above.
Powering down the server
Follow this procedure whenever a server is about to be powered down for shipment or
storage, and will be left off for more than a day. If the system is being restarted or
power-cycled, this procedure is not required.
Contact your representative for special instructions if servers will be in storage for more
than one year.
Procedure
1. From the NAS Platform operating system console, enter the command:
shutdown
--powerdown
2. Wait until the rear panel LEDs turn off.
Note: The PSUs continue to run and the PSU LEDs stay on.
3. Power down the server by removing the power cables from the PSU modules.
Powering on the server or cluster
To start/power on a server or cluster:
Powering down the server
Chapter 6: Rebooting, shutting down, and powering off
Hitachi NAS Platform Series 5000 Hardware Reference
48
