Posts made by theland10

@Sebastian-Roth Intel Core i5-7260U @ 2.2GHz * -shrugs- *

@Sebastian-Roth Yes, see my reply @george1421. Switching to Zstd I was able to successfully capture the image but it took much longer than when I had partclone gzip selected (~1hr 15min). When I attempted to deploy the image after capture I encountered an error and it did not deploy correctly. I changed to partclone uncompressed and successfully captured (much quicker this time to capture). I just successfully deployed my first image on another NUC.

Thank you both for all your help on this project. This thing has been a bugger, lol.

@george1421 Ok, bad news and good news. Bad news is, I changed it and stepped through the debug process. It did not throw an error until on partclone and gave basically the same screen as can be seen here:

The good news is, on the image options in fog image management. I changed image manager from partclone Gzip to partclone Zstd and it is currently capturing fingers crossed.

Here is the actual error in partclone when I attempt to capture from the NUC.

@george1421 Ahhh, I see, thank you, I was able to successfully image another device with the FOS USB after queuing the task first in fog.

As for the NUC see below:

@theland10 No luck with the FOS Boot stick. On the NUC7i5 tried to capture and partclone gives an error with the text broken and spread across the screen, part of it says ‘Maybe check the server to make sure space is good to go?’.

Tried imaging one of our other HP models that I have successfully captured and imaged with the regular USB boot media and receive the following error:

Fatal Error: Unknown request type :: null

Kernel Variables and settings:
boot_image=/boot/bzimage loglevel=4 initrd=init.xz root=/dev/ram0 rw ramdisk_size=127000 keymap= web=172.17.65.19/fog/ boottype=usb consoleblank=0 rootfstype=ext4.

Tried with both original bzimage, bzimage32, init.xz,init_32.xz files and files from our fog server.

@george1421 Yes, I got it! I tested and was able to successfully register the device as host with both quick and full registration options. Will test deploy and capture tomorrow. Thank you!

@Sebastian-Roth I was confused about that myself. The 172.17.65.19 is our fog server. 172.17.1.171 is the server for our virtual devices we have set up for PXE booting, and the reason why we are using the USB boot media as opposed to using straight PXE booting for fog. That IP was not entered anywhere in the setup on rom-o-matic for the efi file. I’m going to try a slight change to the script on that.

@Sebastian-Roth Here is the output from the debugger:

Also, our resident linux guru (I’m very much a beginner but I pick up quickly) and myself have been trying to set up the FOS Linux boot stick in the meantime. We are able to get to the selection menu to choose quick register/full register/capture etc. It sees both our DHCP servers and pulls an IP ok but ends with an error unable to access FogserverIP/fog/index.php or FogserverIP/index.php.

@Sebastian-Roth Yes and yes. That ifstat output was directly after ensuring I had link lights from replugging the Lan cable. Which was directly after entering the ipxe menu from a failed boot using the intel.efi

@Sebastian-Roth Gives MAC address on first line:

xx:xx:xx:xx:xx:xx using i319v-4 on 0000:00:1f.6 (closed)
[Link:up, TX:8 TXE:2 RX:0 RXE:0]
[TXE: 2 x “Operation not supported (http://ipxe.org/3c654083)”]

@george1421 Intel l219-V

PCI\VEN_8086&DEV_15D8&SUBSYS_20688086&REV_21
PCI\VEN_8086&DEV_15D8&SUBSYS_20688086
PCI\VEN_8086&DEV_15D8&CC_020000
PCI\VEN_8086&DEV_15D8&CC_0200

@george1421 With default ipxe.efi from server, same issue. Only slight difference is instead of showing ‘no config methods succeeded’ and immediately kicking back to the boot menu it attempts to configure twice then gives option to hit ‘s’ for iPXE shell. Using ‘dhcp’ command gives same output, no configs succeeded.

@george1421 Thanks George, and yes, I have tried both with updated firmware and with a new one, no changes, straight out of the box. Same issue.

It does have a built in wireless card. I just tried disabling in bios and booting from the stick, no luck. I do not think I have tried with the default ipxe.efi from the server.

I have some things to attend to this morning and will update later today.

Thank you.

@Sebastian-Roth I have confirmed our fog setup works with no fuss on NUC5i3 model.

@Sebastian-Roth Yes that is correct, followed the instructions from ‘the harder way’ here. I just tried the snponly.efi and with it booting to UEFI it shows the iPXE menu for a split second and immediately goes back to the boot selection screen. With UEFI off it’s just as before, no boot device found.

I did find the known working device list and systems with known issues list. The NUC7i5BNH model is not on either list. We have some older NUC models I can try but likewise they aren’t on either list. As for other systems this is the same cable/port/switch I have been using for all systems I have captured/imaged.

@Sebastian-Roth UEFI. If I disable UEFI mode and try booting to legacy it doesn’t even try to boot from the USB stick. Just gives error, no operating system found.

Hello, I work with a company managing ~2000 devices. We’re rolling out windows 10 and ran into problems with our current imaging solution not pushing drivers for some AMD systems or Intel NUCs. I found FOG project and we were able to set it up successfully. We already have a linux based virtual pc deployment system set up on our network to PXE boot so we have been using FOG with USB boot media. I used https://rom-o-matic.eu/ to create the EFI file. Have successfully captured and deployed images for multiple HP models (including the AMD systems we had problems with) but have been unable to get our NUCs to boot to fog.

We have the Intel NUC7i5BNH model. It gets to "Configuring net0 macaddress… and times out with error “no config methods succeeded” which only flashes on the screen for a second before it reverts back to the bios boot menu.

Our FOG version is 1.5.6. Any insight is appreciated

Thank you!