ミラーディスク片系交換後、データ消失

[T_Ku]

ミラー構成のディスクで、片系のディスクを交換後、データが消失してしまいました。
手順のミスだったのか、原因教えて頂きたく、お願いします。
/dev/dsk/c6t0d0が交換したディスクです。
/dev/dsk/c4t0d0がミラーディスクです。

以下、実行コマンドです。
ID0102(root)#date
2010年01月06日 11時57分58秒
ID0102(root)#vgdisplay -v vg01
vgdisplay: Volume group not activated.
vgdisplay: Cannot display volume group "vg01".
ID0102(root)#
ID0102(root)#vgcfgrestore -n /dev/vg01 /dev/rdsk/c6t0d0
Volume Group configuration has been restored to /dev/rdsk/c6t0d0
ID0102(root)#vgchange -a y /dev/vg01
Activated volume group
Volume group "/dev/vg01" has been successfully changed.
ID0102(root)#date
2010年01月06日 12時45分06秒
ID0102(root)#vgdisplay -v /dev/vg01
--- Volume groups ---
VG Name /dev/vg01
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 9
Open LV 9
Max PV 16
Cur PV 2
Act PV 2
Max PE per PV 17373
VGDA 4
PE Size (Mbytes) 4
Total PE 34726
Alloc PE 33382
Free PE 1344
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0

--- Logical volumes ---
LV Name /dev/vg01/lvol1
LV Status available/syncd
LV Size (Mbytes) 4384
Current LE 1096
Allocated PE 2192
Used PV 2

LV Name /dev/vg01/lvol2
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 1024
Allocated PE 2048
Used PV 2

LV Name /dev/vg01/lvol3
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 1024
Allocated PE 2048
Used PV 2

LV Name /dev/vg01/lvol4
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 1024
Allocated PE 2048
Used PV 2

LV Name /dev/vg01/lvol5
LV Status available/syncd
LV Size (Mbytes) 33708
Current LE 8427
Allocated PE 16854
Used PV 2

LV Name /dev/vg01/lvol6
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 1024
Allocated PE 2048
Used PV 2

LV Name /dev/vg01/lvol7
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 1024
Allocated PE 2048
Used PV 2

LV Name /dev/vg01/lvol8
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 1024
Allocated PE 2048
Used PV 2

LV Name /dev/vg01/lvol9
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 1024
Allocated PE 2048
Used PV 2


--- Physical volumes ---
PV Name /dev/dsk/c6t0d0
PV Status available
Total PE 17363
Free PE 672
Autoswitch On

PV Name /dev/dsk/c4t0d0
PV Status available
Total PE 17363
Free PE 672
Autoswitch On

ID0102(root)#mountall
mountall: /dev/vg01/lvol9 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: not a valid vxfs file system
mountall: cannot fsck /dev/vg01/lvol9
mountall: diagnostics from fsck
invalid super-block
file system check failure, aborting ...
itialize aggregate
mountall: /dev/vg01/lvol9 failed in fsck
mountall: /dev/vg01/lvol9 cannot be mounted
mountall: /dev/vg01/lvol8 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: not a valid vxfs file system
mountall: cannot fsck /dev/vg01/lvol8
mountall: diagnostics from fsck
invalid super-block
file system check failure, aborting ...
itialize aggregate
mountall: /dev/vg01/lvol8 failed in fsck
mountall: /dev/vg01/lvol8 cannot be mounted
mountall: /dev/vg01/lvol1 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: not a valid vxfs file system
mountall: cannot fsck /dev/vg01/lvol1
mountall: diagnostics from fsck
invalid super-block
file system check failure, aborting ...
itialize aggregate
mountall: /dev/vg01/lvol1 failed in fsck
mountall: /dev/vg01/lvol1 cannot be mounted
mountall: /dev/vg01/lvol3 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: not a valid vxfs file system
mountall: cannot fsck /dev/vg01/lvol3
mountall: diagnostics from fsck
invalid super-block
file system check failure, aborting ...
itialize aggregate
mountall: /dev/vg01/lvol3 failed in fsck
mountall: /dev/vg01/lvol3 cannot be mounted
mountall: /dev/vg01/lvol2 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: not a valid vxfs file system
mountall: cannot fsck /dev/vg01/lvol2
mountall: diagnostics from fsck
invalid super-block
file system check failure, aborting ...
itialize aggregate
mountall: /dev/vg01/lvol2 failed in fsck
mountall: /dev/vg01/lvol2 cannot be mounted
mountall: /dev/vg01/lvol4 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: not a valid vxfs file system
mountall: cannot fsck /dev/vg01/lvol4
mountall: diagnostics from fsck
invalid super-block
file system check failure, aborting ...
itialize aggregate
mountall: /dev/vg01/lvol4 failed in fsck
mountall: /dev/vg01/lvol4 cannot be mounted
mountall: /dev/vg01/lvol7 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: not a valid vxfs file system
mountall: cannot fsck /dev/vg01/lvol7
mountall: diagnostics from fsck
invalid super-block
file system check failure, aborting ...
itialize aggregate
mountall: /dev/vg01/lvol7 failed in fsck
mountall: /dev/vg01/lvol7 cannot be mounted
mountall: /dev/vg01/lvol6 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: not a valid vxfs file system
mountall: cannot fsck /dev/vg01/lvol6
mountall: diagnostics from fsck
invalid super-block
file system check failure, aborting ...
itialize aggregate
mountall: /dev/vg01/lvol6 failed in fsck
mountall: /dev/vg01/lvol6 cannot be mounted
mountall: /dev/vg01/lvol5 has to be fsck'd
mountall: diagnostics from fsck
vxfs fsck: not a valid vxfs file system
mountall: cannot fsck /dev/vg01/lvol5
mountall: diagnostics from fsck
invalid super-block
file system check failure, aborting ...
itialize aggregate
mountall: /dev/vg01/lvol5 failed in fsck
mountall: /dev/vg01/lvol5 cannot be mounted
ID0102(root)#

よろしくお願いします。

[masaakio65_1]

VxFS ファイルシステムじゃないって、メッセージがでてますから、LVMの不具合や手順のミス等で交換したディスクから同期が取られてしまったのか、元々故障時に壊れてしまっていたのか、どちらかなのですが、わかりませんね。

ディアクティベートされていたようですけれど、オンライン交換ができれば、もしかしたら何かわかったかもしれません。

http://docs.hp.com/en/oshpux11iv2.html#LVM%20Volume%20Manager

ここに、”When Good Disks Go Bad: Dealing with Disk Failures under LVM”というディスク故障にどう対応するかと言うマニュアルがあるのですが、結構11v3寄りの記述が多いです。また、パッチが色々紹介されていて、使っている環境にインストールされていない場合、有効ではない場合もあります。
ソフトウエアミラーの修理は、Know-Howもあるのでエンジニアに任せてしまった方がよい場合もあるとは思います。

良い情報ではなくてすみません。バックアップがあったと思いたいです。