SQL Server Error

Question

2023-04-24 01:20:19.49 Server      Microsoft SQL Server 2019 (RTM) - 15.0.2000.5 (X64) 
	Sep 24 2019 13:48:23 
	Copyright (C) 2019 Microsoft Corporation
	Express Edition (64-bit) on Windows 10 Home 10.0 <X64> (Build 22621: ) (Hypervisor)

2023-04-24 01:20:19.49 Server      UTC adjustment: 9:00
2023-04-24 01:20:19.49 Server      (c) Microsoft Corporation.
2023-04-24 01:20:19.49 Server      All rights reserved.
2023-04-24 01:20:19.49 Server      Server process ID is 2824.
2023-04-24 01:20:19.49 Server      System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: '750XDA'.
2023-04-24 01:20:19.49 Server      Authentication mode is WINDOWS-ONLY.
2023-04-24 01:20:19.49 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS04\MSSQL\Log\ERRORLOG'.
2023-04-24 01:20:19.49 Server      The service account is 'NT Service\MSSQL$SQLEXPRESS04'. This is an informational message; no user action is required.
2023-04-24 01:20:19.49 Server      Registry startup parameters: 
	 -d C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS04\MSSQL\DATA\master.mdf
	 -e C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS04\MSSQL\Log\ERRORLOG
	 -l C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS04\MSSQL\DATA\mastlog.ldf
2023-04-24 01:20:19.49 Server      Command Line Startup Parameters:
	 -s "SQLEXPRESS04"
	 -m "SqlSetup"
	 -Q
	 -q "Korean_Wansung_CI_AS"
	 -T 4022
	 -T 4010
	 -T 3659
	 -T 3610
	 -T 8015
	 -d "C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS04\MSSQL\Template Data\master.mdf"
	 -l "C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS04\MSSQL\Template Data\mastlog.ldf"
2023-04-24 01:20:19.49 Server      SQL Server detected 1 sockets with 4 cores per socket and 8 logical processors per socket, 8 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2023-04-24 01:20:19.49 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2023-04-24 01:20:19.49 Server      Detected 16107 MB of RAM. This is an informational message; no user action is required.
2023-04-24 01:20:19.49 Server      Using conventional memory in the memory manager.
2023-04-24 01:20:19.50 Server      Page exclusion bitmap is enabled.
2023-04-24 01:20:19.58 Server      Buffer Pool: Allocating 2097152 bytes for 1710001 hashPages.
2023-04-24 01:20:19.59 Server      Default collation: SQL_Latin1_General_CP1_CI_AS (us_english 1033)
2023-04-24 01:20:19.60 Server      Buffer pool extension is already disabled. No action is necessary.
2023-04-24 01:20:19.64 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2023-04-24 01:20:19.66 Server      Query Store settings initialized with enabled = 1, 
2023-04-24 01:20:19.66 Server      The maximum number of dedicated administrator connections for this instance is '1'
2023-04-24 01:20:19.66 Server      This instance of SQL Server last reported using a process ID of 31152 at 2023-04-24 오전 1:20:15 (local) 2023-04-23 오후 4:20:15 (UTC). This is an informational message only; no user action is required.
2023-04-24 01:20:19.67 Server      Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2023-04-24 01:20:19.67 Server      Using dynamic lock allocation.  Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.  This is an informational message only.  No user action is required.
2023-04-24 01:20:19.67 Server      In-Memory OLTP initialized on standard machine.
2023-04-24 01:20:19.68 Server      [INFO] Created Extended Events session 'hkenginexesession'

2023-04-24 01:20:19.69 Server      Database Instant File Initialization: enabled. For security and performance considerations see the topic 'Database Instant File Initialization' in SQL Server Books Online. This is an informational message only. No user action is required.
2023-04-24 01:20:19.69 Server      Total Log Writer threads: 2. This is an informational message; no user action is required.
2023-04-24 01:20:19.70 Server      Database Mirroring Transport is disabled in the endpoint configuration.
2023-04-24 01:20:19.70 Server      clwb is selected for pmem flush operation.
2023-04-24 01:20:19.70 Server      Software Usage Metrics is disabled.
2023-04-24 01:20:19.70 spid10s     Warning ******************
2023-04-24 01:20:19.70 spid10s     SQL Server started in single-user mode. This an informational message only. No user action is required.
2023-04-24 01:20:19.70 spid10s     Starting up database 'master'.
2023-04-24 01:20:19.71 spid10s     There have been 256 misaligned log IOs which required falling back to synchronous IO.  The current IO is on file C:\Program Files\Microsoft SQL Server\MSSQL15.SQLEXPRESS04\MSSQL\Template Data\master.mdf.
2023-04-24 01:20:19.81 Server      CLR version v4.0.30319 loaded.
2023-04-24 01:20:19.85 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.

Answer 1

You are running into a known issue, for which Microsoft has published a document with workarounds.

Answer 2

Hi @seung woo lee,

Like Erland said that it is a known issue. Check the resolution mentioned in the documentation.

Consider one of the following solutions:

• If you have multiple drives on this system, you can specify a different location for the database files after installation of SQL Server is complete. Make sure that drive reflects a supported sector size when querying the fsutil commands. SQL Server currently supports sector storage sizes of 512 bytes and 4096 bytes.
• You can add a registry key, which will cause the behavior of Windows 11 and later to be similar to Windows 10. This will force the sector size to be emulated as 4 KB. To add the ForcedPhysicalSectorSizeInBytes registry key, use the Registry Editor or run commands as described in the PowerShell as Administrator section. You must reboot the device after adding the registry key in order for this change to take effect.

Troubleshoot errors related to system disk sector size greater than 4 KB

Regards，

Zoe Hui

---

If the answer is helpful, please click "Accept Answer" and upvote it.