topic Re: System boot problem in Operating System - HP-UX

System boot problem

zsujith — Tue, 18 Mar 2008 05:56:46 GMT

Hi
The system is boot with alternate boot device.We checked and found the primary disk is fine.Can anybody help to find why its happened.
setboot -v
Primary bootpath : 0/1/1/0.1.0
Alternate bootpath : 0/1/1/0.0.0

echo boot_string/S | adb /stand/vmunix /dev/kmem
boot_string:
boot_string: disk(0/1/1/0.0.0.0.0.0.0;0)/stand/vmunix

lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c2t1d0 (0/1/1/0.1.0) -- Boot Disk
/dev/dsk/c2t0d0 (0/1/1/0.0.0) -- Boot Disk

Re: System boot problem

Jeeshan — Tue, 18 Mar 2008 06:46:45 GMT

did you set the setboot?

Re: System boot problem

zsujith — Tue, 18 Mar 2008 08:22:21 GMT

Hello,

How to verify whether the setboot is set or not to primary boot path.

regards

Re: System boot problem

zsujith — Tue, 18 Mar 2008 08:49:45 GMT

Hello,

# setboot
Primary bootpath : 0/1/1/0.1.0
Alternate bootpath : 0/1/1/0.0.0

Autoboot is ON (enabled)
Autosearch is ON (enabled)

Regards

Re: System boot problem

Jeeshan — Tue, 18 Mar 2008 08:51:29 GMT

command is

#setboot

Re: System boot problem

Siju Vadakkan — Tue, 18 Mar 2008 08:53:29 GMT

provide the following details
1. lifls -l /dev/rdsk/c2t1d0
2. lifcp /dev/rdsk/c2t1d0:AUTO -

1. lifls -l /dev/rdsk/c2t0d0
2. lifcp /dev/rdsk/c2t0d0:AUTO -

Re: System boot problem

zsujith — Tue, 18 Mar 2008 10:39:47 GMT

Hi,

See the attachment.

Regards

Re: System boot problem

zsujith — Tue, 18 Mar 2008 11:21:43 GMT

Hi,

Can anyone let us know after seeing the attachment where the problem is?

Regards

Re: System boot problem

Ron Irving — Tue, 18 Mar 2008 12:00:52 GMT

Hi!!

It looks like to me that the drives aren't completely mirrored. You're missing the offline diags portion on c2t0d0.

Hope that helps.

Re: System boot problem

Patrick Wallek — Tue, 18 Mar 2008 12:17:34 GMT

I'm not sure I'd really consider this to be a problem.

It may be that someone booted from the alternate boot disk to verify that it would work, which is a very good idea.

Since the disks are mirrored and the system is running normally I really would not worry about this. You are making unnecessary work!

If you want your mirrors to be absolutely identical, then you need to get the diagnostics on c2t0d0. You should also modify the AUTO string on c2t1d0 so that it reads 'hpux -lq' like the other disk.

That way you will be able to boot from either disk if the other goes bad.

Re: System boot problem

Siju Vadakkan — Tue, 18 Mar 2008 13:24:57 GMT

I couldn't find any problem.May be as patric said some one might have booted the server intentionally with alternative boot path.

1. To make the LIF area identical, do the following.

mkboot -b /dev/rdsk/c2t1d0 /dev/rdsk/c2t0d0

2. Make AUTO string identical on both nodes to aviod quorum checking.

mkboot -a "hpux -lq" /dev/rdsk/c2t1d0
mkboot -a "hpux -lq" /dev/rdsk/c2t0d0