@sebastian-roth
yes thank’you. i found where i can create group and i put version of kernel, it’s perfect.
George give to me howto compiling kernel to fog, but I would like to have your method please 😉
Cheers

Just heard back from our Cali, Columbia office. All is well, device imaged fine with no errors. Thanks again for the awesome support!

@sebastian-roth Well there is some news. So today some others computer who worked before make the same bug, some i relaunch the fog installer. On this computer thats work i havent found the time to test with the first computers so i let you know. But i don’t understand why it work this time and it doesn’t last time.

Thanks for you help

@mechalas Please run ls -al /var/www /var/www/html and post output here. Mind the spaces in the command mentioned.

@sebastian-roth Correct, expect this time I am not importing the DB from my old fog server, new server, new images, new everything. I will open a new topic specific to the HP Probook 430 MAC Address Passthrough issues.

Thanks Sebastian for your help, I appreciate every you do for the FOG Community.

Mike

@Pilar Your upload of the picture didn’t go all the way to the end. If I had to guess I would think that you receive this kind of error: https://forums.fogproject.org/topic/13628/ftp-issue-when-pulling-an-image

Just follow George’s tutorial on how to fix this.

By the way: Here in the forums we try to keep issues separated to help other people follow and better understand it. So please don’t jump from one issue to the next in this one topic. Open a fresh new topic for each and every issue you have and we’ll answer every single one of them.

@george1421 said to @eliaspereira in Error on Start from hard disk (HD):

I see you change the exit mode to Grub. That will work too, but I’m surprised that grub works when SANBOOT didn’t

I find this a bit strange too but well you never know. Hardware can be a real pain and is doing weird things across the board. So I guess there is some hardware out that not able to chainload the OS via EXIT or SANBOOT but is happy with the GRUB method…

@Gameman @george1421 The wording (“bug”) kept me from looking at this for a while now. Found a bit of time to look into this and I think it’s not a bug really. When editing an image definition there is no drop down for “Storage Group” but a whole new settings tab for this (right of “General”). Here you all should be able to assign images to different storage groups as you wish.

Though I have to admit that it might be a bit of a challenge to find this. Not sure why it was designed like this in 1.5.x.

@maddyred You might want to take a look at this topic: https://forums.fogproject.org/topic/15848/api-creating-host

@maddyred Finally found some time to look into this. Not sure where you got some of data field names from. You better take a look at the code. Here you find the reference to the fields used for images: https://github.com/FOGProject/fogproject/blob/dev-branch/packages/web/lib/fog/image.class.php#L35

Just below that your also find the defintion of databaseFieldsRequired (for images) - you need at least those four to be able to create an image defintion: name, path, imageTypeID, osID

Here is an example with some more fields that worked on my tests:

... data = { "name": "fogsvos", "description": "API created image", "path": "/images/fogsvos", "imageTypeID": 1, # Single Disk - Resizable "imagePartitionTypeID": 1, # Everything "osID": 50, # Linux "format": "5", # Partclone Zstd "protected": 0, "compress": 9, "isEnabled": 1, "toReplicate": 1, } ...

@hernani First I would recommend that you update your version of FOG. you are on 1.5.9RC2. I would at least go to 1.5.9 or even better once at 1.5.9 switch to the dev-branch and move up to 1.5.9.111.

If you use the git method to install FOG then just switch to the /root/fogproject directory and do a git pull command then switch to the bin directory and rerun the installer ./installfog.sh script again.

After that if you want to upgrade to the dev-branch you can issue these commands.

cd /root/fogproject git checkout dev-branch git pull cd bin ./installfog.sh

That might not take care of this issue, but at lest if you are on the latest release the devs can help you.

Typically when we see this problem at the end of capture with an ftp error message its because someone changed the fogproject linux user account or password. The memory exhaustion issue might be addressed in the update. I know I’ve seen this error before quite a while ago.

Resolved by running the command udp-sender start then i restarted the Fog machine as ubuntu

@tesparza Its good we can point our finger at low memory as the problem. The small cache space on 4GB is only left 800MB of room so mysql had to commit everything to disk instead of caching it for later. (speculation) I did find it surprising that in the previous top screen shot, you had 4GB of swap space but none was used even when the system was low on ram. It wouldn’t have really helped in your case, but I find it strange that no swap space was used.

Now that you found an acceptable level you can start decreasing your fog client check in time till you find a happy balance between speed and frequency. The only issue I can think of by keeping the check in time to 5 minutes would be during post imaging if the fog client was used to rename the system, connect to AD, or do a scheduled reboot. Its possible the client computer wouldn’t react to the command for about 5 minutes.

@electronico_nc Well lets start off by saying this. FOG Images have 2 parts. There are the raw files that are stored in the /images directory and the meta data that is stored in the database. You have the raw files so rebuilding the data will take some work, good guessing, and a bit of luck.

Just recreate your image definitions by hand as you did in the beginning. Be sure to name them exactly what they were before. In the example above the image name and directory name is almost always the same. So name this image win7_64 (watch your case). Fill out the rest of the settings as you would normally do. One could guess that this image is a windows 7 so you will need to select that in the OS field. If you did not name all of them as clearly, be a good guesser to see what OS it is. The compression values are only used on image capture so you should just guess what you might have used. Just do this for each directory in the /images folder.

The only (not a gotcha, but something to be aware of) is that on the image list view the image size will be zero. This is because the image size is set at capture time only. Since you are side loading these images that field will be zero until you recapture the image.

@madeyem Thanks heaps for testing again and letting me know! As well thanks for your patience.

@btoffolon The fog-client (FOGService) is run as local SYSTEM account.

Sorry guys, the issue was that this particular unit had 2 hard drives, so selecting single disk was the issue.

All good now.

@michaeloberg said in Issues with USB Type C NIC Adaptors:

@kghli @george1421 @Sebastian-Roth

This could be a breakthrough. I just noticed that the system is passing the address through iPXE correctly and that FOG is what is recognizing the USB Type-C dongle’s MAC address - the exact scenario that @kghli is experiencing. I took a screen shot of the issue and here is the iPXE address (which is the correct system address):

3e42e174-18f4-40d4-80a0-22714580ef00-image.png

Then when I boot to FOG (now running Debian 10.11 and FOG 1.5.9, and choose “Client System Information” then choose “Display MAC Address” it show’s the USB Dongle’s MAC:

e70169a5-6a1d-4983-be3c-9d9a7dea4c9e-image.png

Hopefully this is going to help troubleshoot our issues as we have narrowed it down to FOG alone, not the manufacture of the system, the BIOS configuration or the version of FOG.

Thanks in advanced!

Mike

I also recompiled iPXE from (g4bd0) to (g1844a) and verified the date (ls -la /tftpboot/*.efi) was today and it still is not working.

@george1421 I pulled the latest build of Ipxe and the build number did update and had a different build number but it still did the same thing.

I’ve reimaged using deploy image about 5 times now and it consistently works now go figure!

Luckily in my environment we don’t have any old computers, this moving forward will be the lowest spec machine we will have.

One other thing that was strange was when doing a full registration of the host and I was asked would I like to deploy an image if I said yes it accepted my username and password using Ipxe.

Thanks for explaining why Ipxe was picked as a default efi image too. I just wonder how many others will be affected by this change in firmware by HP and what it is changing in the NIC!

David