FOG Problems

• J

  Unable to Image a Lenovo E14 Gen2 (Type 20TA/20TB)
  • JYost

  7
  0
  Votes
  7
  Posts
  23
  Views

  

  @jyost If it does not work, verify that the build number has changed from your previous picture. The build number in the hex code in the square brackets on the ipxe banner page.

  Also if it doesn’t work, try the snponly.efi boot loader instead of ipxe.efi (fog recommended default).

• M

  HP Probook 430 G8 System MAC not passing through USB Type-C Dongle
  • michaeloberg

  23
  0
  Votes
  23
  Posts
  68
  Views

  M

  @george1421 @Sebastian-Roth

  So I disabled the Wi-Fi card in the BIOS:
  
  iPXE still shows the BIOS (System MAC):
  
  FOG still show the Dongle MAC:
  
  So I removed the Wi-Fi Card:
  
  Same thing, here is the MAC on the card and it matches ipconfig in windows:
  
  ipconfig from earlier:
  

• Z

  HP 405 G6 deploy error
  • Zaqen

  20
  0
  Votes
  20
  Posts
  30
  Views

  Z

  @sebastian-roth

  Sebastian, I copied the kernel to the server and start testing this afternoon or tomorrow morning.
  I keep you informed.
  Regards

• S

  SOLVED NBP File Downloaded successfully boot loop
  • sonic136

  8
  0
  Votes
  8
  Posts
  62
  Views

  

  @sonic136 Can you describe what you did to fix the issue rather than just saying solved? I’m still “coming back” but I think a more descript message of what you did to fix the issue can help others more readily too.

• B

  Permission denied on boot.php
  • btoffolon

  8
  0
  Votes
  8
  Posts
  32
  Views

  B

  @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

• M

  Can't update FOG kernels
  • mechalas

  8
  0
  Votes
  8
  Posts
  50
  Views

  S

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

• M

  New FOG Server doesn't recognize System MAC Address
  • michaeloberg

  13
  0
  Votes
  13
  Posts
  47
  Views

  M

  @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

• P

  capturar imagen de 2 discos
  • Pilar

  6
  0
  Votes
  6
  Posts
  30
  Views

  S

  @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.

• E

  Error on Start from hard disk (HD)
  • eliaspereira

  6
  0
  Votes
  6
  Posts
  18
  Views

  S

  @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…

• G

  Move images between storage groups
  • Gameman

  3
  0
  Votes
  3
  Posts
  33
  Views

  S

  @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.

• M

  API - Create Host "error": "Required database field is empty"
  • maddyred

  4
  0
  Votes
  4
  Posts
  25
  Views

  S

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

• M

  Fog api image create 417 error
  • maddyred

  4
  0
  Votes
  4
  Posts
  30
  Views

  S

  @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, } ...
• H

  Error Updating database
  • hernani

  2
  0
  Votes
  2
  Posts
  27
  Views

  

  @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.

• T

  Move images to Archive
  • Technolust

  1
  0
  Votes
  1
  Posts
  10
  Views

  No one has replied

• F

  SOLVED Interface not ready, waiting for it to come up
  • Florent

  19
  0
  Votes
  19
  Posts
  376
  Views

  R

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

• T

  Web GUI error after clicking List Hosts
  • tesparza

  25
  0
  Votes
  25
  Posts
  92
  Views

  

  @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.

• E

  import /images
  • electronico_nc

  3
  0
  Votes
  3
  Posts
  28
  Views

  

  @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.

• M

  FOG deploy: partitions 4 and 5 too big for disk
  • madeyem

  24
  0
  Votes
  24
  Posts
  197
  Views

  S

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

• B

  Fog client does not add printers
  • btoffolon

  11
  0
  Votes
  11
  Posts
  59
  Views

  S

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

• R

  Dell Optiplex 7090 Capture issue
  • Roc1479 0

  2
  0
  Votes
  2
  Posts
  24
  Views

  R

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

  All good now.