Unable to Activate VG01 | Smart Array logical drive failed

[Torsten.]

You may try to activate the VG, maybe some of the LVOLS are still there, but likely 50% of the data (the other PV) is just gone - hence you probably have corrupted filesystems.

What does the controller say (on console) during boot?

[Aamir_Majeed]

After enabling Logical Drive during initail startup, I can activate Volume Group now, But some of LVOLs are not coming.

I am getting following errors;

===============================================================================================

Searching for devices
Scsi(Pun0,Lun0) HP 73.4GST373454LC      HPC2 (320 MBytes/sec)
Scsi(Pun1,Lun0) HP 73.4GST373454LC      HPC2 (320 MBytes/sec)
HP Smart Array 6400-128 Controller       (version 2.34)  2 Logical Drives
1792-Drive Array - Valid Data Found in Array Accelerator
     Data will automatically be written to drive array.
1794-Drive Array - Array Accelerator Battery Charge Low
     Array Accelerator Posted-Write Cache is temporarily disabled.
     Array Accelerator batteries have failed to charge and should be replaced
1779-Drive Array - Replacement drive(s) detected OR previously failed
     drive(s) now appear to be operational:
         SCSI Port 1:  SCSI ID(s) 0, 1  [ Enclosure bay(s): 1, 2 ]
     Logical drive(s) disabled due to possible data loss.
     Restore data from backup if replacement drive(s) have been installed.

Press "F1" to continue...

# mountall
mountall: /dev/vg01/windb has to be fsck'd
mountall: diagnostics from fsck
UX:vxfs fsck: ERROR: V-3-20023: file system on /dev/vg01/windb has structural damage
mountall: cannot fsck /dev/vg01/windb
mountall: diagnostics from fsck
file system check failure, aborting ...
nt 0 has bad checksum
read of primary OLT failed
UX:vxfs fsck: ERROR: V-3-20727: OLT extent 1 has bad magic
read of OLT copy failed
UX:vxfs fsck: ERROR: V-3-20718: no valid OLT, cannot continue
mountall: /dev/vg01/windb failed in fsck
mountall: /dev/vg01/windb cannot be mounted
mountall: /dev/vg01/u02 has to be fsck'd
mountall: diagnostics from fsck
UX:vxfs fsck: ERROR: V-3-20023: file system on /dev/vg01/u02 has structural damage
mountall: cannot fsck /dev/vg01/u02
mountall: diagnostics from fsck
file system check failure, aborting ...
nt 0 has bad checksum
read of primary OLT failed
UX:vxfs fsck: ERROR: V-3-20727: OLT extent 1 has bad magic
read of OLT copy failed
UX:vxfs fsck: ERROR: V-3-20718: no valid OLT, cannot continue
mountall: /dev/vg01/u02 failed in fsck
mountall: /dev/vg01/u02 cannot be mounted
mountall: /dev/vg01/u01 has to be fsck'd
mountall: diagnostics from fsck
UX:vxfs fsck: ERROR: V-3-20023: file system on /dev/vg01/u01 has structural damage
mountall: cannot fsck /dev/vg01/u01
mountall: diagnostics from fsck
file system check failure, aborting ...
nt 0 has bad checksum
read of primary OLT failed
UX:vxfs fsck: ERROR: V-3-20726: OLT extent 1 has bad checksum
read of OLT copy failed
UX:vxfs fsck: ERROR: V-3-20718: no valid OLT, cannot continue
mountall: /dev/vg01/u01 failed in fsck
mountall: /dev/vg01/u01 cannot be mounted

===============================================================================================

Is there any way to recover this damage ?

Thanks,

AM

[Torsten.]

What is the status in

# sautil /dev/ciss4

# saconfig /dev/ciss4

now?

[Aamir_Majeed]

Hi,

One logical drive status is OK and other is still failed, is there any solution available to recover Logical Volumes;

UX:vxfs fsck: ERROR: V-3-20023: file system on /dev/vg01/windb has structural damage
mountall: cannot fsck /dev/vg01/windb
mountall: diagnostics from fsck
file system check failure, aborting ...
nt 0 has bad checksum
read of primary OLT failed
UX:vxfs fsck: ERROR: V-3-20727: OLT extent 1 has bad magic
read of OLT copy failed
UX:vxfs fsck: ERROR: V-3-20718: no valid OLT, cannot continue

Thanks, AM.