The system is not booting !!

[Ignacio Javier]

Hi:

This is the problem i have:

I installed powerpath.
Then i made a insf -e.
powermt config
Everything correct until here.
I made a cmruncl and the system got hung.
I had to reset.

Now is not booting any more:

Loaded ACPI revision 2.0 tables.
NOTICE: cachefs_link(): File system was registered at index 4.
NOTICE: nfs3_link(): File system was registered at index 7.
Boot device's HP-UX HW path is: 0/1/1/0.1.0
iether0: INITIALIZING HP PCI-X 1000Base-T Dual-port Built-in at hardware path 0
/1/2/0
iether1: INITIALIZING HP PCI-X 1000Base-T Dual-port Built-in at hardware path 0
/1/2/1

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 = 8388608
Starting the STREAMS daemons-phase 1
msgcnt 1 vxfs: mesg 037: vx_metaioerr - vx_dirlook - /dev/root file system meta
data read error in block 200688
msgcnt 2 vxfs: mesg 017: vx_dirlook - / file system inode 2812 marked bad incore
?vxfs msgcnt 2 offset 0x00000000 0 0 0 0
?vxfs msgcnt 2 offset 0x00000010 0 0 0 0
?vxfs msgcnt 2 offset 0x00000020 0 0 0 0
?vxfs msgcnt 2 offset 0x00000030 0 0 0 0
?vxfs msgcnt 2 offset 0x00000040 0 0 0 0
?vxfs msgcnt 2 offset 0x00000050 0 0 0 0
?vxfs msgcnt 2 offset 0x00000060 0 0 0 0
?vxfs msgcnt 2 offset 0x00000070 0 0 0 0
?vxfs msgcnt 2 offset 0x00000080 0 0 0 0
?vxfs msgcnt 2 offset 0x00000090 0 0 0 0
?vxfs msgcnt 2 offset 0x000000a0 0 0 0 0
?vxfs msgcnt 2 offset 0x000000b0 0 0
The device file /dev/rroot does not exist or is not correct.
Automatic checks of the root file system not performed.
Calling function e0000000010f73c0 for Shutdown State 8 type 0x2

Stored message buffer up to panic:
0/1/1/1 instance 3: The driver is now online
fcd: Claimed HP A6826-60001 PCI/PCI-X Fibre Channel port at hardware path 0/2/1/
1 (FC Port 2 on HBA)
0/2/1/1 fcd
0/3 lba
0/3/1/0 PCItoPCI
0/3/1/0/4/0 btlan
0/3/1/0/5/0 btlan
0/3/1/0/6/0 btlan
0/3/1/0/7/0 btlan
0/4 lba
0/4/1/0 asio0
0/4/1/1 asio0
0/4/2/0 gvid_core
120 processor
250 pdh
250/0 ipmi
250/1 asio0
250/2 acpi_node
0/2/1/1.6 fcd_fcp
0/2/1/1.6.12.0.0 fcd_vbus
0/2/1/1.6.12.255.0 fcd_vbus
0/2/1/0.5 fcd_fcp
0/2/1/0.5.12.0.0 fcd_vbus
0/2/1/0.5.12.255.0 fcd_vbus
0/2/1/1.6.12.255.0.0 tgt
0/2/1/1.6.12.0.0.0 tgt
0/2/1/1.6.12.255.0.0.0 sctl
0/2/1/1.6.12.0.0.0.0 sdisk
0/2/1/1.6.12.0.0.0.1 sdisk
0/2/1/1.6.12.0.0.1 tgt
0/2/1/1.6.12.0.0.1.0 sdisk
0/2/1/1.6.12.0.0.1.1 sdisk
0/2/1/1.6.12.0.0.1.2 sdisk
0/2/1/1.6.12.0.0.1.3 sdisk
0/2/1/1.6.12.0.0.1.4 sdisk
0/2/1/1.6.12.0.0.1.6 sdisk
0/2/1/1.6.12.0.0.1.7 sdisk
0/2/1/1.6.12.0.0.2 tgt
0/2/1/1.6.12.0.0.2.0 sdisk
0/2/1/0.5.12.255.0.0 tgt
0/2/1/0.5.12.0.0.0 tgt
0/2/1/1.6.12.0.0.2.1 sdisk
0/2/1/0.5.12.255.0.0.0 sctl
0/2/1/0.5.12.0.0.0.0 sdisk
0/2/1/1.6.12.0.0.2.2 sdisk
0/2/1/1.6.12.0.0.2.3 sdisk
0/2/1/0.5.12.0.0.1 tgt
0/2/1/0.5.12.0.0.1.0 sdisk
0/2/1/0.5.12.0.0.1.1 sdisk
0/2/1/0.5.12.0.0.1.2 sdisk
0/2/1/0.5.12.0.0.1.3 sdisk
0/2/1/0.5.12.0.0.1.4 sdisk
0/2/1/0.5.12.0.0.1.6 sdisk
0/2/1/0.5.12.0.0.1.7 sdisk
0/2/1/0.5.12.0.0.2 tgt
0/2/1/0.5.12.0.0.2.0 sdisk
0/2/1/0.5.12.0.0.2.1 sdisk
0/2/1/0.5.12.0.0.2.2 sdisk
0/2/1/0.5.12.0.0.2.3 sdisk
0/1/1/0.7 tgt
0/1/1/0.7.0 sctl
0/1/1/1.1 tgt
0/1/1/1.1.0 stape
0/1/1/1.7 tgt
0/1/1/1.7.0 sctl
Boot device's HP-UX HW path is: 0/1/1/0.1.0
iether0: INITIALIZING HP PCI-X 1000Base-T Dual-port Built-in at hardware path 0
/1/2/0
iether1: INITIALIZING HP PCI-X 1000Base-T Dual-port Built-in at hardware path 0
/1/2/1
btlan: Initializing 10/100BASE-TX card at 0/3/1/0/4/0....
btlan: Initializing 10/100BASE-TX card at 0/3/1/0/5/0....
btlan: Initializing 10/100BASE-TX card at 0/3/1/0/6/0....
btlan: Initializing 10/100BASE-TX card at 0/3/1/0/7/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 = 8388608
Dump device table: (start & size given in 1-Kbyte blocks)
entry 0000000000000000 - major is 31, minor is 0x21000; start = 1538932,
size = 4194300
Starting the STREAMS daemons-phase 1
msgcnt 1 vxfs: mesg 037: vx_metaioerr - vx_dirlook - /dev/root file system meta
data read error in block 200688
msgcnt 2 vxfs: mesg 017: vx_dirlook - / file system inode 2812 marked bad incore
?vxfs msgcnt 2 offset 0x00000000 0 0 0 0
?vxfs msgcnt 2 offset 0x00000010 0 0 0 0
?vxfs msgcnt 2 offset 0x00000020 0 0 0 0
?vxfs msgcnt 2 offset 0x00000030 0 0 0 0
?vxfs msgcnt 2 offset 0x00000040 0 0 0 0
?vxfs msgcnt 2 offset 0x00000050 0 0 0 0
?vxfs msgcnt 2 offset 0x00000060 0 0 0 0
?vxfs msgcnt 2 offset 0x00000070 0 0 0 0
?vxfs msgcnt 2 offset 0x00000080 0 0 0 0
?vxfs msgcnt 2 offset 0x00000090 0 0 0 0
?vxfs msgcnt 2 offset 0x000000a0 0 0 0 0
?vxfs msgcnt 2 offset 0x000000b0 0 0

