Page tree
Skip to end of metadata
Go to start of metadata

Product Version: 9.0
Last Modified: 27 September 2019

Problem

A partition cannot be opened during file recovery. The following error message is displayed:

Cannot open this partition
Transporter assigned to the Backup Repository could not read file system on this partition.

Background

This error message appears in the following case:

  1. A disk from the backup was successfully mounted to the Transporter.
  2. A partition table of the mounted disk was processed successfully.
  3. The OS of the Transporter could not recognize or open the file system.

Such problems can happen for the following reasons:

  • You are trying to recover files from an unsupported file system.
  • You are trying to recover files from a Linux file system using a Windows-based Transporter.
  • The Transporter OS does not have appropriate drivers for this file system.
  • The partition is a raw partition and does not have a file system.
  • The partition is a part of a Windows Dynamic Disk.
  • The partition is a part of a Linux LVM structure.

Solution

To resolve this issue, follow the steps below:

  1. Make sure that you are recovering files from a supported file system.
  2. If you are using a Windows-based Transporter:
    1. Install a Linux-based Transporter.
    2. Edit your Backup Repository and specify the newly assigned Transporter.
    3. Try recovering files again.
  3. If the OS of your Transporter does not have the appropriate drivers:

    1. Install a proper file system driver on the Transporter machine.
    2. Try to recover the files again.
  4. If the partition is part of the Windows Dynamic Disk or Linux LVM structure:
    1. If you are using a Linux-based Transporter:
      1. Find the “Logical volumes” or “Dynamic disks” item in the tree in Step 2 of the File Recovery Wizard.
      2. Click the item and browse the content of logical volumes or dynamic disks directly.
    2. If you are using a Windows-based Transporter:
      1. Install a Linux-based Transporter.
      2. Edit your Backup Repository and specify the newly assigned Transporter.
      3. Try to recover the files again.
  • No labels