Storm season is back, bringing with it the potential for significant weather events. If you have clients in areas prone to infrastructure disruption, visit the Disaster Recovery Resources guide for preparedness information. Datto recommends performing proactive disaster recovery testing to mitigate potential downtime. See our articles about the importance of disaster recovery testing and Preparing For A Cloud Virtualization Test: Policies, Procedures, And Partner Responsibilities to learn more. For live updates, follow @datto on Twitter.

Disaster Recovery: INACCESSIBLE BOOT DEVICE or 0x0000007B STOP error after Image Export

Follow

Issue

A virtual machine created from the image export process boots to an "Inaccessible Boot Device" or "0x0000007B STOP" error screen regardless of the virtual storage controller selected.

Environment

  • Datto ALTO
  • Datto SIRIS
  • VMware
  • Microsoft Hyper-V

Resolution

Attempt to boot the VM using all available virtual storage controllers before following these steps. 
The following instructions apply to VMs running on both VMWare and also Hyper-V.

If the Hypervisor is VMware:

1. Mount a Windows Recovery or install disk using VMware Player.

2. Boot the VM into the recovery environment.

3. At the first screen (Language Selection), type Shift + F10 for a command prompt, then type regedit to open the registry editor.

Alternatively, you can attach the ShadowProtect Recovery Environment ISO to the VM, and use its command line functionality to accomplish this.

4. In the registry, Highlight HKEY_LOCAL_MACHINE.

5. Click File Load Hive.

6. In the virtual machine's registry, expand the following key: HKEY_LOCAL_MACHINE\fix\ControlSet001\Services\intelide.

7. Change the data for the Start value to 0.

If the Hypervisor is Hyper-V:

Right-click the C.vhd or C.vhdx disk image within your datastore, and choose Mount.  Verify that you can navigate to the location of the SYSTEM registry hive: C:\Windows\System32\config\SYSTEM.

Edit the registry hive

1. Open regedit.

2. In the registry, highlight HKEY_LOCAL_MACHINE.

3. Click FileLoad Hive.

4. On the virtual machine's OS (or C:) volume, navigate to the following file: \Windows\System32\config\system.

5. Rename the file. For this example, rename it to fix.

6. In the virtual machine's registry, expand the following key: HKEY_LOCAL_MACHINE\fix\ControlSet001\Services\intelide.

7. Change the data for the Start value to 0.

The following two steps are for Hyper-V only:

8. In the virtual machine's registry, expand the following key: HKEY_LOCAL_MACHINE\fix\ControlSet001\Services\vmbus

9. Change the data for the Start value to 0.

The following steps are for both Hyper-V and VMware

10. In the registry window, Highlight HKEY\LOCAL_MACHINE\fix, Then select File->Unload Hive to unload the hive.

11. Exit regedit.

12. For Hyper-V: right-click the C.vhdx virtual disk under This PC or My Computer and choose Eject.

13. Reboot the VM.

If the issue persists, contact Datto Technical Support.

Additional Resources


Was this article helpful?

0 out of 0 found this helpful

You must sign in before voting on this article.

Want to talk about it? Head on over to our Community Forum!