I guess its working as expected, I see different Labels on your screenshot (C,D,E) and hence it is treating them as separate drive's, there are 2 ways to resolve this:
1. Do a list resource on the node uncheck everything on list resource and submit the same. Wait for one polling cycle check from node view if old drives disappear. If they disappear do a list resource again and add the new one's. If point 1 does not work go to point 2
2. Directly remove old drives from DB, Drives are present under Table "Volumes", keep the nodeid handy.
Open Node View -> http://solarwinds/Orion/Net/NodeDetails.aspx?NetObject=N:XXXX
Use the below query to list the drives on DB:
SELECT * FROM Volumes where NodeID=XXXX
And then remove the same from DB
Hope it helps
Thanks for this it worked a treat.
Surely there must be a way within NPM itself for it to have some logic around volume ID's and removing redundant once particularly as you can un-tick the volumes in the resource list and it still shows the old volumes, resizing volumes in VM is not an uncommon occurrence and this is going to cause us issues as the only way I can see of getting round it is to remove the volumes prior to a resize and then reselect them afterwards.