FOG Problems

• I

  SOLVED Exit boot options
  • ismith.hpu  

  3
  0
  Votes
  3
  Posts
  18
  Views

  A

  okay thanks for the reply
• I

  UNSOLVED Failure in Capturing an image
  • ismith.hpu  

  5
  0
  Votes
  5
  Posts
  35
  Views

  I

  @Sebastian-Roth No changes after updating.
• T

  UNSOLVED FOG installation errors
  • TaTa  

  45
  0
  Votes
  45
  Posts
  145
  Views

  D

  @TaTa What is the result of select vvalue from fog.schemaVersion;?
• L

  UNSOLVED FOG 1.6, identified problems
  • lebrun78  

  39
  0
  Votes
  39
  Posts
  158
  Views

  L

  @Tom-Elliott said in FOG 1.6, identified problems: I have identified a few more issues and been able to correct them. Clicking on pages within the menu as opposed to full refresh on the same page, some elements such as list -> select items to delete, click delete, the modal not appearing requesting password to ensure you want to do this. On full refresh to link it worked. On clicking from the menu it didn’t. Fixed by causing reinitialization. Import elements didn’t return proper notification items. Similarly warnings and info notifications always assumed error. This has been fixed Added rudimentary file upload progress system. Will be working to implement a progress indicator. Creating images when entering the name, the path didn’t auto populate. This has been re-implemented. Snapin file uploads were already set to be operational, but did not work due to typo on the POST field to send up the files. Renamed and introduced. Host export didn’t properly indicate the primac field. It didn’t even pull in the Mac at all and the values were improper. The host name appeared in description, and name field was the spot Mac was trying to populate. Added the primac field and properly pulling the data now. Along with the reinitialization for the modal requesting passwords, this same reinitialization was causing table populating to be reinitialization and throw an error as it already existed. Set to retrieve so not to throw the error. What a job, thank you very much ! When I edit a group, I can’t set module association in client module settings
• L

  UNSOLVED Mounting issue after FOG update
  • LittleTux  

  5
  0
  Votes
  5
  Posts
  21
  Views

  

  @LittleTux There are a few ways to go about this. One method is like the tutorial you found about adding a second (logical) storage node to the FOG server. This method has its good and bad sides. On the good side its pretty easy to implement as long as you follow all of the steps. On the bad side now you have to decide when you create the image definition which disk you want to store the image on. One alternative would be to mount /dev/sdb1 on /images. That would make your /images directory 1,2TiB in size. (there are a few steps that need to happen to make this configuration, but no changes are needed in FOG). The second alternative is to mount /dev/sdb1 below the /images directory. Like /images/administrateur When you create the image definition you again have to decide to put the images in /images or /images/administrateur directory one is on /dev/sda and the other is on /dev/sdb. In my opinion alternative #1 is the best option because it has the least impact on FOG and its settings. If you need to expand the VM disk beyond 1,2TiB you can do that pretty easy as long as /dev/sdb1 is a normal partition.
• K

  SOLVED Official Way to Upgrade 1.4.4 to the newest most stable version?
  • Kevin Talbot  

  11
  0
  Votes
  11
  Posts
  43
  Views

  K

  @Sebastian-Roth the boss wants it updated…
• B

  UNSOLVED PXE boot stuck on initialising devices
  • Baessens  

  6
  0
  Votes
  6
  Posts
  20
  Views

  

  @Baessens We there is nothing wrong with what there. What I see is a different version of undionly.kpxe for FOG 1.5.5 and 1.5.7. So the recommendation as a test take undionly.kpxe from the working FOG server and copy it over (renaming the original first) to the not working fog server then pxe boot. If the problem goes away on the not working fog server then the problem is with undionly.kpxe if the problem stays then its with the different version of hyper-v
• P

  SOLVED DHCP Failed : no configuration methods succedeed.
  • processor  

  5
  0
  Votes
  5
  Posts
  40
  Views

  P

  Thank you! I keep you informed
