Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

node hangs on 554

Status
Not open for further replies.

RBOLLEN

Technical User
Mar 7, 2001
43
NL
Hello,

I have a RS/6000 connected to Control Workstation and it hangs during boot with LED code 554, how can I reboot this node in maintenance shell? Aix 433 installed.

Thanx,
Rudy
 
Is this an SP node ? Please clarify your statement "RS/6000 connected to a control workstation".

Boot info AIX as normal, and when the "speaker scsi memory"... screen comes up, press the "5" key (on ASCII terminal) or the "F1" key on graphic terminals.
 
Yes this is a SP-node, so I have also no direct keyboard or terminal attached on this node.
 
But yo can do a s1term while the system is booting. Let me see...554 is boot device not found or NFS swap space not found.

What has changed ?

From your CWS, send me the result of "splstdata -v".

:cool:
 
You didn't say if it was a mca node or a pci node....
======================

you have a serial cable from you cws to the node or frame?
that is your terminal for the node..

you can get to service with the spmon -k service node1
spmon -p off node1
spmon -p on node1
you have the s1term -w 1 1 (frame1 node1 )

What caused the 554 is the issue....probably a disk gone bad? or corruption
is possible I guess...
 
From the AIX Version 4.3 Messages Guide and Reference :

Display Value 554

Explanation
The IPL device could not be opened or a read failed (hardware not configured or missing).
System Action
The system halts.
User Action
Go to "Hardware Diagnostics" in in AIX Problem Solving Guide and Reference to determine if there is a problem with the device where the files reside.

If these procedures do not find a problem with a device, the problem is usually due to bad information on the boot logical volume, or the log logical volume (/dev/hd8) has been damaged.

To correct the problem with the boot logical volume, enter Maintenance mode (refer to "Accessing a System That Will Not Boot" for information on loading the Maintenance mode onto your system), then run the savebase command. When the savebase command completes, issue the sync; sync command. After this command completes, restart the system in Normal mode.

If this does not correct the problem, reenter Maintenance mode and enter the /usr/sbin/logform /dev/hd8 command. When this command completes, restart the system in Normal mode.

If you are not familiar with this mode or are unable to correct the problem, report the problem to your software service organization, and then stop. You have completed these procedures.

... for what it's worth. Maybe a bit late though :(

B.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top