Avamar: Linux FLR mount fails "Failed to determine the partition type" when target vm disk has mixed partition types

Summary: Avamar: Linux FLR mount fails with "Failed to determine the partition type" when the target vm disk has GPT with mixed partition types.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.

Symptoms

FLR browsing for Linux vm (Debian) with GPT label is failing with an error.

Failed to determine the partition type. Verify that all the disks on the VM have valid/supported partitions

The virtual machine disk configuration shows GPT type, with mixed partition type (sda2 is /boot, sda3 is LVM.)

Disk /dev/sda: 107.4 GB, 107374182400 bytes, 209715200 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk label type: gpt
Disk identifier: 0CAD2943-6656-4D03-9484-5FD19CA701F2


#         Start          End    Size  Type            Name
 1         2048         4095      1M  BIOS boot
 2         4096      2101247      1G  Microsoft basic
 3      2101248    209713151     99G  Linux LVM

 

Cause

Proxy Limitation.
The FLR's MountPoint's GPT code is not able to ignore non-standard partition types (BIOS Boot and mixed types).
A similar disk created with msdos label would mount properly.

 

Resolution

To allow FLR with such GPT disk configuration, a Proxy hotfix is available.

Avamar Version Proxy Hotfix # Release date
7.5.1 309209 N/A
18.1 N/A (not planned) N/A
18.2 311374 (or higher) 2019-08-02
19.1 311375 (or higher) 2019-08-12

 

Affected Products

Avamar

Products

Avamar, Avamar Client for VMware
Article Properties
Article Number: 000053658
Article Type: Solution
Last Modified: 05 Nov 2025
Version:  5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.