SQL VM deployment error

Question

SQL VM deployment error

Carlos Gonzalez 0

Trying to instantiate a VM from the Microsoft image in marketplace:

sql2022 on ws2022 standard

Getting this error:

{

"code": "DeploymentFailed",

"target": "/subscriptions/***********-71e2a43a1ed5/resourceGroups/CREDITSOFTMODEL1_group/providers/Microsoft.Resources/deployments/CreateVm-microsoftsqlserver.sql2022-ws2022-standa-20251013150420",

"message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-deployment-operations for usage details.",

"details": [


  "message": "The resource write operation failed to complete successfully, because it reached terminal provisioning state 'Failed'."

}
  ]

}
and this on the operation:


yaml
{
    "status": "Failed",
    "error": {
        "code": "Ext_StorageConfigurationSettings_ApplyNewTempDbSettingsError",
        "message": "Error: 'System Drive returned status not ready for use '"
    }
}

2 answers

Your answer

Answer 1

Hi Carlos Gonzalez

Regarding your query about the failure while deploying a SQL Server 2022 VM on Windows Server 2022 you have received the below error.

"code": "Ext_StorageConfigurationSettings_ApplyNewTempDbSettingsError", "message": "Error: 'System Drive returned status not ready for use

It was the known issue that mentioned in the below documentation

Reference: https://free.blessedness.top/en-us/troubleshoot/sql/azure-sql/sql-deployment-fails-drive-not-ready

This issue occurs due to how certain newer Azure VM sizes handle ephemeral (temporary) storage. Some VM types include a local SSD (usually the D: drive) that is not initialized when the VM is first created. During deployment, SQL Server tries to place its temporary database (tempdb) on this drive, but since the drive isn’t ready yet, the installation fails.

You might also face this issue later if SQL Server is installed manually on such a VM and configured to use the local SSD for tempdb — in that case, SQL Server fails to start after the VM is restarted or deallocated, because the drive becomes unavailable or shows as RAW (unformatted).

To resolve this:

Use a different VM size that doesn’t include uninitialized ephemeral storage (avoid VM sizes with a lowercase d in their name, such as FXmdsv2).

For example, use FXmsv2 instead.

If you must use the same VM size, deploy a Windows Server-only image, initialize and format the local NVMe drive manually, and then install SQL Server yourself.

Keep in mind: you’ll need to reinitialize the disk each time the VM is restarted or deallocated.

Hope this helps! Please let me know if you have any queries.

If it is helpful. Could you please accept answer and upvote it. If you have any queries, please let me know in comments

Jilakara Hemalatha 3,115 Reputation points Microsoft External Staff Moderator

2025-10-14T16:39:03.6366667+00:00

Hi Carlos Gonzalez

Just checking if above provided responses are helpful to you. please let me know if you have any queries.
Jilakara Hemalatha 3,115 Reputation points Microsoft External Staff Moderator

2025-10-26T11:45:26.6666667+00:00

Hi Carlos Gonzalez

If provided information was helpful to you. please accept the answer and upvote 👍 it so that it will be helpful to the community. If you have any queries, please let me know in comments.

Answer 2

Hello @Carlos Gonzalez

The error "System Drive returned status not ready for use" during SQL VM deployment typically indicates issues with VM size, OS disk configuration, deployment timeouts, or resource conflicts. The recommended solution is to use a larger VM size (D-series or E-series) with Premium SSDs for the OS disk and ensure no network or resource conflicts exist.

If the Answer is helpful, please click Accept Answer and Up-Vote, so that it can help others in the community looking for help on similar topics.

Share via

SQL VM deployment error

2 answers

Your answer