From: Steven Sim (steven.sim@faplccc.net)
Date: Tue Jun 06 2006 - 23:08:42 EDT
Gurus;
I have a Sun 6900 Domain whose root file system was corrupted by an
incorrect usage of ufsdump.
An attempt to boot from OK prompt gave the following messages;
Rebooting with command: boot
@SunOS Release 5.9 Version Generic_118558-06 64-bit
Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
TL = 1, TT = 64. ^@ERROR: ^@Fast Instruction Access MMU Miss
TSTATE= 0x80001601 ^@[ccr = 0x0, asi = 0x80, pstate = 0x16, cwp = 0x1]
TPC= 0000000000000000
TNPC= 0000000000000004
SFSR= 0000000000808008, TAGACCESS = 0000000000000000
TICK= 00000047379f38fe, TICKCMP = 8000000000000000
debugger entered
I then attempted to boot -avs hoping to locate the point of failure but....
Sun Fire E6900
OpenFirmware version 5.18.1 (12/09/04 12:30)
Copyright 2001-2004 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
SmartFirmware, Copyright (C) 1996-2001. All rights reserved.
32768 MB memory installed, Serial #xxxxxxxx.
Ethernet address x:x:xx:x:xx:xx, Host ID: xxxxxxxx.
Rebooting with command: boot -avs
The boot filesystem is logging.
The ufs log is empty and will not be used.
Enter filename [kernel/sparcv9/unix]:
Size: 0x608cb+0x252fd+0x66ac7 Bytes
Enter default directory for modules [/platform/SUNW,Sun-Fire/kernel
/platform/sun4u/kernel /kernel /usr/kernel]:
Name of system file [etc/system]:
SunOS Release 5.9 Version Generic_118558-06 64-bit
Copyright 1983-2003 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
TL = 1, TT = 64. ERROR: Fast Instruction Access MMU Miss
TSTATE= 0x80001601 [ccr = 0x0, asi = 0x80, pstate = 0x16, cwp = 0x1]
TPC= 0000000000000000
TNPC= 0000000000000004
SFSR= 0000000000808008, TAGACCESS = 0000000000000000
TICK= 0000005e7c6d789e, TICKCMP = 8000000000000000
debugger entered.
Subsequently, I boot net and managed to
1. fsck the root file system
2. unencapsulated the root disk from veritas 4.1 encapsulation
(should now boot up clean)
3. installboot using the bootblk from the jumpstart server boot image
But once again, the same error appeared.
An attempt to copy to rebuild the following directories
[/platform/SUNW,Sun-Fire/kernel /platform/sun4u/kernel /kernel
/usr/kernel] from another server at the same patch level yielded the
same results.
I ensured also that the following files, [unix, genunix, krtld] were
intact and verified them using cksum against another live 6900 domain.
Would appreciate some help. Anybody know how to use the debugger at OBP
level?
Warmest Regards
Steven Sim
Fujitsu Asia Pte. Ltd.
_____________________________________________________
This e-mail is confidential and may also be privileged. If you are not the intended recipient, please notify us immediately. You should not copy or use it for any purpose, nor disclose its contents to any other person.
Opinions, conclusions and other information in this message that do not relate to the official business of my firm shall be understood as neither given nor endorsed by it.
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:40:03 EDT