I am working on a script for a number of SQL servers in which we break out the data drives on different SCSI controllers. Code is below:
$oVCenter = "myServer"
$oVM = "myMachine"
Connect-VIServer -Server $oVCenter | Out-Null
$vm = Get-VM $oVM
#region SCSI #1
$newSCSI1 = New-HardDisk -VM $vm -CapacityGB 1024 -StorageFormat EagerZeroedThick | #P at 1:1
New-ScsiController -Type ParaVirtual -Confirm:$false
$newNDrive = New-HardDisk -VM $vm -CapacityGB 1024 -StorageFormat EagerZeroedThick -Controller $newSCSI1 #N at 1:0
#endregion SCSI #1
#region SCSI #2
$newSCSI2 = New-HardDisk -VM $vm -CapacityGB 15 -StorageFormat EagerZeroedThick | #Q at 2:1
New-ScsiController -Type ParaVirtual -Confirm:$false
#endregion SCSI #2
#region SCSI #3
$newSCSI3 = New-HardDisk -VM $vm -CapacityGB 25 -StorageFormat EagerZeroedThick | #R at 3:1
New-ScsiController -Type ParaVirtual -Confirm:$false
New-HardDisk -VM $vm -CapacityGB 20 -StorageFormat EagerZeroedThick -Controller $newSCSI3 #O at 3:0
#endregion SCSI #3
Disconnect-VIServer -Server $sServer -Confirm:$false
The code works just fine. I am merely curious why it seems to always drop a new hdd in slot 1 when creating a new controller. The first call, for example, creates the controller and puts the drive at 1:1. The next drive I create and point at that controller goes to 1:0. Thereafter it seems drives are added in order: 1:2, 1:3, etc. As it stands, the sole drive I am creating on controller 2 is slotted in 2:1 and then I have to move it to 2:0 manually.
So, I am just wondering, is there a reason for the behavior I am seeing? Secondary to this, is there an easy way to create and/or move a disk to the controller and slot that I want? I did some googling, and have been looking at Set-HardDisk doc but am not seeing it a way to call the slot, only the controller.
