FOG Problems

• 

  Wrong Partition is mounted during deployment. (FOG 1.5.7.56)
  • Greg Plamondon  

  7
  0
  Votes
  7
  Posts
  17
  Views

  

  I was able to capture Windows 10 2004 UEFI from a source system with a 70GB disk and deploy it to a target system (VM) with 50GB disk. It deployed/booted and resized the disk without issue. Again my base image doesn’t have the recovery partition. Next week I schedule a new build task in MDT and leave the recovery partition in place at the end of the partition chain to see what happens on a deploy and resize. But for my use case 2004 works correctly deploying to a VM.
• G

  SOLVED Will not Join Domain after 1.5.8 Update
  • Goneski  

  9
  0
  Votes
  9
  Posts
  28
  Views

  

  I discovered this bug too when updating. My solution was just to create a group of all computers and then update the default AD credentials under Fog Settings. Then I just cleared it and repopulated the fields in Fog Settings. Then used the group of all and modified it for all computers at once. I even used the same password as I was. My speculation is that the new password encryption measure put in are breaking it, the length when the password is shown is way off of what it should be when its updated correctly.
• S

  TFTP port is closed is it normal?
  tftp port close • • symrex  

  15
  0
  Votes
  15
  Posts
  27
  Views

  S

  @EZY4 I think we both have different problems. I would suggest that you open a new thread on this. As a tip: Install VirtualBox + ExtensionPack and set up the network boot only. VirtualBox has iPXE, which gives you more information. Furthermore you can use wireshark to check what exactly your machine receives from the dhcp-server. @george1421 Good to know. Thanks for the information and help!
• M

  New fog server installation 1.5.8 on centos 7
  • Mightmar  

  5
  0
  Votes
  5
  Posts
  27
  Views

  M

  fog_error_1.5.9. RC.log Jul 08 16:06:23 PLGDVFOG01 systemd[1]: Starting The PHP FastCGI Process Manager... Jul 08 16:06:23 PLGDVFOG01 systemd[1]: Started The PHP FastCGI Process Manager. --2020-07-08 16:06:26-- https://10.180.8.90//fog//maintenance/backup_db.php Connecting to 10.180.8.90:443... connected. WARNING: cannot verify 10.180.8.90's certificate, issued by ‘/CN=FOG Server CA’: Self-signed certificate encountered. HTTP request sent, awaiting response... 302 Found Location: ?node=schema [following] --2020-07-08 16:06:26-- https://10.180.8.90//fog//maintenance/backup_db.php?node=schema Connecting to 10.180.8.90:443... connected. WARNING: cannot verify 10.180.8.90's certificate, issued by ‘/CN=FOG Server CA’: Self-signed certificate encountered. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/plain] Saving to: ‘/home//fogDBbackups/fog_sql_1.5.9-RC2_20200708_040626.sql’ 0K . 70.1M=0s 2020-07-08 16:06:26 (70.1 MB/s) - ‘/home//fogDBbackups/fog_sql_1.5.9-RC2_20200708_040626.sql’ saved [1305] ERROR 1146 (42S02) at line 1: Table 'fog.globalSettings' doesn't exist fog install. log To improve the overall security the installer will create an unpriviledged database user account for FOG's database access. Please provide the database *root* user password. Be asured that this password will only be used while the FOG installer is running and won't be stored anywhere: OK * Backing up user reports.....................................Done * Stopping web service........................................OK * Setting up Apache and PHP files.............................OK * Testing and removing symbolic links if found................OK * Backing up old data.........................................OK * Copying new files to web folder.............................OK * Creating the language binaries..............................Done * Creating config file........................................OK * Downloading kernel, init and fog-client binaries............Done * Copying binaries to destination paths.......................OK * Enabling apache and fpm services on boot....................OK * Creating SSL CA.............................................OK * Creating SSL Private Key....................................OK * Creating SSL Certificate....................................OK * Creating auth pub key and cert..............................OK * Resetting SSL Permissions...................................OK * Setting up Apache virtual host (SSL)........................OK * Starting and checking status of web services................OK * Changing permissions on apache log files....................OK * Backing up database.........................................Done * You still need to install/update your database schema. * This can be done by opening a web browser and going to: https://10.180.8.90/fog/management * Press [Enter] key when database is updated/installed. * Update fogstorage database password.........................Failed!
