Quantcast
Channel: Symantec Connect - Deployment Solution - Discussions
Viewing all articles
Browse latest Browse all 1130

DS 7.5 megasas2 storage adapter driver validation error

$
0
0
I need a solution

I ran into an issue after migrating to DS 7.5 with the LSI MegaRaid Storage adapter driver 'megasas2' at the end of a Windows 2K8 R2 SOI.  I cannot get this driver to work in DS 7.5, has anyone else had an issue with this driver or a similar storage driver?

Info:

-DS 7.5 HF4

-Driver megasas2

-Driver added to PXE Database

-Driver added to DeployAnywhere Database

-x64 preboot environment (tried a PXE only and a PXE and Automation preboot configuration) - both same result

-Windows SOI starts, Windows expands and starts to install, at the very end of the SOI when Windows is "Completing Installation" it fails with error "Windows installation cannot continue because a required driver could not be installed".

Attached some logs and error screencap.  I've had a case open for well over a month and it is being escalated to dev support.  was just curious if anyone else had this issue or if it is something simple I am just missing...

Drivers are detected in the initial DriversDB scan and are located in the M:\DS_SOI\Symantec\Deployment\DRIVERS and in the M:\DS_SOI\Symantec\Deployment\DriversDB directories in the preboot prior to the windows install.

Attached cbs_unattend.log - Lines 234-267 - Drivers imported

Attached setupact.log - Lines 1475-1484 - Windows setup Failed to inject driver

Attached setuperr.log - Lines 1-2 - Same error as in setupact.log

 

Any help is appreciated, Our 7.1 environment had a hard fault which forced us to 7.5 (or rebuild 7.1), we choose to move to 7.5 and need this working as our admins are building any computers that use this MSM Raid adapter manually by DVD/USB driver import.  I've tried just about everything i can think of from, trying the USB 3.0 workaround in the driversDB, to a CopyFile task to re-copy the files right before the SOI starts, to not using a drivers database and copying all the required drivers to the locations noted in the log files, to playing with the bypass driver validation.  This is the same driver the Admins are using on the USB stick and the same driver installed on ~100+ computers already in production. 

 

 

 


Viewing all articles
Browse latest Browse all 1130

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>