topic Re: Mirroring question in Operating System - HP-UX

Mirroring question

Chris Fadrowski — Mon, 02 Jun 2008 11:09:49 GMT

I just inherited a server, it's a rx6600 IA 64 running 11.23 v3. Supposedly the two internal drives are mirrored (hardware). Can anyone point me to way to verify this? is there a command to see if they are indeed mirrored? Or another process?

Re: Mirroring question

Torsten. — Mon, 02 Jun 2008 11:20:27 GMT

I assume you have the standard SAS controller.

Try this (and adjust sasd0 as needed):

# sasmgr get_info -D /dev/sasd0 -q raid

Re: Mirroring question

Adam Winebaugh — Mon, 02 Jun 2008 11:25:15 GMT

Chris,
Run a lvlnboot -v and see what the output is. If you have a mirror it would look like this:

# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t6d0 (1/0/0/3/0.6.0) -- Boot Disk
/dev/dsk/c4t8d0 (1/0/4/1/0.8.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t6d0
/dev/dsk/c4t8d0
Root: lvol3 on: /dev/dsk/c0t6d0
/dev/dsk/c4t8d0
Swap: lvol2 on: /dev/dsk/c0t6d0
/dev/dsk/c4t8d0
Dump: lvol2 on: /dev/dsk/c0t6d0,

If not.. it is obvious.

Also do a swlist and see it MirrorDisk/UX is even installed........

Re: Mirroring question

Torsten. — Mon, 02 Jun 2008 11:29:53 GMT

Well, the rx6600 is able to do a *hardware* raid, so LVM mirroring is not needed for the boot disks.

Example:

sasmgr get_info -D /dev/sasd0 -q raid

Fri Jan 11 11:05:19 2008

---------- LOGICAL DRIVE 1 ----------

Raid Level : RAID 1
Volume sas address : 0x4b3ec4b544b3333
Device Special File : /dev/rdsk/c3t0d0
Raid State : OPTIMAL
Raid Status Flag : ENABLED
Raid Size : 34332
Rebuild Rate : 0.00 %
Rebuild Progress : 100.00 %

Participating Physical Drive(s) :

SAS Address Enc Bay Size(MB) Type State

0x5000c50000ae1111 1 2 34732 SECONDARY ONLINE
0x5000c50000ae2222 1 1 34732 PRIMARY ONLINE

ioscan:

...
disk 2 0/2/1/0.0.0.0.0 sdisk CLAIMED DEVICE
HP IR Volume
/dev/dsk/c3t0d0 /dev/rdsk/c3t0d0
/dev/dsk/c3t0d0s1 /dev/rdsk/c3t0d0s1
/dev/dsk/c3t0d0s2 /dev/rdsk/c3t0d0s2
/dev/dsk/c3t0d0s3 /dev/rdsk/c3t0d0s3
...

Note: it is called

"HP IR Volume" = integrated RAID

Re: Mirroring question

Jeeshan — Mon, 02 Jun 2008 11:31:27 GMT

Hi Chris

#lvlnboot -v

Re: Mirroring question

Chris Fadrowski — Mon, 02 Jun 2008 11:35:08 GMT

how do you find the proper sasd0?

root@host:/>sasmgr get_info -D /dev/sasd0 -q raid
ERROR: Unable to open the file /dev/sasd0.
Please verify the correctness of the HBA device file specified
with the -D option.

is what i get. Sorry, i have always used mirrorUX in the past.

Re: Mirroring question

Chris Fadrowski — Mon, 02 Jun 2008 11:36:51 GMT

root@hostname:/>lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t6d0s2 (0/0/0/2/0.6.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t6d0s2
Root: lvol3 on: /dev/dsk/c0t6d0s2
Swap: lvol2 on: /dev/dsk/c0t6d0s2
Dump: lvol2 on: /dev/dsk/c0t6d0s2, 0

Here is the lvlnboot -v, all disks appear the same.

Re: Mirroring question

Torsten. — Mon, 02 Jun 2008 11:37:45 GMT

The sas controller looks like this in ioscan:

escsi_ctlr 0 0/1/1/0 sasd CLAIMED INTERFACE HP PCI/PCI-X SAS MPT Adapter
/dev/sasd0

Re: Mirroring question

Torsten. — Mon, 02 Jun 2008 11:38:55 GMT

Could you please post "ioscan -fn"?

Re: Mirroring question

Chris Fadrowski — Mon, 02 Jun 2008 11:42:36 GMT

root@hostname:/>ioscan -fnC escsi_ctlr
Class I H/W Path Driver S/W State H/W Type Description
====================================================================
escsi_ctlr 0 0/4/1/0 sasd CLAIMED INTERFACE HP PCI/PCI-X SAS MPT Adapter
/dev/sasd0

root@hostname:/>sasmgr get_info -D /dev/sasd0 -q raid

Mon Jun 2 07:40:54 2008

---------- PHYSICAL DRIVES ----------
LUN dsf SAS Address Enclosure Bay Size(MB)

/dev/rdsk/c0t0d0 0x5000cca0000dcde9 1 7 70007
/dev/rdsk/c0t1d0 0x5000cca0000bc321 1 8 70007

Re: Mirroring question

Torsten. — Mon, 02 Jun 2008 11:47:54 GMT

The reported disks are c0t0d0 and c0t1d0, but your boot disk is c0t6d0.

So better to post the ioscan as suggested.

Re: Mirroring question

Chris Fadrowski — Mon, 02 Jun 2008 11:53:52 GMT

Class I H/W Path Driver S/W State H/W Type Description
===================================================================================
root 0 root CLAIMED BUS_NEXUS
ioa 0 0 sba CLAIMED BUS_NEXUS System Bus Adapter (4030)
ba 0 0/0 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
tty 0 0/0/1/0 rmp3f01 CLAIMED INTERFACE PCI class(255,0) (103c1303)
tty 1 0/0/1/1 rmp3f01 CLAIMED INTERFACE PCI SimpleComm (103c1302)
tty 2 0/0/1/2 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
/dev/diag/mux2 /dev/mux2 /dev/tty2p0
OO 0 0/0/2/0 UsbOhci CLAIMED INTERFACE USB OHCI Interface
OO 1 0/0/2/1 UsbOhci CLAIMED INTERFACE USB OHCI Interface
OO 2 0/0/2/1.0 UsbMiniBus CLAIMED INTERFACE USB Composite Device
OO 5 0/0/2/1.0.0 UsbBulkOnlyMS CLAIMED DEVICE USB Bulk Only
disk 1 0/0/2/1.0.16 UsbScsiAdaptor CLAIMED DEVICE USB SCSI Stack Adaptor
/dev/deviceFileSystem/Usb/MassStorage/dsk/disk@hp-1008+294=A60020000001
/dev/deviceFileSystem/Usb/MassStorage/rdsk/disk@hp-1008+294=A60020000001
OO 6 0/0/2/2 UsbEhci CLAIMED INTERFACE USB EHCI Interface
ba 1 0/1 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
slot 0 0/1/1 pci_slot CLAIMED SLOT PCI Slot
fc 0 0/1/1/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Sto
rage Adapter
/dev/td0
slot 1 0/1/2 pci_slot CLAIMED SLOT PCI Slot
fc 1 0/1/2/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Sto
rage Adapter
/dev/td1
ba 2 0/2 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
slot 2 0/2/1 pci_slot CLAIMED SLOT PCI Slot
ba 3 0/3 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
slot 3 0/3/1 pci_slot CLAIMED SLOT PCI Slot
ba 4 0/4 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
slot 4 0/4/1 pci_slot CLAIMED SLOT PCI Slot
escsi_ctlr 0 0/4/1/0 sasd CLAIMED INTERFACE HP PCI/PCI-X SAS MPT Adapter
/dev/sasd0
ext_bus 0 0/4/1/0.0.0 sasd_vbus CLAIMED INTERFACE SAS Device Interface
target 1 0/4/1/0.0.0.0 tgt CLAIMED DEVICE
disk 3 0/4/1/0.0.0.0.0 sdisk CLAIMED DEVICE HP DG072A4951
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
target 0 0/4/1/0.0.0.1 tgt CLAIMED DEVICE
disk 2 0/4/1/0.0.0.1.0 sdisk CLAIMED DEVICE HP DG072A4951
/dev/dsk/c0t1d0 /dev/dsk/c0t1d0s2 /dev/rdsk/c0t1d0 /dev/rdsk/c0t1d0s2
/dev/dsk/c0t1d0s1 /dev/dsk/c0t1d0s3 /dev/rdsk/c0t1d0s1 /dev/rdsk/c0t1d0s3
slot 5 0/4/2 pci_slot CLAIMED SLOT PCI Slot
lan 0 0/4/2/0 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000Base-T D
ual-port Core
lan 1 0/4/2/1 iether CLAIMED INTERFACE HP AB352-60003 PCI/PCI-X 1000Base-T D
ual-port Core
ba 5 0/5 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
slot 6 0/5/1 pci_slot CLAIMED SLOT PCI Slot
slot 7 0/5/2 pci_slot CLAIMED SLOT PCI Slot
ba 6 0/5/2/0 PCItoPCI CLAIMED BUS_NEXUS PCItoPCI Bridge
ext_bus 1 0/5/2/0/4/0 mpt CLAIMED INTERFACE HP AB290-60001 PCI/PCI-X U320 SCSI 2-
port U320 SCSI/2-port 1000B-T Combo Adapter
/dev/mpt1
ext_bus 2 0/5/2/0/4/1 mpt CLAIMED INTERFACE HP AB290-60001 PCI/PCI-X U320 SCSI 2-
port U320 SCSI/2-port 1000B-T Combo Adapter
/dev/mpt2
lan 2 0/5/2/0/6/0 iether CLAIMED INTERFACE HP AB290-60001 PCI/PCI-X 1000Base-T 2
-port U320 SCSI/2-port 1000B-T Combo Adapter
lan 3 0/5/2/0/6/1 iether CLAIMED INTERFACE HP AB290-60001 PCI/PCI-X 1000Base-T 2
-port U320 SCSI/2-port 1000B-T Combo Adapter
ba 7 0/6 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
slot 8 0/6/1 pci_slot CLAIMED SLOT PCI Slot
ba 8 0/7 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (12ee)
slot 9 0/7/1 pci_slot CLAIMED SLOT PCI Slot
processor 0 120 processor CLAIMED PROCESSOR Processor
processor 1 121 processor CLAIMED PROCESSOR Processor
processor 2 122 processor CLAIMED PROCESSOR Processor
processor 3 123 processor CLAIMED PROCESSOR Processor
ba 9 250 pdh CLAIMED BUS_NEXUS Core I/O Adapter
ipmi 0 250/0 ipmi CLAIMED INTERFACE IPMI Controller
/dev/ipmi
tty 3 250/1 asio0 CLAIMED INTERFACE Built-in RS232C
/dev/diag/mux3 /dev/mux3 /dev/tty3p0
acpi_node 0 250/2 acpi_node CLAIMED INTERFACE Acpi Hardware

Re: Mirroring question

Torsten. — Mon, 02 Jun 2008 12:02:56 GMT

The both disks are not mirrored at all:

disk 3 0/4/1/0.0.0.0.0 sdisk CLAIMED DEVICE HP DG072A4951
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
target 0 0/4/1/0.0.0.1 tgt CLAIMED DEVICE
disk 2 0/4/1/0.0.0.1.0 sdisk CLAIMED DEVICE HP DG072A4951
/dev/dsk/c0t1d0 /dev/dsk/c0t1d0s2 /dev/rdsk/c0t1d0 /dev/rdsk/c0t1d0s2
/dev/dsk/c0t1d0s1 /dev/dsk/c0t1d0s3 /dev/rdsk/c0t1d0s1 /dev/rdsk/c0t1d0s3

But where the c0t6d0 reported in lvlnboot is coming from? You don't have that disk.

Re: Mirroring question

Chris Fadrowski — Mon, 02 Jun 2008 12:05:10 GMT

am i able to mirror this after the fact? I see two physical disks in the system.

I am not sure of the history of the box or how it was running before. Can i mirror without rebuilding?

Re: Mirroring question

Torsten. — Mon, 02 Jun 2008 12:06:59 GMT

If you want to use the hardware mirror, all data will be deleted. So you need to backup/restore or even cold install after setting up the *hardware* mirror.

Otherwise you can use LVM mirror as usual.

Re: Mirroring question

Chris Fadrowski — Mon, 02 Jun 2008 12:08:16 GMT

i could do a make_tape_recovery, mirror then recover. I don't have mirror-ux installed on the box.

Re: Mirroring question

Torsten. — Mon, 02 Jun 2008 12:10:28 GMT

Yes, you can.

BTW, where did you take the

lvlnboot -v

command?

This server has NO hardware path
/dev/dsk/c0t6d0s2 (0/0/0/2/0.6.0)

Different system?

Re: Mirroring question

Torsten. — Mon, 02 Jun 2008 12:12:30 GMT

Here is the manual link:

http://docs.hp.com/en/J6369-90071/index.html

http://docs.hp.com/en/J6369-90071/ch03s03.html

Re: Mirroring question

Chris Fadrowski — Mon, 02 Jun 2008 12:13:23 GMT

not sure, i was working in two different systems and may have had a paste image in my clipbook. Here is the correct lvlnboot -v

root@hostname:/>lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/disk/disk5_p2 -- Boot Disk
Boot: lvol1 on: /dev/disk/disk5_p2
Root: lvol3 on: /dev/disk/disk5_p2
Swap: lvol2 on: /dev/disk/disk5_p2
Dump: lvol2 on: /dev/disk/disk5_p2, 0

Re: Mirroring question

Torsten. — Mon, 02 Jun 2008 12:16:50 GMT

But this is hp-ux 11.31 (hp-ux 11iv3) - not 11.23.

Anyway, proceed as suggested.

Good luck!

Consider to read this too finally:

http://forums12.itrc.hp.com/service/forums/helptips.do?#33