Windows Server Disk Performance Issues: Troubleshooting Slow Multi-Disk Configurations

Updated: 09 Feb, 2025 • 0 • min read

Table of Contents

Disk performance in Windows Server environments may sometimes exhibit unexpected slowdowns, particularly when utilizing multiple disks. This can be a significant bottleneck, impacting application responsiveness and overall system efficiency. This article addresses a common issue where disk performance is slower than anticipated when using hardware or software-based RAID configurations and provides a detailed resolution to optimize your storage performance.

Symptoms of Slow Disk Performance on Multi-Disk Systems¶

When employing multiple disks in a Windows Server environment, you might observe disk performance that falls short of expectations. This is particularly noticeable in scenarios utilizing Redundant Array of Independent Disks (RAID), whether implemented through hardware or software. The slowdown can manifest in various ways, such as:

Prolonged file access times: Opening, saving, or copying files takes longer than usual.
Application sluggishness: Applications relying heavily on disk I/O become unresponsive or slow.
Database performance degradation: Databases may experience slow query execution and transaction processing.
Virtual machine performance issues: Virtual machines hosted on the affected storage may exhibit poor performance.

Disk Performance

These symptoms can significantly hinder productivity and user experience, making it crucial to identify and resolve the underlying cause of the performance degradation.

Root Cause: Partition Misalignment¶

The primary culprit behind unexpectedly slow disk performance in multi-disk configurations, especially RAID arrays, is often partition misalignment. This issue arises when the starting location of a disk partition is not correctly aligned with the stripe unit boundary of the RAID array.

To understand this, let’s break down the concepts:

Stripe Unit: In a RAID array, data is often striped across multiple disks to improve performance and/or redundancy. The stripe unit is the block size at which data is written across these disks.
Partition Alignment: Ideally, partitions should be aligned with these stripe unit boundaries. This means that a partition should start at a sector that is a multiple of the stripe unit size.

When a partition is misaligned, a single volume cluster (the smallest unit of storage allocation in NTFS) can span across two stripe units. Consequently, when the system attempts to write or read a single volume cluster, it may need to access two different disk groups within the RAID array instead of just one. This extra I/O operation for each cluster access significantly reduces performance.

RAID configuration

Windows, by default, creates partitions based on predefined sector counts. Historically, the starting location for a disk partition has been either the 32^nd or 64^th sector, depending on the storage controller’s information. While this was generally acceptable for single disks, it often leads to misalignment in RAID environments due to the stripe unit structure.

It’s important to note that while partitions reserve the very first sector for boot code and partition information, the actual data portion begins from the second sector. Even with this sector reserved, misalignment can still occur if the partition starting offset is not a multiple of the stripe unit size.

Resolution: Utilizing Diskpart with Offset Alignment¶

To effectively address partition misalignment and optimize disk performance on RAID arrays, the recommended solution is to use the Diskpart.exe command-line utility to create disk partitions with a specific starting offset. By manually specifying the starting offset, we can ensure proper alignment with the RAID stripe unit boundaries.

The optimal starting offset to use with Diskpart is 2,048 sectors (1 megabyte). This offset is designed to accommodate most common stripe unit sizes encountered in RAID configurations. By using this offset, you significantly increase the likelihood of proper partition alignment, thus mitigating the performance penalty associated with misalignment.

Diskpart tool

It’s worth mentioning that Windows Server 2003 Service Pack 1 introduced the enhanced capabilities of Diskpart, including the ability to adjust partition alignment. If you are using an older system without an updated Diskpart version, the diskpar utility (note the missing “t”) might be available as an alternative, although Diskpart is the preferred and more feature-rich tool.

For existing partitions, you can verify their alignment by performing a calculation detailed in the “More Information” section below. If a partition is found to be misaligned, recreating it with the correct offset using Diskpart is the recommended course of action.

Step-by-Step Guide to Align Partitions Using Diskpart¶

The following steps outline how to use Diskpart to create a disk partition with a 2,048-sector offset, ensuring alignment on a RAID array:

Open Command Prompt: Access the command prompt by typing cmd in the Windows search bar and pressing Enter.
Launch Diskpart: At the command prompt, type diskpart and press Enter. This will launch the Diskpart command-line utility.
```
diskpart
```

List Disks: To view the available disks on your system, type list disk and press Enter. Diskpart will display a table summarizing each disk, including its disk number, status, size, free space, and whether it’s a dynamic or GPT disk. Identify the disk number corresponding to your RAID array where you want to create the aligned partition.

list disk

Disk ###  Status         Size     Free     Dyn  Gpt
--------  -------------  -------  -------  ---  ---
Disk 0    Online          37 GB  8033 KB
Disk 1    Online          17 GB  8033 KB
Disk 2    Online          17 GB      0 B
Disk 3    Online          17 GB   148 MB   *
Disk 4    Online          17 GB     8 MB   *
Disk 5    Online          17 GB     8 MB   *
Disk 6    Online          17 GB     8 MB   *
Disk 7    Online          17 GB     8 MB   *
Disk 8    Online          17 GB   435 KB   *
Disk 9    Online          17 GB     8 MB   *
Disk 10   Online          17 GB  8033 KB

The list disk command provides essential information about each disk. The asterisk (*) indicates the currently selected disk (focus). Only fixed and removable disks (IDE, SCSI, 1394, USB) are listed.

