Eire09
Enthusiast
Enthusiast

Editing VMX file to remove vmdk disk

Hi,

I took a clone of a LUN to my DR site. The system drive is on LUN1 & the data drive is on LUN2. I don;t need the data drive however when I try to boot the VM it gives me an error because it cant find the data LUN.

Can i edit the VMX file in order to get it to boot by removing all references to disk 2?

This is the VMDK file:

.encoding = "UTF-8"
config.version = "8"
virtualHW.version = "7"
pciBridge0.present = "true"
pciBridge4.present = "true"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "true"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "true"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "true"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
vmci0.present = "true"
nvram = "IEBCK-MAS - NetBackup Master.nvram"
virtualHW.productCompatibility = "hosted"
powerType.powerOff = "soft"
powerType.powerOn = "hard"
powerType.suspend = "hard"
powerType.reset = "soft"
displayName = "IEBCK-MAS - NetBackup Master 1 DR"
extendedConfigFile = "IEBCK-MAS - NetBackup Master.vmxf"
floppy0.present = "true"
numvcpus = "2"
scsi0.present = "true"
scsi0.sharedBus = "none"
scsi0.virtualDev = "lsisas1068"
memsize = "8192"
scsi0:0.present = "true"
scsi0:0.fileName = "IEBCK-MAS - NetBackup Master.vmdk"
scsi0:0.deviceType = "scsi-hardDisk"
sched.scsi0:0.shares = "normal"
scsi0:1.present = "true"
scsi0:1.fileName = "/vmfs/volumes/4f7440c0-2ba69b42-f0b8-002655d6ba42/IEBCK-MAS - NetBackup Master/IEBCK-MAS - NetBackup Master_1.vmdk"
scsi0:1.deviceType = "scsi-hardDisk"
sched.scsi0:1.shares = "normal"
ide1:0.present = "true"
ide1:0.fileName = ""
ide1:0.deviceType = "atapi-cdrom"
ide1:0.startConnected = "false"
floppy0.startConnected = "false"
floppy0.clientDevice = "true"
ethernet0.present = "true"
ethernet0.virtualDev = "e1000"
ethernet0.networkName = "vProduction 207"
ethernet0.addressType = "vpx"
ethernet0.generatedAddress = "00:50:56:8f:00:48"
svga.vramSize = "8388608"
disk.EnableUUID = "true"
guestOSAltName = "Microsoft Windows Server 2008 R2 (64-bit)"
guestOS = "windows7srv-64"
annotation = "Prod - Backup Exec Master"
uuid.bios = "42 0f 80 73 15 8d 7b 4e-6b ac 19 f7 7c a4 e4 6e"
vc.uuid = "50 0f 5a 70 a1 36 43 69-2e 16 7a 18 c3 b0 81 d3"
log.fileName = "vmware.log"
snapshot.action = "keep"
sched.cpu.min = "0"
sched.cpu.units = "mhz"
sched.cpu.shares = "normal"
sched.mem.minsize = "0"
sched.mem.shares = "normal"
tools.upgrade.policy = "manual"
sched.scsi0:0.throughputCap = "off"
sched.scsi0:1.throughputCap = "off"
deploymentPlatform = "windows"
unity.customColor = "#C0C0C0"
replay.supported = "FALSE"
scsi0:0.redo = ""
vmotion.checkpointFBSize = "8388608"
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
scsi0.pciSlotNumber = "160"
ethernet0.pciSlotNumber = "32"
vmci0.pciSlotNumber = "33"
scsi0.sasWWID = "50 05 05 63 15 8d 7b 40"
hostCPUID.0 = "0000000b756e65476c65746e49656e69"
hostCPUID.1 = "000206c200200800029ee3ffbfebfbff"
hostCPUID.80000001 = "0000000000000000000000012c100800"
guestCPUID.0 = "0000000b756e65476c65746e49656e69"
guestCPUID.1 = "000006f100010800800022010febfbff"
guestCPUID.80000001 = "00000000000000000000000120100800"
userCPUID.0 = "0000000b756e65476c65746e49656e69"
userCPUID.1 = "000206c200200800000022010febfbff"
userCPUID.80000001 = "00000000000000000000000120100800"
evcCompatibilityMode = "TRUE"
scsi0:1.ctkEnabled = "false"
scsi0:1.redo = ""
unity.wasCapable = "false"
vmci0.id = "2091181167"
tools.syncTime = "FALSE"
uuid.location = "56 4d b6 a7 2d a4 cb 8b-2f 44 0e d8 67 b8 3e 12"
cleanShutdown = "FALSE"
migrate.hostlog = "./IEBCK-MAS - NetBackup Master-8980df5e.hlog"
sched.mem.max = "8192"
ide1:0.clientDevice = "TRUE"
sched.swap.derivedName = "/vmfs/volumes/4f7440c0-2ba69b42-f0b8-002655d6ba42/IEBCK-MAS - NetBackup Master/IEBCK-MAS - NetBackup Master-8980df5e.vswp"
scsi0:2.deviceType = "scsi-hardDisk"
scsi0:3.deviceType = "scsi-hardDisk"

0 Kudos
1 Reply
a_p_
Leadership
Leadership

Editing the .vmx file is certainly an option, but why don't you just remove the disk from within the VM's setting?

If you are going to edit the .vmx file, you need to:

  • remove the VM from the inventory
  • backup and edit the .vmx file
  • add the VM to the inventory

André

0 Kudos