Skip to main content
Question

Windows VM does not detect local vdisk

  • 25 July 2024
  • 3 replies
  • 35 views

Hello Team.

 

<issue summary>

Windows server 2016 VM was restored after async DR to another cluster. 

If I check through Prism or CVM acli, the local vdisk looks normal in the list.

However, some local vDisks are not recognized inside Windows OS.

The disks are not identified in "Create and Format Hard Disk Partitions" at all.

The weird thing is that other local vdisk looks normal.
VG attached in DAS way looks normal vdisk.

async DR was performed from AOS 5.20.5 to AOS 6.5.5.5.

 

<Current Environment>
- AOS 6.5.5.5
- OS : Windows Server 2016 Standard
- VirtIO : 1.2.3
- vdisk bus : scsi

 

If you restore it from the AS-IS cluster and check it, the local vdisk looks normal on the OS.

In a TO-BE cluster, some local v disks are not recognized by the OS.

Has anyone had a similar experience?

If you have any, please tell me about the solution or cause.

 

Thank you.

This topic has been closed for comments

3 replies

Userlevel 4
Badge +5

Hi, 

I would recommend to open case with support and get RCA. I had not seen this behavior before.

F>P 

 

Thank you for responding the question.

 

The case is already in progress. But I haven't received a clear answer from the case owner yet. So I left a question in case anyone has similar experience.

 

Userlevel 4
Badge +5

Hi,

  • Nutanix supports cluster-to-cluster replication between all currently supported AOS versions but recommends the replicating clusters run the same AOS versions. For more information on the currently supported AOS versions, see End of Life Information-Software Releases. If both clusters have different AOS versions, each EOL, upgrade the cluster with a lower AOS version to match the cluster with a higher AOS version and then upgrade each cluster to the next supported AOS version. Ensure that the upgrade path is supported before you upgrade the AOS versions. For more information on the upgrade paths, see Upgrade Paths.

I am sure the AOS mismatch is issues here, upgrade AOS to at least 6.x and try again