cancel
Showing results for 
Search instead for 
Did you mean: 

System Boot Issue

SOLVED
Go to solution
Malps
Advisor

System Boot Issue

Hi All

I have been trying to boot one of the disks in my Server (RX2600) but it gives this error.

Loading.: HP-UX Primary Boot: 0/1/1/0.0.0
Starting: HP-UX Primary Boot: 0/1/1/0.0.0

(C) Copyright 2004 Hewlett-Packard Development Company, L.P.All rights reserved

HP-UX Boot Loader for IPF -- Revision 2.027

Press Any Key to interrupt Autoboot
\EFI\HPUX\AUTO ==> boot vmunix
Seconds left till autoboot - 0
AUTOBOOTING....................................
> System Memory = 8180 MB
loading section 0
................................................................... (complete)
loading section 1
............... (complete)
loading symbol table
loading System Directory (boot.sys) to MFS
....
loading MFSFILES directory (avrbac/bootfs) to MFS
Could not open directory for MFS copy
avrbac/bootfs

Launching /stand/vmunix
SIZE: Text:33902K + Data:7437K + BSS:7132K = Total:48473K

Console is on a Serial Device
Booting kernel...

HP-UX will call firmware in physical-addressing mode

Memory Class Setup
-------------------------------------------------------------------------
Class Physmem Lockmem Swapmem
-------------------------------------------------------------------------
System : 8180 MB 8180 MB 8180 MB
Kernel : 8180 MB 8180 MB 8180 MB
User : 7554 MB 6582 MB 6608 MB
-------------------------------------------------------------------------

Loaded ACPI revision 2.0 tables.
krs_read_mfs: The config.krs file was not found.
krs_read_mfs: The config.krs.lkg file was not found.
kc_init: Error opening Modules sub-tree.
Could not initialize static modules list
WARNING: /stand/ioconfig entries corrupted.
NOTICE: cachefs_link(): File system was registered at index 5.
Lowfat driver is the master here
NOTICE: nfs3_link(): File system was registered at index 8.
td: claimed Tachyon XL2 Fibre Channel Mass Storage card at 0/4/1/0
Boot device's HP-UX HW path is: 0/1/1/0.0.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
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
Checking root file system.
file system is clean - log replay is not required
Root check done.
Create STCP device files
Starting the STREAMS daemons-phase 2
$Revision: vmunix: B11.23_LR FLAVOR=perf Fri Aug 29 22:35:38 PDT 2003 $
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 8377152 Kbytes, lockable: 6168040 Kbytes, available: 7162704 Kbytes

/sbin/ioinitrc:
/dev/vg00/lvol1: BAD SUPER BLOCK: MAGIC NUMBER WRONG

/dev/vg00/lvol1: USE -b OPTION TO FSCK TO SPECIFY LOCATION OF AN ALTERNATE

/dev/vg00/lvol1: SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck(1M).

/dev/vg00/lvol1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.

UX:vxfs mount: ERROR: V-3-21268: /dev/vg00/lvol1 is corrupted. needs checking

Unable to mount /stand - please check entries in /etc/fstab

Skipping KRS database initialization - /stand can't be mounted


INIT: Overriding default level with level 's'

INIT: SINGLE USER MODE

INIT: Running /sbin/sh
#
#cat /etc/fstab
# System /etc/fstab file. Static information about the file systems
# See fstab(4) and sam(1M) for further details on configuring devices.
/dev/vg00/lvol3 / vxfs delaylog 0 1
/dev/vg00/lvol1 /stand hfs defaults 0 1

#mountall

mountall: /dev/vg00/lvol1 is seriously damaged
mountall: diagnostics from fsck
Can't open /dev/vg00/lvol1, errno = 6
mountall: cannot mount /dev/vg00/lvol1

# vgchange -a y -q n /dev/vg00 (in lvm maintainance mode)

vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/dsk/c1t15d0":
A component of the path of the physical volume does not exist.
vgchange: Warning: couldn't query physical volume "/dev/dsk/c1t15d0":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query all of the physical volumes.
vgchange: Couldn't activate volume group "/dev/vg00":
Quorum not present, or some physical volume(s) are missing.

# fsck -F hfs /dev/vg00/lvol1

** /dev/vg00/lvol1
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 don't haave any backup for this disk.

Is there any way I can get this disk to boot?

Regards

Deepak
5 REPLIES
Torsten.
Acclaimed Contributor
Solution

Re: System Boot Issue

See

http://h30499.www3.hp.com/t5/Disk/dev-vg00-lvol1-UNEXPECTED-INCONSISTENCY-RUN-fsck-MANUALLY/m-p/4733407#M7661



Consider to learn how to create a backup before the system dies.


http://www.hp.com/go/ignite-UX


Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Thierry D
Valued Contributor

Re: System Boot Issue

Hi Deepak

Can you check in the /var/adm/sbtab to find a backup superblock and then run the following command

fsck -F hfs -b /dev/vg00/rlvol1

Could youalso check via ioscan the disk is not in a NO_HW state

Regards,
Thierry
Malps
Advisor

Re: System Boot Issue

@thierry

I don't see sbtab under /var/adm

# # cd /var/adm
# ls
crash sw wtmps
# pwd
/var/adm

Also the Disk is Claimed.

Thank You!

@Torsten

I am not able to open that link due to some n/w issues will check it. Thank You.
Ismail Azad
Esteemed Contributor

Re: System Boot Issue

Hi,

I can see you have an integrity server and I assume you have not that recent a release of HPUX as your /stand is an HFS file system on an Integrity server. It is obvious that your /stand is corrupted. And it is even more bad news that /stand is HFS as an HFS filesytem is very difficult to recover and there is absolutely no guarantee for filesystem integity. Whenever an HFS filesystem is involved, make sure you have a backup copy because with HFS , you might have to take the whole backup from tape.

Regards
Ismail Azad
Read, read and read... Then read again until you read "between the lines".....
Dennis Handly
Acclaimed Contributor

Re: System Boot Issue

>Ismail: I can see you have an integrity server and I assume you have not that recent a release of HP-UX as your /stand is an HFS file system on an Integrity server.

I also noticed this. All of our 11.23 Integrity servers have vxfs, no HFS.