Why can't I resize a ads_V5 vm to ads_v6?

Question

Why can't I resize a ads_V5 vm to ads_v6?

Fernando Gomes 30

I am unable to resize any VM with a temporary disk to the brand new v6 with temporary disk. Why?

I know one is SCSI and the other one is NVMe, but it should work.

I can create a v6 VM, and I can resize a v5 to v6 if it is a vm with no temporary disk.

Why this limitation?

Fernando Gomes 30 Reputation points

2024-12-15T12:46:51.0333333+00:00

When trying to resize a ads_v5 to ads_v6 I get this error, but this does not make sense, as the ads_v6 has a resource disk

Update-AzVM: Unable to resize the VM 'XXXXXX' since changing from resource disk to non-resource disk VM size and vice-versa is not allowed. Please refer to https://aka.ms/AAah4sj for more details.

ErrorCode: OperationNotAllowed
Andreas Baumgarten 123.4K Reputation points MVP Volunteer Moderator

2024-12-15T13:07:46.3166667+00:00

Hi @Fernando Gomes ,

to resize a VM from one VM series to another it's required both series have the same configuration of a temp disk (local storage).

You cant resize a VM if one of the VM series is using a temp disk an the other series doesn't have a temp disk (local storage).

Please take a look here:

What does no local temp disk mean?

Can I resize a VM size that has a local temp disk to a VM size with no local temp disk?

How do I migrate from a VM size with local temp disk to a VM size with no local temp disk?

