Your Azure VM may fail to boot after recycling if the Azure VM Agent isn't ready. The VM Agent plays a crucial role in managing the VM, reporting its status, and allowing Azure to communicate with it. When the Agent can’t initialize, Azure may show the VM as unavailable.
One of the most common reasons for this issue on Linux VMs is a device name change during the recycle operation. When storage device names change, the VM may fail to mount required disks, which prevents the system from completing the boot process.
Understanding why device names change helps you troubleshoot and prevent the issue from happening again.
-
Check for Linux device name changes
If you're using a Linux storage device driver with several devices, the driver may reassign major and minor numbers from the available range. This can cause your device names to shift after recycling the VM.
When required disks don’t mount, the VM can’t boot properly, and the Azure VM Agent can’t come online. -
Use persistent device naming methods
To prevent the issue, use device identifiers that persist across reboots. Instead of relying on dynamic device names like /dev/sdX, use:-
Filesystem labels
-
UUIDs
-
Derived device paths such as /dev/disk/by-id/ or /dev/disk/by-uuid/
These identifiers remain stable even when the system reassigns device names.
-
-
Review Azure guidance on device naming
Azure provides detailed guidance for troubleshooting Linux device name issues to ensure your VM boots consistently.
For more information, see Troubleshoot Linux VM device name changes.
Related Articles
Resolve SSH connection issues to Flexera-managed AWS instances 2Number of Views Scheduler fails to invoke flxconfig.exe on Windows to bootstrap policy after boot if no schedule is installed due to faili… 6Number of Views Azure VM instances with a "Stopped" or "Stopped (deallocated)" status are inappropriately treated as terminated 5Number of Views "Get Azure VM Instances" Azure import reader step may fail with error: "Could not load file or assembly '[...]' or one of … 12Number of Views VM_UUID Detection Mechanism in Azure 11Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago