HPE 9000 and HPE e3000 Servers
cancel
Showing results for 
Search instead for 
Did you mean: 

booting from disk mirror, whats found on SAN

 
Kevin_31
Regular Advisor

booting from disk mirror, whats found on SAN

Hello geniuses (flatter flattere flatter)

I've got a L3000 with a fairly recent version of hpux11i on it's internal disk, which has been mirrored to the other internal disk.

presented a SAN disk to the server, created the boot sector, added it into vg00, mirrored the volumes, did the lvlnboot commands to configure boot/root/swap, but when I try to boot from this disk I get, "

Booting...
Failed to initialize.

ENTRY_INIT
Status = -7

00000000 FFFFFFF9 00000000 00000000 00000000 FCFC0602 00000000 0000012D
00000000 FC00009D 00000000 000000CA 00000000 FC00009D 00000000 000000CA
00000000 FC00009D 00000000 000000CA 00000000 FC00009D 00000000 000000CA
00000000 FC00009D 00000000 000000CA 00000000 FC00009D 00000000 000000CA
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000

Failed to initialize."

The disk SAN disk showed up as 0/3/0/0.2, but when I did a "sea" from boot prompt is found:

0/3/0/0.8 (see below)

Main Menu: Enter command or menu > sea

Searching for potential boot device(s)
This may take several minutes.

To discontinue search, press any key (termination may not be immediate).


Path# Device Path (dec) Device Path (mnem) Device Type
----- ----------------- ------------------ -----------
P0 0/0/1/1.2 intscsib.2 Random access media
P1 0/0/2/0.2 intscsia.2 Random access media
P2 0/0/2/1.2 Random access media
P3 0/3/0/0.8 Random access media
P4 0/9/0/0.8 Random access media


Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c1t2d0 (0/0/1/1.2.0) -- Boot Disk
/dev/dsk/c2t2d0 (0/0/2/0.2.0) -- Boot Disk
/dev/dsk/c4t2d2 (0/3/0/0.2.16.0.0.2.2) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c2t2d0
/dev/dsk/c4t2d2
Root: lvol3 on: /dev/dsk/c2t2d0
/dev/dsk/c4t2d2
Swap: lvol2 on: /dev/dsk/c2t2d0
/dev/dsk/c4t2d2
Dump: lvol2 on: /dev/dsk/c2t2d0, 0

I don't think that the fact that this is SAN disk really matters, I must be missing something on getting this disk to know it is allowed to boot.

I've experimented with booting to one of the "good" internal disks then saying yes to Interact with ISL so I can then boot the other disk, but that hasn't worked either.

Whadaya think?

(cheers, points forthcoming)
8 REPLIES 8
Leif Halvarsson_2
Honored Contributor

Re: booting from disk mirror, whats found on SAN

Hi,

I remeber a similar problem when booting a rp2430 from SAN. The search command did not show the SAN paths correct but if I typed the complete hardware path as it was showed with the ioscan command (when the machine was booted on a local disk, it worked).Ex:
boot 0/2/0/0.1.2.255.14.15.0
Kevin_31
Regular Advisor

Re: booting from disk mirror, whats found on SAN

cheers Leif, I'll wait to assign some points until I get a chance to give this a try this weekend (rebooting this box has been screwing up my SAN connected tape drive operations!)

looking forward to giving it another go tho
Bruno Vidal
Respected Contributor

Re: booting from disk mirror, whats found on SAN

Hi,
I confirm this answer, it is the same with superdome. This return code comes from the PDC_IODC system call, and the return code -7 means "no such device or address", so it is nearly sure that the path you gave is not complete. The other solution to avoid any boot problem at BCH is to set up the alternate path directly from the OS side by using "setboot -a your_hardware_path", and at BCH prompt directly use "bo alt"

Cheers.
Bernhard Mueller
Honored Contributor

Re: booting from disk mirror, whats found on SAN

Boot over FC:

If you have the A6795 Tachlite FC card you should have at least PDC firmware 42.06,

if you have the A6826 (2 port) FC card you should have at least PDC FW 43.22 (PHSS_28608) which is the latest.

Regards,
Bernhard
Kevin_31
Regular Advisor

Re: booting from disk mirror, whats found on SAN

okay, got it booting (sorta) but the controller number is different on the new server, It's reading it's VG00 info from when it was "c4t2d2" and now it's on c10t2d2.

Since this is the root VG, how do I change it to reflect the new info please?

I could do this if it was any vg other than root, but I'm stuck here.

----------------------------------------------
[MON] vparx loaded
gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: autofs_link(): File system was registered at index 3.
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 6.
td: claimed Tachyon TL/TS Fibre Channel Mass Storage card at 0/10/0/0
DIAGNOSTIC SYSTEM WARNING:
The diagnostic logging facility has started receiving excessive
to determine which I/O subsystem is logging excessive errors.
Entering cifs_init... the excessive I/O logging is corrected.
Initialization finished successfully... slot is 9Daemon Startup command
in stm to start it.
Host is virtual System Console slave the logtool utility in stm
Logical volume 64, 0x3 configured as ROOT
WARNING: Logical volume for Dump expected but not found.
Swap device table: (start & size given in 512-byte blocks)
entry 0 - auto-configured on root device; ignored - no room
WARNING: no swap device configured, so dump cannot be defaulted to primary swap.
WARNING: No dump devices are configured. Dump is disabled.
read_ss_nvm: Cannot validate NVM - -2
Starting the STREAMS daemons-phase 1