(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

Regards

Andreas Baumgarten
Fernando Gomes 30 Reputation points

2024-12-16T11:23:34.7566667+00:00

@Anusree Nashetty thanks, I had already skimmed through those. They point me to the same fundamental link - resizing a VM with a local disk to a VM with no local disk.
That is not what I am after, as both sizes do have a local disk.

If I create a v6 VM from scratch I can confirm that there is a local disk.

My v5 VM has a local disk. The VM I want to resize to also has a local disk. Yet the desired VM size is not listed in the portal as available for resizing.

If I try resizing with powershell, I get "Update-AzVM: Unable to resize the VM 'XXXXXX' since changing from resource disk to non-resource disk VM size and vice-versa is not allowed"

This error message is out of context, as the desired VM size really does have a temp disk.

I get these are brand new VM sizes (they're not even listed in the pricing simulator), this seems like a bug that needs ironing out.
Akshay kumar Mandha 3,390 Reputation points Microsoft External Staff Moderator

2024-12-16T19:57:42.17+00:00

Hi Fernando Gomes,
We understand your concern. could you please provide the exact series name you are using? For example, D4as_v5 or E2as_v5. Providing this detail will help us identify the issue more quickly
Thank you.!
Fernando Gomes 30 Reputation points

2024-12-17T08:29:27.7+00:00

@Akshay kumar Mandha E32ads v5 to E32ads v6.

There should be a direct resize path, but it seems there isn't, right?
Fernando Gomes 30 Reputation points

2024-12-17T08:35:41.54+00:00

@Akshay kumar Mandha I'm trying to resize a E32ads v5 to E32ads v6.
There should be a direct resize path, but it seems there isn't.
Fernando Gomes 30 Reputation points

2024-12-17T10:30:03.9366667+00:00

Thanks, @Anusree Nashetty . That link is really explanatory.

My VM runs Windows Server 2016, so I'm outta luck.

How can I mark your comment as an accepted answer?
Anusree Nashetty 4,385 Reputation points Microsoft External Staff Moderator

2024-12-17T14:30:25.2633333+00:00

Hi Fernando Gomes,

Glad to know it helped for you. I have converted my comment to Answer, please click "Accept Answer" and "Upvote it". If you have any further queries, please do let us know.
Thank you.
Prrudram-MSFT 28,201 Reputation points Moderator

2024-12-20T15:10:21.6633333+00:00

Hello @Fernando Gomes

If provided response by Anusree answered your question, please Accept Answer as a token of appreciation and don't forget to thumbs up for "Was it helpful"!
Anusree Nashetty 4,385 Reputation points Microsoft External Staff Moderator

2024-12-23T01:10:00.35+00:00

Hello Fernando Gomes,

I hope you're doing well. I just wanted to follow up on our previous conversation and ask if the response I provided was helpful to you. If you have any further queries, do let us know. If the answer is helpful, please click "Accept Answer" and "Upvote it."
Fernando Gomes 30 Reputation points

2025-01-02T12:01:32.65+00:00

We've opened a support ticket with Microsoft and are waiting for their official stance on this.
Fernando Gomes 30 Reputation points

2025-02-28T08:52:46.6566667+00:00

For anyone still struggling with this issue, there is this great input from TP at this thread: https://learn.microsoft.com/en-us/answers/questions/2169104/unable-to-change-vm-size-d2ds-v5-to-d2ds-v6

"Unfortunately you cannot directly resize VM from Standard_D2ds_v5 to Standard_D2ds_v6 because Standard_D2ds_v6 effectively does not have a local temporary disk.

Please see screenshot below where Standard_D2ds_v6 shows 0 for ResourceDiskSizeInMB and Standard_D2ds_v5 shows 76800:

Yes, Standard_D2ds_v6 does have a local temporary disk, however, it is NVMe, and is presented to the VM as a raw disk each first time the VM boots after being allocated to a physical host. Since the disk is raw, the OS won't be able to initialize paging file on it during startup.

This is different than Standard_D2ds_v5, in which the local temporary disk is presented as NTFS/ext4 drive, ready for use by paging/swap file.

Azure prevents the resize in order to avoid potential issues since the current size (Standard_D2ds_v5) is likely configured with paging file on temporary disk.

Please see article below for things to consider when using VM sizes with temporary NVMe drives:

https://learn.microsoft.com/en-us/azure/virtual-machines/enable-nvme-temp-faqs#what-changes-should-i-prepare-for-when-configuring-my-vms-with-temp-nvme-disks-

Workaround/Solution:

You can follow steps in article below to manually migrate your VM to the new size:

https://learn.microsoft.com/en-us/azure/virtual-machines/azure-vms-no-temp-disk#how-do-i-migrate-from-a-vm-size-with-local-temp-disk-to-a-vm-size-with-no-local-temp-disk---

Please click Accept Answer and upvote if the above was helpful.

Thanks.

-TP"

Accepted answer

4 additional answers

Your answer

Fernando Gomes 30 Reputation points

2024-12-15T12:46:51.0333333+00:00

When trying to resize a ads_v5 to ads_v6 I get this error, but this does not make sense, as the ads_v6 has a resource disk

Update-AzVM: Unable to resize the VM 'XXXXXX' since changing from resource disk to non-resource disk VM size and vice-versa is not allowed. Please refer to https://aka.ms/AAah4sj for more details.

ErrorCode: OperationNotAllowed
Andreas Baumgarten 123.4K Reputation points MVP Volunteer Moderator

2024-12-15T13:07:46.3166667+00:00

Hi @Fernando Gomes ,

to resize a VM from one VM series to another it's required both series have the same configuration of a temp disk (local storage).

You cant resize a VM if one of the VM series is using a temp disk an the other series doesn't have a temp disk (local storage).

Please take a look here:

What does no local temp disk mean?

Can I resize a VM size that has a local temp disk to a VM size with no local temp disk?

How do I migrate from a VM size with local temp disk to a VM size with no local temp disk?

(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)

Regards

Andreas Baumgarten
Fernando Gomes 30 Reputation points

2024-12-16T11:23:34.7566667+00:00

@Anusree Nashetty thanks, I had already skimmed through those. They point me to the same fundamental link - resizing a VM with a local disk to a VM with no local disk.
That is not what I am after, as both sizes do have a local disk.

If I create a v6 VM from scratch I can confirm that there is a local disk.

My v5 VM has a local disk. The VM I want to resize to also has a local disk. Yet the desired VM size is not listed in the portal as available for resizing.

If I try resizing with powershell, I get "Update-AzVM: Unable to resize the VM 'XXXXXX' since changing from resource disk to non-resource disk VM size and vice-versa is not allowed"

This error message is out of context, as the desired VM size really does have a temp disk.

I get these are brand new VM sizes (they're not even listed in the pricing simulator), this seems like a bug that needs ironing out.
Akshay kumar Mandha 3,390 Reputation points Microsoft External Staff Moderator

2024-12-16T19:57:42.17+00:00

Hi Fernando Gomes,
We understand your concern. could you please provide the exact series name you are using? For example, D4as_v5 or E2as_v5. Providing this detail will help us identify the issue more quickly
Thank you.!
Fernando Gomes 30 Reputation points

2024-12-17T08:29:27.7+00:00

@Akshay kumar Mandha E32ads v5 to E32ads v6.

There should be a direct resize path, but it seems there isn't, right?
Fernando Gomes 30 Reputation points

2024-12-17T08:35:41.54+00:00

@Akshay kumar Mandha I'm trying to resize a E32ads v5 to E32ads v6.
There should be a direct resize path, but it seems there isn't.
Fernando Gomes 30 Reputation points

2024-12-17T10:30:03.9366667+00:00

Thanks, @Anusree Nashetty . That link is really explanatory.

My VM runs Windows Server 2016, so I'm outta luck.

How can I mark your comment as an accepted answer?
Anusree Nashetty 4,385 Reputation points Microsoft External Staff Moderator

2024-12-17T14:30:25.2633333+00:00

Hi Fernando Gomes,

Glad to know it helped for you. I have converted my comment to Answer, please click "Accept Answer" and "Upvote it". If you have any further queries, please do let us know.
Thank you.
Prrudram-MSFT 28,201 Reputation points Moderator

2024-12-20T15:10:21.6633333+00:00

Hello @Fernando Gomes

If provided response by Anusree answered your question, please Accept Answer as a token of appreciation and don't forget to thumbs up for "Was it helpful"!
Anusree Nashetty 4,385 Reputation points Microsoft External Staff Moderator

2024-12-23T01:10:00.35+00:00

Hello Fernando Gomes,

I hope you're doing well. I just wanted to follow up on our previous conversation and ask if the response I provided was helpful to you. If you have any further queries, do let us know. If the answer is helpful, please click "Accept Answer" and "Upvote it."
Fernando Gomes 30 Reputation points

2025-01-02T12:01:32.65+00:00

We've opened a support ticket with Microsoft and are waiting for their official stance on this.
Fernando Gomes 30 Reputation points

2025-02-28T08:52:46.6566667+00:00

For anyone still struggling with this issue, there is this great input from TP at this thread: https://learn.microsoft.com/en-us/answers/questions/2169104/unable-to-change-vm-size-d2ds-v5-to-d2ds-v6

"Unfortunately you cannot directly resize VM from Standard_D2ds_v5 to Standard_D2ds_v6 because Standard_D2ds_v6 effectively does not have a local temporary disk.

Please see screenshot below where Standard_D2ds_v6 shows 0 for ResourceDiskSizeInMB and Standard_D2ds_v5 shows 76800:

Yes, Standard_D2ds_v6 does have a local temporary disk, however, it is NVMe, and is presented to the VM as a raw disk each first time the VM boots after being allocated to a physical host. Since the disk is raw, the OS won't be able to initialize paging file on it during startup.

This is different than Standard_D2ds_v5, in which the local temporary disk is presented as NTFS/ext4 drive, ready for use by paging/swap file.

Azure prevents the resize in order to avoid potential issues since the current size (Standard_D2ds_v5) is likely configured with paging file on temporary disk.

Please see article below for things to consider when using VM sizes with temporary NVMe drives:

https://learn.microsoft.com/en-us/azure/virtual-machines/enable-nvme-temp-faqs#what-changes-should-i-prepare-for-when-configuring-my-vms-with-temp-nvme-disks-

Workaround/Solution:

You can follow steps in article below to manually migrate your VM to the new size:

https://learn.microsoft.com/en-us/azure/virtual-machines/azure-vms-no-temp-disk#how-do-i-migrate-from-a-vm-size-with-local-temp-disk-to-a-vm-size-with-no-local-temp-disk---

Please click Accept Answer and upvote if the above was helpful.

Thanks.

-TP"

Answer 1

Hi Fernando,

Unfortunately you cannot directly resize VM from Standard_E32ads_v5 to Standard_E32ads_v6 because Standard_E32ads_v6 effectively does not have a local temporary disk.

Please see screenshot below where Standard_E32ads_v6 shows 0 for ResourceDiskSizeInMB and Standard_E32ads_v5 shows 1228800:

powershell output of two vm sizes

Yes, Standard_E32ads_v6 does have a local temporary disk, however, it is NVMe, and is presented to the VM as a raw disk each first time the VM boots after being allocated to a physical host. Since the disk is raw, the OS won't be able to initialize paging file on it during startup.

This is different than Standard_E32ads_v5, in which the local temporary disk is presented as NTFS/ext4 drive, ready for use by paging/swap file.

Azure prevents the resize in order to avoid potential issues since the current size (Standard_E32ads_v5) is likely configured with paging file on temporary disk.

Please see article below for things to consider when using VM sizes with temporary NVMe drives:

https://learn.microsoft.com/en-us/azure/virtual-machines/enable-nvme-temp-faqs#what-changes-should-i-prepare-for-when-configuring-my-vms-with-temp-nvme-disks-

Workaround/Solution:

You can follow steps in article below to manually migrate your VM to the new size:

https://learn.microsoft.com/en-us/azure/virtual-machines/azure-vms-no-temp-disk#how-do-i-migrate-from-a-vm-size-with-local-temp-disk-to-a-vm-size-with-no-local-temp-disk---

Please click Accept Answer and upvote if the above was helpful.

Thanks.

-TP

Answer 2

Anusree Nashetty 4,385 Microsoft External Staff Moderator

Hi Fernando Gomes,

Thanks for getting back with the detailed explanation. As both the VM size have Local storage but are of different types E32ads_v5 has SCSI type and E32ads_v6 has NVMe type storage. Your current size E32ads_v5(SCSI) does not support resizing VM to E32ads_v6(NVMe). The only supported sizes to Azure boost are here.
For more information, please check Converting Azure Virtual Machines running Windows from SCSI to NVMe

You can resize to same Storage type SCSI with the equal vCPU and RAM. Here are below some VM size which are supported to resize from E32ads_v5. User's image

If you have any further queries, please do let us know. Thank you.

Fernando Gomes 30 Reputation points

2024-12-18T13:00:59.9166667+00:00
@Anusree Nashetty @Andreas Baumgarten I can confirm this is a real issue/limitation.
I went through all the steps in the links you provided.
Even after following the steps to convert a VM with SCSI disk controllor to NVMe disk controller:

I can convert a D2as V5 to D2as V6 (no temporary disk)

I cannot convert a D2ads V5 to D2ads V6 (temporary disk)

This seems to be a serious issue (or otherwise limitation).
Anusree Nashetty 4,385 Reputation points Microsoft External Staff Moderator

2024-12-19T01:45:04.1166667+00:00

Hi Fernando Gomes,

You can convert Standard_D2as_v5 vm size to Standard_D2as_v6 because the vm sizes does not have Local storage, so you can resize them if it is available in the region. Some VM sizes are specific to region and Zone availability. Please refer this document for resizing vm with no local disk Limitations

The VM size Standard_D2ads_v5(SCSI) is unable to resize to Standard_D2ads_v6(NVMe) because both have Local Storage but are of different types. The size D2ads_v5 is not listed in the current availability to support Azure boost.

If you have further queries, please do let me know. Can you please provide more details as in which region you are trying to resize.

Thank you.
Anusree Nashetty 4,385 Reputation points Microsoft External Staff Moderator

2024-12-20T06:56:16.0733333+00:00

Hi Fernando Gomes,

Did you get a chance to look at my response? Please let me know if you have any questions.

Answer 3

@Deepanshu katara so you've just admitted in that other thread that you dumped information that was not related to the OP's issue and instead of really trying to get to the issue, you choose to close the thread and advise me against making personal remarks - which I didn't.

I'm sorry if I hurt your feelings or otherwise sound unprofessional, but how professional is it (by you) to keep posting unrelated replies and asking for upvotes? I'm available for that one-on-one call, but I'm more interested in having usefull help made public.

Can you actually help resolving this issue?

https://learn.microsoft.com/en-us/answers/questions/2169104/unable-to-change-vm-size-d2ds-v5-to-d2ds-v6

Answer 4

What I can tell you is that the culprit has something to do with how these VMs don't consider a NVMe temporary disk as the old SCSI versions did.

You can come to this conclusion by creating and trying to resize a couple of test VMs which are availabe with both NVMe and SCSI: E2bds_v5

Virtual Machine A - E2bds_v5 with NMVe disabled (effectively SCSI disk controller)

Virtual Machine B - E2bds_v5 with NMVe enabled

Resizing VM A to Standard_D2ds_v6 you get the error you've mentioned. There is no path to resize here.

Resizing Virtual Machine B to Standard_D2ds_v6 you can convert to Standard_D2ds_v6 (with temp disk) and you can also convert to Standard_D2s_v6 (with NO temp disk).

The fact that you can convert a VM with a temp disk to a VM without temp disk is counter intuitive, but this is what happens.

We're going to test converting our E32ads V5 to a E32bds_V5, then convert that to NMVe (there is a script around for that, google it) and then convert to a E32ads_V6.

Answer 5

Fernando Gomes 30

@Sean Bernard I'm truly sorry that my remarks in your thread caused it to be closed.

If you're still struggling, you can follow this thread instead.

Share via

Why can't I resize a ads_V5 vm to ads_v6?

4 additional answers

Your answer