SUN V880 OBP阶段挂死
各位好：客户那边一台v880很久没用了，今天利旧，重新加电后最大化自检通过，进行至OBP阶段就挂死，强制进入OK后无法boot,报错如下请各位大侠分析分析！！！
0>Turn DAR errors on
0>Turn error traps on
0>INFO:
0> POST Passed all devices.
0>POST: Return to OBP.
CPU0: System Power On Selftest Completed
Pass/Fail Status= 0000.0000.0000.0000
ESB Overall Status= ffff.ffff.ffff.ffff
<*>
POST Reset
@(#)OBP 4.10.8 2003/07/25 08:42 Sun Fire 880
Front Panel Keyswitch is in Diagnostic position.
Online:CPU0 Ultra-III+ (v2.3) 6:1 900MHz 8MB 3:1 ECache
Online:CPU1 Ultra-III+ (v2.3) 6:1 900MHz 8MB 3:1 ECache
Online:CPU2 Ultra-III+ (v2.3) 6:1 900MHz 8MB 3:1 ECache
Online: *CPU3 Ultra-III+ (v2.3) 6:1 900MHz 8MB 3:1 ECache
Configuring CPUs..........
... CPU0 Rated Speed 900MHz, Safari 150MHz, want 6:1, got 6:1 ==> CPU 900MHz
Ecache 8MB 3.3ns mode=4-3-3 2-way ECCR: 0000.0000.0329.4400
... CPU1 Rated Speed 900MHz, Safari 150MHz, want 6:1, got 6:1 ==> CPU 900MHz
Ecache 8MB 3.3ns mode=4-3-3 2-way ECCR: 0000.0000.0329.4400
... CPU2 Rated Speed 900MHz, Safari 150MHz, want 6:1, got 6:1 ==> CPU 900MHz
Ecache 8MB 3.3ns mode=4-3-3 2-way ECCR: 0000.0000.0329.4400
... CPU3 Rated Speed 900MHz, Safari 150MHz, want 6:1, got 6:1 ==> CPU 900MHz
Ecache 8MB 3.3ns mode=4-3-3 2-way ECCR: 0000.0000.0329.4400 Done
<*>
CPU Configuration Reset
@(#)OBP 4.10.8 2003/07/25 08:42 Sun Fire 880
Front Panel Keyswitch is in Diagnostic position.
Online:CPU0 Ultra-III+ (v2.3) 6:1 900MHz 8MB 3:1 ECache
Online:CPU1 Ultra-III+ (v2.3) 6:1 900MHz 8MB 3:1 ECache
Online:CPU2 Ultra-III+ (v2.3) 6:1 900MHz 8MB 3:1 ECache
Online: *CPU3 Ultra-III+ (v2.3) 6:1 900MHz 8MB 3:1 ECache
Mungeing Memory...........Done
HiMem: 0000.00b0.0000.0000, size: 0000.0001.0000.0000
Configuring Memory........ CPU0 CPU1 CPU2 CPU3 Done
Init ICache/etc........... CPU0 CPU1 CPU2 CPU3 Done
Init ECache Tags.......... CPU0 CPU1 CPU2 CPU3 Done
Clearing TLBs............. CPU0 CPU1 CPU2 CPU3 Done
......
......
tftp SUNW,i2c-ram-device
SUNW,fru-device
Loading onboard drivers: ebus flashprom bbc power i2c fru fru fru fru
fru fru fru fru fru fru fru fru fru fru fru fru fru fru fru fru fru
fru fru fru fru fru fru fru fru fru fru fru fru fru fru fru i2c
controller smbus-ara controller controller controller temperature
temperature temperature ioexp temperature adio adio ioexp ioexp
ioexp ioexp ioexp ioexp ioexp ioexp ioexp adio adio adio adio
temperature-sensor temperature-sensor fru fru fru fru fru fru fru
rscrtc hotplug-controller hotplug-controller hotplug-controller
hotplug-controller bbc i2c i2c nvram idprom rtc gpio pmc rsc-control
rsc-console serial
Probing /pci@8,700000/pci@5 Device eNothing there
Probing /pci@8,700000/pci@5 Device fNothing there
Probing /pci@9,600000 Device 1scsi disk tape scsi disk tape
Probing /pci@9,600000 Device 2Nothing there
Probing /pci@9,700000 Device 1network usb
Probing /pci@9,700000 Device 2Nothing there
Probing /pci@9,700000 Device 3Nothing there
Probing /pci@9,700000 Device 4Nothing there*************到此处挂死**********
{3} ok
{3} ok boot
FATAL: OpenBoot initialization sequence prematurely terminated.
FATAL: system is not bootable, boot command is disabled
{3} ok This type of a warning can appear on systems such as a Sun Fire V880.
In most cases, this warning occurs at the OBP "ok" prompt if the power-up initialization (right after the banner was displayed) was aborted. Usually, this is done by using the Stop-A keystroke (XIR Reset). If after such an occurrence "boot" command is executed, the system displays the following error:
{1} ok boot
FATAL: OpenBoot initialization sequence prematurely terminated.
FATAL: system is not bootable, boot command is disabled
The system at that point does not boot. In most cases, this just means that since the proper initialization of the machine wasn't allowed to complete, the system is unable to boot. This is done to make sure that OS deamons (such as picld) do not have problems as they start up during boot (because of the improperly initialized memory, etc.). To get the machine to boot properly, issue the "reset-all" command. If for whatever reason there is a need for the "boot" command to be executed manually, please run the following command sequence at the "ok" prompt:
oksetenv auto-boot? false
okreset-all
Now, the machine will reset. Allow it to fully initialize. It will then give the ok prompt without booting automatically. At this point if the "boot" command is manually executed, it should work without errors. Also, before running the manual boot, the "auto-boot?" variable could be set back to "true". This way, the system will again be set back to its original setting for the next time it is reset or power cycled. NOTE: Seeing the "FATAL: system is not bootable ..." message even after following the above procedure most likely indicates a real problem (possibly a hardware problem) with that machine. Another possibility may be an invalid setting. If you suspect this you can use the following procedure. This procedure resets all parameters to factory default settings, so use caution.
okprintenv ### save this information ###
okset-defaults ### to reset all parameters to factory default settings ###
okreset-all
谢谢蜘蛛大哥，下午去现场试一把，有什么信息马上反馈回来。
个人的一点怀疑，会不会是保存OBP的类似象NVRAM的芯片坏了造成的。
当时收集的printenv信息
{3} ok printenv
Variable Name Value Default Value
test-args
diag-passes 1 1
local-mac-address? false false
fcode-debug? false false
silent-mode? false false
scsi-initiator-id 7 7
oem-logo No default
oem-logo? false false
oem-banner No default
oem-banner? false false
ansi-terminal? true true
screen-#columns 80 80
screen-#rows 34 34
ttyb-rts-dtr-off false false
ttyb-ignore-cd true true
ttya-rts-dtr-off false false
ttya-ignore-cd true true
ttyb-mode 9600,8,n,1,- 9600,8,n,1,-
ttya-mode 9600,8,n,1,- 9600,8,n,1,-
output-device screen screen
input-device keyboard keyboard
auto-boot-on-error? false false
load-base 16384 16384
auto-boot? false true
boot-command boot boot
diag-file
diag-device net net
boot-file
boot-device /pci@8,600000/SUNW,qlc@2 ... disk net
use-nvramrc? false false
nvramrc devalias vx-rootmirr /pc ...
security-mode none No default
security-password No default
security-#badlogins 0 No default
diag-out-console false false
post-trigger error-reset power-on-res ... error-reset power-on-res ...
diag-script normal normal
diag-level max min
diag-switch? false false
obdiag-trigger error-reset power-on-res ... error-reset power-on-res ...
error-reset-recoveryboot boot
{3} ok setenv diag-levle min
Unknown option: diag-levle
{3} ok setenv diag-level min
diag-level = min
{3} ok
{3} ok
{3} ok
{3} ok poweroff
poweroff ?
{3} ok power-off
是否路径没做修改
probe-scsi-all
devalias
boot+绝对路径试试 在OK状态看show-post-results ;
然后probe-scsi-all，从硬盘绝对路径引导。
页:
[1]