You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/sql/azure-sql/sql-deployment-fails-drive-not-ready.md
+15-12Lines changed: 15 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,9 +1,9 @@
1
1
---
2
2
title: SQL Server Azure VM Deployment Fails with Drive Not Ready Error
3
3
description: Resolves an issue that occurs when you try to deploy a SQL Server on Azure VM image in Azure Marketplace.
4
-
ms.date: 03/31/2025
5
-
ms.author: dpless
6
-
author: dplessMSFT
4
+
ms.date: 04/02/2025
5
+
ms.author: mathoma
6
+
author: MashaMSFT
7
7
ms.reviewer: mathoma, v-sidong
8
8
ms.custom: sap:SQL Licensing, Installation and Patching
9
9
---
@@ -13,12 +13,17 @@ This article helps you resolve a failed deployment of a SQL Server on Azure Virt
13
13
14
14
_Applies to:_ SQL Server on Azure VMs
15
15
16
+
> [!NOTE]
17
+
> The investigation of this issue is actively ongoing. The information in this article is subject to change as new details become available.
18
+
16
19
## Symptoms
17
20
18
21
When you try to deploy a SQL Server on Azure VM image in Azure Marketplace, the deployment fails with a status of `Conflict` and the following error:
19
22
20
23
> System Drive returned status not ready for use.
21
24
25
+
:::image type="content" source="media/sql-deployment-fails-drive-not-ready/sql-deployment-error.png" alt-text="Screenshot of the deployment error in the Azure portal." lightbox="media/sql-deployment-fails-drive-not-ready/sql-deployment-error.png":::
26
+
22
27
## Cause
23
28
24
29
Some of the newest Azure VM sizes present a RAW Local SSD volume for ephemeral storage configured with the Non-Volatile Memory Express (NVMe) interface. This configuration might cause the deployment of a SQL Server on Azure VM image to fail because it attempts to place `tempdb` data files on the local SSD volume.
@@ -38,13 +43,11 @@ This issue occurs with VMs that are deployed with an uninitialized temporary dri
0 commit comments