• I

  SOLVED Linux on nvme drive: Failed to read back partitions (runPartProbe)
  • ismith.hpu  

  7
  0
  Votes
  7
  Posts
  42
  Views

  I

  @Tom-Elliott This did resolve the issue.
• K

  UNSOLVED Failed to upload image (Process Hung)
  • Keating178  

  13
  0
  Votes
  13
  Posts
  57
  Views

  

  @Keating178 The Invalid Storage Group error you were seeing should be fixed if you can upgrade to the latest within the dev-branch from GIT. Hopefully this will fix the issue you were seeing too.
• J

  UNSOLVED L390 Yoga Lenovo
  • John L Clark  

  4
  0
  Votes
  4
  Posts
  31
  Views

  

  @george1421 said in issue with netcard of dock gen2 of lenovo l390: @JJ-Fullmer The r8152.c from the torvalds github site failed to compile on 4.19.65, I’m suspecting its for a later release of linux. The version from the torvalds site was 1.10.10. The version in 4.19.65 was 1.9.9 of the realtek driver. I was able to compile the realtek driver from the wget github site. This version is 2.12. Here is a link to that kernel with the 2.12 driver built in. I also enabled the usb-c code in the kernel that appears to have not been set. I don’t know if its relevant, but it should be on for other applications. https://drive.google.com/open?id=1wZwwOwbEr0nR3mnPLKg7AsulwJaGhO0A Download this as bzImageRT (watch your case) and copy it to the ipxe directory with the other kernel images. Manually register the host and then in the host definition add in bzImageRT as the kernel for that host. Then pxe boot into FOS Linux debug mode to see if the network adapter inits correctly with this updated driver. @John-L-Clark I realize that this is a few months old, but this problem sounds similar. Give this solution a try, download the kernel @george1421 made and set it on that host. It worked for me with the lenovo usb-c ethernet adapter, I imagine you’re using that or a similar adapter, this kernel fixed the issues we were having with the L390 and X390
• E

  SOLVED Some computer models adding garbage bytes to undionly.kpxe tftp filename, causing failure to PXE boot.
  • EBCF  

  9
  0
  Votes
  9
  Posts
  81
  Views

  E

  Thanks everyone for the support. @Daniel-Miller and @Sebastian-Roth I opted for the approach you suggested of making TFTPD ‘correct’ the filenames. The affected PC now goes to the FOG menu. I missed Sebastian’s map file and ended up writing my own which is: # Workaround for PXE clients that misinterpret the DHCP options # because they expect a null-terminated string # match the extensions followed by any characters and replace it with # just the extensions r \.pxe.* \.pxe r \.ipxe.* \.ipxe r \.kpxe.* \.kpxe r \.kkpxe.* \.kkpxe @george1421 I wouldn’t even have guessed that proxy DHCP was a thing. I’ve decided not to go for it this time but I’ll keep it in mind for future.
• 

  UNSOLVED Can't find network interface - kernel
  • Interrupt  

  5
  0
  Votes
  5
  Posts
  36
  Views

  

  @george1421 said in issue with netcard of dock gen2 of lenovo l390: @JJ-Fullmer The r8152.c from the torvalds github site failed to compile on 4.19.65, I’m suspecting its for a later release of linux. The version from the torvalds site was 1.10.10. The version in 4.19.65 was 1.9.9 of the realtek driver. I was able to compile the realtek driver from the wget github site. This version is 2.12. Here is a link to that kernel with the 2.12 driver built in. I also enabled the usb-c code in the kernel that appears to have not been set. I don’t know if its relevant, but it should be on for other applications. https://drive.google.com/open?id=1wZwwOwbEr0nR3mnPLKg7AsulwJaGhO0A Download this as bzImageRT (watch your case) and copy it to the ipxe directory with the other kernel images. Manually register the host and then in the host definition add in bzImageRT as the kernel for that host. Then pxe boot into FOS Linux debug mode to see if the network adapter inits correctly with this updated driver. @Interrupt Give this solution a try, download the kernel @george1421 made and set it on that host. It worked for me with the lenovo usb-c ethernet adapter, it stands to reason it will work for the dock too.
