by hypoeddy » Tue Sep 20, 2016 5:50 am
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?
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?