|
1 | 1 | --- |
2 | | -title: SQL Server Azure VM deployment fails with drive not ready error |
3 | | -description: This article provides a resolution for the failure that can occur when you try to deploy certain SQL Server on Azure VM images from Azure Marketplace. |
| 2 | +title: SQL Server Azure VM Deployment Fails with Drive Not Ready Error |
| 3 | +description: Resolves an issue that occurs when you try to deploy a SQL Server instance on an Azure VM image in Azure Marketplace. |
4 | 4 | ms.date: 03/22/2025 |
5 | 5 | ms.author: dpless |
6 | 6 | author: dplessMSFT |
7 | | -ms.reviewer: mathoma |
8 | | -ms.custom: sap:Azure SQL virtual machine |
9 | | -ms.topic: troubleshooting |
| 7 | +ms.reviewer: mathoma, v-sidong |
| 8 | +ms.custom: sap:SQL Licensing, Installation and Patching |
10 | 9 | --- |
11 | 10 | # Error (System Drive returned status not ready for use) and Azure SQL Server VM deployment fails |
12 | 11 |
|
13 | | -This article helps you resolve a failed deployment of a SQL Server on Azure VM image from Azure Marketplace. |
| 12 | +This article helps you resolve a failed deployment of a SQL Server instance on an Azure VM image in Azure Marketplace. |
14 | 13 |
|
15 | | -_Applies to:_ SQL Server on Azure VMs |
| 14 | +_Applies to:_ SQL Server on Azure VMs |
16 | 15 |
|
17 | 16 | ## Symptoms |
18 | 17 |
|
19 | | -When you try to deploy a SQL Server on Azure VM image from Azure Marketplace, the deployment fails with the following error message: |
| 18 | +When you try to deploy a SQL Server instance on an Azure VM image in Azure Marketplace, the deployment fails with the following error message: |
20 | 19 |
|
21 | | -`System Drive returned status not ready for use.` |
| 20 | +> System Drive returned status not ready for use. |
22 | 21 |
|
23 | 22 | ## Cause |
24 | 23 |
|
25 | | -Some of the newest Azure VM sizes present a RAW Local SSD volume for ephemeral storage prepared with the NVMe interface. This configuration can cause a SQL Server on Azure VM deployment to fail because it attempts to place tempdb data files on the local SSD volume. |
| 24 | +Some of the newest Azure VM sizes present a RAW Local SSD volume for ephemeral storage configured with the NVMe interface. This configuration might cause the deployment of a SQL Server instance on an Azure VM to fail because it attempts to place tempdb data files on the local SSD volume. |
26 | 25 |
|
27 | | -The deployment fails because the RAW Local SSD volume is not formatted and initialized, making the ephemeral storage unavailable, which prevents SQL Server from accessing it during installation. |
| 26 | +The deployment fails because the RAW Local SSD volume isn't formatted or initialized, which makes the ephemeral storage unavailable and prevents SQL Server from accessing it during installation. |
28 | 27 |
|
29 | 28 | ## Resolution |
30 | 29 |
|
31 | | -This issue occurs because of the selected Azure VM size. If it is not possible to use another VM SKU, deploy the VM using a Windows Server only image, then manually install SQL Server after you [format and initialize the temporary NVMe drive](/azure/virtual-machines/enable-nvme-temp-faqs#how-can-i-format-and-initialize-temp-nvme-disks-in-windows-when-i-create-a-vm-). Additionally, be sure to check that the VM isn't configured using a [sector size greater than 4 KB](sql-installation-fails-sector-size-error-azure-vm.md#resolution) before installing SQL Server. |
| 30 | +This issue occurs because of the selected Azure VM size. To solve the issue, use one of the following methods: |
32 | 31 |
|
33 | | -If it is possible, use another VM SKU instead, such as the ones listed in the [VM size best practices](/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-vm-size#checklist). |
| 32 | +- If it's possible, use another VM SKU instead, such as the ones listed in the [VM size best practices](/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-vm-size#checklist). |
| 33 | +- If it's not possible to use another VM SKU, deploy the VM using a Windows Server only image, [format and initialize the temporary NVMe drive](/azure/virtual-machines/enable-nvme-temp-faqs#how-can-i-format-and-initialize-temp-nvme-disks-in-windows-when-i-create-a-vm-), and then manually install SQL Server. Additionally, make sure that the VM isn't configured using a [sector size greater than 4 KB](sql-installation-fails-sector-size-error-azure-vm.md#resolution) before installing SQL Server. |
34 | 34 |
|
35 | | - |
36 | | - ## Impacted VMs |
| 35 | +## Impacted VMs |
37 | 36 |
|
38 | 37 | This issue occurs with virtual machines that deploy with an uninitialized temporary drive, such as the following VM sizes: |
39 | 38 |
|
40 | | -:::row::: |
41 | | - :::column::: |
42 | | - <br /> Intel Gen 10.2 |
43 | | - <br />- Dlsv6 |
44 | | - <br />- Dldsv6 |
45 | | - <br />- Ddsv6 |
46 | | - <br />- Esv6 |
47 | | - <br />- Edsv6 |
48 | | - <br />- Esv6 constrained core sizes |
49 | | - <br />- Edsv6 constrained core sizes |
50 | | - <br />- Lsv3 – All Azure VMs |
51 | | - <br />- M-series VMs |
52 | | - :::column-end::: |
53 | | - :::column::: |
54 | | - <br /> AMD Gen 9.1: |
55 | | - <br />- Dalsv6 |
56 | | - <br />- Daldsv6 |
57 | | - <br />- Dasv6 |
58 | | - <br />- Dadsv6 |
59 | | - <br />- Easv6 |
60 | | - <br />- Eadsv6 |
61 | | - <br />- Falsv6 |
62 | | - <br />- Fasv6 |
63 | | - <br />- Famsv6 |
64 | | -:::row-end::: |
| 39 | +|Intel Gen 10.2|AMD Gen 9.1| |
| 40 | +|-|-| |
| 41 | +|Dlsv6|Dalsv6| |
| 42 | +|Dldsv6|Daldsv6| |
| 43 | +|Ddsv6|Dasv6| |
| 44 | +|Esv6|Dadsv6| |
| 45 | +|Edsv6|Easv6| |
| 46 | +|Esv6 constrained core sizes|Eadsv6| |
| 47 | +|Edsv6 constrained core sizes|Falsv6| |
| 48 | +|Lsv3 - All Azure VMs|Fasv6| |
| 49 | +|M-series VMs|Famsv6| |
65 | 50 |
|
0 commit comments