Video Screencast Help

Disk Error After Deploying Ghost Hardware Independent Image to Blade BL460c Gen 8

Created: 15 Feb 2013 | 3 comments
mlombardo's picture

We've recently moved our server imaging process to DS 7.1 and Workflow. Our reference images were all built on VMWare servers hosted on an ESX host. The images all deploying and working as expected.  

I am now trying to add Blade servers as an available device to image in our Workflow. So far, I've added the proper preboot drivers and am able to deploy a Ghost image to a Blade BL460c Gen 8 and to work with the machine in automation. However, the Blade fails to properly boot after the image has been deployed. It boots to a 0x0000007b Disk Error/Blue Screen.

From what I've gathered, the most likely culprit here is that the required storage and storage controller drivers are missing from the reference image. As a result, the machine is unable to locate any disks from which to boot. I've tried capturing and injecting the CriticalDeviceDrivers key from a properly functioning Blade (with only an out of box OS image and required 3rd party drivers installed) into the registry of the freshly imaged Blade while in automation, but have not had any luck getting it to boot. My last option is to create Blade images for each production OS that we might use, but I am trying to avoid having more reference images to manage. Has anyone had any luck deploying a hardware independent image that was not created on a Blade to their Blade servers? We're working strictly with Server 2008 images at present.

Thanks!

 

Comments 3 CommentsJump to latest comment

Sachin_Joshi5's picture

Hello,

Have you tried adding critical drivers to DeployAnywhere database & then selecting 'DeployAnywhere' option in deploy image task?

Thanks,
Sachin

mlombardo's picture

Sachin,

 

I've added the drivers to the DeployAnywhere DB. When I run a scan in eval mode, the drivers are not detected. Here's the output.

 

Mike

 

Missing critical driver detected : 

 

type =  NETWORK DEVICE
PCI ID = PCI\VEN_19A2&DEV_0710&SUBSYS_337B103C&REV_01
Desc = @oem5.inf,%pci\ven_19a2&dev_0710&subsys_337b103c.devicedesc%;HP FlexFabric 10Gb 2-port 554FLB Adapter
Inf Source = Windows InfDirectory
Inf File = 
 
Missing critical driver detected : 
type =  NETWORK DEVICE
PCI ID = PCI\VEN_19A2&DEV_0710&SUBSYS_337B103C&REV_01
Desc = @oem5.inf,%pci\ven_19a2&dev_0710&subsys_337b103c.devicedesc%;HP FlexFabric 10Gb 2-port 554FLB Adapter
Inf Source = Windows InfDirectory
Inf File = 
 
Missing critical driver detected : 
type =  NETWORK DEVICE
PCI ID = PCI\VEN_19A2&DEV_0710&SUBSYS_337B103C&REV_01
Desc = @oem5.inf,%pci\ven_19a2&dev_0710&subsys_337b103c.devicedesc%;HP FlexFabric 10Gb 2-port 554FLB Adapter
Inf Source = Windows InfDirectory
Inf File = 
 
Missing critical driver detected : 
type =  NETWORK DEVICE
PCI ID = PCI\VEN_19A2&DEV_0710&SUBSYS_337B103C&REV_01
Desc = @oem5.inf,%pci\ven_19a2&dev_0710&subsys_337b103c.devicedesc%;HP FlexFabric 10Gb 2-port 554FLB Adapter
Inf Source = Windows InfDirectory
Inf File = 
 
Missing critical driver detected : 
type =  NETWORK DEVICE
PCI ID = PCI\VEN_19A2&DEV_0710&SUBSYS_337B103C&REV_01
Desc = @oem5.inf,%pci\ven_19a2&dev_0710&subsys_337b103c.devicedesc%;HP FlexFabric 10Gb 2-port 554FLB Adapter
Inf Source = Windows InfDirectory
Inf File = 
 
Missing critical driver detected : 
type =  NETWORK DEVICE
PCI ID = PCI\VEN_19A2&DEV_0710&SUBSYS_337B103C&REV_01
Desc = @oem5.inf,%pci\ven_19a2&dev_0710&subsys_337b103c.devicedesc%;HP FlexFabric 10Gb 2-port 554FLB Adapter
Inf Source = Windows InfDirectory
Inf File = 
 
Matching critical driver detected : 
type =  STORAGE DEVICE
PCI ID = PCI\VEN_103C&DEV_323B&SUBSYS_3355103C&REV_01
Desc = @system32\drivers\pci.sys,#260;RAID Controller
Inf Source = Windows InfDirectory
Inf File = D:\Windows\inf\hpsamd.inf
 
Matching critical driver detected : 
type =  STORAGE DEVICE
PCI ID = SCSI\Disk&Ven_DGC&Prod_RAID_5
Desc = DGC RAID 5 SCSI Disk Device
Inf Source = Windows InfDirectory
Inf File = D:\Windows\inf\disk.inf
 
Existing Sysprep answer file will be modified if retargeting is performed.
 
 
Warnings exist.
mlombardo's picture

Sachin,

Deploy Anywhere is not an option for us. We're using a custom tokenized sysprep file that contains computer name, domain and OU tokens that are created by our workflow. The last time we tested Deploy Anywhere, we realized that it overwrites our custom sysprep file. Has that been changed?

Thanks,

Mike