1753973 Members
7750 Online
108811 Solutions
New Discussion юеВ

Re: Ignite Server Issue

 
Arunkumar.B
Trusted Contributor

Ignite Server Issue

Hi Guru's,

I am having two superdomes with 3 npar each & 9 vpars in each superdome.

Sd1 vpars are configured as ignite Client in SD2.

SD2 vpars are configured as ignite client in SD1


Now One of My vpar configured as ignite server in SD2 primary disk is giving I/O error.My alternate mirror disk in that vpars physical extent 0000(lvol1) shows stale.

When i tried to take ignite backup from sd2 to sd1.Its giving completed with warning saying that VPMON I/0 error.

Now the sd2 ignite server vpar running fine with I/O error Primary disk & alternate root disk with 0000 physical extents as stale.


How should i change my Primary root disk

1)should i try with Ignite backup completed with warning (vpmon I/O error)

2)Should i mirror from the secondry disk which is having stale in physical extents 0000


Cheers
Arunkumar.B
Necessity breaks iron
6 REPLIES 6
Arunkumar.B
Trusted Contributor

Re: Ignite Server Issue

Hi Guru's

Anyone please ???


Help me ???

Its urgent

Cheers
Arunkumar.B
Necessity breaks iron
Mridul Shrivastava
Honored Contributor

Re: Ignite Server Issue

I would suggest you to try booting from alternate disk, I suspect because of primary disk became bad alternate disk developed some stale extents. So there won't be a problem while booting from alternate disk.
it gave warning vpmon I/o error because of the I/O error on primary disk so restoring this would be a second option.
Time has a wonderful way of weeding out the trivial
Mridul Shrivastava
Honored Contributor

Re: Ignite Server Issue

Arun,

Try to boot from alternate disk as because of IO erros on prmiary disk we recd vpmon io error. It depends that which physical extents has gone bad so whether server will boot with ignite restore or not.

Botting from alternate disk won't be an issue else what is the purpose of having mirror disk on the servers.
Time has a wonderful way of weeding out the trivial
Arunkumar.B
Trusted Contributor

Re: Ignite Server Issue

HI Midhal,


Thanx for ur reply.Just now i tried that one.

vparboot -p neptune -B ALTBOOT -o "-lq"

It is throwing me the error

"can't boot /stand/vmunix"
neptune halted

Is there any other way ???
Necessity breaks iron
Michael Steele_2
Honored Contributor

Re: Ignite Server Issue

If you can't boot to primary then:

1a) reboot and interupt the boot process
1b) sea ipl (* check for bootable devices and verify that an alternate exists
1c) bo alt (* is exists

If no alt exists and you're able to boot to run level one:

2a) umount /stand
fsck -p /dev/vg00/rlvol1 (* check for bad sectors for example then bad disk *)

2b) #dd if=/dev/rdsk/cxtydx of=/dev/null bs=1024k (* check bad disk for failure *)

If fsck OK but still can't boot and probably if you just rebuilt the kernel, like with new patches *)

3) reboot and interact with IPL

ISL > hpux -ll /stand/system (* verify vmunix.prev

ISL > hpux /stand/vmunix.prev (* boot from vmunix.prev

4) If still fails then call HW and get your latest ignite tape and prepare to recover.
Support Fatherhood - Stop Family Law
Arunkumar.B
Trusted Contributor

Re: Ignite Server Issue

We Got it work without Ignite restore

1)stale in the secondry PE 0000
2)Ignite Restoration failed with errors

Here is the scoop
1)mirrored all lvol's except lvol1 (Stand)
2)created new lvol mounted as standbak in the secondry
3)copy the stand directory to standbak
4)copied vpmon from another vpar
5)then normal lvlnboot,booted with alt successfully.
6)Replaced the primary then vgcfgrestore & dd lvolbak to lvol1
7)onceagain lvlnboot

Started working Fine


Thankx guys for ur Help

Arunkumar.B
Necessity breaks iron