VMware Cloud Community
am312
Contributor
Contributor

Windows drive letter changes after migrating VM from ESXi 6.0 ->ESXi 6.6

I am migrating a Windows 2012 Server guest from an ESXi 6.0 host to a ESXi 6.6 host.  When the Windows guest comes up the 1TB drive has moved from E: to 😧 (messing up drive shares) and Window's storage manager does not allow me to reassign it back to E:.   Probably windows thinks something is still on E, just disconnected.

Windows guest has 3 drives

     80GB

     10GB Swap

     1TB (E: drive, "REPO01_1.vmdk")

1) shutdown Windows Server 2012 guest on ESXi 6.0

2) delete 1TB disk from VM config

3) migrate VM to ESXi 6.6 host using VMware vCenter Converter Standalone

4) SFTP the 1TB VMDK file to ESXi 6.6 host

5) add 1TB drive to VM on ESXi 6.6 host using VMDK file

6) start Windows guest on ESXi 6.6 host

I use SFTP because it's 20x faster than VMware's converter.  Moving 1TB+ drive would take days with it.

Looks like I'm on SCSI 0:1 so I'd expect the drive to be migrated as expected.

Source VM:

[root@ESX02:/vmfs/volumes/5ab95e62-7d552784-050c-98f2b328fd94/REPO01] grep -i scsi REPO01.vmx

scsi0.virtualDev = "lsisas1068"

scsi0.present = "TRUE"

scsi0:0.deviceType = "scsi-hardDisk"

scsi0:0.fileName = "REPO01.vmdk"

scsi0:0.present = "TRUE"

sched.scsi0:0.throughputCap = "off"

sched.scsi0:0.shares = "high"

scsi0:1.deviceType = "scsi-hardDisk"

scsi0:1.fileName = "REPO01_1.vmdk"  <-- 1TB disk

sched.scsi0:1.shares = "high"

sched.scsi0:1.throughputCap = "off"

scsi0:1.present = "TRUE"

scsi0.pciSlotNumber = "160"

scsi0.sasWWID = "50 05 05 6e 40 53 60 f0"

scsi0:1.redo = ""

scsi0:0.redo = ""

Destination VM:

[root@ESX04:/vmfs/volumes/5dcc5389-e14224e2-7655-002590be2724/REPO01] grep scsi REPO01.vmx

scsi0.virtualDev = "lsisas1068"

scsi0.present = "TRUE"

scsi0:0.deviceType = "scsi-hardDisk"

scsi0:0.fileName = "REPO01.vmdk"

sched.scsi0:0.shares = "high"

sched.scsi0:0.throughputCap = "off"

scsi0:0.present = "TRUE"

scsi0:1.deviceType = "scsi-hardDisk"

scsi0:1.fileName = "/vmfs/volumes/5dd30100-83438218-99b6-002590be2724/REPO01/REPO01_1.vmdk"  <-- 1TB disk

sched.scsi0:1.shares = "normal"

sched.scsi0:1.throughputCap = "off"

scsi0:1.present = "TRUE"

scsi0.pciSlotNumber = "160"

scsi0:1.redo = ""

scsi0:0.redo = ""

scsi0.sasWWID = "50 05 05 6f 79 08 3b a0"

What can I do to fix this besides letting the VMware Converter handle all 3 drives meaning it works its magic on the 1TB partition for 48 hours?

Thanks

0 Kudos
1 Reply
a_p_
Leadership
Leadership

Not sure what caused the drive letter to change. Windows should basically have identified the disk/partition by its ID.

Anyway, check whether the original drive letter has been assigned to something else, e.g. a CD/DVD drive.

André

0 Kudos