# Check GRUB identifiers when Site Recovery reports error 95320

> Why can device-name references in GRUB prevent a Linux machine from being protected by Site Recovery?

- Canonical URL: https://update.dsesecurity.com/updates/dse-20260909-483-check-grub-identifiers-when-site-recovery-reports-error-95320/
- Publisher: Detection Systems & Engineering (DSE Security)
- Author: DSE Security Editorial Team
- Published: 2026-09-10T00:23:53+00:00
- Modified: 2026-09-10T02:08:05+00:00
- Last reviewed by DSE: 2026-09-09
- Resource type: Guide
- DSE priority: Information
- Topics: Business Continuity, IT
- Reading time: 2 minutes

## What you need to know

Why can device-name references in GRUB prevent a Linux machine from being protected by Site Recovery?

## Potentially affected

Investigate this specific error for a Linux source machine being protected with Site Recovery. Confirm the relevant bootloader configuration and actual device mapping; do not apply a copied UUID or assume that another machine has the same storage layout.

## DSE recommendation

Have the Linux owner review a mapping from every affected root or resume reference to its intended device and UUID.

## Article

## Source facts

Site Recovery error 95320 identifies GRUB configurations whose root or resume parameters use device names instead of UUIDs. Microsoft’s guidance requires UUIDs because device names can change when the VM restarts, creating a risk at failover. Its documented correction first obtains each device’s UUID and then substitutes the corresponding identifier in the boot configuration before retrying protection. [Microsoft Learn](https://learn.microsoft.com/en-us/azure/site-recovery/vmware-azure-troubleshoot-push-install).

## Applicability

Investigate this specific error for a Linux source machine being protected with Site Recovery. Confirm the relevant bootloader configuration and actual device mapping; do not apply a copied UUID or assume that another machine has the same storage layout.

## DSE recommendation

Have the Linux owner review a mapping from every affected root or resume reference to its intended device and UUID. Preserve the current boot configuration and agree on recovery access before making an approved correction. Keep the change narrowly tied to the reported references rather than combining it with unrelated storage or bootloader restructuring.

## Verification

Validate that each proposed identifier resolves to the intended device and that the applicable boot configuration contains the approved values. Use a controlled restart and recovery test appropriate to the machine before relying on the change operationally. Retry the protection workflow and inspect whether the original error is resolved. Retain the mapping and outcome, without claiming that removal of this one error establishes complete disaster-recovery readiness.

## Official references

[Microsoft Learn: Troubleshoot Mobility Service push installation with Azure Site Recovery](https://learn.microsoft.com/en-us/azure/site-recovery/vmware-azure-troubleshoot-push-install).

## Primary reference

- Name: Troubleshoot Mobility Service push installation with Azure Site Recovery - Azure Site Recovery | Microsoft Learn
- Authority: Microsoft Learn
- URL: https://learn.microsoft.com/en-us/azure/site-recovery/vmware-azure-troubleshoot-push-install
- Source publication date: Not stated by the source

## Citation and use

Preferred citation: “Check GRUB identifiers when Site Recovery reports error 95320,” DSE Security, https://update.dsesecurity.com/updates/dse-20260909-483-check-grub-identifiers-when-site-recovery-reports-error-95320/
Publishing principles: https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/
Usage and citation policy: https://update.dsesecurity.com/usage/
Copyright © 2026 Detection Systems & Engineering. All rights reserved.