RESOLVED! I downloaded George1421’s file (fos-usb_03-20-18.img) and modified the grub.cfg file to point to my fog server IP. Burned to usb with Rufus and it WORKED! Works on both my late 2013’s and my mid-2015’s. Thank you all for your suggestions and guidance. This has been an ongoing project for me for months.
Posts made by rboan
-
RE: Mid-2015 Macbook Pros will NOT Pxe boot to FOG server
-
RE: Mid-2015 Macbook Pros will NOT Pxe boot to FOG server
@george1421
I would absolutely appreciate some guidance. Thank you. This has been a daily thorn in my side. -
RE: Mid-2015 Macbook Pros will NOT Pxe boot to FOG server
I started working through the steps in this troubleshooting guide (http://ipxe.org/dev/driver) and finally had some kind of break through. Not sure what to do with it but some headway, nonetheless. I get the typical errors on trying to grab dhcp for net0 and net1. Then I can hit ‘s’ to go to ipxe command prompt. Once I am there, I unplug and reinsert the usb dongle. Ifstat shows me that it is now net2 (net0 is gone). I can now run dhcp net2 and I get an IP immediately. I can then go to chain http://x.x.x.x/fog/service/ipxe/boot.php and it brings up my fog menu. I am unable to do much in here because it goes through the process of loading the menu item (ie. Quick registration) and then it errors out. But this is progress. Doesn’t appear to be a driver issue. Thoughts?
-
RE: Mid-2015 Macbook Pros will NOT Pxe boot to FOG server
I am running OS X El Capitan Version 10.11.6. Not an upgrade, it came pre-installed with this version. The unit is brand new out of the box.
-
RE: Mid-2015 Macbook Pros will NOT Pxe boot to FOG server
Thank you for this suggestion. I think I already tried this but I am going to give it another try. I will update soon.
-
RE: Mid-2015 Macbook Pros will NOT Pxe boot to FOG server
No internal ethernet adapter. I have both an external Apple ethernet to usb adapter (model A1277) and an external Apple ethernet to thunderbolt adapter. The latter does not boot at all. The usb one is the one I am using.
-
Mid-2015 Macbook Pros will NOT Pxe boot to FOG server
I have successfully setup and deployed Fog Imaging server for my Windows laptops and servers, and my Ubuntu laptops and servers, but I cannot get a working usb pxe boot solution for my mid-2015 Macbook Pros. The standard ipxe.efi file from pxe.org works fine on any Macbook earlier (I am using two versions of late-2013 models) but I get the following error for mid-2015’s:
Configuring (net0 08:6d:41:e6:d4:de) …NO configuration methods succeeded (http://ipxe.org/040ee186)
Could not open net1: Input/Output error (http://ipxe.org/1d6a4698)Appears to be a dhcp timeout issue. Not enough of a delay before it loads the driver.
If I go to the pxe prompt,
ifstat: tells me net0 link is up but (closed) and there are txe and rxe errors. Also using NIII have tried multiple .efi files and none of them work. I have also tried to install the file created by Tomsealy here (https://github.com/FOGProject/mac-boot) but no luck. Just spins for days.
-
RE: Unable to UEFI boot to Fog Server
We have tried the options outlined in the suggested link but we are running Windows Server 2008 DHCP so, according to the document, “Nobody in the FOG Community has succeeded with this as of yet.”
With that said, I was able to get the HP 640G3 and 840 G3/4 laptops to boot UEFI and Hyper-V Gen 2 to the Fog Server on a 2008 DHCP Server to Capture an Image, but it errors out when I try to Deploy an image after booting to the Fog Menu. Attached is the error that we are getting.
-
Could not boot image : Exec format error (2e008001); Could not open net1: Input/output error (1d6a4698)
I am struggling to get my Mac machine to boot to my Fog Server. My Windows machines boot without issue. The error occurs right after the machine is assigned an IP address and it reads the undionly.kpxe file. My Windows server is my DHCP server.
-
RE: Image file does not "expand" the full size of the drive it is being deployed to
I booted in debug mode and ran the command fdisk -l /dev/nvme0n1
Below are screenshots of output
![1_1506439862790_2.jpg](Uploading 100%) ![0_1506439862789_1.jpg](Uploading 100%) -
RE: Image file does not "expand" the full size of the drive it is being deployed to
for clarification, I chose “Single disk - resizable”
-
RE: Image file does not "expand" the full size of the drive it is being deployed to
I am running Fog version 1.4.4 on Ubuntu 16.04
My original image capture was configured for Single partition- resizable and it creates an image file the size of the data (e.g. 22Gb) which is ideal.
However this image, when deployed to a smaller hdd system, only creates the primary OS partition as the size of the data (22 Gb) and leaves the rest of the drive as unallocated space in disk manager
-
Image file does not "expand" the full size of the drive it is being deployed to
I am creating a Win10 universal image for the 3 laptop models at work. I created the original Master image on a drive that has 3 partitions:
(1- system reserved 500Mb)
(2- boot OS partition 500Gb)
(3- Recovery partition 4.65Gb)I chose the first option for type --> Single partition/single drive so it was expandable --> image file size approx. 22 Gb
When I deployed this image to a second laptop with original 3 partitions:
(1- system reserved 500Mb)
(2- boot OS partition 220Gb)
(3- Recovery partition 4.65Gb)The resulting drive size for the Boot OS partition is whatever the size of the image was (22 Gb is this case)
I see the rest of the drive in Device Manager as ~200 Gb UNALLOCATED
If I choose to capture my image on Laptop A (bigger hdd) as a Multi-partition Single Disk, I get a 500 Gb size image file and then it cannot deploy to my smaller drive (220Gb ) on Laptop B
If I choose to capture my image on Laptop B (smaller hdd) as a Multi-partition Single Disk, I get a 220 Gb size image file, it will deploy to Laptop A, HOWEVER, the Boot OS drive shows up as the size of the image file (220 Gb) and the rest is UNALLOCATED in Device Manager.
WHAT AM I DOING WRONG???
I want to image either/or as a, capturing all 3 partitions, creating an image file that is only the size of the actual data (22 Gb) and deploy it to other laptops that will have drive sizes from 200 Gb to 2 Tb - and show up as whatever size partitions it has expanded to 100%.
Is this possible?