/build/static/layout/Breadcrumb_cap_w.png

Systems Deployment Question


Image load issue and RAID driver

07/13/2020 100 views

Good day.

Running in to an issue where the RAID driver does not seem to load to the computer.  This cause the OS not to boot.

The image is a tried and true setup and imaged to same unit model.  Some reason the image will load to the computer and says its done.  After reboot it cant seem to boot due to missing disk.

The computer unit is setup with a RAID set and Dell validated the configuration is set right and pointed to missing RAID driver.  Support had me test using OEM media boot flash driver and manually install the RAID driver.

This works 1st try.  This point me to the image.  In our log on K2000 it says everything went OK.  PreBoot driver inventory verifies the right driver is included. 

The only part I can't validate is if the RAID driver actually made it to the computer itself.  K2000 does not provide details on this.

Thanks

4 Comments   [ + ] Show comments

Comments

  • Still an issue after referring Nick's info. But here is what I found.
    The unit is Dell Precision 7920 using Avago MegaRAID 9460-16i.
    DISM log tells no useful info.
    2020-07-13 22:04:37, Info DISM PID=512 TID=724 Scratch directory set to 'X:\windows\TEMP\'. - CDISMManager::put_ScratchDir
    2020-07-13 22:04:37, Info DISM PID=512 TID=724 DismCore.dll version: 10.0.16299.15 - CDISMManager::FinalConstruct
    2020-07-13 22:04:37, Info DISM Initialized Panther logging at C:\dismlog.txt
    2020-07-13 22:04:37, Info DISM PID=512 TID=724 Successfully loaded the ImageSession at "X:\windows\system32\Dism" - CDISMManager::LoadLocalImageSession
    2020-07-13 22:04:37, Info DISM Initialized Panther logging at C:\dismlog.txt
    2020-07-13 22:04:37, Info DISM DISM Provider Store: PID=512 TID=724 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2020-07-13 22:04:37, Info DISM DISM Provider Store: PID=512 TID=724 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2020-07-13 22:04:37, Info DISM DISM Provider Store: PID=512 TID=724 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2020-07-13 22:04:37, Info DISM Initialized Panther logging at C:\dismlog.txt
    2020-07-13 22:04:37, Info DISM DISM Manager: PID=512 TID=724 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
    2020-07-13 22:04:37, Info DISM DISM.EXE:
    2020-07-13 22:04:37, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
    2020-07-13 22:04:37, Info DISM DISM.EXE:
    2020-07-13 22:04:37, Info DISM DISM.EXE: Host machine information: OS Version=10.0.16299, Running architecture=amd64, Number of processors=6
    2020-07-13 22:04:37, Info DISM DISM.EXE: Dism.exe version: 10.0.16299.15
    2020-07-13 22:04:37, Info DISM DISM.EXE: Executing command line: "X:\windows\system32\dism.exe" /apply-image /imagefile:y:\wim\183\C_C.wim /index:1 /ApplyDir:C: /logpath:C:\dismlog.txt
    2020-07-13 22:04:37, Info DISM DISM Provider Store: PID=512 TID=724 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
    2020-07-13 22:04:37, Info DISM DISM Provider Store: PID=512 TID=724 Connecting to the provider located at X:\windows\system32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2020-07-13 22:04:37, Warning DISM DISM Provider Store: PID=512 TID=724 Failed to load the provider: X:\windows\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2020-07-13 22:04:37, Info DISM DISM Provider Store: PID=512 TID=724 Connecting to the provider located at X:\windows\system32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2020-07-13 22:04:37, Info DISM DISM Provider Store: PID=512 TID=724 Connecting to the provider located at X:\windows\system32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2020-07-13 22:04:37, Info DISM DISM Provider Store: PID=512 TID=724 Connecting to the provider located at X:\windows\system32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2020-07-13 22:04:37, Info DISM DISM Provider Store: PID=512 TID=724 Connecting to the provider located at X:\windows\system32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2020-07-13 22:04:37, Info DISM DISM Provider Store: PID=512 TID=724 Connecting to the provider located at X:\windows\system32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2020-07-13 22:04:37, Warning DISM DISM Provider Store: PID=512 TID=724 Failed to load the provider: X:\windows\system32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2020-07-13 22:04:37, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2020-07-13 22:04:37, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2020-07-13 22:04:37, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager
    2020-07-13 22:04:37, Info DISM DISM.EXE: Attempting to add the commands from provider: FfuManager
    2020-07-13 22:04:37, Info DISM DISM.EXE: Succesfully registered commands for the provider: FfuManager.
    2020-07-13 22:04:37, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager
    2020-07-13 22:04:37, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager.
    2020-07-13 22:04:37, Info DISM DISM.EXE: Attempting to add the commands from provider: VHDManager
    2020-07-13 22:04:37, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
    2020-07-13 22:04:37, Info DISM DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
    2020-07-13 22:04:37, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
    2020-07-13 22:04:37, Info DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
    2020-07-13 22:08:36, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
    2020-07-13 22:08:36, Info DISM DISM.EXE:
    2020-07-13 22:08:36, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
    2020-07-13 22:08:36, Info DISM DISM.EXE:
    2020-07-13 22:08:36, Info DISM DISM Provider Store: PID=512 TID=724 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2020-07-13 22:08:36, Info DISM DISM Provider Store: PID=512 TID=724 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
    2020-07-13 22:08:36, Info DISM DISM Provider Store: PID=512 TID=724 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider
    2020-07-13 22:08:36, Info DISM DISM Provider Store: PID=512 TID=724 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
    2020-07-13 22:08:36, Info DISM DISM Provider Store: PID=512 TID=724 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
    2020-07-13 22:08:36, Info DISM DISM Provider Store: PID=512 TID=724 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
    2020-07-13 22:08:36, Info DISM DISM Provider Store: PID=512 TID=724 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
    2020-07-13 22:08:36, Info DISM DISM Provider Store: PID=512 TID=724 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider
    2020-07-13 22:08:36, Info DISM PID=2276 TID=2236 Scratch directory set to 'X:\windows\TEMP\'. - CDISMManager::put_ScratchDir
    2020-07-13 22:08:36, Info DISM PID=2276 TID=2236 DismCore.dll version: 10.0.16299.15 - CDISMManager::FinalConstruct
    2020-07-13 22:08:36, Info DISM Initialized Panther logging at C:\dismlog.txt
    2020-07-13 22:08:36, Info DISM PID=2276 TID=2236 Successfully loaded the ImageSession at "X:\windows\system32\Dism" - CDISMManager::LoadLocalImageSession
    2020-07-13 22:08:36, Info DISM Initialized Panther logging at C:\dismlog.txt
    2020-07-13 22:08:36, Info DISM DISM Provider Store: PID=2276 TID=2236 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger
    2020-07-13 22:08:36, Info DISM DISM Provider Store: PID=2276 TID=2236 Failed to get and initialize the PE Provider. Continuing by assuming that it is not a WinPE image. - CDISMProviderStore::Final_OnConnect
    2020-07-13 22:08:36, Info DISM DISM Provider Store: PID=2276 TID=2236 Finished initializing the Provider Map. - CDISMProviderStore::Final_OnConnect
    2020-07-13 22:08:36, Info DISM Initialized Panther logging at C:\dismlog.txt
    2020-07-13 22:08:36, Info DISM DISM Manager: PID=2276 TID=2236 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession
    2020-07-13 22:08:36, Info DISM DISM.EXE:
    2020-07-13 22:08:36, Info DISM DISM.EXE: <----- Starting Dism.exe session ----->
    2020-07-13 22:08:36, Info DISM DISM.EXE:
    2020-07-13 22:08:36, Info DISM DISM.EXE: Host machine information: OS Version=10.0.16299, Running architecture=amd64, Number of processors=6
    2020-07-13 22:08:36, Info DISM DISM.EXE: Dism.exe version: 10.0.16299.15
    2020-07-13 22:08:36, Info DISM DISM.EXE: Executing command line: "X:\windows\system32\dism.exe" /apply-image /imagefile:y:\wim\119\S_S.wim /index:1 /ApplyDir:S: /logpath:C:\dismlog.txt
    2020-07-13 22:08:36, Info DISM DISM Provider Store: PID=2276 TID=2236 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection
    2020-07-13 22:08:36, Info DISM DISM Provider Store: PID=2276 TID=2236 Connecting to the provider located at X:\windows\system32\Dism\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2020-07-13 22:08:36, Warning DISM DISM Provider Store: PID=2276 TID=2236 Failed to load the provider: X:\windows\system32\Dism\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2020-07-13 22:08:36, Info DISM DISM Provider Store: PID=2276 TID=2236 Connecting to the provider located at X:\windows\system32\Dism\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2020-07-13 22:08:36, Info DISM DISM Provider Store: PID=2276 TID=2236 Connecting to the provider located at X:\windows\system32\Dism\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2020-07-13 22:08:36, Info DISM DISM Provider Store: PID=2276 TID=2236 Connecting to the provider located at X:\windows\system32\Dism\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2020-07-13 22:08:36, Info DISM DISM Provider Store: PID=2276 TID=2236 Connecting to the provider located at X:\windows\system32\Dism\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2020-07-13 22:08:36, Info DISM DISM Provider Store: PID=2276 TID=2236 Connecting to the provider located at X:\windows\system32\Dism\CompatProvider.dll. - CDISMProviderStore::Internal_LoadProvider
    2020-07-13 22:08:36, Warning DISM DISM Provider Store: PID=2276 TID=2236 Failed to load the provider: X:\windows\system32\Dism\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e)
    2020-07-13 22:08:36, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table.
    2020-07-13 22:08:36, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider
    2020-07-13 22:08:36, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager
    2020-07-13 22:08:36, Info DISM DISM.EXE: Attempting to add the commands from provider: FfuManager
    2020-07-13 22:08:36, Info DISM DISM.EXE: Succesfully registered commands for the provider: FfuManager.
    2020-07-13 22:08:36, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager
    2020-07-13 22:08:36, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager.
    2020-07-13 22:08:36, Info DISM DISM.EXE: Attempting to add the commands from provider: VHDManager
    2020-07-13 22:08:36, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericImagingManager
    2020-07-13 22:08:36, Info DISM DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager.
    2020-07-13 22:08:36, Info DISM DISM.EXE: Attempting to add the commands from provider: Compatibility Manager
    2020-07-13 22:08:36, Info DISM DISM.EXE: Succesfully registered commands for the provider: Compatibility Manager.
    [2276] [0x80070001] EnableShortnamesOnApplyTarget:(565): Incorrect function.
    [2276] [0x80070001] WIMSetFileShortName:(662): Incorrect function.
    [2276] [0x8144012d]
    2020-07-13 22:08:37, Warning DISM DISM WIM Provider: PID=2276 [MarkImage:(992) -> Failed to mark image for wimboot state.] (null) (HRESULT=0x0) - CWimManager::WimProviderMsgLogCallback
    [2276] [0x8144012d]
    2020-07-13 22:08:37, Warning DISM DISM WIM Provider: PID=2276 [MarkImage:(1001) -> Failed to mark image for compact state.] (null) (HRESULT=0x0) - CWimManager::WimProviderMsgLogCallback
    2020-07-13 22:08:37, Info DISM DISM.EXE: Image session has been closed. Reboot required=no.
    2020-07-13 22:08:37, Info DISM DISM.EXE:
    2020-07-13 22:08:37, Info DISM DISM.EXE: <----- Ending Dism.exe session ----->
    2020-07-13 22:08:37, Info DISM DISM.EXE:
    2020-07-13 22:08:37, Info DISM DISM Provider Store: PID=2276 TID=2236 Found the OSServices. Waiting to finalize it until all other providers are unloaded. - CDISMProviderStore::Final_OnDisconnect
    2020-07-13 22:08:37, Info DISM DISM Provider Store: PID=2276 TID=2236 Disconnecting Provider: FolderManager - CDISMProviderStore::Internal_DisconnectProvider
    2020-07-13 22:08:37, Info DISM DISM Provider Store: PID=2276 TID=2236 Disconnecting Provider: FfuManager - CDISMProviderStore::Internal_DisconnectProvider
    2020-07-13 22:08:37, Info DISM DISM Provider Store: PID=2276 TID=2236 Disconnecting Provider: WimManager - CDISMProviderStore::Internal_DisconnectProvider
    2020-07-13 22:08:37, Info DISM DISM Provider Store: PID=2276 TID=2236 Disconnecting Provider: VHDManager - CDISMProviderStore::Internal_DisconnectProvider
    2020-07-13 22:08:37, Info DISM DISM Provider Store: PID=2276 TID=2236 Disconnecting Provider: GenericImagingManager - CDISMProviderStore::Internal_DisconnectProvider
    2020-07-13 22:08:37, Info DISM DISM Provider Store: PID=2276 TID=2236 Disconnecting Provider: Compatibility Manager - CDISMProviderStore::Internal_DisconnectProvider
    2020-07-13 22:08:37, Info DISM DISM Provider Store: PID=2276 TID=2236 Releasing the local reference to DISMLogger. Stop logging. - CDISMProviderStore::Internal_DisconnectProvider

    AHCI mode does not allow to boot to Windows.
    Driver used is current.
    BIOS and RAID firmware current
  • OK, make sure this is the DISM.log from C:\Windows\dism.log and Not the one from C:\windows\logs\dism\ .

    If this si truly the one inside C:\Windows\ folder, then I see the SDA is NOT injecting drivers.

    1- The System Image is not Sysprepped (the SDA only injects drivers to sysprepped Images OR Scripted Installations) - I would try with a basic scripted installation, and then compare the DISM.log.

    2- The Drivers are downloaded to a wrong folder.
    When I searched for 7920, I get two models from the Library's Driver feed.

    Precision Precision 7920 Rack
    Precision Precision 7920 Tower

    Could specify which one is that?

    Also generate a log from driver feed discovert tool.
    1- Go to your SDA Samba Share, drivers post install folder
    \\SDA-ip\drivers_postinstall

    There is a folder named "feed_tools", copy that folder from there into the Desktop of one of those Precision 7920.

    Open that folder, inside Run a VBS file named "driver_feed_discovery_tool.vbs"
    Wait a few seconds, and Click OK to all Messages (two or three).
    Now a new LOG\TXT file should be present inside that folder.

    Copy the contents of that file here. (I'm looking to determine what is the path inside drivers_postinstall where the SDA is expecting the drivers to be placed).
  • Copied the driver to Precision Precision 7920 Tower
    Feed tools:

    ** 7/15/2020 3:40:24 AM
    Computer Name : MININT-OQA4OQ8
    Manufacturer reported by WMI : >Dell Inc.<
    Manufacturer expected by Driver Feed : >dell<
    Model reported by WMI : >precision 7920 tower<
    Model expected by Driver Feed : >precision 7920 tower<
    OS : Microsoft _x64
    Path : dell\Microsoft _x64\precision 7920 tower
    NOTE: Manufacturer and Model strings shown between > and < markers
  • Go to Settings > Appliance Maintenance click Recache all Drivers.

    Wait for that to finish.

    Make sure those drivers are stored in your SDA Samba Share at:
    \\SDA-IP\drivers_postinstall\dell\windows_10_x64\precision 7920 tower\

    They all should be there.

    Next, if this is a System Image deployment, make sure it says Sysprep YES, if it's says Sysprep NO, no drivers will be injected.
    In the same System Image Detail page, make sure you have checked the option to use the driver feeds.

    Try to image again, and pull the DISM log from C:\Windows\dism.log
    • Thanks for all your tips but KACE support was able to resolve the issue today.
      The Driver Feed was corrupt and it was updated to A10. Plus the driver path got reset to incorrect path. This was corrected. This finally fixed the image.

All Answers

0

The SDA (formerly known as K2000), does NOT install drivers, it injects the drivers into the C:\  system drive before Windows starts(before the first reboot), and when Windows loads up the first time, it uses\install those drivers.
When this is happening on the KBE you should see the drivers being injected in a CMD Window.... this process could take 10 seconds up to 2 minutes..

DISM is the tool used to inject the drivers, your Windows OS will have a DISM.log, showing ALL DRIVERS that were injected into the OS and Who (the IP address and source folder).

I recommend you boot back to the KBE, open CMD from Troubelshooting Tools, get the dism.log from c:\windows\dism.log  and it should be there.

(Not the one from c\windows\logs\dism\dism.log).

The KACE SDA is not thorwing any errors, because is 
1- formatting the drive
2- applying the image
3- injecting all the drivers

4- rebooting the device 

^^IF all of these steps are performed just fine, then no error will be logged, the KACE SDA is just waiting for Windows load back to the Windows Desktop to proceed with Post Install tasks (if any if present).

I would not be the first time of a manufacturer issue with the driver pack itself.

See:
https://www.dell.com/community/Precision-Fixed-Workstations/Deploying-to-Precision-5820-Tower/td-p/5735889

https://www.reddit.com/r/sysadmin/comments/8z72t1/dell_precision_5820_tower_nvme_deployment_offline/

Specially if it's still the A00 or A01 version of a driver pack.

You haven't mention the model....

Also some devices are UEFI Only, because of the CPU, if you are using Intel CPUs and these are new models. DO NOT Image in Legacy, as the BIOS won't recognize any boot sectors.

See:
https://www.dell.com/support/article/en-pa/sln301692/no-boot-device-found-when-you-change-the-boot-sequence-to-legacy-mode?lang=en

NOTE: If you already tried to use AHCI instead of RAID mode in the BIOS Storage settings, and if you're not getting a BSOD or something more Windows related, I DO NOT think this is a drivers issue... I mean the OS is not even booting.... I'm sure drivers have not been "summoned" yet.
This is somewhere between the BIOS settings and the CPU being unable to locate a compatible boot sector. (Make sure BIOS is up to date, and make sure you're truly booting in UEFI mode when imaging).
Have you tried using another device (same model) and test the same process?, Wouldn't be the first time I had to RMA a brand new device because of some odd issues.

Answered 07/14/2020 by: Channeler
Red Belt

  • This content is currently hidden from public view.
    Reason: Removed by member request For more information, visit our FAQ's.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