Operating System - HP-UX
1753814 Members
7361 Online
108805 Solutions
New Discussion юеВ

problems with mirror disk

 
jose luis_4
Occasional Contributor

problems with mirror disk

I have a question on mirroring.
I configure disk mirroring on one itanium rx1620.
Main disk failed.
How can i do to back up the second disk used ignite software, the software , send this messages :


* Creating local directories for configuration files and archive.

======= 05/17/06 20:42:22 MDT Started make_tape_recovery. (Wed May 17
20:42:22 MDT 2006)
@(#) Ignite-UX Revision B.5.4.50
@(#) net_recovery (opt) $Revision: 10.637 $

* Testing pax for needed patch
* Passed pax tests.
* Checking Versions of Ignite-UX filesets
* Creating System Configuration.
* /opt/ignite/bin/save_config -f
/var/opt/ignite/recovery/2006-05-17,20:42/system_cfg vg00
vgdisplay: Warning: couldn't query physical volume "/dev/dsk/c2t1d0s2":
The specified path does not correspond to physical volume attached to
this volume group
vgdisplay: this volume group
lvdisplay: Warning: couldn't query all of the physical volumes.
lssf: Must specify a special_file
usage: lssf special_file ...
save_config: error - unknown disk type for , not SCSI or HPFL
save_config: error - cannot determine root disk

======= 05/17/06 20:42:40 MDT make_tape_recovery completed unsuccessfully


Any help or information to this would be helpful thanks.
5 REPLIES 5
Torsten.
Acclaimed Contributor

Re: problems with mirror disk

Please provide some more information first, e.g. "ioscan -fn" "lvlnboot -v" "vgdisplay -v vg00" "strings /etc/lvmtab"

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   
Ninad_1
Honored Contributor

Re: problems with mirror disk

I think since your 1st disk has failed and the vg00 VG info still refers to the primary disk - it is giving error that its not able to query the disk (naturally bcos that disk is failed).
The disk c2t1d0s2 must be your primary boot disk.
Check using lvlnboot -v
Check which are the mirrored volumes using
vgdisplay -v /dev/vg00 | grep 'LV Name' | while read lvolname
do
echo "$lvolname $(lvdisplay -v $lvolname | grep 'Mirror') "
done
Check if the mirrored volumes are using the failed disk.

If necessary you can use lvreduce -m 0 for the mirrored volumes which are using the failed disk and then vgreduce to remove the failed disk.

Regards,
Ninad
jose luis_4
Occasional Contributor

Re: problems with mirror disk

Hi Torsten-
i send the information:

ioscan -fn

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 (1229)
ba 0 0/0 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
usb 0 0/0/1/0 hcd CLAIMED INTERFACE NEC USB Interface
usbhub 0 0/0/1/0.1 hub CLAIMED DEVICE USB Root Hub
usbhid 1 0/0/1/0.1.2 hid CLAIMED DEVICE USB HID Kbd(0) Mouse(1)
usb 1 0/0/1/1 hcd CLAIMED INTERFACE NEC USB Interface
usbhub 1 0/0/1/1.1 hub CLAIMED DEVICE USB Root Hub
/dev/hub
usb 2 0/0/1/2 ehci CLAIMED INTERFACE NEC USB Interface
sideba 0 0/0/2/0 side_multi CLAIMED INTERFACE CMD IDE controller
ext_bus 0 0/0/2/0.0 side CLAIMED INTERFACE IDE Primary Channel
target 0 0/0/2/0.0.0 tgt CLAIMED DEVICE
disk 0 0/0/2/0.0.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-C
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
target 1 0/0/2/0.0.7 tgt CLAIMED DEVICE
ctl 0 0/0/2/0.0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c0t7d0
ext_bus 1 0/0/2/0.1 side CLAIMED INTERFACE IDE Secondary Channel
target 2 0/0/2/0.1.7 tgt CLAIMED DEVICE
ctl 1 0/0/2/0.1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c1t7d0
lan 0 0/0/3/0 intl100 CLAIMED INTERFACE Intel PCI Pro 10/100Tx Server Adapter
ba 1 0/1 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
ext_bus 2 0/1/1/0 mpt CLAIMED INTERFACE Ultra320 Wide LVD SCSI
target 3 0/1/1/0.0 tgt CLAIMED DEVICE
disk 1 0/1/1/0.0.0 sdisk CLAIMED DEVICE HP 146 GST3146807LC
/dev/dsk/c2t0d0 /dev/rdsk/c2t0d0
/dev/dsk/c2t0d0s1 /dev/rdsk/c2t0d0s1
/dev/dsk/c2t0d0s2 /dev/rdsk/c2t0d0s2
/dev/dsk/c2t0d0s3 /dev/rdsk/c2t0d0s3
target 4 0/1/1/0.1 tgt CLAIMED DEVICE
disk 2 0/1/1/0.1.0 sdisk CLAIMED DEVICE HP 146 GST3146807LC
/dev/dsk/c2t1d0 /dev/rdsk/c2t1d0
/dev/dsk/c2t1d0s1 /dev/rdsk/c2t1d0s1
/dev/dsk/c2t1d0s2 /dev/rdsk/c2t1d0s2
/dev/dsk/c2t1d0s3 /dev/rdsk/c2t1d0s3
target 5 0/1/1/0.7 tgt CLAIMED DEVICE
ctl 2 0/1/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c2t7d0
ext_bus 3 0/1/1/1 mpt CLAIMED INTERFACE Ultra320 Wide LVD SCSI
target 6 0/1/1/1.7 tgt CLAIMED DEVICE
ctl 3 0/1/1/1.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c3t7d0
lan 1 0/1/2/0 igelan CLAIMED INTERFACE HP PCI 1000Base-T Core
ba 2 0/2 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
ba 3 0/3 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
ba 4 0/4 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
ext_bus 4 0/4/1/0 c8xx CLAIMED INTERFACE SCSI C1010 Ultra160 Wide LVD A6828-60101
target 7 0/4/1/0.3 tgt CLAIMED DEVICE
tape 0 0/4/1/0.3.0 stape CLAIMED DEVICE HP C7438A
/dev/rmt/0m /dev/rmt/c4t3d0BESTn
/dev/rmt/0mb /dev/rmt/c4t3d0BESTnb
/dev/rmt/0mn /dev/rmt/c4t3d0DDS
/dev/rmt/0mnb /dev/rmt/c4t3d0DDSb
/dev/rmt/c4t3d0BEST /dev/rmt/c4t3d0DDSn
/dev/rmt/c4t3d0BESTb /dev/rmt/c4t3d0DDSnb
target 8 0/4/1/0.7 tgt CLAIMED DEVICE
ctl 4 0/4/1/0.7.0 sctl CLAIMED DEVICE Initiator
/dev/rscsi/c4t7d0
ba 5 0/5 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
ba 6 0/6 lba CLAIMED BUS_NEXUS Local PCI-X Bus Adapter (122e)
tty 0 0/6/1/0 asio0 CLAIMED INTERFACE PCI SimpleComm (103c1290)
/dev/diag/mux0 /dev/mux0 /dev/tty0p0
tty 1 0/6/1/1 asio0 CLAIMED INTERFACE PCI Serial (103c1048)
/dev/MPdiag1 /dev/mux1 /dev/tty1p2
/dev/diag/mux1 /dev/tty1p0 /dev/tty1p4
graphics 0 0/6/2/0 gvid_core CLAIMED INTERFACE PCI Display (10025159)
processor 0 120 processor CLAIMED PROCESSOR Processor
ba 7 250 pdh CLAIMED BUS_NEXUS Core I/O Adapter
ipmi 0 250/0 ipmi CLAIMED INTERFACE IPMI Controller
/dev/ipmi
tty 2 250/1 asio0 CLAIMED INTERFACE Built-in RS232C
/dev/diag/mux2 /dev/mux2 /dev/tty2p0
tty 3 250/2 asio0 CLAIMED INTERFACE Built-in RS232C
/dev/diag/mux3 /dev/mux3 /dev/tty3p0
acpi_node 0 250/3 acpi_node CLAIMED INTERFACE Acpi Hardware




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

lvlboot -v


not: Couldn't query physical volume "/dev/dsk/c2t1d0s2":
The specified path does not correspond to physical volume attached to
this volume group





-------------------------------------------------------------------------------
vgdisplay -v vg00
--- Volume groups ---
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 12
Open LV 12
Max PV 16
Cur PV 2
Act PV 1
Max PE per PV 4356
VGDA 2
PE Size (Mbytes) 32
Total PE 4346
Alloc PE 3130
Free PE 1216
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/stale
LV Size (Mbytes) 320
Current LE 10
Allocated PE 20
Used PV 1

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

LV Name /dev/vg00/lvol3
LV Status available/stale
LV Size (Mbytes) 224
Current LE 7
Allocated PE 14
Used PV 1

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

LV Name /dev/vg00/lvol5
LV Status available/stale
LV Size (Mbytes) 32
Current LE 1
Allocated PE 2
Used PV 1

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

LV Name /dev/vg00/lvol7
LV Status available/stale
LV Size (Mbytes) 2816
Current LE 88
Allocated PE 176
Used PV 1

LV Name /dev/vg00/lvol8
LV Status available/stale
LV Size (Mbytes) 4608
Current LE 144
Allocated PE 288
Used PV 1

LV Name /dev/vg00/lvol9
LV Status available/stale
LV Size (Mbytes) 10240
Current LE 320
Allocated PE 640
Used PV 1

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

LV Name /dev/vg00/lvol11
LV Status available/stale
LV Size (Mbytes) 51200
Current LE 1600
Allocated PE 3200
Used PV 1

LV Name /dev/vg00/lvol12
LV Status available/stale
LV Size (Mbytes) 10240
Current LE 320
Allocated PE 640
Used PV 1


--- Physical volumes ---
PV Name /dev/dsk/c2t0d0s2
PV Status available
Total PE 4346
Free PE 1216
Autoswitch On





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

/etc/lvmtab

├Г┬и /dev/vg00 ├В┬л ├Е 7A├в ├Л ├Л /dev/dsk/c2t1d0s2 /dev/dsk/c2t0d0s2 -----------------------------------------------------------


Thanks an greetings

Jose Luis
Torsten.
Acclaimed Contributor

Re: problems with mirror disk

Your disks seems to be not completly dead, since it is shown in ioscan. Ignite is trying to touch every configured disk.

Perhaps it will help to deactivate the disk device.

# pvchange -a n /dev/dsk/c2t1d0

But I guess you have to reduce the mirror.

Read this document (chapter 5 - removing the disk) for how to lvreduce using the -k (key) option:

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

The same document is telling you how to re-mirror your Integrity system.

Hope this helps!
Regards
Torsten.

__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.

__________________________________________________
No support by private messages. Please ask the forum!

If you feel this was helpful please click the KUDOS! thumb below!   

Re: problems with mirror disk


If you want to use make_tape_recovery you definitely need to reduce the mirror, since it does't work when you have missing PVs.

If you want to quickly save the working PV, you can also use a dd of the /dev/rdsk if you have an empty working disk, or an fbackup or a tar of the entire syetem excluding file systems containing data (ex. databases or such which makes no sense to save without closing the database)

When you will replace the faulty disk, you need to run ioscan, then pvcreate -B, then mkboot to set "hpux -lq" autostart string, then vgcfgrestore as specified in the whitepaper.

Best regards, good luck
Alessandro Bocchino
http://www.risolve.com
We work in the dark, we do what we can, we give what we have, our doubt is our passion, and our passion is our task - the rest, is the madness of art - Henry James