• A

  MAC already exists
  • astrugatch  

  3
  0
  Votes
  3
  Posts
  13
  Views

  A

  @Sebastian-Roth The Mac shows up in the table. Assigned to my device, but under pending. So I went to pending and approved the Mac addresses. Though when I went back and tried to remove the temporary Mac that is in the primary field and move the built in MAC address to the primary field but it still gives the error when I save that the Mac is already assigned (to the machine who’s page I’m on). There are 3 Mac addresses in the mix. The temporary usb adapter another USB adapter that the user usually has. This one doesn’t support PXE hence the temp adapter. The Wifi Mac that I keep as a secondary because we use the client and I want the machine to still check in while on Wifi.
• L

  Failed to start php-fpm.service
  • LOF  

  13
  0
  Votes
  13
  Posts
  26
  Views

  L

  @Sebastian-Roth Thanks Sebastian, I already know the answer and it’s Yes. Also, I’ve already pulled down the dev-branch and got the error before my initial post. So what’s next? Should I delete the previous dev-branch install and download/run it again?
• T

  SOLVED HP 250 G7 fails to upload image
  • Trev-lchs  

  3
  0
  Votes
  3
  Posts
  6
  Views

  T

  This is now resolved, on checking it appears that the kernel downloaded was the ARM64 instead of 64.
