error when starting system

[Tung_1]

Hi everybody, my system is running HP-UX 11i and today i can't start my system, it show this information on screen:
Checking root file system.
vxfs fsck: file system had I/O error(s) on meta-data.
log replay in progress
file system is not clean, full fsck required
pass0 - checking structural files
pass1 - checking inode sanity and blocks
vxfs fsck: fsck read failure bno = 8487, off = 0, len = 8192
file system check failure, aborting ...
Root check done.



Firmware Version 44.20

Duplex Console IO Dependent Code (IODC) revision 1



Stored message buffer up to panic:
gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: autofs_link(): File system was registered at index 3.
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 6.
0 sba
0/0 lba
0/0/1/0 hcd
0/0/1/0.1 hub
0/0/1/1 hcd
0/0/1/1.1 hub
0/0/1/2 ehci
0/0/2/0 side_ba
0/0/2/0.0 side
0/0/2/0.0.0 tgt
0/0/2/0.0.0.0 sdisk
0/0/2/0.0.7 tgt
0/0/2/0.0.7.0 sctl
0/0/2/0.1 side
0/0/2/0.1.7 tgt
0/0/2/0.1.7.0 sctl
0/1 lba
c8xx BUS: 2 SCSI C1010 Ultra160 Wide LVD assigned CPU: 0
0/1/1/0 c8xx
0/1/1/0.0 tgt
0/1/1/0.0.0 sdisk
0/1/1/0.1 tgt
0/1/1/0.1.0 sdisk
0/1/1/0.7 tgt
0/1/1/0.7.0 sctl
c8xx BUS: 3 SCSI C1010 Ultra160 Wide LVD assigned CPU: 1
0/1/1/1 c8xx
0/1/1/1.7 tgt
0/1/1/1.7.0 sctl
0/1/2/0 igelan
0/2 lba
0/3 lba
c8xx BUS: 4 SCSI C1010 Ultra160 Wide LVD A6828-60101 assigned CPU: 0
0/3/1/0 c8xx
0/3/1/0.7 tgt
0/3/1/0.7.0 sctl
0/3/1/0.9 tgt
0/3/1/0.9.0 sdisk
0/3/1/0.10 tgt
0/3/1/0.10.0 sdisk
0/3/1/0.15 tgt
0/3/1/0.15.0 sctl
0/4 lba
c8xx BUS: 5 SCSI C1010 Ultra160 Wide LVD A6828-60101 assigned CPU: 1
0/4/1/0 c8xx
0/4/1/0.0 tgt
0/4/1/0.0.0 sdisk
0/4/1/0.1 tgt
0/4/1/0.1.0 sdisk
0/4/1/0.2 tgt
0/4/1/0.2.0 sdisk
0/4/1/0.7 tgt
0/4/1/0.7.0 sctl
0/4/1/0.15 tgt
0/4/1/0.15.0 sctl
0/6 lba
0/7 lba
0/7/1/0 asio0
0/7/1/1 asio0
8 memory
16 ipmi
128 processor
129 processor
igelan0: INITIALIZING HP PCI 1000Base-T Core at hardware path 0/1/2/0

System Console is on the Built-In Serial Interface
Logical volume 64, 0x3 configured as ROOT
Logical volume 64, 0x2 configured as SWAP
Logical volume 64, 0x2 configured as DUMP
Swap device table: (start & size given in 512-byte blocks)
entry 0 - major is 64, minor is 0x2; start = 0, size = 16777216
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0000000000000000 - major is 31, minor is 0x20000; start = 527200,
size = 8388608
Starting the STREAMS daemons-phase 1

System Panic:

