Handling of Abnormal PowerDown of OMCR Server

ZTE Corporation

Legal Information

Copyright 2006 ZTE CORPORATION.

The contents of this document are protected by copyright laws and
international treaties. Any reproduction or distribution of this document or any
portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this
document are protected by contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or
registered trade or service marks, of ZTE CORPORATION or of their respective
owners.
This document is provided as is, and all express, implied, or statutory
warranties, representations or conditions are disclaimed, including without
limitation any implied warranty of merchantability, fitness for a particular
purpose, title or non-infringement. ZTE CORPORATION and its licensors shall
not be liable for damages resulting from the use of or reliance on the
information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual
property rights or applications covering the subject matter of this document.
Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire
any license to the subject matter herein.
The contents of this document and all policies of ZTE CORPORATION,
including without limitation policies related to support or training are subject
to change without notice.

Preface
During the running procedure of OMCR server, power-down may occur due
to power supply system fault or other reasons. This document introduces the
basic method of handling possible file system faults after power-down occurs.

Contents
Chapter 1 Handling of Abnormal Power-Down of OMCR Server..............................................1
1.1 Possible Faults due to Abnormal Power-Down.......................................................................1
1.2 Handling of Faults due to Abnormal Power-Down.................................................................1

Chapter 1 Handling of Abnormal

Power-Down of OMCR Server
1.1 Possible Faults due to Abnormal Power-Down
Power-down suddenly occurring during the OMCR server running procedure
while the system is implementing disk read/write operation at the moment
will cause file system integrity damage and file system inconsistency. If the
file system check fails after restarting the server, the system will prompt the
administrator to log on in single user mode to implement file system check
and correction.

1.2 Handling of Faults due to Abnormal Power-Down

After confirming the power supply is restored, handle the faults according to
the following steps:
1 If there exists disk array, turn on the disk array power first.
2 Turn on the server again;
FUJITSU server: Before turning on the power, make sure the DIP
switch on the server panel is put to the lock state (there are three states
in total: maintenance, unlock, lock), then press the power button to
turn on the server.
SUN server: Usually, put the turn-on key to the ON position, and then
turn on the power, the DIP switch on the server panel should also be
put to the lock state
3 Wait the server self-test to complete. The servers power-on self-test
procedure is usually between 3 to 4 minutes. After the self-test
completes, the system automatically enters the start flow. Input boot
to enter the start flow if system is kept in the state with ok> prompt.
4 The file system will be checked when the server is starting. If there are
no such file system errors that cannot be automatically corrected, the
server will continue starting and completes starting. If there are
serious file system errors, the system will prompt the user to log on as
the root user to enter single user mode to implement system
maintenance manually (or press ctrl+d to enter common start
procedure).
1

5 If the system prompts the user to enter single user mode to implement
system maintenance, input the root user and password.
6 Input fsck y under the # prompt to implement file system check and
correction:
#fsck -y
** /dev/rdsk/c0t0d0s0
** Last Mounted on /
** Phase 1 - Check Blocks and Sizes
** Phase 2 - Check Pathnames
** Phase 3 - Check Connectivity
** Phase 4 - Check Reference Counts
** Phase 5 - Check Cyl groups
7 files, 14 used, 279825 free (17 frags, 347891 blocks, 0.0%
fragmentation)

The system will check file system for each partition and correct errors
automatically if there is any.
Run fsck y twice to thrice after a check completes to make sure all
errors are corrected.
7 Run the command reboot to restart the system after file system check
is completed.
# reboot