forum.opsi.org

Verfasst: **19 Apr 2016, 13:22**

Hello,

Today I bought a new Dell Precision T7510 shipped with SSD disk and I'm trying to deploy Windows 7 x64 with OPSI.

I needed to use opsisetuplib.py from win7-x64_4.0.6.2-3.opsi to detect /dev/nvme* disks.
But, later I got this error during begin of WinPE (step when startned.cmd is invoked) :

Code: Alles auswählen

the system cannot find the drive specified

I try to list disk with diskpart.exe but it shows nothing. list vol report nothing too.
Just to clarify my setup, I've rebuild my WinPE from scratch including latest WinPE Driver 3.0 from Dell but still same error at the same stage.
I also try to select different BIOS options : None | AHCI | Raid on. but no success without any mode.

If someone has an idea...
Thank you.

Info :

Code: Alles auswählen

# dpkg -l|grep opsi
ii  opsi-atftpd                                     0.7.dfsg-5                        amd64        advanced TFTP server - opsi version with pcre, fifo and max-blksize patches
ii  opsi-configed                                   4.0.6.3.5.1-2                     all          OPSI config editor
ii  opsi-depotserver                                4.0.6.4-2                         all          opsi depotserver configuration package
ii  opsi-linux-bootimage                            20160322-1                        amd64        opsi bootimage for netboot tasks.
ii  opsi-utils                                      4.0.6.9-1                         all          utilites for working with opsi.
ii  opsiconfd                                       4.0.6.11-2                        all          opsi configuration service
ii  opsipxeconfd                                    4.0.5.5-2                         all          opsi pxe configuration daemon
ii  python-opsi                                     4.0.6.34-1                        all          opsi python library

Verfasst: **19 Apr 2016, 16:24**

Just for clarification. Neither startnet.cmd nor the spawned work.cmd deals with the local disk.

The output 'the system cannot find the drive specified' you are seeing comes from a failed net use command, I'd say.
This in turn leads me to the assumption that you are not only missing the proper hard disk controller drivers but the network drivers, too.

On what ADK is your WinPE based? Are the Dell WinPE 3.0 drivers compatible with this version?
Have you tried the 'normal' drivers?
(I recall, back when I was young, struggling with the little bastards called Dell PE drivers. They didn't work at all. But that were server machines.)

Verfasst: **19 Apr 2016, 17:20**

I followed 4.3.6 chapter of the OPSI doc and using Windows AIK (link in the doc) on a fresh windows 7 x64 machine.
In addition to the WinPE 3.0 drivers I added my specific model drivers (http://en.community.dell.com/techcenter ... river-pack) but still same behavior.
I just added the network and storage directories to boot.wim.

You are right about network drivers. An ipconfig in the PE environnement shows nothing...
How can I check if the drivers are really present in boot.wim ? And how to do to verify if they are loaded in the PE environment ?

Verfasst: **19 Apr 2016, 17:32**

I tried to download and extract only the network driver (http://www.dell.com/support/home/fr/fr/ ... 72/drivers).
Then copy it on a USB stick and use command

Code: Alles auswählen

drvload E1C62x64.inf E1D62x64.inf E1R62x64.inf

Few seconds later everything seems to be loaded but an ipconfig still show nothing. Tried unplugged/plugg the cable too..

How is it suppose to work ?

Verfasst: **19 Apr 2016, 17:43**

I found an excellent documentation here : http://support.rm.com/TechnicalArticle. ... TEC1287003
After using this command :

Code: Alles auswählen

netcfg -winpe

An IP is assigned !

What's next ?

Verfasst: **19 Apr 2016, 18:37**

I checked and the network drivers are present in the WinPE environnement in the target machine directory :

Code: Alles auswählen

X:\winpe\mount\Windows\System32\DriverStore\FileRepository\e1d62x64.inf_amd64_neutral_0337bad15cc7c5d9

Don't know why they are not automatically loaded

Verfasst: **19 Apr 2016, 18:57**

I see that the correct driver is been added to a file named work.cmd :

Code: Alles auswählen

# grep work.cmd /var/log/opsi/bootimage/ivsfrlt-d52rp72.ivsdomain.fr.log 
[5] [Apr 19 12:47:18] Creating work.cmd (setup.py|769)
 (setup.py|799)47:23] Adding to work.cmd: drvload c:\drv\64\E1D62x64.inf
[6] [Apr 19 12:47:23] Executing: /bin/cat '/mnt/hd/opsi/work.cmd' (Posix.py|763)
 (Posix.py|840)47:23] >>> copy c:\opsi\work.cmd x:\work.cmd >nul
[7] [Apr 19 12:47:23] >>> x:\work.cmd (Posix.py|840)

But work.cmd is not present on the target computer. Maybe this is the real problem.

Verfasst: **20 Apr 2016, 13:04**

Hi,

you can try to extend the winPE. Only copying is not the key, you have to extend the PE with dism, if you want to add your drivers in PE. Then you must try to find PE-drivers. Normal Windows drivers are not all PE-Compatible, because many of them works after an Reboot properly, and in an PE-Environment this is really bad.

Here are documented, how you extend your PE:

http://download.uib.de/opsi4.0/doc/html ... ckages-nt6

Verfasst: **20 Apr 2016, 14:28**

Back to square one.
Build a clean WinPE according to the documentation.
Note the type of NIC and HD Controller of your machine. (OPSI hardware inventory should help.)
Get the WinPE 3.0 drivers from here: http://en.community.dell.com/techcenter ... /wiki/2069
Find the matching drivers for your NIC and HD Controller. Mind the architecture. x86 drivers might work in a x64 WinPE, but chances are they don't.
Clean up DISM.log (Rename c:\windows\logs\DISM\dism.log)
Add the drivers to your WinPE (dism /add-driver).
Check for any errors on the console.
Finalize your WinPE.
Check dism.log for any warnings/errors.
Give it a try.

Notes:
'Adding to work.cmd: drvload c:\drv\64\E1D62x64.inf'
This means that you are having drivers in the drivers folder of your netboot product.
Mixing a 'patched' WinPE and the OPSI mechanism for driver integration might work, but may lead to problems.

'But work.cmd is not present on the target computer'
work.cmd does not reside inside the Linux boot image. It will be created from within the boot image and written to the WinPE partition of the machine you are installing.
And if you receive the error 'the system cannot find the drive specified' it is there. Because the net use command is started from work.cmd.

Verfasst: **20 Apr 2016, 22:32**

I would recommend building a win10 or win81 based winpe along the new package

opsi-winpe

http://download.uib.de/opsi4.0/products ... 1.0-1.opsi on a client see

http://download.uib.de/opsi4.0/doc/html ... ckages-nt6

regards,
Bardo Wolf

forum.opsi.org

WINPE : the system cannot find the drive specified

WINPE : the system cannot find the drive specified

Re: WINPE : the system cannot find the drive specified

Re: WINPE : the system cannot find the drive specified

Re: WINPE : the system cannot find the drive specified

Re: WINPE : the system cannot find the drive specified

Re: WINPE : the system cannot find the drive specified

Re: WINPE : the system cannot find the drive specified

Re: WINPE : the system cannot find the drive specified

Re: WINPE : the system cannot find the drive specified

Re: WINPE : the system cannot find the drive specified