Developers

@FuriousGamer065 said in FOG Failing to Capture and Deploy image.:

I am using a Storage Node on a 1TB drive on the Fog Server.

Can you please explain this a bit more? Is this drive within your master FOG server? Wow exactly was it setup? We need more details. Run lsblk and mount, post output here. As well take a picture of the settings in the Web UI.

As a quick fix you can manually move the captured image from /images/dev/00:16:d4:90:ca:f0/ to /images/Win7MasterNoIEv1/

About the FTP error you want to read this: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_FTP

@Sebastian-Roth if my memory serves correctly, GUI watcher was a part of the now very old client

@weite Ok, seems like we are stuck at the same point as in the other topic. Can you do the the debugging on iPXE as well? Take a clear screenshot of the output on screen and post here.

Possibly the installer doesn’t handle pining to a HTTPS server directly. Not sure at the moment.

@Schuede said in Xps15 Fail to deploy image - Ipxe / Uefi:

listen-address=127.0.0.1

Why listen to localhost only?

You need to decide if you want your router to serve PXE booting information to your clients or if dnsmasq should be doing it. Using both might cause some trouble.

@ty900000 I will have a bit more time next week. Will see what I can do.

@Daniel-Miller Nice catch!!

@lebrun78 Are you sure this is working fine for you with 0.11.16 version?

@ismith-hpu Did you get to fully test the was I proposed? Would be interesting to see if that does it.

@george1421 Yeah seems like we have another slow disk issue model here. Good to know the kernel parameter did help in this case.

@darkxeno About all the other pre partclone (blue screen) issues on bootup. Those have nothing to do with the slowness issue but have different causes. Nie as we see you made you made it past that point several times I am wondering if it’s some network/DHCP issue that happens not always but only sometimes?? Maybe you have a rough DHCP in your network?

@IdahoTech First check the DB actually runs: systemctl status mysql

Post output here.