Posts made by greichelt

All,

I have been happily using FOG for about a year now with the legacy boot options. We just got some new Dell notebooks in that are UEFI only (Latitude 5500). All I had to do was change the boot file section on my SonicWALL to read “ipxe.efi” and my Dell laptops now boot to UEFI PXE without issue. I am having 2 problems. The first problem may be due to my unattend.xml or a Windows update issue in the image as I am getting the never-ending spinning dots at the “Just a Moment” blue screen. The second problem is all 3 notebook models I have tested (Latitude 5500, Latitude E5450, and Latitude 7212 Rugged) halt after the Partclone imaging process with the following message displayed on the screen:

In Progress * Rebooting system as task is complete
reboot: Restarting system

At first I though the “Just a Moment” hang problem I was having on the new 5500 was being caused by this refusal to reboot, like some of the imaging process was not quite done; however, when I imaged the 7212 I had no issues outside of it hanging with the same message after the Partclone imaging process. Maybe I’m just being impatient; I let the workstation sit at the Restarting system message for about 15 minutes before force reboot (FYI, after forcing reboot, the system does boot; however, the SetupComplete.cmd looks like it didn’t run i.e. device manager is a mess as if the drivers did not get installed, some applications I install with SetupComplete.cmd are not installed, etc.)

I am currently treating the “Just a Moment” issue as a problem with my unattend or Windows update problem as the 7212 system I was able to successfully image did not have this problem (it uses a more up to date golden image and unattend file). I have only mentioned it to be thorough. Here are some server version and some setting that may be pertinent. If you need anything else, please let me know.

Fog 1.5.7
Kernel 4.19.48 (also tried 4.19.64 and had the same issue)
ACPI=off
Boot File is ipxe.efi

@Tom-Elliott and @george1421

That did it. All drivers have installed successfully. Have a good day, all!

@Tom-Elliott and @george1421

SUCCESS!!! Thank you both so very much! Drivers are pulling now. Hopefully, I have everything else right. I’ll let you know if I have any further issues.

@Tom-Elliott

LoL, thanks! I’m hoping that is what my issue is. I extracted the Dell .cab file and left the directory structure in place. Hopefully changing Win10 to win10 does it for me.

@george1421

I updated the code snippet as you suggested and get the same error in the screenshot below. The one thing I did notice is that the capitalization of the W in the screenshot error is different than the W in the path in the file system. Being new to Linux, I am not sure if that matters when calling a network path, so I changed the path from “/images/drivers/Latitude 5491/Win10” to “/images/drivers/Latitude 5491/win10” and am testing again.

@george1421

Thank you this will save me some time today. In my previous post I had mentioned that my driver injection was working flawlessly. I hadn’t realized it at the time, but I had followed your post to get the driver injection working on my OptiPlex 3060 (https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed). I just finished imaging my Latitude 5491 and found that no drivers were installed despite adding them to the /images/drivers folder. The path I have is /images/drivers/Latitude 5491. I left the space in because I didn’t quite understand what this part of your post meant, “note that the space has been removed for “Optiplex 7040” to this Optiplex7040. There is a clean up line above that removes spaces in the product name.” Does the clean up line mean I should leave the space in the path (/images/drivers/Latitude 5491) or remove it (/images/drivers/Latitude5491)?

@Sebastian-Roth and @george1421

Thank you both for your replies. Sebastian, I tried the variable acpi=off using Kernel 4.15.2 x64 and it worked flawlessly. I did get an error that the HDD was not found, but a change in the BIOS from RAID to AHCI resolved the issue; after the next PXE boot, imaging kicked right off.

George1421, if I get time today, I will upgrade to Kernel 4.18.11 x64, use the acpi=off arg and see if the GPT/MBR issue is resolved for me.

This post can be marked as resolved!

I’ve just started using FOG last week and am new to Linux as well. I setup an Ubuntu 16.04 LTS server and FOG 1.5.4. The setup was pretty painless following the various forums and in a few days I had a Windows 10 1803 image built, sysprepped with an unattend.xml file and deployed successfully to 30 Dell OptiPlex 3060 workstations. I even setup the driver injection and it worked flawlessly. I decided to attempt to image 5 Dell Latitude 5491 laptops and ran into my first issue. I was able to PXE boot and get the PXE menu. I selected the image option to image the laptop and got the errors that are in the attached image. I’ve googled the various errors and found nothing relevant to FOG. I tried using various kernels (I had downgraded to 4.15.2 x64 because it was taking 15 minutes to wipe GPT/MBR) from 4.15.2 all the way up to 4.18.3; the error messages changed, but the behavior was the same. The system would not boot past the errors shown in the attached image. I’m not sure where to go from here. Any assistance would be greatly appreciated!