High disk write IOPS on the OS disk were observed, with write IOPS exceeding 30% of the baseline disk IOPS limit of 500.

FPI Erick Aspiras(Erick Aspiras) 20 Reputation points
2025-03-27T08:15:37.5+00:00

High disk write IOPS on the OS disk were observed, with write IOPS exceeding 30% of the baseline disk IOPS limit of 500.

I ran performance diagnostics and this is one of the issues reported. However, how to find out what disk is this?

\?\ide#diskvirtual_hd______________________________1.1.0___#5&1278c138&0&0.0.0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}

5

SQL Server Database Engine
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Peter Verniest (iTech) 0 Reputation points
    2025-03-31T10:59:02.1466667+00:00

    Can't you find the identifier using Get-WmiObject Win32_DiskDrive?

    Hereby example of a script?

    Get-WmiObject Win32_DiskDrive | ForEach-Object {
      $disk = $_
      $partitions = "ASSOCIATORS OF {Win32_DiskDrive.DeviceID='$($disk.DeviceID)'} WHERE AssocClass=Win32_DiskDriveToDiskPartition"
      Get-WmiObject -Query $partitions | ForEach-Object {
        $partition = $_
        $logicalDisks = "ASSOCIATORS OF {Win32_DiskPartition.DeviceID='$($partition.DeviceID)'} WHERE AssocClass=Win32_LogicalDiskToPartition"
        Get-WmiObject -Query $logicalDisks | ForEach-Object {
          [PSCustomObject]@{
            DiskModel     = $disk.Model
            DeviceID      = $disk.DeviceID
            Volume        = $_.DeviceID
            Partition     = $partition.DeviceID
            PNPDeviceID   = $disk.PNPDeviceID
          }
        }
      }
    }
    
    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.