• R

  SOLVED SSD fails at Restoring Partition Tables (GPT) with error code 4
  • rwilsonadvantage  

  19
  0
  Votes
  19
  Posts
  64
  Views

  S

  @rwilsonadvantage You are welcome! I just marked it as solved (Topic Tools -> Mark as solved, not sure if you have access to this).
• B

  SOLVED Multiple master nodes syncing images
  • Baessens  

  5
  0
  Votes
  5
  Posts
  18
  Views

  S

  @Baessens In this special case I’d suggest you use basic Linux commands to export/import image definitions and sync the image files to your other node. Optional: Create a sync user account on your main master node - otherwise you’d use the root account to do that but don’t use the fogproject account! Setup SSH keys to be able to login using the sync (or root) account from node B to node A Setup a cron job on your node B to do the DB and file sync Make sure rsync is installed on both nodes. Here is just a quick outline of how you might do this (untested!): #!/bin/bash ssh syncuser@nodeA mysqldump -u root -pPassw0rd fog images >/tmp/images.sql mysql -u root -pPassw0rd </tmp/images.sql rsync -ave ssh syncuser@nodeA:/images /images >>/var/log/fog/myimagesync.log 2>&1 This will wipe the images table on your node B and import all the definitions you have on node A.
• R

  UNSOLVED Error trying to restore GPT partition tables
  • rankinc  

  4
  0
  Votes
  4
  Posts
  30
  Views

  S

  @rankinc This partition number 5 is a recovery partition which FOG doesn’t move on the disk. So it’s unable to shrink your main Windows partition.
• R

  SOLVED Extremely Slow Deploy to NVME drives
  • robbit  

  34
  0
  Votes
  34
  Posts
  336
  Views

  D

  @Quazz said in Extremely Slow Deploy to NVME drives: @DeRo93 If available, install firmware updates, BIOS updates and such. Already done. Nothing helped :/. I hope there will be a Solution in future. We only work with HP. And i think the new one will all get NVME SSD´s… Anyway thank your for your Help.
• C

  SOLVED HP PROBOOK 450
  • crustyjeff  

  6
  0
  Votes
  6
  Posts
  30
  Views

  S

  @crustyjeff said in HP PROBOOK 450: No, so how can i remove the recovery partition from the clone? Well just delete it from your master host, maybe even expand the third partition using the Windows disk management view and re-capture the image. Probably a good idea that you leave the image Accessing2019 on your FOG server and create a new image definition for the capture you take after removing the forth partition. This way you can always go back to the original state in case you figure that you’d need it for some reason. Deleting partitions is kind of a dangerous task. Do it on your own risk and if unsure take another backup copy of the whole system before you go ahead!
• I

  SOLVED Could not complete tasking (/bin/fog.download)
  • ismith.hpu  

  2
  0
  Votes
  2
  Posts
  16
  Views

  

  Updated /var/www/html/fog/lib/fog/task.class.php getStorageGroup method to do: return new StorageGroup($this->get('storagenode')->get('storagegroupID')); This way it’s not relying on a potential return from the group that may not be assigned to the tasking. It relies on the storage node that was associated to the tasking. I will update the main codebase with this issue and fix. Thank you,
• Z

  SOLVED Stopping web service........................................Failed!
  • ziomario  

  5
  0
  Votes
  5
  Posts
  32
  Views

  S

  @ziomario Thanks to Tom’s work the installer now works with Ubuntu 19.10 as well. Just finished a test install with dev-branch. Though you need to choose one of the development versions. Either go with working-1.6 (upcoming version 1.6 with new GUI) or dev-branch (latest development version of FOG 1.5.x). sudo -i cd /home/ziomario/Scaricati/Linux/ git clone https://github.com/FOGProject/fogproject cd fogproject git checkout working-1.6 cd bin ./installfog.sh Choose the version at the above command where it says “git checkout …”