topic Re: Inaccessible_Boot_Device When Deploying SysPrep Image to a Server with a Different HAL in ProLiant Deployment and Provisioning

Inaccessible_Boot_Device When Deploying SysPrep Image to a Server with a Different HAL

MIke Repine — Sat, 26 Jun 2004 19:13:14 GMT

I've created a Win2k SysPrep image that I would like to use on various platforms for DR purposes. When I deployed this image to a server with a different HAL, during NT Detect I received a Stop error stating Inaccessible_Boot_Device. I'm sure it's a problem with the Windows Mass Storage SCSI device driver since the platforms are different. Is there anyway way to resolve this issue? Can I add the storage driver files to the $OEM$ SCSI directory to fix the problem? Any assistance would be greatly appreciated.

Re: Inaccessible_Boot_Device When Deploying SysPrep Image to a Server with a Different HAL

Robert Hearn — Mon, 28 Jun 2004 08:06:45 GMT

You can add the files, but you'll also have to update the TXTSETUP.OEM file there, as well as the SYSPREP.INF to point to those drivers.

However, if you're landing this image to a system with a different HAL, you may be unable to get it to run anyway. Sysprep docs say the HALs must be compatible. THe only allowable HAL changes are to move from MP to UP or back.

Robert Hearn