ioscan -m dsf, vgdisplay, and syslog.log not consistent re boot device

[dgangemi]

Hi

First I hope this is the right forum let me know if I have it wrong.

I've just installed my first Itanium/11.31 OS - an rx3600. The syslog.log has the following entry:
vmunix: Boot device's HP-UX HW path is: 0.4.1.0.500000e015501382.0

This corresponds with c0t0d0 as shown in ioscan -funC disk:
disk 4 0/4/1/0.0.0.0.0 sdisk CLAIMED DEVICE HP DG072A9BB7
/dev/dsk/c0t0d0 /dev/dsk/c0t0d0s2 /dev/rdsk/c0t0d0 /dev/rdsk/c0t0d0s2
/dev/dsk/c0t0d0s1 /dev/dsk/c0t0d0s3 /dev/rdsk/c0t0d0s1 /dev/rdsk/c0t0d0s3
disk 2 0/4/1/0.0.0.1.0 sdisk CLAIMED DEVICE HP DG072A9BB7
/dev/dsk/c0t1d0 /dev/rdsk/c0t1d0

vgdisplay -v vg00 gives me the DSF pvname of disk5_p2:
vgdisplay -v vg00
.
.
.
--- Physical volumes ---
PV Name /dev/disk/disk5_p2
PV Status available

but ioscan -m dsf shows me this:
Persistent DSF Legacy DSF(s)
========================================
/dev/rdisk/disk5 /dev/rdsk/c0t1d0
/dev/rdisk/disk6 /dev/rdsk/c0t0d0
/dev/rdisk/disk6_p1 /dev/rdsk/c0t0d0s1
/dev/rdisk/disk6_p2 /dev/rdsk/c0t0d0s2
/dev/rdisk/disk6_p3 /dev/rdsk/c0t0d0s3

Well obviosly something is wrong disk 5 cant be the boot device - it doesn't have the partitioning. Furthermore, I *know* that c0t1d0 is in vg01:
vgdisplay -v vg01
.
.
.
--- Physical volumes ---
PV Name /dev/dsk/c0t1d0
PV Status available
Total PE 17501
Free PE 0
Autoswitch On

PV Name /dev/dsk/c0t2d0
PV Status available
Total PE 17501
Free PE 0
Autoswitch On

PV Name /dev/dsk/c0t3d0s2
PV Status available
Total PE 17276
Free PE 0
Autoswitch On

PV Name /dev/dsk/c0t4d0
PV Status available
Total PE 17501
Free PE 0
Autoswitch On

PV Name /dev/dsk/c0t5d0s2
PV Status available
Total PE 17276
Free PE 5331
Autoswitch On

ioscan -fenC disk shows that the device reported as the boot device in syslog.log is c0t0d0s2 as you would expect:
disk 4 0/4/1/0.0.0.0.0 sdisk CLAIMED DEVICE HP DG072A9BB7
/dev/dsk/c0t0d0 /dev/dsk/c0t0d0s2 /dev/rdsk/c0t0d0 /dev/rdsk/c0t0d0s2
/dev/dsk/c0t0d0s1 /dev/dsk/c0t0d0s3 /dev/rdsk/c0t0d0s1 /dev/rdsk/c0t0d0s3
Acpi(HWP0002,PNP0A03,400)/Pci(1|0)/Sas(Addr500000E015501382, Lun0)/HD(Part1,SigF9558A84-1545-11DC-8000-D6217B60E588)/\EFI\HPUX\HPUX.EFI

But vgdisplay is implying that it is disk5 (c0t1d0) not c0t0d0.

So either I've got a LVM problem, or ioscan -m dsf is mis-mapping the DSF's.

Any thoughts?

[Steven E. Protter]

Shalom,

strings /etc/lvmtab

Lets see what the system thinks the score is.

SEP

[dgangemi]

Pretty much what you would expect given the vgdisplay output:

#strings /etc/lvmtab
/dev/vg00
/dev/disk/disk5_p2
/dev/vg01
/dev/dsk/c0t1d0
/dev/dsk/c0t2d0
/dev/dsk/c0t3d0s2
/dev/dsk/c0t4d0
/dev/dsk/c0t5d0s2

[marie-noelle jeanson]

Hi,

To verify the boot device associated with hw path 0.4.1.0.500000e015501382.0 , you can also use the ioscan command with new -N option:
ioscan -kfnNC lunpath will show LUNs with their lunpath hardware path. Description field shows "lunpath for disk#".
To see the associated dsf name, run ioscan -kfnNC disk -I # (# being in disk# above).

Marie.

[marie-noelle jeanson]

Hi,

Did you resolve your problem? If not, a console messages or syslog file may help identify the problem if you want to post the info (if still available).

Marie.

[dgangemi]

No - sorry got temporarily pulled off to another project - you know how it is. I ran ioscan -kfnNC disk and what came back seems to be implying that I'm getting two DSFs per disk:

Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
disk 15 0/0/2/1.0x0.0x10 UsbScsiAdaptor CLAIMED LUN_PATH USB SCSI Stack Adaptor
disk 5 64000/0xfa00/0x0 esdisk CLAIMED DEVICE HP DG072A9BB7
/dev/disk/disk4 /dev/disk/disk5 /dev/rdisk/disk5
disk 6 64000/0xfa00/0x1 esdisk CLAIMED DEVICE HP DG072A9BB7
/dev/disk/disk5_p1 /dev/disk/disk6 /dev/disk/disk6_p3 /dev/rdisk/disk6_p2
/dev/disk/disk5_p2 /dev/disk/disk6_p1 /dev/rdisk/disk6 /dev/rdisk/disk6_p3
/dev/disk/disk5_p3 /dev/disk/disk6_p2 /dev/rdisk/disk6_p1




When I run ioscan -kfnNC lunpath as you suggested, it confirms that the boot device (...1382...) is disk6, which corresponds with c0t0d0. So why does vgdisplay -v vg00 show me disk5 - which is c0t1d1 - and is par of vg01?
Class I H/W Path Driver S/W State H/W Type Description
==================================================================
lunpath 1 0/4/1/0.0x500000e0154fcb22.0x0 eslpt CLAIMED LUN_PATH LUN path for disk5
lunpath 3 0/4/1/0.0x500000e015501382.0x0 eslpt CLAIMED LUN_PATH LUN path for disk6
lunpath 4 0/4/1/0.0x500000e015512022.0x0 eslpt CLAIMED LUN_PATH LUN path for disk9
lunpath 0 0/4/1/0.0x500000e0155198e2.0x0 eslpt CLAIMED LUN_PATH LUN path for disk13
lunpath 5 0/4/1/0.0x500000e015528622.0x0 eslpt CLAIMED LUN_PATH LUN path for disk11
lunpath 2 0/4/1/0.0x500000e015528bf2.0x0 eslpt CLAIMED LUN_PATH LUN path for disk12

[marie-noelle jeanson]

Hi,

Looks like you have a real mapping problem here for some reason.
Under disk 5, you have dsfs for disk5 and disk4.
And under disk6, you have dsfs for disk5 partitions and disk6.

Does not look good. I am not sure how you can clear/clean up your dsf assignments. But that would help.

Marie.

[marie-noelle jeanson]

Hi,

Could you run the command:
escsi_diag > escsi_diag.out
and post the output?

Marie.

[dgangemi]

Thats a pretty healthy sized dump! See attached.

[dgangemi]

What would you say to my just renaming /etc/lvmtab and running vgscan -a? Do you think that would be any help, or would it put me in a worse situation?