Hp-Ux rp3410 not booting

[Nedved]

Dear all,

Today morning i tried to boot server and its failed .
and when i try to login to the single user mode i get the following error

ISL> hpux -is -lq

Boot
: disk(0/1/1/0.0.0.0.0.0.0;0)/stand/vmunix
11198464 + 2260992 + 11032504 start 0x1f2268




alloc_pdc_pages: Relocating PDC from 0xfffffff0f0c00000 to 0x3f900000.
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.
igelan0: INITIALIZING HP PCI 1000Base-T Core at hardware path 0/1/2/0
igelan1: INITIALIZING HP A6825-60101 PCI 1000Base-T Adapter at hardware path 0/4/1/0

System Console is on the Built-In Serial Interface
Entering cifs_init...
Initialization finished successfully... slot is 9
Logical volume 64, 0x3 configured as ROOT
LVM : Failure in attaching PV (0/1/1/0.1.0) to the root volume group.
error no : 5


Can Someone help me how to solve this problem .

Thanks

[Victor Fridyev]

Hi,

It looks like vg00 is mirrored and the second disk has a HW problem.
In any case try to boot as
hpux -lm

HTH

[Asif Sharif]

Hi Nedved,

It seems your HDD header information is damaged and you need to repair it. The OS doesnt recognize that disk as LVM. The next option is to restore from Ignite image.

Regards,
Asif Sharif

[Kranti Mahmud]

If the LVM subsystem detects that vital information is corrupted on the boot disk, it scans all the attached devices to try to find the physical volumes that are part of the root volume group.

Failure in attaching PV to the root volume group means...
The physical volume does not belong to the root volume group.

Check the following log:

/var/adm/syslog/syslog.log

Rgds-Kranti

[sujit kumar singh]

hi
As can be seen that one disk is not attaching to the root VG that means that the quorum of the root VG is not meeting so this is better that you can once trying to boot the system in the LVM maint Mode or in Quorum Override mode. or in a combination of both.

Interrupt the autoboot and inetract with IPL (Y) and do
ISL>hpux -lq
to boot in Quorum Override mode
ISL>hpux -lq -lm

this shall boot the system in the LVM Maint Mode Overriding the Quorum in the Root VG.

after that please post ioscan -fnCdisk
vgdisplay -v vg00
regards
sujit

[Nedved]

I boot up the server using

hpux -lq in the isl prompt and in the vgdisplay
output i found this

vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t1d0":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: Warning: couldn't query all of the physical volumes.


So i ordered for a disk to replace.

Can some one tell me what is the " hpux -lq "
switch done to boot up the server.

[Asif Sharif]

Hi Nedved,

hpux -lq

Boot the system with quorum override option. This option is used in a scenario where a disk is removed from the system or is otherwise unavailable, but the corresponding entry for the physical volume has not yet been removed from the volume group using vgreduce.

http://docs.hp.com/en/B2355-60127/hpux.1M.html

Regards,
Asif Sharif

[Nedved]

Now i removed the failed disk from the server.
Is there any procedure to insert the new disk or i can simply add the new disk in bay??

[Torsten.]

Plug the disk in and follow the LVM configuration steps to restore the config:

http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad_WP.pdf

[Kranti Mahmud]

Hi Nedved,

If the disks of vg00 is H/W RAID, the newly insert disk will automatically found. If S/W RAID configured, you may use the following commands:

# vgsync /dev/vg00
# lvsync /dev/vg00/(lvolname)

If possible, provide the following:

# ioscan -fnC disk
# vgdisplay -v /dev/vg00

Rgds-Kranti