Staging sql failure error

Author: MashaMSFT

support/sql/azure-sql/media/sql-installation-fails-error-azure-vm/4k-sector-size-example.png

@@ -0,0 +1,63 @@
+---
+title: SQL Server installation fails with error on Azure VM
+description: This article provides a resolution for the problem that occurs when you try to install a SQL Server instance on Windows Server 2022 on an Azure virtual machine (VM).
+ms.date: 03/15/2025
+ms.custom: sap:Azure SQL virtual machine
+ms.reviewer: 
+ms.topic: troubleshooting
+---
+# Error (Cannot use file 'master.mdf' because it was originally formatted with sector size 4096) and SQL Server installation fails on a Windows Server 2022 Azure VM
+
+This article helps you resolve a problem that occurs when you try to install SQL Server on Windows Server 2022 on a Microsoft Azure virtual machine (VM).
+
+_Applies to:_   SQL Server on Azure VM - Windows, Windows Server 2022
+
+## Symptoms
+
+When you try to install a SQL Server instance on a Windows Server 2022 Microsoft Azure virtual machine (VM), the installation fails and you receive the following error message in the SQL Server error log when the engine tries to start during the installation:
+
+> Cannot use file '...\master.mdf' because it was originally formatted with sector size 4096 and is now on a volume with sector size 8192. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
+
+In this situation, you can see the following additional information in the Summary.txt log file in the SQL Server setup folder:
+
+```
+Detailed results:
+  Feature:                       Database Engine Services
+  Status:                        Failed
+  Reason for failure:            An error occurred during the setup process of the feature.
+  Next Step:                     Use the following information to resolve the error, uninstall this feature, and then run the setup process again.
+  Component name:                SQL Server Database Engine Services Instance Features
+  Component error code:          0x851A0019
+  Error description:             Could not find the Database Engine startup handle.
+```
+
+
+## Cause
+
+NVMe is a communication protocol that facilitates faster and more efficient data transfer between servers and storage systems by using nonvolatile memory (NVMe). With NVMe, data can be transferred at the highest throughput and with the fastest response times. 
+
+Some of the newest Azure VM generations (such as Da/Ea/Fav6) have an NVMe-only storage interface and require an OS image that supports NVMe. However, these latest Azure VM generations deploy with a default sector size of 8 KB, which isn't currently supported by SQL Server. SQL Server currently supports disks with a standard native sector sizes of 512 bytes and 4 KB. 
+
+If an Azure virtual machine was deployed using the 8-KB sector size, and you attempt to install SQL Server after deployment, the installation can fail. 
+
+## Resolution
+
+To resolve this problem, you must reinstall SQL Server after forcing the Azure VM to use the 4-KB sector size.  
+
+To successfully install SQL Server on your Azure VM, follow these steps:
+
+1. If you've already installed SQL Server, then uninstall SQL Server. Otherwise, skip to the next step. 
+1. Add the [ForcedPhysicalSectorSizeInBytes](../database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size.md#resolutions) registry key. 
+1. Verify the sector size is 4-KB by running the following command in an elevated command prompt: `fsutil fsinfo sectorinfo <volume pathname>`
+1. Restart the Azure VM.
+1. Reinstall SQL Server. 
+
+The following screenshot shows the output of the `fsutil fsinfo sectorinfo` command for the `E:` drive, which has a sector size of 8 KB: 
+
+:::image type="content" source="media/sql-installation-fails-error-azure-vm/8k-sector-size-example.png" alt-text="Screenshot of command prompt output of 8k sector size.":::
+
+The following screenshot shows the output of the `fsutil fsinfo sectorinfo` command for the `E:` drive after updating the registry key to use the 4-KB sector size:
+
+:::image type="content" source="media/sql-installation-fails-error-azure-vm/4k-sector-size-example.png" alt-text="Screenshot of command prompt output of 4-KB sector size.":::
+
+The `ForcedPhysicalSectorSizeInBytes` registry key is an OS-level setting, meaning that all drives currently attached, and those attached in the future, use the 4-KB sector size unless this registry key is removed. 

support/sql/azure-sql/media/sql-installation-fails-error-azure-vm/8k-sector-size-example.png

@@ -9,8 +9,9 @@ items:
 
 - name: Azure SQL Virtual Machine
   items:
+  - name: SQL Server installation fails on some Azure VMs
   - name: FCI installation fails with error on Azure VM
-    href: azure-sql/fci-installation-fails-error-azure-vm.md
+    href: azure-sql/sql-installation-fails-error-azure-vm.md
 
 - name: Data Quality Services (DQS)
   items: