SIRIS, ALTO, and NAS: 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.
  • If the problem persists, boot the machine into safe mode with or without networking and then reboot normally. If successful, reboot normally once more to confirm.
  • If the above steps are unsuccessful, follow the steps listed for your hypervisor below.

On VMware hypervisors

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.

4. In the registry, highlight HKEY_LOCAL_MACHINE.

5. Click File Load Hive.

6. In the window that opens, select the virtual machine's OS (or C:) volume, then navigate to the following file and select it:

\Windows\System32\config\system.

7. You'll be prompted to name the loaded hive. In this example, we name it fix.

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

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

10. In the registry window, Highlight the following key:

HKEY\LOCAL_MACHINE\fix

Then select FileUnload Hive to unload the hive.

11. Exit regedit.

12. Reboot the VM.

On Hyper-V hypervisors

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

In the Registry hive, the vmbus START key and the LSI keys must be set to 0 to allow bootability.

1. Open regedit.

2. In the registry, highlight HKEY_LOCAL_MACHINE.

3. Click FileLoad Hive.

4. In the window that opens, select the virtual machine's OS (or C:) volume, then navigate to the following file and select it:

\Windows\System32\config\system.

5. It will ask you for a name to use for the loaded hive. For this example, name it as: 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.

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.

10. Make sure the following keys also have start values set to 0:

Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\LSI_SAS
Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\LSI_SAS2i
Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\LSI_SAS3i
Computer\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\LSI_SSS

11. In the registry window, Highlight the following key:

HKEY\LOCAL_MACHINE\fix

Then select FileUnload Hive to unload the hive.

12. Exit regedit.

13. Right-click the C.vhdx virtual disk under This PC or My Computer and choose Eject.

14. Reboot the VM.

If the issue persists, contact Datto Technical Support.


Was this article helpful?

2 out of 2 found this helpful

You must sign in before voting on this article.

Want to talk about it? Have a feature request?

Head on over to our Datto Community Forum or the Datto Community Online.

For more Business Management resources, see the Datto RMM Online Help and the Autotask PSA Online Help .

Still have questions? Get live help.

Datto Homepage