sun T5140各种方法都试了就是进不了OK模式该怎么办

z191837954

-> set /HOST/bootmode script="setenv auto-boot? false"
Set 'script' to 'setenv auto-boot? false'

-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y

Serial console started.  To stop, type #.

Serial console stopped.

-> reset /SYS
Are you sure you want to reset /SYS (y/n)? y
Performing hard reset on /SYS

-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y

Serial console started.  To stop, type #.



Serial console stopped.

-> set /HOST send_break_action=break
Set 'send_break_action' to 'break'

-> start /SP/console
Are you sure you want to start /SP/console (y/n)? y

Serial console started.  To stop, type #.

c)ontinue, s)ync, r)eset? c
SUNW-MSG-ID: SUNOS-8000-0G, TYPE: Error, VER: 1, SEVERITY: Major
EVENT-TIME: 0x53ec48cb.0x0 (0xe5000baa3b)
PLATFORM: SUNW,T5140, CSN: -, HOSTNAME: t5140-2
SOURCE: SunOS, REV: 5.10 Generic_138888-01
DESC: Errors have been detected that require a reboot to ensure system
integrity.  See http://www.sun.com/msg/SUNOS-8000-0G for more information.
AUTO-RESPONSE: Solaris will attempt to save and diagnose the error telemetry
IMPACT: The system will sync files, save a crash dump if needed, and reboot
REC-ACTION: Save the error summary below in case telemetry cannot be saved


panic[cpu67]/thread=2a103155ca0: Fatal error has occured in: PCIe root complex.(0x10)(0x0)

000002a1031bdd50 px:px_err_panic+1ac (1940c00, 1346800, 0, 2a1031bde00, 10, 0)
  %l0-3: 0000000000000000 00000600340daf40 000000e50006f354 0000000000000001
  %l4-7: 0000000000000000 0000000001872000 0000000000000001 0000000000000000
000002a1031bde60 px:px_err_intr+158 (3, 3, 1, 33, 1, 1941800)
  %l0-3: 0000000000000001 0000000000014000 0000060040f7b6c8 000003000377b540
  %l4-7: 0000000000000010 0000000000000000 0000030001e212b0 0000000000000001
000002a1031bdf50 unix:current_thread+164 (d, f, d, 10, 1063148, 30004752000)
  %l0-3: 0000000001009908 000002a103154dc1 000000000000000e 000000007001ac80
  %l4-7: 00000600333fc808 000000dfcfa9ccde 000000000000000d 000002a103155670
000002a103155710 unix:cpu_idle_self+a4 (2a1031551e1, 0, 1063148, 30004752000, 0, 10c)
  %l0-3: 000000000000010c 0000000001835234 0000000000000001 0000000001835000
  %l4-7: 0000000000000043 0000000000000043 0000030004752000 0000000000000008
000002a1031557e0 unix:ktl0+64 (16, 8, 0, 7bff3afaf49bd7e5, 0, 12)
  %l0-3: 0000030004752000 0000000000000218 0000000080001604 000000000101b950
  %l4-7: 00000000018a7400 0000000000000058 0000000000000000 000002a103155890
000002a103155930 unix:cpu_halt+14c (1b, 18787e0, 43, 18786a8, 30004752000, 1)
  %l0-3: 00000600333ac89c 0000000000000000 0000000000000016 0000000000000001
  %l4-7: 0000000001000000 0000000000000002 0000000000000001 0000000000000008
000002a1031559e0 unix:idle+128 (182a400, 0, 30004752000, ffffffffffffffff, 44, 1829400)
  %l0-3: 00000600333ac878 000000000000001b 0000000000000000 ffffffffffffffff
  %l4-7: 0000030004752000 0000000000000000 000002a103155ca0 000000000104118c

syncing file systems... 1 done
ereport.io.fire.epkt ena=10782ab927f10c01 detector=[ version=0 scheme="dev"
device-path="/pci@500" ] sysino=53e ehdl=4310000000000002 stick=10782ab927f
rc_descr=
"Valid Epkt contents:
Block: 0x3, Op: 0x3, Phase: 0xe, Cond: 0x5
Dir: 0xf, Flags: STOP=0, H=0, R=0, D=0
M=0, S=0, Size: 0x0, Addr: 0x0
Hdr1: 0x0, Hdr2: 0x0, Res: 0x0
Err Severity: 0x10
"

