@jemerson93 unable to find image store means fos cannot see your image files anywhere. Do they exist? If you have other nodes, do those nodes also have the image?

@geekjosh Then for safety in the future:

Please run:

mv /var/www/fog{,_backupold}
ln -s /var/www/html/fog /var/www/fog

@geekjosh It is reading it from that location. Now there is a possibility that you have two separate installs of fog going on your machine, this happens from time to time.

Try:

cp /var/www/{fog,html/fog}/service/ipxe/refind.conf

Then try booting your machine.

@george1421 On the wiki page, that’s the storvsc portion of the additional patches.

For understanding,

If the page size is 4096, it’s supposed to do stuff. However, not all disks use a 4096 page size. This is noticed particularly when initializing/erasing mbr/gpt structures on a disk. It’s just strange, to me, that it only seems to be impacting Windows based installs. At least from what I’ve seen.

I’m hoping you guys get this figured out. Sorry been distant for the last couple weeks. Just started a new position so not a lot of time right now during the day.

Of note, Linux kernel is now in the 4.18 series. I’m going to be building a new kernel relatively shortly, just need time (probably this weekend.)

@george1421 Would you mind building a plain jane 4.18 based on the TomElliott.config? Don’t forget to do the patches:

https://wiki.fogproject.org/wiki/index.php?title=Build_TomElliott_Kernel#Additional_Patches

In particular the patches for:
mmc (The path used to be mmc/card/ is now mmc/core/) and scsi/storvsc (this is whats supposed to help with the mbr/gpt erasing issue).

I believe the e1000 patch was already fixed in 4.17 so we shouldn’t need to do anything, but you can open the and check.

Sorry I can’t be more useful right now.

Either way, awesome work guys.

What’s your machine’s timestamp compared to an atomic clock?

Atomic clock can be found here: https://www.time.gov/

Of course your timezone will adjust slightly, but the main point is you cannot be more or less than 5 minutes of the atomic clocks (typically) as that will cause the SSL cert to be invalidated (hence the ssl error you’re seeing.) Of course there could be many other reasons to what’s causing this, but I would recommend checking the time first as its the simplest course of action.

Is our postdownload telling the machine to reboot? Possibly there’s an error occurring during Post download?

As @george1421 suggested, please watch the machine. Maybe grab a slo-mo video of the tail end of the partclone screen until the machine reboots?

Exit type possibly?

In FOG you can set exit per host, and globally.

The defaults are:

BIOS Boot: SANBOOT
UEFI Boot: EXIT

The global settings are found in FOG Configuration Page->FOG Settings->Boot Settings.

If you set a specific host with defined exit types, that will override the Global for that host. Hopefully that helps.

@andrewg78 it’s because of the huge history. There is no fixing that can cure it beyond cleaning it out. With 1.6, however, it will be somewhat alleviated to the use of proper sql pagination. This isn’t a leak persay, it just can’t store the amount of information in the memory space.

@mpatel the second question doesn’t do anything anymore. It is from before the fos system was able to grab dns from dhcp.

The first question is only needed if you’re using fog for dhcp, so no is the correct answer.