Submit a ticketCall us

Solarwinds & Cisco Live! Barcelona
Join us from the 29th of January to the 2nd of February at Cisco Live 2018 in Barcelona, where we will continue to show how monitoring the network with SolarWinds will keep you ahead of the game. At our booth (WEP 1A), we will demonstrate how SolarWinds network solutions can help. As a bonus, we are also hosting a pre-event webinar - Blame the Network, Hybrid IT Edition with our SolarWinds Head Geek™, Patrick Hubbard on January 24th - GMT (UTC+0): 10:00 a.m. to 11:00 a.m. There's still time to RSVP.

Home > Success Center > Failover Engine (FoE) > System Crash (Stop Error) 0x7B, Inaccessible Boot Device on Windows Server 2008

System Crash (Stop Error) 0x7B, Inaccessible Boot Device on Windows Server 2008

Created by Justin Wyllys, last modified by MindTouch on Jun 23, 2016

Views: 981 Votes: 0 Revisions: 8

Overview

This article describes how to troubleshoot System Crash (Stop Error) 0x7B, Inaccessible Boot Device errors on Windows Server 2008 and 2008 R2 and when installing Neverfail Heartbeat on Windows Server 2008 and 2008 R2 with different disks.

 

When Neverfail Heartbeat restarts following a restore on the Secondary (or Tertiary) server, the server stops with the following error message:

System Crash (Stop Error) 0x7B, Inaccessible Boot Device

Environment

  • FoE all versions
  • Windows Server 2008 and 2008 R2

Cause

This error occurs when the system disks on the Primary and the Secondary (or Tertiary) servers have different disk/RAID controllers.

Resolution

To recover from the error, perform the following steps:

  1. Reinstall the operating system on the Secondary (or Tertiary) server.
  2. Run msinfo32.exe on both servers and:
    a. Expand the Components node and the Storage node.
    b. Select the IDE and\or SCSI node depending on the type of disk controllers in use.
    c. Make a note of the disk controllers' names (for example, viaide.sysintelide.syspciide.sys, or cercsr6.sys).
  3. On the Secondary (or Tertiary) server, navigate to Start > Run, enter Regedit.exe and click OK.
  4. Navigate to HKLM\System\CurrentControlSet\Control\BackupRestore\KeysNotToRestore.
  5. Create a Multi-String Value and assign a name (for example, Disks Controllers).
  6. Add all of the Primary server's disk controller's information in the Secondary (or Tertiary) exclusion multi-string value created using the following syntax:
    CurrentControlSet\Services\<DriverNameWithoutExtension>\
  7. Enter each driver on a separate line as shown in the following example of the viaide.sys and intelide.sys drivers:
    CurrentControlSet\Services\viaide\
    
    CurrentControlSet\Services\intelide\
  8. Proceed to install FoE on the Secondary (or Tertiary) server using the default procedure.
Last modified

Tags

Classifications

Public