@Zourous Try updating to 1.5.6, it should include the newer init files which I believe should not run into this error, but should be tested of course.
Posts
-
RE: Error on image uploadposted in FOG Problems
-
RE: Bypass DHCP completly?posted in General Problems
@george1421 Can confirm, had to switch to ProxyDHCP after the ISP upgraded the modem that has a buggy DHCP implementation (turning off DHCP makes it not give out IPs but the DHCP server is still running so it just NACKs all the IPs lol)
-
RE: Windows 10 Image Deploying to Automatic Repairposted in Windows Problems
You want to sysprep (with generalize switch) before capture, not after deploy.
If you want clients to get the OOB experience, you can simply go back into audit mode on first boot of windows after deploy, install drivers, etc and sysprep (without generalize switch) to make it ready.
That said, it’s not necessarily what is causing your issues.
-
RE: EFI and Legacyposted in General Problems
@jmeyer Something about an oversized partition? It’s normal, happens regardless of whether you boot EFI or legacy
-
RE: EFI and Legacyposted in General Problems
FOG will detect the imagetype based on what’s on the disk, not what mode the PC is running in. (though mostly it doesn’t care about it anyway)
I personally use the Virtualbox EFI image -> boot legacy PXE to capture method and it works fine.
Just make sure to choose shutdown after complete for your capture task.
-
RE: Error on image uploadposted in FOG Problems
@Sebastian-Roth Perhaps it’s not so much that the USB stick is first, but rather that the command that check the partition flags fails when it’s plugged in for some reason.
Although, I’d have no clue how that would even possible since the parted command explicitly is ran against a single disk, which doesn’t appear to be the USB stick anyway.
And the command shouldn’t fail on it regardless as far as I can tell.
edit: Given the line throwing the error, I can only assume he’s using older init files (since there’s no test command at line 109 at latest)
I can see this line throwing such an error under certain conditions:
if [[ $(parted -l "$hd" | grep boot | awk '{print $1}') -eq $part_number || $(parted -l "$hd" | grep msftres | awk '{print $1}') -eq $part_number || $(parted -l "$hd" | grep hidden | awk '{print $1}') -eq $part_number ]]; thenwhich was changed at https://github.com/FOGProject/fos/commit/693a4f74d81fad5eba09799768c53f25b7c50e3c#diff-9c3fc2c5bb45d13976e29f477b8e67d4
-
RE: Large Image sizesposted in FOG Problems
Are they actually seperate drives or only seperate partitions on the same drive?
-
RE: Error trying to restore GPT partition tables. Exit returned code 4posted in FOG Problems
@Matthieu-Jacquart 1903 is no problem on my end, though I must highlight I’m confused by your partition layout.
On a standard W10 GPT install you’d expect 4 partitions (minimum), and on a standard MBR install you’d expect 2.
What FOG version you on?
-
RE: Error on image uploadposted in FOG Problems
@Sebastian-Roth Good idea in general, though, not entirely sure how to go about that at the moment.
-
RE: FOG Partition Problemposted in FOG Problems
@phil-dosi Sorry, didn’t mean to leave you hanging, but don’t know exactly why this is happening. I can only assume that the resize test failed causing it to think it needed to be captured as is.
-
RE: FOG Partition Problemposted in FOG Problems
@phil-dosi What’s the content of d1.fixed_size_partitions ?
-
RE: Unable to deploy Imageposted in FOG Problems
A lot of these laptops have a “RAID” mode that isn’t really intended for traditional RAID, but rather to enable Intel Rapid Storage caching.
Then again, they’re often set to RAID while not even having a cache SSD to begin with, making it pretty pointless.
-
RE: Connecting FOG to Virtual Machineposted in General Problems
@agray Good shout, I get the same problem on the ICH9 chipset, the PIIX3 one works fine though.
-
RE: Connecting FOG to Virtual Machineposted in General Problems
@agray Just looked at the PCAP.
Your router is also dishing out IPs at 192.168.1.1 which is causing the conflict as suspected.
You can check it out by installing wireshark and typign in
bootpas filterIf you can’t turn off or modify the router DHCP, you will need dnsmasq proxyDHCP on the FOG server.
https://wiki.fogproject.org/wiki/index.php?title=ProxyDHCP_with_dnsmasq
-
RE: Connecting FOG to Virtual Machineposted in General Problems
@agray Yes, and around that same area it is mentioned that there is a DHCP server on the router?
-
RE: Connecting FOG to Virtual Machineposted in General Problems
@agray I’m assuming that if it’s on the domain that there already is a DHCP server on the network and that it is conflicting with the FOG one. Haven’t taken a look at the PCAP (don’t have time), though
-
RE: Connecting FOG to Virtual Machineposted in General Problems
@agray You need to serve the ipxe.pxe file that’s on the FOG server, since it seems to be the DHCP server.
That being said
I can boot VirtualBox 5.2 VMs to IPXE on undionly.kpxe as well as ipxe.pxe just fine.
Do you have the VirtualBox extension pack installed?
-
RE: Connecting FOG to Virtual Machineposted in General Problems
@agray Where did you change these things?
-
RE: Connecting FOG to Virtual Machineposted in General Problems
@agray Well, if I’m following this thread correctly, the IP of the DHCP server initially is the FOG server itself, not the router.
If you can’t change IPXE options on the router and still want to use its DHCP server rather than FOG DHCP, then you have to set up proxyDHCP via dnsmasq on the FOG server (and disable the dhcp server on it)