Solaris

Dear All

I am getting these error while I boot the Netra 440 server. Could anyone tell me what can be the problem


Regards


Copyright 2004 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.


Sun(tm) Advanced Lights Out Manager 1.5.4 (indcc01ma02)

Please login: admin
Please Enter password: *****


sc> console -
Error: Invalid command option
Usage: console [-f]
sc>
Invalid command. Type 'help' for list of commands.
sc> console -f
Warning: User <admin> currently has write permission to this console and forcibl
y removing them will terminate any current write actions and all work will be lo
st. Would you like to continue? [y/n]y
Enter #. to return to ALOM.

Could not read diag-switch? from NVRAM!
Could not read diag-level from NVRAM!
Could not read diag-script from NVRAM!
ERROR: Could not read aft pins!
Could not read security-mode from NVRAM!
Could not read service-mode? from NVRAM!
Could not read diag-trigger from NVRAM!
Could not read verbosity from NVRAM!
ERROR: Could not read keyswitch!
@(#)OBP 4.18.10 2006/03/03 13:57 Sun Fire V440,Netra 440
Clearing TLBs
Power-On Reset
Executing Power On Self Test
0>
0>@(#) Sun Fire[TM] V440,Netra[TM] 440 POST 4.18.10 2006/03/03 14:17
/export/delivery/delivery/4.18/4.18.10/post4.18.0/Fiesta/chalupa/integrat
ed (root)
0>Copyright © 2006 Sun Microsystems, Inc. All rights reserved
SUN PROPRIETARY/CONFIDENTIAL.
Use is subject to license terms.
0>Hard Powerup RST thru SW
0>OBP->POST Call with %o0=00001000.01ff2000.
0>Diag level set to MIN.
0>Verbosity level set to MAX.
0>I/O port set to TTYA.
0>Start Selftest.....
0>CPUs present in system: 0 1 2 3
0>Test CPU(s).....
0>Init SB
0>Initialize I2C Controller
0>
0>INFO: INFO: FIRE-I Version < 1.0. Cannot Run Diags
0>
0>ERROR: TEST = Initialize I2C Controller
0>H/W under test = Motherboard I2C
0>Repair Instructions: Replace items in order listed by 'H/W under test' above.
0>MSG =


ERROR:3 AFSR Error 00204000.00000000, AFAR 00000000.0000e950.


0>END_ERROR

0>Decode of afsr bits 00204000.00000000
0> ME Bit: Multiple errors of same type occured.

0> UMS Bit: Error due to unsupported store

0>
0>
0>ERROR: TEST = Initialize I2C Controller
0>H/W under test = Motherboard I2C
0>Repair Instructions: Replace items in order listed by 'H/W under test' above.
0>MSG = Fatal CPU error on master, rolling over to new master.
0>END_ERROR

1>Soft Power-on RST thru SW
1>OBP->POST Call with %o0=00001000.01ff2000.
1>Diag level set to MIN.
1>Verbosity level set to MAX.
1>I/O port set to TTYA.
1>Start Selftest.....
1>CPUs present in system: 1 2 3
1>Test CPU(s).....
1>Init SB
1>Initialize I2C Controller
1>
1>INFO: INFO: FIRE-I Version < 1.0. Cannot Run Diags
1>Init CPU
1>DMMU
1>DMMU TLB DATA RAM Access
1>DMMU TLB TAGS Access
1>IMMU Registers Access
1>IMMU TLB DATA RAM Access
1>IMMU TLB TAGS Access
1>Init mmu regs

I am also getting these errors




0> start self test
0>Cpu present in system :0,1
0>Init sb
0>Initialize I2C controller
0>
0> Info:Info Fire I version <1.0 cannt run diags

0> Error: Test= Initialize I2C controller
0> H/W under test= Motherboard I2C
0> Repair Instruction: replace items in order listed by "H/W under test" above
0> MSG=
ERROR:3 afsr ERROR 00204000.00000000 , aFAr. 000000000.0000E950.

0>eND ERROR
0> dECODE OF AFSR bits 00204000.00000000
0> ME bit: Multiple errot of same type occured

0> UMS bit: Error due to unsupported store



-----------------------------------------------------------------------------------------------------------------------------------------------

Msg= Fatal error on Mater, rolloing over to new master


enter# to return to ALOM

3.> Waiting for Master cpu=2 , timeout in 134 sec
Error test=slave spin
h/w under test =motherboard,cpu(system initialization)
repair instruction:replace items in order listed by h/w under test above
MSG=error :timeout waiting for master ,doing reconfig reset


SC alert :host power-on failed system power ok, open boot not responding?from NVram
Error could not keyswitch.

The nvram chip seems to be corrupt.. Are you able to get to the ok> prompt at all? If yes, try a reset-all. set the diag-switch to false and diag-level to min before you do a reset-all. If you cant even get the OBP, I suppose your nvram is gone, need to replace

> H/W under test= Motherboard I2C
this could mean that your system board has died (if you cant even get to the OBP) or a possible nvram corruption

Thanks for The advice incredible

how can u know that u have all permission with your admin acount ? this is probabelly the problem

Thhis got nothing to do with the hardware errors that you get

This got nothing to do with the hardware errors that you get