@gn_ro Hi and thanks,

You have solve my problem, disk was already in thick mode but i change the NIC and capture going to the end.

So thanks again, have a good day.

@tom-elliott yes, Zm9nOnBhc3N3b3Jk (default fog:password), as you can see on screenshot. I’m also create new user, enable API for him and get same result.

And same result with curl:

[root@ ~]# curl -H 'fog-api-token: <token>' -u fog:password -X GET http://<fog-ip>/fog/system/status [root@ ~]# curl -H 'fog-api-token: <token>' -H 'Authorization: Basic Zm9nOnBhc3N3b3Jk' -X GET http://<fog-ip>/fog/system/status [root@ ~]# curl -H 'fog-api-token: <token>' -H 'fog-user-token: <token>' -X GET http://<fog-ip>/fog/system/status **success**

Only auth with two tokens work fine.

Hi Sebastian,

I want to say thank you for all your assistance. You changes hit the nail right on the head. Thank you very much.

Kind regards
Duane

@nasmod OK we have a bit of confusion in your post. We actually have 2 linux machines in this picture. The first is the FOG server.
The second is FOS Linux running on the target computer. The target computer gets its network settings from YOUR network not the FOG server. So its IP address is assigned by the DHCP server. Now if FOG is your dhcp server for this target computer we can talk. If its your enterprise dhcp server doing this then you need to talk to your enterprise group.

The order the dns entries are added are also part of the dhcp server settings. FOS Linux is only adding them in the order they are defined in your dhcp server.

I don’t want you to think I’m saying its not a FOG issue as a matter of deflection, but in this case your infrastructure is telling the FOS Linux about the network, not the fog server.

You made reference to the resolv.conf file, that is on the FOG server. Changing that order or name servers will only impact the ability for the FOG server to look up and ping the target computers, when referenced by name. It will not have an impact on the target computer at all.

@brakcounty said in Imaging from large drive to small drive:

I am assuming that this would have to be done for each image.

Correct.

my dir listing works but when i click the kickstart file, it doesnt ask me to download it, where as it should instead of just viewing me the contents of it

is it ok to add this line in my httpd.conf as i know @george1421 advised against it

<Directory /var/www/html/listing>
Options +Indexes
</Directory>

@Patrix While you might have the same issue it could be a totally different problem as well. We just don’t know enough of you specs to tell yet.

So if you want help I ask you to open your very own topic and post all the information of you setup:

FOG version Init version Linux OS and version of your FOG server OS installed on the host you want to capture/deploy contents of d1.minimum.partitions of the particular image you want to deploy to a smaller size disk

@george1421 Thank you for the clarification. This is duly noted. Appreciate the help, you saved my ass today basically.

@mperriello ok so you are using the post init script to update the unattend.xml file with the system name? I’m trying to understand where its falling down. In the link I provided you there should be a section of the code that calls.

${postdownpath}fog.updateunattend

That line is commented out in the tutorial. Remove the hashtag from in front of that line and it should update your unattend.xml file. You may need to update the code if your unattend.xml file is not found in the standard location.

@tesparza You will need to do a Full Host Registration when you do the network boot.

@dmcadams Sorry for the late reply but I’ve had too much on my table this week and couldn’t find the time to think through this again.

Great you tested different kernels and found one working fine. Short answer is, name this kernel binary different to the default Kernel naming theme, e.g. bzImage-4.19.6 or whatever suites you and set this name as Host Kernel in each host’s settings having this issue. Make sure you update the general kernel to the latest via FOG settings again so all your other machines will use the new one.

The longer answer is: With that new information I don’t think it’s a temperature issue really. Sounds like this kicks in with a certain Kernel version probably because it has some new driver or feature added that is causing this. Often some new features (e.g. NVMe optimization or so) are implemented differently by various vendors. While drives from vendor A might go with it just fine some other vendor uses a different code in its firmware causing a problem in the Linux kernel.

If you are really keen we can go and test each kernel version one by one to find what’s causing it and possibly find a solution (special kernel parameter or a patch for the code). Though this will need work and time. I can give you many hints and instructions but it’s your call to work on it. Compiling kernel after kernel (very easy to do) and testing each while keeping close track of the results to find it. It really needs determination to stick with it. But you will learn a lot I am sure.

@epatterson Any changes made to the Synology or FOG server configuration? Why should it work in the morning and error out later if nothing was changed?

Maybe restart first the Synology and test, then the FOG server and test again.

@tom-elliott
Thank you, will do it that way.

@jim-holcomb Was an upgrade recently done?

@tom-elliott Ahhh, thank you. Yes, that seemed to be my problem. Can that be sent along with the API request, out of curiosity?

@george1421 - Wow I am still amazed at how powerful this gem is! Thanks so much!!

@yoshideoeuf said in UEFI can't PXE boot:

it’s /24 for both

So do you have a dhcp helper service enabled on the router between .2.x and .3.x subnets?

Do you have the dhcp option 66 and 67 filled out for both subnets?

@thecount1829 Well I don’t see this as a total waste of time. Mainly because you now know more than you did this AM. You also learned how to debug pxe booting issues. Knowing where to look is the key.

As I tell the youngins I mentor, “If it would have worked the first time, what would you have learned?”. Its all good here. In the end you solved the problem and can keep moving with your project. Well done!!

issue was with the actual ISO and is now resolved!

With easy mode vmware must tailor the VM config to match the settings on the install ISO. I have vmware workstation 15 on my office computer I’ll have to see if there is a way to tweak the VM this way.

@ricardomartins For updating to dev-branch you don’t need to reinstall. Just follow theses steps:

sudo -i git clone https://github.com/FOGproject/fogproject/ cd fogproject git checkout dev-branch cd bin ./installfog.sh

Here is the fix:
Try every boot file until you find the right one for you.

This is what I did as I ran out of options and it turned out to be good. Follow this tutorial: https://wiki.fogproject.org/wiki/index.php/Using_FOG_with_an_unmodifiable_DHCP_server/_Using_FOG_with_no_DHCP_server under DNSMASQ settings for iPXE