Ошибка boot failed efi scsi device hyper v 2012

Are you stuck with boot failed EFI SCSI device error in Hyper-V? We can help you fix it.

The common reason for the error is because of the Boot Architecture in Hyper-V

At Bobcares, we often receive requests to fix Hyper V errors as part of Server Management Services.

Today, let’s see how our Support Engineers resolve boot failed EFI SCSI device error.

Cause for boot failed EFI SCSI device in Hyper-V

One of the major causes of the error is that servers are not created using the correct generation.

Microsoft introduced two Hyper-V Boot Architectures setup. One for BIOS and another for UEFI. Generation 1 supports BIOS whereas Generation 2 supports UEFI.

So when creating a server with an older OS version we need to create it in Generation 1 since it is for BIOS-based.

The sample error looks like:

Let’s discuss how our Support Engineers create Generation 1 servers. Also, let’s discuss alternative methods to resolve the error.

How we fix boot failed EFI SCSI device in Hyper-V

Recently one of our customers approached us saying that they were unable to boot the server and were getting this error. Let’s see how our Support Engineers fix it for our customer.

Create a Generation 1 Hyper-V

Now let’s see how our Support Engineers create Generation 1 servers in Hyper-V

1. Open Hyper-V Manager. Click on Hyper-V host and click on Virtual Machine.

2. Now a new window appears and then click Next. Select a location to store the Virtual Machine data.

3. In the Specify Generation, our Engineers select Generation 1 and click Next.

4. In Assign Memory we specify the memory. Now, in Configure Networking we select the Virtual Switch.

5. Then in Connect Virtual Hard disk, we select the required option and click Next.

6. Now the summary displays. We verify the details and finally, we click Finish.

Disable Secure boot

Another workaround to resolve the error without changing the Generation is to disable secure boot. Let’s discuss how our Support Engineers disable secure boot for a VM.

Initially, we open Hyper-V Manager. We select the virtual machine. Right-click on the VM and click on the setting.

Then we click on the Security tab. Uncheck Enable Secure Boot.

Thus it resolved the error when loading the Virtual Machine.

Booting from a DVD drive

Another reason for the error to occur is when trying to load from the DVD drive. Let’s discuss how our Support Engineers change the boot order to resolve the error.

So when ISO is mounted as a DVD drive we need to change the boot order at the startup.

To change it we right-click on the VM and select properties. We select the Firmware tab.

Then we move the DVD Drive to the top of the list. Thus starting the VM the OS loaded without any issue.

[Need assistance to fix Hyper-V error? – We can help you fix it]

Conclusion

In short, we have discussed the causes of the error boot failed EFI SCSI device. Also, we have discussed how our Support Engineers resolves the error for our customers.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

I’ve installed Windows 2012 server on a few Hyper-V images in the past but ran into an error that looked unfamiliar. I created my Hyper-V machine, configured it with a dynamic hard drive, added a DVD and mounted the Windows Server 2012 ISO making sure the DVD drive was top of the boot order and started it up.

I was then presented with a black screen an the error message:

Boot Failed. EFI SCSI Device.

Here’s the long winded explanation from the Senior Program Manager of the Hyper-V team (John Howard).

The short answer: It’s because the virtual machine was created as a Generation 2 machine rather than Generation 1.

To get past this error simply hold down a key as you start up the virtual machine. You’ll notice at the top of the error screen it says “Press any key to boot from CD or DVD…..” the issue is that it doesn’t wait for you to press a key, just make sure you have a key held down when it gets to this point and you should see the Windows Boot Manager prompt allowing you to boot to the DVD image.

Then hey presto you’ll get a successful boot to DVD and the Windows Setup window you expected.

Hello guys,

Here is an issue that I am trying to resolve: After crashing of Hyper-V Host, I have successfully restored 2 out of 3 VMs, by using their VHD files stored in a different location. 

Unfortunately, the 3rd VM ( the most important) is failing with the «Boot Failed. EFI SCSI Device» error. 

This particular VM is a Generation-2 with 11 snapshots which are still available, and I did not take the precaution to export the VMs and I don’t have any sort of backup in place either. Hyper-V is running on Windows Server 2012 R2.

Looking at the Boot settings under Firmware, I can see that the required *.efi file is missing which explains the error.

Any help to overcome this situation or at least recover the data on that VM would be greatly appreciated.