• T

  UEFI Problem- HP 250 G7
  • Trev-lchs  

  3
  0
  Votes
  3
  Posts
  12
  Views

  T

  I actually brought my laptop in from home, this I know is a uefi BIOS, on testing it, it booted into Fog with no issues ( it has been imaged in the past with FOG. So i then knew that UEFI boot was working. I have to hold my hands up on checking the HP 250 G7 it had not had secure boot switched off in the BIOS, this is a silly error and for this I blame my technician lol, (well i should have checked myself) on checking this morning i saw it was still on, I was lead down the FOG path after the kernel update failed. however i now have a different issue which i shall post.
• 

  FOG 1.5.9-RC2 incompatible with Windows 10 v2004 Partition Structure
  • sudburr  

  24
  0
  Votes
  24
  Posts
  122
  Views

  S

  @sudburr Is the partition layout still fine when you see this blkid: error: /dev/sda4 thing on subsequent tries? May I ask you to do the following: Let it try to capture a few times more. Every time you save a copy of the /images/dev/aabbccddeeff/d1.partitions (this aabb… is the MAC address of the host without colons) file to another location for us to compare those afterwards. Whenever you see the blkid... error you name it d1.partitions_fail_X (put in numbers instead of X) and if you don’t see the error you name it d1.partitions_ok_X.sfdiskPartitionFileName What kind of VM do you use? I am wondering if I am able to replicate the issue using the same setup?!
• T

  SOLVED Kernel Update Failed transfer
  • Trev-lchs  

  16
  0
  Votes
  16
  Posts
  14
  Views

  T

  @george1421 Yep thanks for your help George, we have it pixie booting now, unfortunately, on checking it this morning the Tech had not switched secure boot off in the laptop bios. due to the other issue i had been having i thought it was FOG, FOG is blameless in this instance.
• J

  Latitude 5410 No Legacy boot
  • John L Clark  

  52
  0
  Votes
  52
  Posts
  113
  Views

  J

  @george1421 I was able to edit the Grub.cfg and add our Fog server IP in and then boot with USB and register and capture and deploy. Thank you again for all the help.
• J

  FOS OS capturing error
  • janith  

  1
  0
  Votes
  1
  Posts
  8
  Views

  No one has replied

• G

  Multicast task has been killed
  • geezer  

  1
  0
  Votes
  1
  Posts
  6
  Views

  No one has replied

• 

  SOLVED Can't upload image "Could not find partitions (/bin/fog.upload)
  • Tonydpala  

  6
  0
  Votes
  6
  Posts
  16
  Views

  

  It’s completly dumb i just didn’t created the image entirely so i couldn’t upload anything ^^" But thanks anyway for your help and your work !
• M

  New fog server installation 1.5.8 on centos 7
  • Mightmar  

  5
  0
  Votes
  5
  Posts
  40
  Views

  M

  Issue solved, yet we have now version 1.5.9 RC and there is new problem with node offline
• M

  Firmware bug: TSC_DEADLINE disable due errata with FOG 1.5.9-RC2.10
  • mgep  

  3
  0
  Votes
  3
  Posts
  10
  Views

  

  Please also include the hardware (mfg and model) of the source image where it was take from and the hardware of where you send it to. Without a picture of the actual error we can only guess the problem is with the send to computer hardware and the FOS linux kernel.
• 

  Updating FOG and Storages from 1.5.4 to lattest version
  • scosta  

  4
  0
  Votes
  4
  Posts
  20
  Views

  S

  @scosta Sorry but I don’t get what you mean by that quoting the term ClusterSSH as well. Please rephrase your question.
• M

  REAR Backup Rescue and FOG Project
  • matekub  

  12
  0
  Votes
  12
  Posts
  27
  Views

  M

  Thanks for your time and response. Yes, any of those 3 commands didn’t work. Based on information from that topic in REAR GitHub - the user after using PXE mode, they had pxelinux config and probably as you mentioned kernel (kernel file) and maybe file system (initrg.cgz) for BIOS, not UEFI. I guess i have the same and trying to boot on UEFI system. How to determine which file is for UEFI? I guess it should be part of ISO which works fine on BIOS and UEFI system. I have this content of ISO: Then I have this content in ISO: EFI G:\EFI boot G:\boot isolinux G:\isolinux BOOT G:\EFI\BOOT fonts G:\EFI\BOOT\fonts locale G:\EFI\BOOT\locale BOOTX64.efi G:\EFI\BOOT\BOOTX64.efi embedded_grub.cfg G:\EFI\BOOT\embedded_grub.cfg grub.cfg G:\EFI\BOOT\grub.cfg grubx64.efi G:\EFI\BOOT\grubx64.efi grub G:\boot\grub efiboot.img G:\boot\efiboot.img grub.cfg G:\boot\grub\grub.cfg boot.cat G:\isolinux\boot.cat chain.c32 G:\isolinux\chain.c32 hdt.c32 G:\isolinux\hdt.c32 initrd.cgz G:\isolinux\initrd.cgz isolinux.bin G:\isolinux\isolinux.bin isolinux.cfg G:\isolinux\isolinux.cfg kernel G:\isolinux\kernel ldlinux.c32 G:\isolinux\ldlinux.c32 libcom32.c32 G:\isolinux\libcom32.c32 libgpl.c32 G:\isolinux\libgpl.c32 libmenu.c32 G:\isolinux\libmenu.c32 libutil.c32 G:\isolinux\libutil.c32 menu.c32 G:\isolinux\menu.c32 message G:\isolinux\message pci.ids G:\isolinux\pci.ids rear.help G:\isolinux\rear.help reboot.c32 G:\isolinux\reboot.c32 vesamenu.c32 G:\isolinux\vesamenu.c32
• C

  WebUI not deleting images in file system
  • Chad  

  5
  1
  Votes
  5
  Posts
  35
  Views

  

  I’m still on 1.5.6 and this doesn’t work for me. Honestly it has not worked in many iterations of FOG prior either. I usually just go into the VM and manually remove them after I delete the definitions in the GUI. Thought it was just a bug on my end.
• B

  Snapin problem on fog 1.5.9-RC1 and 1.5.9-RC2
  • borg  

  13
  0
  Votes
  13
  Posts
  15
  Views

  B

  UPDATE: Checked permissions fogproject:apache user has full rights to all snapins, why it is the apache group I don’t really know. also changed the www.conf file. No change unfortunately.