dumping to /dev/md/dsk/d62, offset 860749824, content: kernel
100% done: 186001 pages dumped, compression ratio 7.71, dump succeeded
rebooting...
Resetting...


T5140, No Keyboard
Copyright 2008 Sun Microsystems, Inc.  All rights reserved.
OpenBoot 4.28.8, 32544 MB memory available, Serial #82000554.
Ethernet address 0:14:4f:e3:3a:aa, Host ID: 84e33aaa.



Type boot , go (continue), or login (command mode)
> go
Type boot , go (continue), or login (command mode)

这系统还能怎么装？ 谢谢

z191837954

> go
Type boot , go (continue), or login (command mode)
> continue
Firmware Password:
还有个这个固件密码

DC_楚楚

先不考虑进入到OK，因为你OBP设置了密码，没密码进不到的~ 忘记了就得换PROM了

貌似系统有问题，reset  /SYS 后， start /SP/console 看看完整的引导过程  

z191837954

回复 3# DC_楚楚


    哥  找到了  1 /SYS/MB           Host detected fault MSGID: SUN4-8000-0Y  UUID: 3ee32d84-b  就这个   是主板吗？

liuxitao0728

应该是做过安全加固吧，找找有没有security-mode，关闭security-mode应该就可以了，以前在m5000上遇到过。

DC_楚楚

回复 4# z191837954


    SUN4-8000-0Y - PCI-Express subsystem problem (文档 ID 1021357.1)

DETAILS

Predictive Self-Healing Article
SUN4-8000-0Y - PCI-Express subsystem problem

PCI-Express subsystem problem



Type

Fault
  fault.io.fire.asic
Severity

Critical
Description

A problem was detected in the PCI-Express subsystem.
Automated Response

This fault does not have an automated response agent and thus requires interaction from the user and/or Sun Services.
Impact

Loss of services provided by the device instances associated with this fault
Suggested Action for System Administrator

Schedule a repair procedure to replace the affected device. Use fmdump -v -u EVENT_ID to identify the device or contact Sun for support.

If this message occurs on a Sun Fire T2000 also refer to the NOTE at the end of the Details section below.
Details

The Message ID:  SUN4-8000-0Y indicates an internal parity error has occurred within the hostbridge. Use the fmdump -v -u EVENT_ID command to determine the faulty Field Replaceable Unit (FRU). As shown in the example below, the IOBD is identified as the failing component by the FRU:tag in the fmdump output.
fmdump -v -u f1ae0753-0981-6019-ca62-92125659ce6d
TIME                 UUID                                 SUNW-MSG-ID
Dec 31 21:32:09.6466 f1ae0753-0981-6019-ca62-92125659ce6d SUN4-8000-0Y
  100%  fault.io.fire.asic
         FRU: hc://product-id=SUNW,Sun-Fire-T200/component=IOBD
        rsrc: hc:///ioboard=0/hostbridge=0/pciexrc=1

Have this information available when contacting Sun Services for a repair.
NOTE - If this message occurs on a Sun Fire T2000, it may be because a required parameter has not been set in the /etc/system file. See the Sun Fire T2000 Server Product Notes available at the Sun Documentation Center for details (enter "Sun Fire T2000 Server Product Notes" in the Search Documentation box).

DC_楚楚

回复 4# z191837954


    PCIE卡的报错。
    可以尝试手动清除。

    T5xx0 用ALOM模式登录；

1、创建ALOM用户的方式：
-> create /SP/users/admin role=Administrator cli_mode=alom

2、登录ALOM用户
sc> clearfault uuid

DC_楚楚

liuxitao0728 发表于 2014-08-15 16:36
应该是做过安全加固吧，找找有没有security-mode，关闭security-mode应该就可以了，以前在m5000上遇到过。

这个security-mode也要在OBP下面关闭，现在忘记密码了，就没办法了

silencewangit

1. T5xx0 用ALOM模式登录
2. 然后在sc下poweroff , poweron
3. console -f
4. 当系统打印信息“HOST ID”的时候，及时按下“#”和“.”退到sc
5.退到sc后，输入break。

这样，系统就会进入到OK模式。

zhaopingzi

回复 8# DC_楚楚


    这个应该有方法吧。普通PC密码忘记可以放cmos电。