1845772 Members
3895 Online
110250 Solutions
New Discussion

System boot problem

 
zsujith
Frequent Advisor

System boot problem

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
"The most wasted day is that in which we have not laughed."
10 REPLIES 10
Jeeshan
Honored Contributor

Re: System boot problem

did you set the setboot?
a warrior never quits
zsujith
Frequent Advisor

Re: System boot problem

Hello,

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

regards
"The most wasted day is that in which we have not laughed."
zsujith
Frequent Advisor

Re: System boot problem

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
"The most wasted day is that in which we have not laughed."
Jeeshan
Honored Contributor

Re: System boot problem

command is

#setboot
a warrior never quits
Siju Vadakkan
Trusted Contributor

Re: System boot problem

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 -
zsujith
Frequent Advisor

Re: System boot problem

Hi,

See the attachment.

Regards
"The most wasted day is that in which we have not laughed."
zsujith
Frequent Advisor

Re: System boot problem

Hi,

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

Regards
"The most wasted day is that in which we have not laughed."
Ron Irving
Trusted Contributor

Re: System boot problem

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.
Should have been an astronaut.
Patrick Wallek
Honored Contributor

Re: System boot problem

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.
Siju Vadakkan
Trusted Contributor

Re: System boot problem

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