VMware Cloud Community
rm-rf
Contributor
Contributor
‎11-12-2020 11:34 AM

Task to add disk to the VM throws error message

Hi all,

ESXi 5.5 Update 3b (yes unsupported and really old)

VCentre6.5

Ansible module: community.vmware.vmware_guest

We are deploying Windows 2016 and 2019 using Ansible Tower and it is working fine. However we are creating other playbooks to carry out extra configuration as/when required.

We are trying to add extra Hard Disks to an existing Windows machine. This can be on an existing controller or by adding an extra controller. We have tried all sort of permutations and although the disk gets deployed and the controller created (either paravirtual or lsilogicsas) in the VM tasks we see an error which gets reported to Ansible.

We are not, at the moment, using "ignore_error" for Ansible to continue the playbook and get inside the VM to initialize the disk, format with NTFS and bring it online; as we want to understand what is happening.

Has anyone come across this before or could put me in the right direction???

 

'Invalid configuration for device 0'

 

Extract from VM vmx file

 

scsi0.virtualDev = "lsisas1068"
scsi0.present = "TRUE"
scsi0:3.deviceType = "scsi-hardDisk"
scsi0:3.fileName = "myvm_4.vmdk"
sched.scsi0:3.vFlash.enabled = "false"
scsi0:3.present = "true"
scsi0:3.redo = ""

 

Extract from VM 

 

020-11-11T14:08:12.456Z| vmx| I120: HotAdd: Adding scsi-hardDisk with mode 'persistent' to scsi0:3
2020-11-11T14:08:12.458Z| vmx| I120: DISK: OPEN scsi0:3 '/vmfs/volumes/5a5df866-c07edfe6-f3c9-0025b51a0010/myvm/myvm_4_4.vmdk' persistent R[]
2020-11-11T14:08:12.461Z| vmx| I120: DISKLIB-VMFS  : "/vmfs/volumes/5a5df866-c07edfe6-f3c9-0025b51a0010/myvm/myvm_4-flat.vmdk" : open successful (10) size = 1073741824, hd = 2091105629. Type 3
2020-11-11T14:08:12.461Z| vmx| I120: DISKLIB-DSCPTR: Opened [0]: "myvm_4-flat.vmdk" (0xa)
2020-11-11T14:08:12.461Z| vmx| I120: DISKLIB-LINK  : Opened '/vmfs/volumes/5a5df866-c07edfe6-f3c9-0025b51a0010/myvm/myvm_4.vmdk' (0xa): vmfs, 2097152 sectors / 1 GB.
2020-11-11T14:08:12.461Z| vmx| I120: DISKLIB-LIB   : Opened "/vmfs/volumes/5a5df866-c07edfe6-f3c9-0025b51a0010/myvm/myvm_4.vmdk" (flags 0xa, type vmfs).
2020-11-11T14:08:12.461Z| vmx| I120: DISK: Disk '/vmfs/volumes/5a5df866-c07edfe6-f3c9-0025b51a0010/myvm/myvm_4.vmdk' has UUID '60 00 c2 9c 70 64 7c c7-78 92 2b 4b 29 d6 67 fa'
2020-11-11T14:08:12.461Z| vmx| I120: DISK: OPEN '/vmfs/volumes/5a5df866-c07edfe6-f3c9-0025b51a0010/myvm/myvm_4.vmdk' Geo (512/128/32) BIOS Geo (0/0/0)
2020-11-11T14:08:12.464Z| vmx| I120: SCSI DEVICE (scsi0:3): Computed value of scsi0:3.useBounceBuffers: default
2020-11-11T14:08:12.464Z| vmx| I120: Creating virtual dev for scsi0:3
2020-11-11T14:08:12.464Z| vmx| I120: DumpDiskInfo: scsi0:3 createType=11, capacity = 2097152, numLinks = 1, allocationType = 2
2020-11-11T14:08:12.464Z| vmx| I120: SCSIDiskESXPopulateVDevDesc: Using FS backend
2020-11-11T14:08:12.464Z| vmx| I120: DISKUTIL: scsi0:3 : geometry=512/128/32
2020-11-11T14:08:12.465Z| vmx| A115: ConfigDB: Setting scsi0:3.deviceType = "scsi-hardDisk"
2020-11-11T14:08:12.465Z| vmx| A115: ConfigDB: Setting scsi0:3.fileName = "myvm_4.vmdk"
2020-11-11T14:08:12.465Z| vmx| A115: ConfigDB: Setting sched.scsi0:3.vFlash.enabled = "false"
2020-11-11T14:08:12.465Z| vmx| A115: ConfigDB: Setting scsi0:3.present = "true"
2020-11-11T14:08:12.465Z| vmx| A115: ConfigDB: Setting scsi0:3.redo = ""
2020-11-11T14:08:12.491Z| vcpu-0| I120: LSI:Event notification sent for SAS device scsi0:3...

 

 

 

 

0 Kudos
0 Replies