linkstamp: Sun Nov 5 02:28:59 TST 2006
_release_version: @(#) $Revision: vmunix: vw: -proj selectors: C
UPI80_BL2000_1108 -c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CU
PI80_BL2000_1108' Wed Nov 8 19:24:56 PST 2000 $
panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????

PC-Offset Stack Trace (read across, top of stack is 1st):
0x0020c958 0x00304210 0x0036b70c
0x0048054c 0x0036c1c0 0x0017690c
0x001fa664
End Of Stack

sync'ing disks (0 buffers to flush): (0 buffers to flush):
0 buffers not flushed
0 buffers still dirty



*** A system crash has occurred. (See the above messages for details.)
*** The system is now preparing to

*** The dump will be a SELECTIVE dump: 344 of 4094 megabytes.
*** To change this dump type, press any key within 10 seconds.
*** Proceeding with selective dump.

*** The dump may be aborted at any time by pressing ESC.
*** Dumping: 0% complete (0 of 344 MB) (device 64:0x2) *** Dumping: 2
% complete (8 of 344 MB) (device 64:0x2) *** Dumping: 4% complete (16 o
f 344 MB) (device 64:0x2) *** Dumping: 6% complete (24 of 344 MB) (devi
ce 64:0x2)
*** Dumping: 9% complete (32 of 344 MB) (device 64:0x2) *** Dumping
: 11% complete (40 of 344 MB) (device 64:0x2) *** Dumping: 13% complete
(48 of 344 MB) (device 64:0x2) *** Dumping: 16% complete (56 of 344 MB)
(device 64:0x
2) *** Dumping: 18% complete (64 of 344 MB) (device 64:0x2) *** D
umping: 20% complete (72 of 344 MB) (device 64:0x2) *** Dumping: 23% co
mplete (80 of 344 MB) (device 64:0x2) *** Dumping: 25% complete (88 of 3
44 MB) (device
64:0x2) *** Dumping: 27% complete (96 of 344 MB) (device 64:0x2)
*** Dumping: 30% complete (104 of 344 MB) (device 64:0x2) *** Dumping:
32% complete (112 of 344 MB) (device 64:0x2) *** Dumping: 34% complete
(120 of 344 MB
) (device 64:0x2) *** Dumping: 37% complete (128 of 344 MB) (device 64:0
x2) *** Dumping: 39% complete (136 of 344 MB) (device 64:0x2) ***
Dumping: 41% complete (144 of 344 MB) (device 64:0x2) *** Dumping: 44%
complete (152
of 344 MB) (device 64:0x2) *** Dumping: 46% complete (160 of 344 MB) (d
evice 64:0x2) *** Dumping: 48% complete (168 of 344 MB) (device 64:0x2)
*** Dumping: 51% complete (176 of 344 MB) (device 64:0x2) *** Dum
ping: 53% com
plete (184 of 344 MB) (device 64:0x2) *** Dumping: 55% complete (192 of
344 MB) (device 64:0x2) *** Dumping: 58% complete (200 of 344 MB) (devic
e 64:0x2) *** Dumping: 60% complete (208 of 344 MB) (device 64:0x2)
*** Dumping
: 62% complete (216 of 344 MB) (device 64:0x2) *** Dumping: 65% complet
e (224 of 344 MB) (device 64:0x2) *** Dumping: 67% complete (232 of 344
MB) (device 64:0x2) *** Dumping: 69% complete (240 of 344 MB) (device 64
:0x2) *
** Dumping: 72% complete (248 of 344 MB) (device 64:0x2) *** Dumping: 7
4% complete (256 of 344 MB) (device 64:0x2) *** Dumping: 76% complete (2
64 of 344 MB) (device 64:0x2) *** Dumping: 79% complete (272 of 344 MB)
(device 64:0x2
) *** Dumping: 81% complete (280 of 344 MB) (device 64:0x2) *** D
umping: 83% complete (288 of 344 MB) (device 64:0x2) *** Dumping: 86% c
omplete (296 of 344 MB) (device 64:0x2) *** Dumping: 88% complete (304 o
f 344 MB) (dev
ice 64:0x2) *** Dumping: 90% complete (312 of 344 MB) (device 64:0x2)
*** Dumping: 93% complete (320 of 344 MB) (device 64:0x2) *** Dumpi
ng: 95% complete (328 of 344 MB) (device 64:0x2) *** Dumping: 97% compl
ete (336 of 34
4 MB) (device 64:0x2) *** Dumping: 99% complete (343 of 344 MB) (device
64:0x2) *** Dumping: 100% complete (344 of 344 MB) (device 64:0x2)
*** Dumping: 100% complete (344 of 344 MB).
*** System rebooting.

Now, what can i do to recover my system ?
help me pls

[Peter Godron]

Hi,
and welcome to the forums !

The first messages give you the details:
bno = 8487, off = 0, len = 8192
8192 bytes starting at block 8487 can not be read.

Solutions:
1. If you are running a mirrorored root, replace the faulty drive
2. Restore your system from backup
3. Rebuild your system disk from scratch.

Please read:
http://forums1.itrc.hp.com/service/forums/helptips.do?#33 on how to reward any useful answers given to your questions.