VMware Cloud Community
GreenfieldIT
Contributor
Contributor
Jump to solution

Problem with virtual drive boot order on ESX 3.0.2 guest.

I had an issue during a host shutdown in my HA cluster. A Win2k3 vm failed to abort a vmotion migration and went orphaned. When I recreated it and attached the system and data drives, I added the smaller one first, thinking it was the system drive. It turned out to be the latter. Anyway, the result was, that the guest was trying to boot off the data drive. I tried to delete them and re-add them, but the only way I was able to get the VM to boot was to remove the data drive, wait until the VM was booting into windows and add the data drive later. I then had to rediscover in disk manager before the server would function properly.

I suppose if this wasn't a critical box, I would have been better just blowing away the virtual machine and starting over, but I was under a time restraint. Is there a simple way to rectify this, or do I need to rebuild it?

Reply
0 Kudos
1 Solution

Accepted Solutions
Natsidan
Enthusiast
Enthusiast
Jump to solution

You can edit the disk properties of the VM itself click on the disk and choose the scsi id disk order.

View solution in original post

Reply
0 Kudos
2 Replies
Natsidan
Enthusiast
Enthusiast
Jump to solution

You can edit the disk properties of the VM itself click on the disk and choose the scsi id disk order.

Reply
0 Kudos
GreenfieldIT
Contributor
Contributor
Jump to solution

Thank you Natsidan,

That was a big fat Duhh! If the choice was any more obvious I would have tripped over it and broken something.

Cheers!

Reply
0 Kudos