SQL Server 2019 Express installation error

Question

Hello,

I am facing with installation error of SQL Server 2019 Express Edition.

ERRORLOG.txt

ERRORLOG1.txt

ERRORLOG2.txt

HkEngineEventFile_0_133325309678680000.txt

HkEngineEventFile_0_133325309703490000.txt

HkEngineEventFile_0_133325309730630000.txt

Thank You.

Answer 1

Hi @MilkLatte

Found this There have been 256 misaligned log IOs which required falling back to synchronous IO. in your error log.
Please refer to this Tech Doc: Message misaligned log IOs which required falling back to synchronous IO in SQL Server Error Log
SQL Server storage engine logic detects the disk Sector Size and will align the Transaction Log Files metadata and internal boundaries to match the Sector Size (either 512 or 4096 bytes). The error message is generated when SQL Server has detected that Log Entries have been written assuming a Sector Size different to the Sector Size found on the current SQL Server instance. This can happen in scenarios such as the below:

1. Log Shipping from a Production server with one disk sector size to a DR server with a larger sector size
2. AlwaysOn or Database Mirroring from a server with one disk sector size to a DR server with a larger sector size
3. When adding a 4K Native SSD card to hold the Transaction Log on a server where the Transaction Log was created conventional SAN disk with 512 sector size
   To ensure consistency SQL Server may switch from performing asynchronous IO to synchronous IO. This can have an adverse performance impact if technologies like synchronous AlwaysOn or Mirroring are used.
   As a best practice, Microsoft recommends having the same sector size for all disks on all replicas (at least all disks that host log files). In mixed environments, where the secondary has a physical sector of 512 bytes and the primary has a sector size of 4KB, we can use Trace Flag 1800 as a start-up flag on all servers or replicas that have the 512 byte physical sector size. This makes sure that the ongoing log creation format uses a 4KB sector size. Microsoft recommends enabling trace flag 1800 to overcome this issue.
   For more information, please refer to this blog: SQL Server misaligned log IOs which required falling back to synchronous IO.

Best regards,

Cosmog Hong

---

If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Note: Please follow the steps in our Documentation to enable e-mail notifications if you want to receive the related email notification for this thread.