Select Disk: Choose the disk you want to partition by using the select disk command followed by the disk number identified in the previous step. For example, to select Disk 2, type select disk 2 and press Enter.
```
select disk 2
```
Create Partition with Alignment: Create the primary partition with the alignment parameter using the create partition primary align=1024 command. The align=1024 parameter in this context specifies an alignment of 1024 kilobytes, which is equivalent to 2048 sectors (since 1 kilobyte = 2 sectors at 512 bytes per sector, and 1024 KB * 2 sectors/KB = 2048 sectors).
```
create partition primary align=1024
```
You should receive a confirmation message: “DiskPart succeeded in creating the specified partition.”

The align=number parameter is particularly useful for hardware RAID Logical Unit Numbers (LUNs) that are not cylinder-aligned. It aligns the primary partition at the disk’s beginning and rounds the offset to the nearest alignment boundary. The number value represents kilobytes from the disk’s beginning to the alignment boundary. If used with offset=number, the offset must be within the first usable cylinder.
Exit Diskpart: Type exit and press Enter to close the Diskpart utility.
```
exit
```
Open Disk Management: Click Start, then Run, type diskmgmt.msc, and click OK to open the Disk Management MMC snap-in.
Assign Drive Letter: In Disk Management, locate the newly created partition (it will likely be unformatted). Right-click on the partition and select “Change Drive Letter and Paths…” to assign a drive letter.
Format Partition: Right-click on the partition again and select “Format…”. Choose the NTFS file system and assign a desired cluster size. It’s generally recommended to use the default allocation unit size unless you have specific performance requirements.

This procedure is designed for creating a single partition per RAID group. If you need multiple partitions, you would repeat steps 4-9 for each partition, ensuring the initial partition on the RAID group is aligned.

More Information: Verifying Partition Alignment and Understanding Offsets¶

To confirm if an existing partition is correctly aligned, you can perform a simple calculation. This involves dividing the stripe unit size of your RAID array by the starting offset of the disk partition. The formula is:

((Partition offset) * (Disk sector size)) / (Stripe unit size)

Important: Ensure that both the disk sector size and stripe unit size are expressed in the same units, either bytes or kilobytes (KB). The standard disk sector size is 512 bytes (0.5 KB).

Example Calculation (256 KB Stripe Unit Size):

Let’s consider a RAID array with a 256 KB stripe unit size and examine different starting offsets:

Calculations in Bytes:

Offset 63 sectors: (63 * 512) / 262144 = 0.123046875 (Not Aligned)
Offset 64 sectors: (64 * 512) / 262144 = 0.125 (Not Aligned)
Offset 128 sectors: (128 * 512) / 262144 = 0.25 (Not Aligned)
Offset 256 sectors: (256 * 512) / 262144 = 0.5 (Not Aligned)
Offset 512 sectors: (512 * 512) / 262144 = 1 (Aligned)

Calculations in Kilobytes:

Offset 63 sectors: (63 * 0.5) / 256 = 0.123046875 (Not Aligned)
Offset 64 sectors: (64 * 0.5) / 256 = 0.125 (Not Aligned)
Offset 128 sectors: (128 * 0.5) / 256 = 0.25 (Not Aligned)
Offset 256 sectors: (256 * 0.5) / 256 = 0.5 (Not Aligned)
Offset 512 sectors: (512 * 0.5) / 256 = 1 (Aligned)

These examples clearly demonstrate that for a 256 KB stripe unit size, the partition is only correctly aligned when created with a starting offset of 512 sectors or a multiple thereof. The recommended 2048-sector offset (1MB) from Diskpart provides ample alignment for various stripe unit sizes.

Important Considerations:

The number of disks in the RAID array does not directly affect partition alignment. The critical factors are the stripe unit size and the partition starting offset.
While the examples use 256 KB stripe units, RAID configurations can utilize different stripe unit sizes. Consult your RAID controller documentation to determine the stripe unit size used in your specific setup.

Finding the Starting Offset of an Existing Partition:

To determine the starting offset of an existing partition, you can use the wmic command-line tool:

Open Command Prompt: Open a command prompt as described earlier.

Execute wmic Command: Type the following command and press Enter:

wmic partition get BlockSize, StartingOffset, Name, Index

This command retrieves information about partitions, including their block size, starting offset, name, and index.

BlockSize  Index  Name                        StartingOffset
512        0      Disk #1, Partition #0      32256
512        0      Disk #2, Partition #0      32256
512        0      Disk #3, Partition #0      32256
512        0      Disk #4, Partition #0      1048576
512        0      Disk #0, Partition #0      32256
512        1      Disk #0, Partition #1      41126400

Analyze Output: Examine the output, noting the BlockSize and StartingOffset values for each partition. The Index indicates the partition number on a given disk (Index 0 is the first partition).
Calculate Starting Sector: To find the partition starting offset in sectors, divide the StartingOffset value by the BlockSize value. For example, using the output above:
```
32256 / 512 = 63 sectors
1048576 / 512 = 2048 sectors
```
In the example, partitions with a starting offset of 32256 bytes (63 sectors) are likely misaligned, while the partition with 1048576 bytes (2048 sectors) is properly aligned.

By understanding partition alignment and utilizing Diskpart to create partitions with appropriate offsets, you can significantly improve disk performance in Windows Server multi-disk and RAID environments, ensuring optimal system responsiveness and efficiency.

If you have any questions or further insights regarding disk performance optimization on Windows Server, feel free to leave a comment below!

Computacionvinchi