Submit a ticketCall us
Home > Success Center > Server & Application Monitor (SAM) > Volume stops reporting after a resize or name change

Volume stops reporting after a resize or name change

Overview


This article discuses a number of reason(s) as to why the Volume resource in the Orion web console is not updating or the volume does not provide any status after the volume has been resized or renamed
 

Environment

  • All SAM versions

Cause  

  • This issue occurs when the volume Serial ID has changed and Orion is detecting it as a new volume.
    (If a volume is resized or renamed, etc Windows automatically applies a new Serial ID to the device. There is no workaround for this. Solarwinds will recognize the renamed device as a new volume by design).
     
  • Volumes may appear as unknown or appear to be duplicating themselves in the webconsole but this is really caused by when a volume Serial ID changes and Solarwinds recognizes the volume as a 'new' volume.

 

Resolution  

  1. Log on to the SolarWinds Web Console using an account that has Node Management rights.
  2. Go to Settings > Manage Nodes.
  3. Find the node with the failing volume.
  4. Click the + icon on the left to expand the node details.
  5. Select the Volume that has stopped responding and then click Delete.
  6. Select the checkbox next to the node name.
  7. Click on List Resources.
  8. Select all the Volumes to be monitored and click Submit.
     
  9. Alternatively as this can be a tedious process you can set up a discovery to auto discover new Volumes as they become available in your environment - Add Discovered Device to Solarwinds

 

For a comprehensive list of Volumes that are not currently reporting correctly, you can run the following query against the Orion database
 

SELECT * FROM Volumes WHERE VolumeIndex <='0'

 

 

Last modified

Tags

Classifications

Public