Problem with Script Install (OptiPlex 7060 HD SSDR 250, MICRON) ( Resolved )
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
akmagnum
5 years ago
Try this.....
Select disk 0
Clean
Convert gpt
Create partition efi size=200
Assign letter=s
Format quick fs=FAT32
Create partition msr size=128
Create partition primary
Assign letter=c
Format quick fs=NTFS
Exit
Comments:
-
I used this command before, created the partition, and then formatted.
* Creat UEFI Partition -->
Select disk 0
Clean
Convert gpt
Create partition efi size=200
Assign letter=s
Format quick fs=FAT32
Create partition msr size=128
Create partition primary
Assign letter=c
Format quick fs=NTFS
Exit
* Format Partition C: as NTFS --->
format /q /y /s:enable /fs:ntfs c:
But still not work - madro 5 years ago
Posted by:
akmagnum
5 years ago
Please refer to this link and read the article....
https://www.itninja.com/blog/view/bios-uefi-combined-tasks
Look in the comments section ...... particularly the conversation between the users .....
Should solve your problem.
Posted by:
JordanNolan
5 years ago
A couple of things to check:
- Check that the BIOS is setup for UEFI Boot and not Legacy Boot.
- Check if the disk controller is set to the correct style in the BIOS (AHCI or RAID).
- Your KBE may have the driver for the Storage Controller, but your driver feed that loads the driver during setup may not.
Comments:
-
Hi Jordan,
Thank you for you comment,
I've looked at KBE and I have the machine model driver installed, today you know a way I can figure out how I can see if the latest driver for the storage controller is installed?
Thank you - madro 5 years ago-
You should see if you have the drivers downloaded to your Drive Feed in the K2000. I also like to confirm they are their by going to the folder on the K2000 share:
\\k2000\drivers_postinstall\dell\windows_10_x64\7060
You will see a Storage folder under your model. In there should be the drivers for each types of possible storage controller.
If you have an updated driver you can add another folder to the list and extract the driver to the new folder. The driver cannot be in a Setup.exe. It has to be extracted so you can import the inf and sys files.
I would also run the Driver Feed Discovery script in:
\\k2000\drivers_postinstall\feed_tools\driver_feed_discovery_tool.vbs
Because I have seen cases where K2000 did not download the files to the correct or expected path or the BIOS was reporting a slight variation in the model of the computer which threw off the driver import during setup. - JordanNolan 5 years ago-
Hi Jordan,
I checked and the driver is up to date, I think some way the preinstallation is not mounting the disk correctly.
I tried this command to mount partition, but still not work
Select disk 0
Clean
Convert gpt
Create partition efi size=200
Assign letter=s
Format quick fs=FAT32
Create partition msr size=128
Create partition primary
Assign letter=c
Format quick fs=NTFS
Exit - madro 4 years ago
-
Work Now Guys!!
Just you know as the basis of knowledge, we have been able to solve the problem.
We had to another way we started the PXE boot, previously we used the Legacy PXE to install on UEFI machines.
Now we change in the DHCP server to accept boot UEFI mode,
After starting UEFI, the system installed the boot sector correctly.
Thanks - madro 4 years ago
