none
Discovery of Physical Machine using Azure Migrate does not pick up addtional disk "Disk1" on physical machine with no options shown RRS feed

  • Question

  • Discovery of Physical Machine using Azure Migrate does not pick up Disk1 on physical machine no additional options are shown when configuring replication in Azure Migrate

    the only choice is \\.\PHYSICALDRIVE0

    The replication process completes with only Disk0  Disk 0 contains 2 Volumes c,D

    Disk1 is Drive letter F and is a Simple Basic Disk 995.6 GB Healthy Marked as a Primary Partition.

    Why would the Mobility Client version ASR Agent Version Microsoft-ASR_UA_9.29.0.0_Windows_GA_12Sep2019_Release.

    Has anyone ever encounterd this and is there a way for us to adjust the Agent configuration to look for \\.\PHYSICALDRIVE0 as well as others like \\.\PHYSICALDRIVE1 (Just a Guess)

    Thanks,

    Jim

    Wednesday, October 30, 2019 4:59 PM

Answers

  • Hello Sadiqh,


    I found an agent log on the physical machine with the Mobility client installed.  This is where I found these entries.  The Drives were part of a SAN attached through Fibre Channel.  MPIO on the machine was mis-configured and had multiple paths to the same drive (SameDisk ID) which caused the OS to ignore mis-report the configuration.  

    The log was named svagents_curr_188.log

    The errors encountered were:

    #~> (10-30-2019 15:06:05):   ERROR  13868 13328 1987 For disk device name: \\.\PHYSICALDRIVE2 found multiple disks with same id: {2094470860} with different disk numbers 2,1. Hence not reporting any disk matching the id.<o:p></o:p>

    #~> (10-30-2019 15:06:05):   ERROR  13868 13328 1988 Failed to process a wmi record for query SELECT * FROM Win32_DiskDrive with error For disk device name: \\.\PHYSICALDRIVE2 found multiple disks with same id: {2094470860} with different disk numbers 2,1. Hence not reporting any disk matching the id.

    #~> (10-30-2019 15:06:05):   ERROR  13868 13328 1989 NativeDiskRecordProcessor::ProcessDisk : Found multiple disks \\.\PHYSICALDRIVE2,\\.\PHYSICALDRIVE1 with same id: {2094470860}. Hence not reporting any disk matching the id.<o:p></o:p>

    #~> (10-30-2019 15:06:05):   ERROR  13868 13328 1990 NativeDiskRecordProcessor::ProcessDisk : Found multiple disks \\.\PHYSICALDRIVE2,\\.\PHYSICALDRIVE1 with same id: {2094470860}. Hence not reporting any disk matching the id.

    correctly identified by the Azure Mobility Agent both version 9.29 and 9.30. on Window Server 2008 R2 SP1

    Thanks for replying and offering assistance.  I hope this helps someone else as it cost me about a week of progress on this project.

    Have a good day!

    Jim



    • Edited by jfoege1 Wednesday, November 13, 2019 4:25 PM
    • Marked as answer by jfoege1 Wednesday, November 13, 2019 4:26 PM
    Wednesday, November 13, 2019 4:24 PM

All replies

  • Hello Jim,

    We need some additional information to investigate this issue. Please send us an email at AzCommunity [at] Microsoft dot com with your subscription id and project name. 

    Do not forget to mark me in the subject as ATTN: Sadiqh and share the link to this forum for context.


    Monday, November 4, 2019 10:29 AM
    Moderator
  • Hello Sadiqh,

    I have responded to the community.  

    Only disk0 is discovered in bot Azure Migrate and Azure ASR . Physical infrastructure discovery Windows Server 2008 R2 SP1

    Here is the information

    DISKPART> list disk

       Disk ###  Status         Size     Free     Dyn  Gpt

      --------  -------------  -------  -------  ---  ---

      Disk 0    Online          273 GB  1024 KB

      Disk 1    Online         1238 GB  1024 KB

      Disk 2    Offline        1238 GB  1024 KB

    I believe the WMI Query being used is no recognized...

    Thanks,

    Jim

    Monday, November 4, 2019 4:25 PM
  • Please share the subscription id and project name to start investigation into this.
    Tuesday, November 5, 2019 9:20 AM
    Moderator
  • @Jim, We need to review SDP logs and also need your subscription and project details to investigate this issue. We strongly recommend you reach out to us by creating a technical support ticket. Here is the link https://docs.microsoft.com/en-in/azure/azure-supportability/how-to-create-azure-support-request to create support case. In case you have limitation in your support plan to open Azure Support Tickets please let us know and we will help enable one time free support to assist with resolution on the issue.

    Thursday, November 7, 2019 7:36 AM
    Moderator
  • Hello Sadiqh,

    How do I get verified to include images or such in my replies?

    Thanks,

    Jim

    Wednesday, November 13, 2019 4:07 PM
  • Hello Sadiqh,


    I found an agent log on the physical machine with the Mobility client installed.  This is where I found these entries.  The Drives were part of a SAN attached through Fibre Channel.  MPIO on the machine was mis-configured and had multiple paths to the same drive (SameDisk ID) which caused the OS to ignore mis-report the configuration.  

    The log was named svagents_curr_188.log

    The errors encountered were:

    #~> (10-30-2019 15:06:05):   ERROR  13868 13328 1987 For disk device name: \\.\PHYSICALDRIVE2 found multiple disks with same id: {2094470860} with different disk numbers 2,1. Hence not reporting any disk matching the id.<o:p></o:p>

    #~> (10-30-2019 15:06:05):   ERROR  13868 13328 1988 Failed to process a wmi record for query SELECT * FROM Win32_DiskDrive with error For disk device name: \\.\PHYSICALDRIVE2 found multiple disks with same id: {2094470860} with different disk numbers 2,1. Hence not reporting any disk matching the id.

    #~> (10-30-2019 15:06:05):   ERROR  13868 13328 1989 NativeDiskRecordProcessor::ProcessDisk : Found multiple disks \\.\PHYSICALDRIVE2,\\.\PHYSICALDRIVE1 with same id: {2094470860}. Hence not reporting any disk matching the id.<o:p></o:p>

    #~> (10-30-2019 15:06:05):   ERROR  13868 13328 1990 NativeDiskRecordProcessor::ProcessDisk : Found multiple disks \\.\PHYSICALDRIVE2,\\.\PHYSICALDRIVE1 with same id: {2094470860}. Hence not reporting any disk matching the id.

    correctly identified by the Azure Mobility Agent both version 9.29 and 9.30. on Window Server 2008 R2 SP1

    Thanks for replying and offering assistance.  I hope this helps someone else as it cost me about a week of progress on this project.

    Have a good day!

    Jim



    • Edited by jfoege1 Wednesday, November 13, 2019 4:25 PM
    • Marked as answer by jfoege1 Wednesday, November 13, 2019 4:26 PM
    Wednesday, November 13, 2019 4:24 PM
  • Thanks for the update! Glad to hear it is resolved Certainly this would be helpful for others on this community.
    Thursday, November 14, 2019 6:32 AM
    Moderator