System Panic:

panic: all VFS_MOUNTROOTs failed: NEED DRIVERS ?????
Stack Trace:
IP Function Name
0xe000000000f46580 vfs_mountroot+0x1d0
0xe000000001247220 im_preinitrc+0x300
0xe000000001614350 DoCalllist+0x3a0
End of Stack Trace

linkstamp: Thu Jan 25 15:49:33 MET 2007
_release_version: @(#) $Revision: vmunix: B11.23_LR FLAVOR=perf Fri Aug 29
22:35:38 PDT 2003 $

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 dump physical memory to disk, for use
*** in debugging the crash.

*** Cannot dump with compression because there are too few processors
*** Dumping without compression
*** The dump will be a SELECTIVE dump: 286 of 2037 megabytes.
*** To change this dump type, press any key within 10 seconds.
*** Proceeding with selective dump.



¿ Could you please helpme ?

[Peter Godron]

Hi,
for your message 17 and 37 error:
http://uw714doc.sco.com/en/ODM_FSadmin/fssag-11.html see Message: 017 and Message: 037

[spex]

Hi,

It appears that your root disk is corrupt. How are your backups?

PCS

[Ignacio Javier]

Thanks Peter:

Well, it looks bad....

Both actions recomed to make a full fsck.

I have boot from the dvd but i am not able to perform that fsck.

What do you think i should do ?


Thanks a lot

[Ignacio Javier]

Hi:

I haver booted from the recupertation DVD and
perform:

# fsck -y /dev/rdsk/c2t1d0
** /dev/rdsk/c2t1d0
BAD SUPER BLOCK: MAGIC NUMBER WRONG
USE -b OPTION TO FSCK TO SPECIFY LOCATION OF AN ALTERNATE
SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck(1M).

I have read some other place that it could be fixable....
What do you think ? Do you know what value o b shoud i give ?

Thanks all

[spex]

/var/adm/sbtab on a few of my systems lists 16, 64, 2504, 5056, among others. You can try those values as alternate super-blocks, if you'd like. However, you'll probably have to perform a restore/re-installation of the OS to fix a volume this badly hosed.

[Sandman!]

>I have read some other place that it could be fixable....
>What do you think ? Do you know what value o b shoud i give ?

Lookup the file /var/adm/sbtab for redundant locations of the superblock. Pick the first entry listed in that file as the argument to the "-b" option of fsck or post the output of cat /var/adm/sbtab here.

~hope it helps

[Ignacio Javier]

Hi:

I have tried with all the values you tell and the anser is allways:

# fsck -b32 /dev/rdsk/c2t0d0
Alternate super block location: 32
** /dev/rdsk/c2t0d0
BAD SUPER BLOCK: MAGIC NUMBER WRONG
USE -b OPTION TO FSCK TO SPECIFY LOCATION OF AN ALTERNA
SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck(1M).


the file /var/adm/sbtab is empty


any idea ?

Thanks everybody

[Matti_Kurkela]

You're pointing the fsck tool to the raw disk.
If your system is an Itanium, this certainly won't work, as there is an EFI boot partition in the beginning of the disk.
Even on a PA-RISC system, there's the boot LIF which can cause confusion.

Try something like:
fsck -y /dev/vg00/lvol3
fsck -y /dev/vg00/lvol1

[Ignacio Javier]

Hi:

I have installed a golden ignite image and recovered the system.

Thanks everybody

[Ignacio Javier]

Hi:

What i have just said.


Regards everybody