From: Loukinas, Jeremy (Jeremy.Loukinas@evenflo.com)
Date: Fri Jan 09 2004 - 11:12:24 EST
Have an E450 with 2 cpu's 2gb memory. Not 100% familiar with the internals
of the system because I didn't build it. Looking at a boot device of c0t0d0.
Solaris 8 with recommended cluster in the last 6 months or so. Running
Veritas Netbackup 4.5MP5. Root disk encapsulated with VXVM. System became
unresponsive required a stop -A ran a sync @ ok> prompt
And this is what I get when the system boots.. Never seen this error before.
configuring IPv4 interfaces: ge0 hme0.
Hostname: evvan2bbu01
SUNW,pci-gem0: Using Gigabit SERDES Interface
SUNW,pci-gem0: Auto-Negotiated 1000 Mbps Full-Duplex Link Up
ld.so.1: /usr/bin/loadkeys: fatal: /usr/lib/libc.so.1: unknown file type
Killed
Killed
ld.so.1: expr: fatal: /usr/lib/libc.so.1: unknown file type
ld.so.1: expr: fatal: /usr/lib/libc.so.1: unknown file type
VxVM starting special volumes ( )...
ld.so.1: vxrecover: fatal: /usr/lib/libc.so.1: unknown file type
Killed
ld.so.1: egettxt: fatal: /usr/lib/libc.so.1: unknown file type
Killed
Killed
WARNING: /proc could not be mounted
ld.so.1: expr: fatal: /usr/lib/libc.so.1: unknown file type
ld.so.1: swap: fatal: /usr/lib/libc.so.1: unknown file type
Killed
Killed
The / file system (/dev/vx/rdsk/rootvol) is being checked.
ld.so.1: /usr/sbin/fsck: fatal: /usr/lib/libc.so.1: unknown file type
Killed
WARNING - fatal error from fsck - error 137
Unable to repair the / filesystem. Run fsck manually
(fsck -F ufs /dev/vx/rdsk/rootvol). System will reboot when you exit the
shell.
Type control-d to proceed with normal startup,
(or give root password for system maintenance):
Jeremy S. Loukinas
_______________________________________________
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:27:48 EDT