After a HDD crash the Datastore was not recognized by vSphere Hypervisor anymore.
However, the partition is still there...
A check with voma gave me the following result:
##########################################################
voma -m ptbl -f check -d /vmfs/devices/disks/naa.
600300570128c0f01fa34076a6a6143c
Running Partition table checker version 0.1 in check mode
Phase 1: Checking device for valid primary GPT
Detected valid GPT signatures
Number Start End Type
1 10229760 1169686494 vmfs
Found a valid partition table on the device
Total Errors Found: 0
[root@localhost:/vmfs/volumes] voma -m vmfs -f check -d /vmfs/devices/disks/naa.
600300570128c0f01fa34076a6a6143c
Checking if device is actively used by other hosts
Running VMFS Checker version 1.2 in check mode
Initializing LVM metadata, Basic Checks will be done
Initializing LVM metadata../
LVM magic not found at expected Offset,
It might take long time to search in rest of the disk.
VMware ESX Question:
Do you want to continue (Y/N)?
0) _Yes
1) _No
Select a number from 0-1: 0
Phase 1: Checking VMFS header and resource files
Detected VMFS file system (labeled:'datastore1') with UUID:51baf2a5-cbf90d8b-b88d-001999feac3a, Version 5:58
ON-DISK ERROR: corrupted SFD address <INVALID c0 r0> for resource file PB2
ERROR: Failed to check pb2.sf.
VOMA failed to check device : Severe corruption detected
Total Errors Found: 1
##########################################################
Is there any way to repair that pb2.sf file? Or any other may to get the datastore working again?
.