System Console is virtual

Checking root file system.
file system is clean - log replay is not required
Root check done.
Create STCP device files
Starting the STREAMS daemons-phase 2
$Revision: vmunix: vw: -proj selectors: CUPI80_BL2000_1108 -
c 'Vw for CUPI80_BL2000_1108 build' -- cupi80_bl2000_1108 'CUPI80_BL2000_1108'
Wed Nov 8 19:24:56 PST 2000 $
Memory Information:
physical page size = 4096 bytes, logical page size = 4096 bytes
Physical: 1030144 Kbytes, lockable: 729680 Kbytes, available: 846472 Kbytes

/sbin/ioinitrc:
Can't open /dev/vg00/lvol1, errno = 6
/dev/vg00/lvol1: CAN'T CHECK FILE SYSTEM.
/dev/vg00/lvol1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
/dev/vg00/lvol1: No such device or address
Unable to mount /stand - please check entries in /etc/fstab
Skipping KRS database initialization - /stand can't be mounted
# vgchange -a y vg00
vgchange: Warning: Couldn't attach to the volume group physical volume "/dev/ds
/c4t2d2":
The path of the physical volume refers to a device that does not
exist, or is not configured into the kernel.
vgchange: Warning: couldn't query physical volume "/dev/dsk/c4t2d2":
The specified path does not correspond to physical volume attached to
this volume group
vgchange: Warning: couldn't query all of the physical volumes.
vgchange: Couldn't activate volume group "vg00":
Quorum not present, or some physical volume(s) are missing.
--------------------------------------------
Leif Halvarsson_2
Honored Contributor

Re: booting from disk mirror, whats found on SAN

Hi,
How do you created the SAN bootdisk ?
I used Ignite to clone the internal boot disk to the SAN disk and this worked without problem.
Jeff Schussele
Honored Contributor

Re: booting from disk mirror, whats found on SAN

Hi Kevin,

If you need to change the controller number listed fo the VG because it changed, then the best way is vgscan.
Move /etc/lvmtab to anither name or location, then run
vgscan -av
to recreate the lvmtab file. Strings it for proper values for ALL VGs. If a problem move/rename the new & bring the old lvmtab back if necessary.

Rgds,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!
Kevin_31
Regular Advisor

Re: booting from disk mirror, whats found on SAN

Cheers Jeff for that suggestion.

I've got one significant step closer now.

I can boot to LVM maint mode with "-lm" options, but no matter what I seem to do I still get these errors at bootup:

/sbin/ioinitrc:
Can't open /dev/vg00/lvol1, errno = 6
/dev/vg00/lvol1: CAN'T CHECK FILE SYSTEM.
/dev/vg00/lvol1: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
/dev/vg00/lvol1: No such device or address
Unable to mount /stand - please check entries in /etc/fstab
Skipping KRS database initialization - /stand can't be mounted


INIT: Overriding default level with level 's'

INIT: SINGLE USER MODE

INIT: Running /sbin/sh

------------------------

So I do a vgchange -a y
and fsck /dev/vg00/lvol1

then I can mount /usr and
strings /etc/lvmtab:

# strings /etc/lvmtab
/dev/vg00
KS?\^n
/dev/dsk/c8t0d5
#

which is correct!

So what's wrong? If I try to boot without "-lm" I get a software error:

ISL booting hpux

Boot
: disk(0/9/0/0.2.18.255.0.0.5;0)/stand/vmunix
9728000 + 1728512 + 1344048 start 0x1ee7e8




alloc_pdc_pages: Relocating PDC from 0xffff800000 to 0x7fa01000.
gate64: sysvec_vaddr = 0xc0002000 for 2 pages
NOTICE: autofs_link(): File system was registered at index 4.
NOTICE: cachefs_link(): File system was registered at index 5.
NOTICE: nfs3_link(): File system was registered at index 6.
td: claimed Tachyon TL/TS Fibre Channel Mass Storage card at 0/3/0/0
td: claimed Tachyon TL/TS Fibre Channel Mass Storage card at 0/9/0/0

System Console is on the Built-In Serial Interface
Entering cifs_init...
Initialization finished successfully... slot is 9

************* SYSTEM ALERT **************
SYSTEM NAME: blahblah
DATE: 09/10/2003 TIME: 12:10:40
ALERT LEVEL: 12 = Software failure

REASON FOR ALERT
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail

LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH FLASH OFF ON ON

0xF8E000C01100B800 00000000 0000B800 - type 31 = legacy PA HEX chassis-code
0x58E008C01100B800 00006708 0A0C0A28 - type 11 = Timestamp 09/10/2003 12:10:40
A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry

I have a feeling I'm almost there, anyone have any ideas what next?

cheers,
Kevin