Skip to content

Commit 6f481cf

Browse files
authored
Updates from editor
1 parent 1d23f6b commit 6f481cf

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

support/sql/database-engine/database-file-operations/troubleshoot-os-4kb-disk-sector-size.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ _Applies to_:   SQL Server all versions
1818

1919
## Scenario 1: Move the file to a volume with a compatible sector size
2020

21-
If you try to use sector size higher than 4 KB, you see the following error message:
21+
If you try to use sector size greater than 4 KB, you see the following error message:
2222

2323
```output
2424
Error: 5179, Severity: 16, State: 1.
@@ -48,7 +48,7 @@ For more information, see [SQL Server installation fails with sector size error
4848

4949
## Scenario 3: Wait on the Database Engine recovery handle failed
5050

51-
When you install any version of SQL Server, you see errors similar to the following message for the Database Engine Services component of SQL Server:
51+
When you install any version of SQL Server, you see errors that resemble the following message for the Database Engine Services component of SQL Server:
5252

5353
```output
5454
Feature: Database Engine Services
@@ -60,7 +60,7 @@ Component error code: 0x851A001A
6060
Error description: Wait on the Database Engine recovery handle failed. Check the SQL Server error log for potential causes.
6161
```
6262

63-
Or, you see the following errors in the SQL Server Error Log:
63+
Or, you see the following errors in the SQL Server error Log:
6464

6565
```output
6666
2025-02-26 20:01:16.79 spid14s Starting up database 'master'.
@@ -93,7 +93,7 @@ Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
9393

9494
## Scenario 6: Move the file to a volume with a sector size that is the same as or smaller than the original sector size
9595

96-
You install LocalDB on a Windows 11 device. The setup fails. In the SQL Server error log, you notice the following entries:
96+
You install LocalDB on a Windows 11 device and the setup fails. In the SQL Server error log, you notice the following entries:
9797

9898
```output
9999
2021-12-15 23:25:04.28 spid5s Cannot use file 'C:\Users\Administrator\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\TestInstance\master.mdf' because it was originally formatted with sector size 4096 and is now on a volume with sector size 16384. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
@@ -192,7 +192,7 @@ Additionally, be aware of the Windows support policy for file system and storage
192192
- If you don't add the registry key and you have multiple drives on this system, you can specify a different location for the database files after the installation of SQL Server is complete. Make sure that the drive reflects a supported sector size when querying the `fsutil` commands. SQL Server currently supports sector storage sizes of 512 bytes and 4,096 bytes.
193193

194194
> [!CAUTION]
195-
> If you've already created a storage pool with disks that have a sector size greater than 4 kb to host SQL Server files, you must first remove the storage pool, apply one of the troubleshooting methods mentioned in this article, and then rebuild the storage pool before attempting to install SQL Server on the storage pool or pools.
195+
> If you've already created a storage pool with disks that have a sector size greater than 4 KB to host SQL Server files, you must first remove the storage pool, apply one of the troubleshooting methods mentioned in this article, and then rebuild the storage pool before attempting to install SQL Server on the storage pool or pools.
196196

197197
## More information
198198

0 commit comments

Comments
 (0)