Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
Issue with Azure Migrate – Disk Error During Replication
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(169.60000000000002, 93%, 26%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJR%3C/text%3E%3C/svg%3E)
Julien Rivoire
45
Reputation points
Hello,
I’ve been using Azure Migrate for the past few months to migrate on-premises virtual servers to Azure. The virtual servers are hosted in a private cloud, and during replication, I treat them as physical servers.
I’ve successfully migrated several Windows servers using this method; however, in the past few days, the process has stopped working. I attempted to migrate three additional servers, but each attempt fails with the same error message:
One or more disks ('.\PHYSICALDRIVE0') are not present on the virtual machine XXX. Disks might have been detached or are in an offline state.
There’s nothing unique about these servers compared to the ones I previously migrated successfully.
Could you please help me identify what might be causing this issue or suggest next steps for troubleshooting?
Thank you,
Azure Migrate
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(259.20000000000005, 79%, 35%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EGK%3C/text%3E%3C/svg%3E)
Greg Krzeminski 0 Reputation points2025-10-31T09:49:45.3933333+00:00 Hi,
I have similar problem when trying to enable replication for our servers. I have started the process two days ago. I wonder if it might be caused by an update. My components versions on replication appliance are:
Recovery services agent 2.0.9948.0
Replication service 1.44.9599.16367
Re-protection server 1.47.9599.16272
Proxy server 1.43.9570.20861
Push install agent 1.46.9599.16201
Site Recovery provider 5.25.904.11
Appliance configuration manager 6.0.1387.371
Physical Discovery server 2.0.3146.482
Discovery server 2.0.3146.516
Process server 9.66.7567.1
-
Alexander Scholz 0 Reputation points2025-10-31T12:09:39.86+00:00 Hello,
i have the same issue in my lab environment aswell as customer infrastructure.
Component Name Installed Version
Physical Discovery server 2.0.3146.482
Discovery server 2.0.3146.516
Site Recovery provider 5.25.904.11
Appliance configuration manager 6.0.1387.371
Proxy server 1.43.9570.20861
Replication service 1.44.9599.16367
Re-protection server 1.47.9599.16272
Push install agent 1.46.9599.16201
Recovery services agent 2.0.9948.0
Process server 9.66.7567.1
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(137.6, 61%, 23%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPM%3C/text%3E%3C/svg%3E)
Patrick McClintick 20 Reputation points2025-11-01T00:14:54.33+00:00 I just ran into this same issue today setting up a new migration. Don't have versions in front of me right now but they should all be current versions.
-
Julien Rivoire 45 Reputation points
2025-11-01T00:43:05.61+00:00 I tried creating a new Azure Migrate project with a new Site Recovery infrastructure and ASR replication appliance, but I’m encountering the same issue. I’m not sure if this is relevant, here are component versions:
First appliance's components
Component Name Installed Version
Recovery services agent 2.0.9948.0
Replication service 1.44.9599.16367
Re-protection server 1.47.9599.16272
Proxy server 1.43.9570.20861
Push install agent 1.46.9599.16201
Site Recovery provider 5.25.904.11
Appliance configuration manager 6.0.1387.371
Physical Discovery server 2.0.3146.482
Discovery server 2.0.3146.516
Process server 9.66.7567.1
Second appliance's components
Component Name Installed Version
Physical Discovery server 2.0.3146.482
Discovery server 2.0.3146.516
Site Recovery provider 5.25.904.11
Appliance configuration manager 6.0.1387.371
Proxy server 1.43.9570.20861
Replication service 1.44.9599.16367
Re-protection server 1.47.9599.16272
Push install agent 1.46.9599.16201
Recovery services agent 2.0.9948.0
Process server 9.66.7567.1
As a workaround, I was able to replicate the disks directly through the Recovery Services vault used by the project, under Replicated items. From there, replication and migration completed successfully.
However, during the migration step, I noticed that only Windows Server 2022 is available as a target OS. The process attempted to upgrade the OS automatically, which failed (fortunately, since I did not want the OS upgraded), but the VM itself was successfully migrated.
-
Aman Mishra 0 Reputation points2025-11-02T06:16:04.9466667+00:00 Hi,
I have also encountered this issue while migrating the physical servers to Azure using Azure Migrate service.
Error Message
Failed to enable replication of the machine 'xxxx'.
- Possible causes One or more disks ('\.\PHYSICALDRIVE0') are not present on the virtual machine 'xxxx'. Disks might have been detached or are in offline state.
- Recommendation Ensure only attached and active disks are passed through the parameter 'DisksToInclude' OR ensure specified disks are online and attached to the machine. Retry the operation with above mentioned inputs I have tried multiple workaronds but still stuck here.....
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(163.2, 84%, 25%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EB%3C/text%3E%3C/svg%3E)
BB 0 Reputation points2025-11-05T09:01:18.2933333+00:00 Hi Team,
The same issue facing the during replication
- Error Message Failed to enable replication of the machine 'vm01'.
- Possible causes One or more disks ('\.\PHYSICALDRIVE0') are not present on the virtual machine VM01. Disks might have been detached or are in offline state.
- Recommendation Ensure only attached and active disks are passed through the parameter 'DisksToInclude' OR ensure specified disks are online and attached to the machine. Retry the operation with above mentioned inputs
Please help on this issue.
BB
-
Greg Krzeminski 0 Reputation points
2025-11-05T12:06:52.9933333+00:00 Hi,
I was able to workaround the issue by installing Mobility agent manually on the servers and then registering it with replication appliance. The process of installation and registration is described in the below article (section 'Install the Mobility service using UI (Modernized)' or 'Install the Mobility service using command prompt (Modernized)'. I have chosen to tick/enable the 'Perform credential-less discovery...' option during the registration. Once registered you can enable replication without the use of saved credentials.
https://learn.microsoft.com/en-us/azure/site-recovery/vmware-physical-mobility-service-overview
I hope this helps.
-
Julien Rivoire 45 Reputation points
2025-11-05T19:58:29.7066667+00:00 Thank you for the information @Greg Krzeminski
I spent some time exploring this solution but wasn’t able to locate the installer. I don’t have the folder %ProgramData%\ASR, only %ProgramData%\ASRLogs.Could you please let me know where you obtained the installer from?
Thank you,
-
Greg Krzeminski 0 Reputation points
2025-11-05T23:10:51.8433333+00:00 Hi,
If it is a newly deployed replication appliance you can find latest installers on it's cache drive in folder (Cache drive drive letter):\Software\Agents. You can also download original zip file with the installation package for the appliance (https://aka.ms/V2ARcmApplianceCreationPowershellZip) and extract it. Inside there should be a folder called 'Agents' which contains the installers. Finally there is a github site where you can download current and previous agents - https://github.com/Azure/Azure-SiteRecovery/blob/main/MobilityAgent/OnPremiseToAzure/AgentDownloadLinks.md .
-
Julien Rivoire 45 Reputation points
2025-11-07T14:46:26.32+00:00 Thank you @Greg Krzeminski
I was able to find the installer and complete the registration process.
Could you please share the process you used for the migration? I’m still encountering the same issue.
In my case, I go to Azure Migrate > Select project > Execute > Migrations > Replicate, and then follow the wizard by selecting:
Physical server
On-premise appliance: MyMigrationServer (Simplified)
I then select the credentials, choose the server I want to migrate (where the Mobility service agent is installed and registered), and proceed with the remaining steps.
-
Greg Krzeminski 0 Reputation points
2025-11-10T12:47:32.14+00:00 Hi,
As per my post about workaround, I tick the 'Perform credential-less discovery...' box when registering the agent on server.
The replication process looks as you have described it but when it comes to picking credentials, I choose 'credentilLessRunAsAccount'.
Sign in to comment
Sign in to answer