/build/static/layout/Breadcrumb_cap_w.png

KBE10 x64 unable to "see" hard drive

I am trying to build a new KBE for Windows 10 to use with Lenovo X1 Carbon Gen 5 and Lenovo M800. When I boot off the new KBE and attempt to capture image the Image Source field is empty. I assume it is an issue of missing drivers for the hard drives. I have run the Driver Feed Builder and added some of the drivers to the KBE. I must be missing the correct drivers or some simple step. Also, I am re-caching drivers before building the KBE. I have version 3.7.120345 server.

5 Comments   [ + ] Show comments
  • Download the latest WINPE10 driver pack from Quest. You might also have to change the BIOS setting for the hard drive controller from RAID to AHCI. - flip1001 7 years ago
  • Thanks for your reply flip1001. I have done both those things. Could it be that the server needs to be updated? - rrichter@sog.unc.edu 7 years ago
  • Are you booting to a UEFI KBE? That model looks to come with a PCIe SSD which will give you problems if not booting via UEFI. - Desktop Jockey 7 years ago
  • Hummm could be an unpartitioned hard drive... to make sure, go to Recovery Tools, CMD, and type DISKPART, do a LIST DISK and see if you HDD is there... If it is, do a LIST VOL.

    Also, I would like to know what folders do you have in your \\K2000\drivers\kbe_x64\ folder?
    There make sure you ONLY have the Network and the Storage folders from the PE10 driver pack.

    If not then re-arrange, recache all drivers and try to build a new KBE - Channeler 7 years ago
  • Thanks to the last two posters. I will try those two things and let you know. - rrichter@sog.unc.edu 7 years ago

Answers (1)

Posted by: Nico_K 7 years ago
Red Belt
1
this looks like a driver is missing.

The first step would be:
Build a new KBE with the latest driver pack:
https://support.quest.com/kb/124396
If this does not help you need to inject the correct driver (the X1 uses a bunch of possible drives, NVMe (which is not an issue with W10), normal SSD (also no issue by default) and OPAL2 devices over NVMe which may be an issue without the correct driver.


Comments:
  • Sorry for the delayed response. I added what I believe are the correct Samsung NVMe drivers and the KBE boot stops right when the blue Windows icon appears. - rrichter@sog.unc.edu 7 years ago

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