Michael,
As indicated earlier this is not the best approach, sharing nonetheless since you have requested
Do note that VMware does not support/perform data recovery services and I doubt if there are any utilities to provide file to LBA mapping.
As reverse engineering , you can try these for vmdk's alone. see the below example,
~ # vmkfstools -t0 /vmfs/volumes/Openfiler_3/
Test/Test.vmdk
Mapping for file /vmfs/volumes/Openfiler_3/TestDBS/Test.vmdk (1073741824 bytes in size):
[ 0: 1073741824] --> [VMFS Z- LVID:52d63c04-fcdad496-be74-000c29409d5c/52d63c03-c120e0bb-6715-000c29409d5c/1:( 2746220544 --> 3819962368)]
Logical LBA range is for file is - [ 0: 1073741824]
Physical Byte offsets - 2746220544 --> 3819962368
Divide the physical byte offset by 512 and you would have the physical HBA range. Which may or may not include the LBA's you know as impacted.
Pretty much needle in a haystack!!!