vg00 on rx2600

[Geoff Wild]

Just setup my new rx2600 with 11iv2 (my new workstation!).

Just wondering why my disks look like this:

# ioscan -funC disk
Class I H/W Path Driver S/W State H/W Type Description
============================================================================
disk 0 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-N
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 36.4GST336754LC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 36.4GST336754LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0
disk 3 0/1/1/1.2.0 sdisk CLAIMED DEVICE HP 36.4GST336754LC
/dev/dsk/c3t2d0 /dev/dsk/c3t2d0s3 /dev/rdsk/c3t2d0s2
/dev/dsk/c3t2d0s1 /dev/rdsk/c3t2d0 /dev/rdsk/c3t2d0s3
/dev/dsk/c3t2d0s2 /dev/rdsk/c3t2d0s1


And vg00 like so:

# vgdisplay -v
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 10
Open LV 10
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 4238
VGDA 2
PE Size (Mbytes) 8
Total PE 4228
Alloc PE 3328
Free PE 900
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/syncd
LV Size (Mbytes) 512
Current LE 64
Allocated PE 64
Used PV 1

LV Name /dev/vg00/lvol2
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 512
Allocated PE 512
Used PV 1

LV Name /dev/vg00/lvol3
LV Status available/syncd
LV Size (Mbytes) 512
Current LE 64
Allocated PE 64
Used PV 1

LV Name /dev/vg00/lvol4
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 128
Allocated PE 128
Used PV 1

LV Name /dev/vg00/lvol5
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 128
Allocated PE 128
Used PV 1

LV Name /dev/vg00/lvol6
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 512
Allocated PE 512
Used PV 1

LV Name /dev/vg00/lvol7
LV Status available/syncd
LV Size (Mbytes) 512
Current LE 64
Allocated PE 64
Used PV 1

LV Name /dev/vg00/lvol8
LV Status available/syncd
LV Size (Mbytes) 8192
Current LE 1024
Allocated PE 1024
Used PV 1

LV Name /dev/vg00/lvol9
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 512
Allocated PE 512
Used PV 1

LV Name /dev/vg00/lvol10
LV Status available/syncd
LV Size (Mbytes) 2560
Current LE 320
Allocated PE 320
Used PV 1


--- Physical volumes ---
PV Name /dev/dsk/c3t2d0s2
PV Status available
Total PE 4228
Free PE 900
Autoswitch On


Why does there appear to be slices?

Other v2 boxes don't have them - is this an Itanium difference?

Rgds....Geoff

[Torsten.]

Yes, you need partitions on your root disk: 1 for EFI, 1 for HP-UX, 1 for diag + tools

Notice, also the mirror procedure is different. There are a lot of forum threads regarding this.

[Chan 007]

Geoff,

Yes in Itanium it is like what you got.

E.g. from one of the boot I manuals I gone,

#ioscan -fnkC disk
disk 0 0/0/0/2/0.6.0 sdisk CLAIMED DEVICE HP 73.4GST373453L
C
/dev/dsk/c0t6d0 /dev/rdsk/c0t6d0
/dev/dsk/c0t6d0s1 /dev/rdsk/c0t6d0s1 (EFI boot partition)
/dev/dsk/c0t6d0s2 /dev/rdsk/c0t6d0s2 (HP-UX partition)
/dev/dsk/c0t6d0s3 /dev/rdsk/c0t6d0s3 (EFI partition (for future))

007

[Robert-Jan Goossens_1 · Accepted solution]

Hi Geoff,

Yes it is an Itanium specific difference.

Check this doc,

Chapter "Boot disk layout and EFI"

http://www.itrc.hp.com/service/iv/docDisplay.do?docId=prodITRC/DE_SW_UX_swrec_EN_01_E/Itanium.pdf

Best regards,
Robert-Jan

[James R. Ferguson]

Hi Geoff:

Yes, Itanium uses slices for the root disk. One discussion (for creating mirrors of the root disk on Itanium servers) can be found here:

http://docs.hp.com/en/5991-1236/When_Good_Disks_Go_Bad.pdf

Have a look to at chapter-29 (Itanium Architecture) in the HP-UX Software Recovery Handbook:

http://www1.itrc.hp.com/service/iv/docDisplay.do?docId=prodITRC/DE_SW_UX_swrec_EN_01_E/Itanium.pdf

Regards!

...JRF...

[Geoff Wild]

Solution provided above.

Thanks all!

[Jeff Schussele]

Hi Geoff,

Yep - this is due to the Itanium architecture - specifically it's ability to run LINUX as well as Windoze. As such, the boot disk must use the FAT-32 filesystem instead of the native HP-UX HFS/VXFS structure for boot/root.
Since the rpXXXX systems cannot run Windoze, the 11iv2 for PA-RISC does not need FAT-32 so nothing changes on them filesystem-wise.
Oh....and wait 'til you see the new method for root/boot mirroring....QUITE....different.
And the coup-de-grace - because the FAT-32 cannot be written onto tapes - you can't directly boot MTRs. You have to boot the DVD & then extract data from the tape. That's a problem in my book, not to even mention the time lost havibg to deal with 2 sets of media during a DR scenario. We'll be using MNRs on all our Itanium HP-UX systems - for sure.

HTH,
Jeff