Mirroring problem with 11i

[Mr Simon Murray]

I have a Blade BL60 with two 146Gb disks which are mirrored. I have lost a disk, and managed to rebuild. However, neither will now boot. I can boot in single user mode, ( boot vmunix -is ) or in lvm maintenance mode ( -lm ) or without quorum ( -lq )

I have rechecked my build (EFI setboot idisk mkboot lvlnboot ) and everything looks good.

Any advice appreciated as this has me beat !

thanks and regards

Simon Murray

[Marco A.]

Have you tried to boot from your previous kernel? vmunix.prev

Regards,


Marc0

[Marco A.]

I forgot...


#hpux -is /stand/vmunix.prev

Hope this helps,

Marc0

[Mr Simon Murray]

There isn't a vmunix.prev as I haven't actually changed anything. This is a fresh build from scratch which is then mirrored. I have lost a disk due to a hardware failure and recovered from that but ended up here!

[Marco A.]

When trying to boot into multiuser mode, what error is the system showing?

Marc0

[Mr Simon Murray]

Trying to boot gives the following...,

HPUX> boot vmunix
Could not open file vmunix to check for a directory
Could not open vmunix
loading failed

Yet single user, maintenance or quorum boots ok

HPUX> boot vmunix -lq
> System Memory = 2028 MB
loading section 0

etc etc

[Torsten.]

Hi,

HPUX> boot vmunix
does not work, but
HPUX> boot vmunix -lq
does work from the same disk?

Can you reach a prompt?

[Marco A.]

Try to run the following command from the "shell".

#Shell> drivers

Let me know the output ...

[Mr Simon Murray]

Both disk behave the same, neither will boot vmunix but both will do single, maintenance and quorum.

I can reach a unix prompt from any of these methods of booting yes.

[Torsten.]

So go to single user mode,
vgchange -a y vg00
and attempt a repair first:

lvlnboot -r /dev/vg00/lvol3
lvlnboot -b /dev/vg00/lvol1
lvlnboot -s /dev/vg00/lvol2
lvlnboot -d /dev/vg00/lvol2

[Mr Simon Murray]

Marco,

Sorry, don't understand. From the unix shell in multi-user I get:

# drivers
sh: drivers: not found.
#

Do you mean from the HPUX prompt before booting ??

[Marco A.]

yes!!! ... actually it says "shell>"

[TwoProc]

I'm thinking you just need to turn off quorum checking in your default boot string. Juat add the -lq option.

So, if your AUTO file contents are:
"vmunix" then change your file to "vmunix -lq".

To see the contents of AUTO:
$> lifcp /dev/dsk/ /tmp/AUTO
$> cat /tmp/AUTO

To change the auto string from "vmunix" to "vmumix -lq":

mkboot -a "vmunix -lq" /dev/rdsk/

should fix your problem.

I suspect that even though you mirrored your replacement disk, you didn't make it ootable, AND you didn't create the AUTO file as per above.

When you replaced your new disk, did you:
A) do a:
$> mkboot /dev/rdsk/
command on it after you did your "pvcreate" on it?
B) do a:
$> mkboot -a "vmunix -lq" /dev/rdsk/
on it after making it bootable?

After the above is done, THEN you should gone on to fixing your mirrors in vg00.

[Marco A.]

I said that because could be an issue with the SCSI drivers, check what is the driver installed.

Marc0

[Torsten.]

Also, compare your steps made with this document:

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

[Mr Simon Murray]

Torsten, yes, that's the document I have based my work on.

John,

Yes, my AUTO content files are good, primary is boot vmunix and secondary is boot vmunix -lq . And yes, after replacing the disk I did exacly that. Output of my lvlnboot looks good;

# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t1d0s2 (0/1/1/0.1.0) -- Boot Disk
/dev/dsk/c0t0d0s2 (0/1/1/0.0.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t1d0s2
/dev/dsk/c0t0d0s2
Root: lvol3 on: /dev/dsk/c0t1d0s2
/dev/dsk/c0t0d0s2
Swap: lvol2 on: /dev/dsk/c0t1d0s2
/dev/dsk/c0t0d0s2
Dump: lvol2 on: /dev/dsk/c0t1d0s2, 0

#

[Torsten. · Accepted solution]

Also check your patch level. There was a boot loader patch, but I can't remember the number.

Did you perform the lvlnboot commands I posted again?

[Mr Simon Murray]

Torsen,

It worked. I had to boot vmunix -is -lm but once there I ran all the lvlnboot commands again and I can now boot vmunix on the primary and boot vmunix -lq on the secondary.

Can you tell me why it works? I followed the mirroring procedure to the letter!

Many thanks

Simon Murray

[Steven E. Protter]

Shalom Simon,

What mirroring procedure?

pvcreate -B /dev/rdsk/c1t0d0 #use real disk

mkboot -l /dev/rdsk/c1t0d0
mkboot -a "hpux -lq (;0)/stand/vmunix" /dev/rdsk/c1t0d0 # use real disk


# mkboot -b /usr/sbin/diag/lif/updatediaglif -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c?t?d?

If you are running 64-bit OS:

# mkboot -b /usr/sbin/diag/lif/updatediaglif2 -p ISL -p AUTO -p HPUX -p PAD -p LABEL /dev/rdsk/c?t?d?


vgextend /dev/vg00 /dev/dsk/c1t0d0 # same thing
lvextend -m 1 /dev/vg00/lvol1 /dev/dsk/c1t0d0

# real disk. repeat for other lvols

lvlnboot -r /dev/vg00/lvol3 # root fs /
lvlnboot -s /dev/vg00/lvol2 #swap
lvlnboot -d /dev/vg00/lvol2 #swap/dump
lvlnboot -b /dev/vg00/lvol1
lvlnboot -R
lvlnboot -v
setboot
setboot -a 52.1.0 # second disk

SEP

[Torsten.]

IMHO to run

lvlnboot -R

is not enough, because the man page says:

"Whenever mkboot(1M) is used to restore the LIF area of a damaged root physical volume, the -b boot_lv option of lvlnboot must be performed afterwards to record the boot volume information inside the new LIF (see lif(4)). Subsequent lvlnboot commands such as lvlnboot -R are dependent on the boot_lv information inside the LIF."
http://docs.hp.com/en/B2355-60105/lvlnboot.1M.html

Therefore I always use

lvlnboot -r /dev/vg00/lvol3
lvlnboot -b /dev/vg00/lvol1
lvlnboot -s /dev/vg00/lvol2
lvlnboot -d /dev/vg00/lvol2

instead of lvlnboot -R

Without getting "your" problem.



Remember to assign some points!

Have fun ;-)

[Patrick Wallek]

SEP,

The procedure you posted will NOT work on an Itanium machine, which the BL60 blades are.

Please remember that the procedure is different for PA-RISC and Itanium machines. You are doing a disservice by posting PA-RISC procedure in an Itanium thread.

[Torsten.]

@SEP:

You should prepare a second procedure for cut and paste and use this for Integrity servers (thread owners will be really confused otherwise).
This thread is about an Blade BL60 - an Integrity.

Take this as an example:
http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad.pdf
Appendix A - How to mirror the root volume (Integrity servers)

(better to replace the line
"# lvlnboot -R /dev/vg00"
as suggested
;-)

[Mr Simon Murray]

Thanks everyone. Problem solved and knowledge increased!!