Skip to content

Commit 8960a77

Browse files
authored
minor updates for readability
1 parent 8450c34 commit 8960a77

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

support/sql/azure-sql/sql-deployment-fails-drive-not-ready.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -15,15 +15,15 @@ _Applies to:_  SQL Server on Azure VMs
1515

1616
## Symptoms
1717

18-
When you try to deploy SQL Server on Azure VM image in Azure Marketplace, the deployment fails with a status of `Conflict` and the following error:
18+
When you try to deploy SQL Server on an Azure VM image in Azure Marketplace, the deployment fails with a status of `Conflict` and the following error:
1919

2020
> System Drive returned status not ready for use.
2121
2222
## Cause
2323

2424
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 SQL Server on an Azure VM image to fail because it attempts to place tempdb data files on the local SSD volume.
2525

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 the installation that occurs in SQL Server on Azure VM deployment process.
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 the installation process of SQL Server on an Azure VM.
2727

2828
## Resolution
2929

0 commit comments

Comments
 (0)