Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Failover Engine (FoE) > Blue Screen on Secondary Physical Server Due to Windows Server 2008 R2 SCSI Raid to SAS Raid Cloning

Blue Screen on Secondary Physical Server Due to Windows Server 2008 R2 SCSI Raid to SAS Raid Cloning

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

Views: 58 Votes: 0 Revisions: 7

Overview

Attempting to perform an Install Clone installation on a Windows Server 2008 R2 server that has a SCSI Raid bus and the Secondary/Tertiary server that has a SAS Raid bus results in a failure of the Operating System to properly start. 

Environment

  • FoE all versions

Cause

When Windows Server 2008 R2 starts, it disables services that are not used. Since the backup is taken on a SCSI Raid bus, the SAS Raid services are not started. 

Resolution

Prior to taking the backup of the Primary (SCSI Raid bus) server, edit the registry to enable the SAS Raid services.

 

To enable the SAS Raid services:

  1. Navigate to Start > Run, type Regedit.exe, and click OK.
  2. Navigate to the following registry keys:
    HKLM\SYSTEM\CurrentControlSet\services\LSI_SAS
    HKLM\SYSTEM\CurrentControlSet\services\LSI_SAS2
  3. Change the value of the registry keys from "3" to "0".
  4. Save the changes.
  5. Take the backup of the Primary (SCSI Raid bus) server.
  6. Proceed with the remainder of the installation process.
Last modified

Tags

Classifications

Public