I have a destriped RAID with several VMDK files existing within a VMFS file system. Any scan only shows fat or NTFS volumes. The list of file systems to search for does not include "vmfs". Is the software somehow going into each vmdk, recognizing it as a volume, and then just listing the contents?
The other question I have regards opening a scan file of a partial scan. When I open an NTFS volume which I know was a vmdk, it hangs midway after showing a list of fixup errors. If I scan futher, the fixup list will start with a larger record number for the error. It seems like when I scan further, it must be locating files and associating them with the NTFS records. It would seem that I shouldn't have to scan to that area in order for the software to look there once I open the volume and it traverses the NTFS records. Are unscanned areas not looked at when you open a found volume?
VMware VMFS recovery
Re: VMware VMFS recovery
Who/what determined that the RAID is correctly destriped?
Than you for clarifying
Than you for clarifying
Robert
Technical Manager @ Recupero Dati RAID FAsTec (Italy)
USEFUL RULES and GUIDELINES
1) What to check BEFORE begin a disk image/clone process [link]
2) Disks that are too slow while imaging/cloning them [link]
3) All my posts on this forum [link]
Technical Manager @ Recupero Dati RAID FAsTec (Italy)
USEFUL RULES and GUIDELINES
1) What to check BEFORE begin a disk image/clone process [link]
2) Disks that are too slow while imaging/cloning them [link]
3) All my posts on this forum [link]
Re: VMware VMFS recovery
R-Studio doesn't support the VMFS file system yet. So it might find NTFS file systems incorrectly.hypoeddy wrote:I have a destriped RAID with several VMDK files existing within a VMFS file system. Any scan only shows fat or NTFS volumes. The list of file systems to search for does not include "vmfs". Is the software somehow going into each vmdk, recognizing it as a volume, and then just listing the contents?
The other question I have regards opening a scan file of a partial scan. When I open an NTFS volume which I know was a vmdk, it hangs midway after showing a list of fixup errors. If I scan futher, the fixup list will start with a larger record number for the error. It seems like when I scan further, it must be locating files and associating them with the NTFS records. It would seem that I shouldn't have to scan to that area in order for the software to look there once I open the volume and it traverses the NTFS records. Are unscanned areas not looked at when you open a found volume?
Re: VMware VMFS recovery
VMFS can be a challenge to recover. Send me a PM if you'd like some remote assistance.
Re: VMware VMFS recovery
Yes, definitely
Remote support is available also at our side
If you need it just drop a private message
Remote support is available also at our side
If you need it just drop a private message
Robert
Technical Manager @ Recupero Dati RAID FAsTec (Italy)
USEFUL RULES and GUIDELINES
1) What to check BEFORE begin a disk image/clone process [link]
2) Disks that are too slow while imaging/cloning them [link]
3) All my posts on this forum [link]
Technical Manager @ Recupero Dati RAID FAsTec (Italy)
USEFUL RULES and GUIDELINES
1) What to check BEFORE begin a disk image/clone process [link]
2) Disks that are too slow while imaging/cloning them [link]
3) All my posts on this forum [link]