I ran into an issue while doing some tests at night for changing SCSI controllers on a virtual machine and thought this might be a common problem for others in the field so I hope this post will help anyone who may run into this problem.
Problem
You’ve added an additional drive by performing the following steps:
You’ve intentionally chosen SCSI (1:0) for Virtual Device Node because you would like a new SCSI controller created:
Now when you boot the virtual machine, it appears as if you have no hard drive attached:
Solution
The problem is because the BIOS’ boot order now has the boot order with the new empty drive ahead of the original disk in the priority. I believe this may happen regardless of whether you’ve chosen a different or the same SCSI controller.
To rectify this, reset the virtual machine and boot into the BIOS:
Note: Don’t worry about the primary master being empty. That doesn’t have anything to do with the hard drive to be booted.
Navigate to the Boot section in the BIOS, expand the Hard Drive list and you’ll now see the boot order of devices:
You will now immediately notice that the boot order has Bootable Add-in Cards and the new hard drive on SCSI (1:0) on the top (priority is top to bottom) which would explain why you’re not able to boot into the OS anymore. All you need to do now is to use the + and - buttons to change the priority of the devices you can boot from:
Once you’ve changed the boot order, save the changes and reboot:
With the devices in the proper boot order, you’ll be able to get back into the OS now:
1 comment:
Thank you Boss ..
Post a Comment