Disk Storage: Unable to resize Premium V2 disk — Error with dataDisk.diskIOPSReadWrite and empty storage account type

Admin JoeS 0 Reputation points
2026-11-18T15:20:22.06+00:00

Problem description

I am trying to resize a Premium V2 disk attached to an Azure Virtual Machine, but the operation fails. The error mentions 'dataDisk.diskIOPSReadWrite' and indicates an issue with an empty storage account type. The resize is from 6144 GB to 8192 GB.

Environment

Azure Virtual Machines with Disk Storage (Premium SSD V2) in the affected region.

What I've already tried

I attempted to resize the disk from the Azure portal by navigating to the VM's Disk settings and changing the size under 'Size and Performance'.

Current status

I am seeking assistance to understand why the resize operation fails and how to resolve the issue, possibly related to the error involving 'dataDisk.diskIOPSReadWrite' and the storage account type.

Azure Disk Storage
Azure Disk Storage

A high-performance, durable block storage designed to be used with Azure Virtual Machines and Azure VMware Solution.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Chandra Boorla 15,180 Reputation points Microsoft External Staff Moderator
    2026-11-18T23:59:20.48+00:00

    Hi @Admin JoeS

    Greetings of the day!

    Thank you for choosing Microsoft.

    Thank you for your time on the remote session today. I appreciate your cooperation while we reviewed and reproduced the disk resize issue. 

    As discussed, please find below a summary of our findings and the agreed action plan.

    Issue:

    You are attempting to resize the Premium SSD v2 data disk siaoracle-prod2_DataDisk_0 from 6144 GiB to 8192 GiB. During our session, we reproduced the issue while attempting the resize operation.

    The operation fails with the following error:

    “Property 'dataDisk.diskIOPSReadWrite' is not supported for disks having storage account type ''.” 

    Findings:

    • The affected disk is a Premium SSD v2 data disk.
    • The disk is currently attached to the production VM siaoracle-prod2.
    • We reproduced the resize failure during the session.
    • Since this is a production workload, you confirmed that the VM cannot currently be stopped/deallocated and the disk cannot be detached.
    • You also confirmed that the next planned maintenance window is expected next month. 

    Resolution / Action Plan:

    As discussed during the call, no disruptive changes will be performed on the production VM at this time.

    During the next available maintenance window, the recommended approach is to retry the disk resize while the VM is stopped/deallocated or, if required, by temporarily detaching the data disk, completing the resize, and attaching the same disk back to the VM.

    For reference: Troubleshoot Azure VM disk resize errors - Virtual Machines | Microsoft Learn

    Thank you again for your time and cooperation during the troubleshooting session.

    Was this answer helpful?

    0 comments No comments

  2. Eber Daniel Perez 165 Reputation points
    2026-11-18T15:46:13.5433333+00:00

    Hi! I haven't seen that exact error text documented, so I can't tell you the root cause for sure. But the message (diskIOPSReadWrite + an empty storage account type) looks like the VM's Disks blade is sending an incomplete disk update. Here's what I'd check, in this order.

    1. Resize from the disk resource, not from the VM

    Go to Disks > your Premium SSD v2 disk > Size + performance and change only the size to 8192 GiB. Or do it with CLI, sending only the size (no IOPS/MBps):

    az disk update --resource-group <rg> --name <disk> --size-gb 8192
    

    That's the command from the official expand guide. If this works, the problem was the request coming from the VM blade.

    2. Documented limits that also block a Premium SSD v2 resize

    • 4 changes per 24 hours: "You can adjust the performance of a Premium SSD v2 four times within a 24-hour period" (creating the disk counts as one). If you already changed IOPS/throughput/size several times today, wait and retry.
    • Background copy: you can't expand the disk while a background copy is running on it (for example if it was created from a snapshot recently).
    • Regional quota: by default Premium SSD v2 gives you 100 TiB per region per subscription. Going from 6 to 8 TiB adds 2 TiB, so check you're not hitting that if you have other v2 disks in the region.

    3. Downtime / controller

    The 4 TiB "deallocate first" rule doesn't apply to Premium SSD v2. The docs say you can expand Premium SSD v2 without downtime on VMs with NVMe controllers. If your VM uses SCSI and the online resize keeps failing, try it with the VM deallocated.

    4. After the resize

    Allow up to 10 minutes and rescan the disk inside the OS (Disk Management > Rescan Disks on Windows, or the rescan steps on Linux), then extend the partition/filesystem.

    If none of this works, open a support case with the full error and the correlation ID of the failed operation from the Activity log.

    Docs:

    Hope it helps!

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.