VMware Cloud Community
gculbert70
Contributor
Contributor
Jump to solution

Virtual Server Adding Hard Drives

Hello,

I have a virtual server in VMWare that normally has 2 hard drives assigned to it. The other day I found it added 3 more drives pointing to other virtual servers on the cluster. I removed these to get it back to the configuration it needs to have but for some reason it keeps adding these drives back to its configuration. I can not figure out why it is doing this or how to stop it.  I can see in the tasks that the reconfiguration is being done by the administrator.  I am adding the information for the task that added a disk back to the vm -

Reconfigured ann-idpa-prx2 on ann-ent-esxi-03.us.terumo.com in VxRail-Datacenter . Modified: config.hardware.device(1000).device: (2000, 2002) -> (2000, 2002, 2001); Added: config.hardware.device(2001): (key = 2001, deviceInfo = (label = "Hard disk 3", summary = "209,715,200 KB"), backing = (fileName = "ds:///vmfs/volumes/vsan:5264694f35f810a7-c52768776621b8ca/d0397f64-86e6-2b08-80ec-b49691d37f58/ANN-SQLPROD5.us.terumo.com.vmdk", datastore = 'vim.Datastore:2eafa2ff-939a-4a60-b138-8206ddbf8d5d:datastore-21', backingObjectId = "d1397f64-ace4-814a-6ca6-b49691d37f58", diskMode = "independent_nonpersistent", split = false, writeThrough = false, thinProvisioned = true, eagerlyScrub = false, uuid = "6000C298-332a-1283-aee6-00f65160f13f", contentId = "98067a3b7c15c300bcfbd1605824ce6c", changeId = <unset>, parent = null, deltaDiskFormat = <unset>, digestEnabled = false, deltaGrainSize = <unset>, deltaDiskFormatVariant = <unset>, sharing = "sharingNone", keyId = null, cryptoIntegrityProtectionType = <unset>), connectable = null, slotInfo = null, controllerKey = 1000, unitNumber = 1, numaNode = <unset>, capacityInKB = 209715200, capacityInBytes = 214748364800, shares = (shares = 1000, level = "normal"), storageIOAllocation = (limit = -1, shares = (shares = 1000, level = "normal"), reservation = 0), diskObjectId = "32-2001", vFlashCacheConfigInfo = null, iofilter = <unset>, vDiskId = null, virtualDiskFormat = <unset>, nativeUnmanagedLinkedClone = false, independentFilters = <unset>); config.extraConfig("scsi0:1.redo"): (key = "scsi0:1.redo", value = "/vmfs/volumes/vsan:5264694f35f810a7-c52768776621b8ca/2ccaa163-6a37-7b59-443b-b49691d38098/./ANN-SQLPROD5.us.terumo.com.vmdk.REDO_7lWUew"); config.extraConfig("scsi0:1.ctkEnabled"): (key = "scsi0:1.ctkEnabled", value = "TRUE"); Deleted:

 

I am open to any suggestions.

Labels (1)
Reply
0 Kudos
1 Solution

Accepted Solutions
Thomas_França
Enthusiast
Enthusiast
Jump to solution

Here are some potential reasons :

  1. Automation or Orchestration Tools: If you're using automation or orchestration tools like vCenter Server, vRealize Automation, or any other third-party tool, they might be responsible for automatically adding these drives as part of their configuration. Check the automation policies, scripts, or templates to ensure that they are not inadvertently adding these drives.

  2. VM Templates or Cloning: If the virtual server was created from a template or if you've been cloning it, there might be residual configuration settings that are causing these drives to reappear. Review the template configuration and the cloning process to ensure there are no references to these additional drives.

  3. Snapshot Rollbacks: If you've recently rolled back to a snapshot of the virtual server, the snapshot might have included these additional drives. When you revert to that snapshot, the drives could be added back. Make sure you're rolling back to a snapshot that corresponds to the desired configuration.

  4. Misconfigured Resource Pools or VM Overrides: Check if there are any resource pools or VM overrides in your cluster that might be pushing unwanted configurations onto your virtual server. These could include storage or disk settings.

  5. Shared Storage or Datastore: If your virtual server is using shared storage or datastores, it's possible that other virtual servers are somehow influencing its configuration. Ensure that there are no misconfigurations or shared settings causing this issue.

  6. Permissions and Access Control: Review the permissions and access controls for your virtual server. Unauthorized users or processes might be making changes to its configuration.

View solution in original post

1 Reply
Thomas_França
Enthusiast
Enthusiast
Jump to solution

Here are some potential reasons :

  1. Automation or Orchestration Tools: If you're using automation or orchestration tools like vCenter Server, vRealize Automation, or any other third-party tool, they might be responsible for automatically adding these drives as part of their configuration. Check the automation policies, scripts, or templates to ensure that they are not inadvertently adding these drives.

  2. VM Templates or Cloning: If the virtual server was created from a template or if you've been cloning it, there might be residual configuration settings that are causing these drives to reappear. Review the template configuration and the cloning process to ensure there are no references to these additional drives.

  3. Snapshot Rollbacks: If you've recently rolled back to a snapshot of the virtual server, the snapshot might have included these additional drives. When you revert to that snapshot, the drives could be added back. Make sure you're rolling back to a snapshot that corresponds to the desired configuration.

  4. Misconfigured Resource Pools or VM Overrides: Check if there are any resource pools or VM overrides in your cluster that might be pushing unwanted configurations onto your virtual server. These could include storage or disk settings.

  5. Shared Storage or Datastore: If your virtual server is using shared storage or datastores, it's possible that other virtual servers are somehow influencing its configuration. Ensure that there are no misconfigurations or shared settings causing this issue.

  6. Permissions and Access Control: Review the permissions and access controls for your virtual server. Unauthorized users or processes might be making changes to its configuration.