FLR of archive taken in Ranger 4.x or 5.x shows "unrecognized volume" after mount operation and is not browseable.
Normal, non-dynamic, non GUID Partition Table-formatted (GPT) disk shows "unrecognized volume" when attempting to mount an archive for an FLR operation. The mount, although successful, does not allow the drive or folders to be explored for selecting folders/files to recover via the FLR.
If using ESX(i) 4.0 or later, and the VM being backed-up is configured to use Change Block Tracking, the Change Block Tracking files on the VM may have become corrupted, rendering a non-useable archive. A full restore of the volume will confirm this, yielding a non-bootable VM.
To "reset" the change tracking files and fix the issue:
1) DISABLE Change Tracking for the VM(s) in question (right-click the VM in vRanger's "My Inventory" screen and select "Disable Change Tracking".
2) Using the VMware client, take a NEW snapshot of the VM(s).
3) When complete, go into Snapshot Manager for the VM(s) and perform a "Delete All" operation.
4) Re-enable Change Tracking on the VM.
5) Take a NEW backup of the VM.
6) Attempt the FLR on this new backup. The "unrecognized volume" should now be replaced by valid drive contents. A Full restore of the VM will be bootable.
