Network Management

Resolving Incorrect Disk Size or Drive Letter Mismatch Due to Duplicate Volume Serial Numbers in SolarWinds Platform

Accurate disk monitoring is critical for maintaining system health and ensuring timely alerts in your environment. Occasionally, SolarWinds may display incorrect disk sizes or mismatched drive letters, causing confusion and potential monitoring gaps. This article explains a common cause of such issues—duplicate Volume Serial Numbers—and provides steps to resolve and prevent them.

First published date

2/4/2026 4:37 PM

Last published date

2/4/2026 4:37 PM

Overview

SolarWinds Platform uses the Volume Serial Number as the unique identifier for volumes during polling. This identifier allows SolarWinds to track and differentiate volumes across nodes reliably. However, when multiple volumes share the same Volume Serial Number, SolarWinds cannot distinguish between them, leading to incorrect or overlapping data in the monitoring console.

Product section

Orion Platform

Cause

Multiple volumes on the same or different nodes having identical Volume Serial Numbers. This can happen due to cloning, imaging, or manual duplication of volumes without reassigning unique serial numbers. When SolarWinds polls these volumes, it receives the same identification data, causing conflicts and inaccurate reporting.
 
For example, two volumes labeled “F:\ Label ” might both have the serial number DCE294B3, confusing SolarWinds during polling.

Volumes Table in the Database:
 
 
Symptoms:
 
  • Disk sizes reported incorrectly in SolarWinds (e.g., showing 3TB instead of the actual 5TB).
  • Duplicate or missing volumes appearing in the SolarWinds web console.
  • Polling errors or data synchronization issues related to the affected node or volumes.

     

Resolution

To resolve the issue, verify if duplicate Volume Serial Numbers are causing the issue first:
 
  1. Use WMI tools such as WBEMTest on the SolarWinds server to query volume serial numbers directly from the node.
  2. Compare the serial numbers of all volumes on the node to identify duplicates.
  3. Review SolarWinds Collector and polling logs for errors or warnings related to volume polling or interface synchronization.
 
After confirming duplicate Volume Serial Numbers are causing the issue:
 
  1. Ensure unique Volume Serial Numbers: Work with your server administrators to update duplicate serial numbers at the operating system level. Windows assigns serial numbers to volumes, and these can be changed if duplicates exist.

  2. Remove duplicate volumes from SolarWinds: In the SolarWinds Web Console, delete the duplicate or orphaned volumes from the node’s resources.

  3. Re-add corrected volumes: Use the “List Resources” feature or network discovery to add the updated volumes back into SolarWinds for proper monitoring.

    Please Note: If interface synchronization errors are present, rebuild the interface cache for the node and restart the Collector and Job Engine services to clear stale data.

  4. Verify: Confirm that SolarWinds now displays the correct disk sizes and drive letters for the affected node.

    Prevention

    • Regularly audit volume serial numbers across your environment to detect duplicates early.
    • Avoid cloning or imaging processes that duplicate volume serial numbers without reassigning them.
    • Use SolarWinds network discovery and resource listing to detect new or changed volumes promptly and maintain accurate monitoring.

    Additional Resources