@tfoote01 I resolved this. after watching the capture it was bad sectors. I was running my fog server on an old windows client. Used a different machine and this worked without issue.
 
Posts
- 
RE: Error Capture imageposted in General
- 
RE: Error Capture imageposted in GeneralI am getting this same error now when trying to capture an image. Sure would be nice to know what I can do to make sure there is 100Gb in a /var location. Instead I will need to now research how to check the logs and make sure the image directory has enough storage. 
- 
RE: Bit of a bugger here. DHCP failing on image capture. Dell Optiplex 9010/9020posted in FOG ProblemsThis can be closed. I switched my switch and this error went away! Different error now but this is gone after HW change. 
- 
Bit of a bugger here. DHCP failing on image capture. Dell Optiplex 9010/9020posted in FOG ProblemsHey all, I have a small isolated test environment set up. I am running Win Server 2016 with AD DS, DHCP, DNS. “Testing.local” is my domain. I have run the gammut with this banging my head. Here is what I have I have a machine running 16.04.01. Fog server 1.4.4. I have the server running no issue, client deployed to my machines. I was getting ACPI errors but updated kernel arguments with noacpi and that took care of the initial errors. But now I am running into :UDHCPC: starting…doing DORA and failing… 
 “No DHCP responses on interface eth0”I have the DHCP server pointing to the fog server: 192.168.1.230(both Ubuntuserver and fogserver have this IP) 
 DHCP server is 192.168.1.5I have made sure resolv.conf points to the DNS server 192.168.1.5, and I looked at the .fogsettings and made sure IP is right and I DO NOT have fog server running DHCP. Maybe I am missing something. Is there a log file I can get somewhere that will tell me why DHCP is failing here. It works fine on the windows side. I am perplexed. 
- 
RE: /Default.ipxe connection timeout on Dell onlyposted in FOG ProblemsNot sure what the fix was, Second DHCP server? I’m running 1.4.4 and getting this same issue but I dont see anywhere what the fix was, 
