@briancurry said in PXE Boot Errors:
Now the endpoint boots to what looks like the FOG imaging menu but then goes away after about 2 seconds.
Can you take a picture of this? Not sure if I follow what you say here. Don’t think I’ve seen this before that the menu goes away after 2 seconds, usually it’s 8 or so by default.
@phishphan said in Issue Imaging HP EliteDesk 800 G3:
I currently have the partition set to Singe Disk - Resizeable but I’ve also tried Multiple Part Single Not Resizeable without any success.
When switching to non-resize, did you re-capture the image from your master machine? You need to!
Your partition layout is preventing FOG from being able to properly resize as the third partitions seems to be the recovery part which we don’t want to move as it could break recovery.
Are you saying that you deploy the image to the very same machine or is it another one from the same model? Compared all BIOS settings? Same BIOS firmware version?
@cjp82placer Possibly some kind of reverse SSL proxy within your network that is intercepting and maybe filtering all HTTPS connections?
@george1421 I am really keen to hear what you did with kernel -300m as this seems to make a difference… right track I suppose. Maybe this is some kind of timeout?!
@rayco said in Customized image of Windows10 1803 RS4, partition resize issue:
I’m traying diferents methods but with unlucky results.
What exactly have you tried and which errors occurred? We can’t help without knowing more details from you.
@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.