Subcategories

• FOG Problems

  Technical help directly related to FOG.
  9.1k
  Topics
  84.8k
  Posts

  F

  @Small0145 No, it’s not.

• Hardware Compatibility

  Problems with specific computer models.
  699
  Topics
  8.3k
  Posts

  G

  @Donutsrule5

  OK lets see if we can boot from a usb drive. This tutorial will instruct you on how to build a usb boot image. https://forums.fogproject.org/post/69606 the google drive link below will take you to step 7 in the thread.

  https://drive.google.com/file/d/1psCrPVzBTvlakLkCMvhdoScAEZp1CKE6/view?usp=drive_link

  Once you build the usb boot drive, take the kernel and init.xz from your current version of fog and replace the ones on the flash drive with the ones in from the FOG server. The files are in /var/www/html/fog/service/ipxe directory.

  Once you have the usb drive ready, pxe boot into the grub menu on the flash drive, then go into debug mode. After several pages of text you need to clear with the enter key you will be dropped at a fos linux command prompt. If you can get that far then fos linux is OK and the problem is probably with ipxe or the handoff between the two.

  If you want to image with the flash drive, schedule the task in the fog server BEFORE you usb boot and select option 1 from the menu. If you get it out of sequence you will get an error that says something about Null. Basically its saying you don’t have a task scheduled on the fog server so there is nothing to do. Lets see if we can get it to boot this way.

• Windows Problems

  Technical help related to a Windows Problem.
  1.0k
  Topics
  8.2k
  Posts

  S

  @Almeida BitLocker is enabled in your master ? If yes, you should disable it. Enable it only on the final computer.

  We do have the BCD issue when enabling BitLocker on 24h2 image, we are running the same commands, but you are missing one.

  You need to set device partition=C: for the recover from hibernate entry too. The annoying part is that its ID is dynamic.

• Linux Problems

  Technical help related to a Linux Problem.

  719
  Topics
  6.2k
  Posts

  M

  Sorry for diging up this post.
  Just for us the solution was a missing package : gcc-aarch64-linux-gnu

• Mac Problems

  Technical help related to a Mac Problem.

  79
  Topics
  941
  Posts

  M

  @george1421 Hi,

  Thanks for your reply. Its strange. I am working with (almost exclusively) early 2012 hardware. My older Imacs 2009-2011 afaict pxe boot fine image with FOG w/o issue. The problem comes along when, I try to image our macbooks. They display different levels of progress before they flat out hang. I had one mbpx,y I’m almost sure it was a 3rd gen intel just can’t find it right now. I may be being processed to go out the door to our clients.

  Yes the 2019 verison of ipxe was executed from a boot of clonezill 3.1.x the version I would attempt to boot from ventory stick or from an imaged usb stick would display an error regarding not having efi capability and/or hang or return to the ventoy menu. If I just let them be long enough the MBP would just restart.

  So I did attempted to roll my own and ran into the same problem with the oobox downloadable iso/zip file. Hang… I am researching w/o much success with how clonezilla compiled their ipxe menu entry or how to just plain add efi capability to ipxe.iso/zip and burn it to a usb stick. I just am not knowledable enough to formulate a good question or find what I am looking for (cause I don’t know:))

  So thanks again for your reply. I have a large donations of older MBP’s coming just before the holidays and I would lik to be able to make it rain.

  Regards,

• General Problems

  General Developer questions relating to FOG.
  668
  Topics
  5.0k
  Posts

  S

  @Tom-Elliott I fixed it by directly removing the dirty flag using Linux. sudo ntfsfix -d /dev/nvme...

  We need to redo our golden image, so we will check at that time if we still get the same behavior.

  Thx for the help !