Operating System - HP-UX
1836932 Members
3267 Online
110111 Solutions
New Discussion

Changed Primary Boot Path

 
SOLVED
Go to solution
AIMC
Frequent Advisor

Changed Primary Boot Path

Hi,

I am installing HPUX 11i from scratch, i have loaded the operating system & now i have moved the boot disk onto a new scsi card so the H/W path has changed. I rebooted the server & changed the primary path from BCH, booted & the server panics while booting /stand/vmunix with unexpected lbolts, i rebooted & brought the server to maintenance mode (hpux -lm) & vgexported vg00 & reimported it on the new path... this worked fine & init 4 brought the server to multi user mode, i rebooted again & the server still panics when booting /stand/vmunix? I tried going to maintenance mode again & from their to multi user & this works fine every time, alternatively letting the system boot normally panics every time with unexpected lbolts & does a TOC. I have a feeling that i need to update some LVM or I/O configuration files but cannot think of what i have missed here.

Aidan
7 REPLIES 7
Stephen Keane
Honored Contributor

Re: Changed Primary Boot Path

lbolts are usually a hardware issue, bad cable, not plugged in fully, loose card, unterminated SCSI chain etc. I would check your hardware before getting too fixated on the configuration first.
Steven E. Protter
Exalted Contributor

Re: Changed Primary Boot Path

lbolt has always led to the replacement of disk or disk technology(drive cage, scsi card etc) in our shop.

Seems you may have had some bad luck, or the disk had an issue previously unknown to you. The hardware issue will need to be resolved prior to getting the installation to work.

The installation may proceed, but you have found out the hard way that it won't work in an environment where the hardware is not stable.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
AIMC
Frequent Advisor

Re: Changed Primary Boot Path

Hi,

I would normally have thought it was a bad disk but these lbolts only occur when trying to autoboot into multi user, also when the TOC happens i have noticed errors along the lines of

panic: LVM: Configuration Failure

Aidan
doug mielke
Respected Contributor

Re: Changed Primary Boot Path

Is it possible that the disk and scsi controller are not compatable?

Not that cables can be swapped from say, scsi 2 to scsi 3, but there are adaptors out there (that don't usually work) that could be in place. I don't remember if lvd vs se cables are the same, but I know the drives / controllors are not interchangeable.

can you try the drive again on the original scsi card as a test?
Stephen Keane
Honored Contributor

Re: Changed Primary Boot Path

If you have more than one disk, don't assume the lbolt errors relate to the boot disk, unless you can read the screen quickly enough.

Try booting the machine, interrupting the boot and at the Main Menu ...

Main Menu: Enter command or menu > IN

Information Menu: Enter command > IO

Note they are both capital i's, not ones.

If that works OK, when the system is fully booted, try an ioscan (without the -k flag)or two, to see if you can upset the SCSI controller.

A. Clay Stephenson
Acclaimed Contributor

Re: Changed Primary Boot Path

Run an lvlnboot -v /dev/vg00 and make sure that all is well. I would also do a lifls on the boot disk. You may have a bad boot string so I would issue a new mkboot -a "hpux (;0)/stand/vmunix" /dev/rdsk/cXtYd0.
If it ain't broke, I can fix that.
Solution

Re: Changed Primary Boot Path

Aidan,

Check to make sure that /stand/bootconf has the proper device file in it:
l /dev/dsk/c1t6d0

The "l" (lower-case L) indicates that the boot device is an LVM disk...

Also, I would recommend booting into LVM Maintenance Mode and rebuilding the BDRA using the commands:
# vgchange -a y /dev/vg00
# lvlnboot -v /dev/vg00

# lvrmboot -r /dev/vg00

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

# lvlnboot -R /dev/vg00

# lvlnboot -v /dev/vg00

Hopefully, a normal reboot will work for you now...

Steve Hamilton