Merge pull request #8703 from sevend2/CI5384

AB#5384: Post edit PR#8669

Author: sevend2

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

@@ -1,17 +1,18 @@
 ---
-title: SQL Server VMs Failing to Deploy or SQL Server Instance Not Coming Online
-description: Learn how to address a failure when you try to deploy a SQL Server on Azure VM image in Azure Marketplace, or when a manually-installed SQL Server instance fails to come online after an Azure VM is restarted or deallocated.
-ms.date: 04/08/2025
+title: SQL Server VMs Fails to Deploy or SQL Server Instance Not Come Online
+description: Addresses a failure when you deploy a SQL Server on Azure VM image in Azure Marketplace or when a manually installed SQL Server instance fails to come online after an Azure VM is restarted or deallocated.
+ms.date: 04/16/2025
 ms.author: mathoma
 author: MashaMSFT
 ms.reviewer: mathoma, v-sidong
 ms.custom: sap:SQL Licensing, Installation and Patching
 ---
-# SQL Server on Azure VM failing to deploy or SQL Server instance not coming online
+# SQL Server on Azure VM fails to deploy or SQL Server instance fails to come online
 
-This article helps you resolve the following scenarios: 
- - a SQL Server on Azure Virtual Machine (VM) Azure Marketplace image failing to deploy.
- - a SQL Server instance failing to come online after an Azure VM is restarted or deallocated.
+This article helps you resolve the following scenarios:
+
+- A SQL Server on Azure virtual machine (VM) Azure Marketplace image fails to deploy.
+- A SQL Server instance fails to come online after an Azure VM is restarted or deallocated.
 
 _Applies to:_  SQL Server on Azure VMs
 
@@ -20,7 +21,8 @@ _Applies to:_  SQL Server on Azure VMs
 
 ## Symptoms
 
-If you encounter this issue, you are likely to see: 
+If you encounter this issue, you're likely to see:
+
 - SQL Server on Azure VM deployments failing when using an Azure Marketplace image.
 - SQL Server failing to come online after an Azure VM is restarted for manually installed instances of SQL Server.
 
@@ -30,7 +32,7 @@ When you try to deploy a SQL Server on Azure VM image from Azure Marketplace, th
 
 > System Drive returned status not ready for use.
 
-For example, if you're deploying an image from the Azure portal, you might see the following error for the deployment in the Activity log: 
+For example, if you're deploying an image from the Azure portal, you might see the following error for the deployment in **Activity log**: 
 
 :::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":::
 
@@ -65,17 +67,17 @@ tempdb files could not be initialized.
 
 ## Cause
 
-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 results in failure because SQL Server attempts to place the `tempdb` database on the ephemeral storage and fails as the local SSD volume isn't available. Additionally, the ephemeral storage shows as RAW after the machine is deallocated. 
+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 results in failures because SQL Server attempts to place the `tempdb` database on the ephemeral storage and fails as the local SSD volume isn't available. Additionally, the ephemeral storage shows as RAW after the machine is deallocated. 
 
-The RAW local SSD volume causes the SQL VM deployment to fail, and prevents manually installed SQL Server instances from coming online after the VM is restarted. In both cases, SQL Server is trying to initialize the `tempdb` database on the ephemeral storage, which is not available. The deployment fails because SQL Server is installed during the deployment of the Azure VM, and the ephemeral storage isn't available. Likewise, manually installed instances of SQL Server fail to come online after the VM is restarted because the ephemeral storage isn't available when SQL Server tries to create the `tempdb` database.
+The RAW local SSD volume causes the SQL VM deployment to fail, and prevents manually installed SQL Server instances from coming online after the VM is restarted. In both cases, SQL Server is trying to initialize the `tempdb` database on the ephemeral storage, which isn't available. The deployment fails because SQL Server is installed during the deployment of the Azure VM, and the ephemeral storage isn't available. Likewise, manually installed instances of SQL Server fail to come online after the VM is restarted because the ephemeral storage isn't available when SQL Server tries to create the `tempdb` database.
 
 ## Resolution
 
 This issue occurs because of the selected Azure VM size. To solve the issue, use one of the following methods:
 
 - If possible, use another VM SKU, such as those listed in the [VM size best practices](/azure/azure-sql/virtual-machines/windows/performance-guidelines-best-practices-vm-size#checklist). 
-- If you want to use a particular VM that is on the [impacted VMs](#impacted-vms) list, use a machine without the lowercase `d` in the name, which places `tempdb` on the same storage as the SQL Server data files. For example, use the `FXmsv2` VM size instead of the `FXmdsv2`. The latter has uninitialized ephemeral storage, as indicated by the `d` in the name.
-- If you can't use another VM SKU without a RAW local SSD, then 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. **You must reinitialize the disk before starting SQL Server every time the VM is restarted, or deallocated.**
+- If you want to use a particular VM that is on the [impacted VMs](#impacted-vms) list, use a machine without the lowercase `d` in the name, which places `tempdb` on the same storage as the SQL Server data files. For example, use the `FXmsv2` VM size instead of `FXmdsv2`. The latter has uninitialized ephemeral storage, as indicated by `d` in the name.
+- If you can't use another VM SKU without a RAW local SSD, 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. *You must reinitialize the disk before starting SQL Server every time the VM is restarted or deallocated.*
 
 > [!NOTE]
 > Make sure 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.