FOG Problems

• R

  boot php - denied
  • robertkwild

  4
  0
  Votes
  4
  Posts
  12
  Views

  R

  i disable UEFI by default everytime i image pcs, i always set bios to legacy and secure boot disabled

  i can log in to the dashboard fine (see pic below) and i havnt changed the self signed cert fog installed on the initial setup

  but as i said, it works on other pcs i need to image just this one i couldnt and i find it bizare

• B

  Imaging from large drive to small drive
  • brakcounty

  12
  0
  Votes
  12
  Posts
  35
  Views

  S

  @brakcounty Didn’t say it would be easy, did I??

  FOG uses text based partition layout files (e.g. the one you posted) as well as a binary copy. Messing with the text file is easy but less so with the binary file! Unless you are keen to use hexedit to change the binary file I’d advice you follow the steps as outlined.

  Make a backup copy of d1.minimum.partitions and d1.mbr of that image you want to mess with! Edit d1.minimum.partitions, remove that line starting with last-lba: ... and also change /dev/sda4 : start= 967014400, ... to /dev/sda4 : start= 46583808,. Note: This is not in general for all your images as each partition layout is different. I will give more general instructions later. Copy that changed d1.minimum.partitions to /images/dev/ as we need it there too in a moment. Schedule a debug deploy task for one host that you want to deploy this image to and PXE boot it. Hit ENTER twice to get to the command shell and manually mount the /images/dev directory on your FOG server via NFS: mkdir -p /mnt && mount -o nolock,proto=tcp,rsize=32768,wsize=32768,intr,noatime x.x.x.x:/images/dev /mnt (use your FOG server IP instead of x.x.x.x) Find out what the local disk is named on this computer by running lsblk (usually /dev/sda or maybe /dev/nvme0n1) and use that with the following commands. Clean the current partition table on that computer: sgdisk -Z /dev/sda Deploy the modified partition layout: sfdisk /dev/sda < /mnt/d1.minimum.partitions Grab a binary copy of that new partition layout: sgdisk -b /mnt/d1.mbr /dev/sda Leave that machine for now and go back to your FOG server. Move the created /images/dev/d1.mbr file over to the correct images folder (the one you started with backing up the two files). Ok, now once again back to the machine and start deploying as usual by issuing the fog command.
• F

  iPXE Boot issue: boot.php... Permission denied.
  • fmohammed

  7
  0
  Votes
  7
  Posts
  44
  Views

  F

  @sebastian-roth Thanks, we gave that a go and now there is an error with the chainloading failing. So progress from denied.

  Researching the error on ipxe (3e11623b) the error seems to be based on the lack of a DNS server. Currently these custom certs don’t have the IP address of the fog server as part of the certificate SAN, so we’re going to see if a certificate with the SAN containing the IP and hostname resolves this error.

• W

  FOG Update IPXE Issues
  • wkratky

  9
  0
  Votes
  9
  Posts
  109
  Views

  S

  @wkratky said in FOG Update IPXE Issues:

  I am wondering if the problems are related to git. I followed the Update to latest page in the Wiki, and when I run the git cmds, I get the attached messages. I was not doing this in previous attempts when I did the ./installfog.sh.

  Well, it looks like you don’t run the git commands in the right directory. Not sure where you have put it but maybe try cd fogproject before running the git commands. Otherwise search the disk to find it find / -name "installfog.sh"

  Here is the output from the last message’s request. Note this is from after yum update -y and yum -y install git, but not the actual version update.

  The output from the commands look fine. There is no issue with the web directory on your install. So go ahead und re-run the installer.

  Here is that reading post 1.5.9 update. Now instead of errors, it is just a blank screen when attempting to run the image.

  Not sure what you mean by that. The picture posted is pretty much the same as the other one.

• J

  Chainloading failed
  • jherron

  1
  0
  Votes
  1
  Posts
  6
  Views

  No one has replied

• T

  Nouveau dossier partagé pour ghosts.
  • tallier

  11
  0
  Votes
  11
  Posts
  55
  Views

  G

  @tallier Vous devez rechercher des messages d’erreur plus détaillés sur le serveur et le client.
  Vérifiez que /images est correctement monté sur le serveur.
  Vérifiez si vous pouvez monter /images à partir d’un autre ordinateur.
  Assurez-vous que les services NFS sont démarrés avec toutes les dépendances.

• T

  REFInd-Initializing - hangs
  • Trev-lchs

  28
  0
  Votes
  28
  Posts
  34
  Views

  S

  @trev-lchs said in REFInd-Initializing - hangs:

  having now tried all the various options of exit in the latest version of FOG I have had no luck, this is with the rEFInd.efi renamed and the latest X64 REFInd file copied over it (0132) and named rEFInd.efi.

  The case of the filenames do actually matter on Linux systems!! Not sure but that could be the problem now.

  Beside that it’s very hard to help without knowing what exactly has been done. Maybe run the following commands and post output here so we know what it looks like at the moment:

  ls -al /var/www/ ls -al /var/www/html/ ls -al /var/www/html/fog/service/ipxe/
• T

  Problème Dossier partagé images
  • tallier

  1
  0
  Votes
  1
  Posts
  5
  Views

  No one has replied

• T

  Fog UPDATE AILED PHP Failed To install Properly
  • Trev-lchs

  9
  0
  Votes
  9
  Posts
  9
  Views

  T

  @trev-lchs now to test refind lol

• C

  move to Fog Pxe menu
  • chris_unit

  5
  0
  Votes
  5
  Posts
  23
  Views

  

  @chris_unit said in move to Fog Pxe menu:

  Is the directory /images/ shared out over http ?

  No its not the docbase for http on ubuntu is /var/www/ I believe. So your os/ubuntu/Desk... path should start form there.

  I would also confirm with a browser that you can reference the url to get the iso. That will tell you its working before you attempt to pxe boot.

• T

  Storage Node not appearing on Web interface?
  • tesparza

  4
  0
  Votes
  4
  Posts
  47
  Views

  T

  @sebastian-roth Yup its was, “Is Graph Enabled (On Dashboard)” Working now. thanks.

• R

  Very slow boot.php and bzImage during pxe boot
  • rodluz

  2
  0
  Votes
  2
  Posts
  13
  Views

  S

  @rodluz said in Very slow boot.php and bzImage during pxe boot:

  Only changes I have done to the server recently are post download scripts and add new images/snapins.

  Not the things that would cause the described issue I think.

  I took a laptop that I know doesn’t work to a coworker’s area and used her FOG to see what would happen and there was no issue. This makes me think I screwed up on something with my FOG server.

  That’s interesting. Surely tried a couple of times to make sure it works fine consitently on her FOG server? What FOG version is the other server?

  The next thing to look at is the network components. Try connecting the laptop as close to the FOG server as possible. Best if you can take it to the server room and plug it to the very same switch the FOG server is on just for testing the PXE boot.

• T

  FOG not seeing Hard drive when Bios is set to Raid On
  • tesparza

  2
  0
  Votes
  2
  Posts
  10
  Views

  S

  @tesparza Search the forums for both topics. There are numerous posts on both.

• J

  Boot from hard disk issue
  • jrm

  5
  0
  Votes
  5
  Posts
  27
  Views

  J

  @george1421

  Hi Thanks for this informations, I maked the change but do you know if we can bypass the “press any key to continue” in rEFInd?

  Thanks for your help

• I

  could not map attribute 0x80 in inode FOG 1.5.9
  • IronAngel777

  2
  0
  Votes
  2
  Posts
  12
  Views

  I

  Well, I did the exact same update and capture to the next new Lenovo, out of the box, and it captured fine. Perhaps, CHkDSK does not completely repair NVME drives.

  Anyway…

• G

  Restoring GPT Partition Table Error
  • GeorgeBells

  1
  0
  Votes
  1
  Posts
  12
  Views

  No one has replied

• M

  Error with UEFI
  • MaximeGuidez

  3
  0
  Votes
  3
  Posts
  27
  Views

  

  @yeet said in Error with UEFI:

  Just two points to clarify here.

  I’ve stopped using ipxe.efi altogether, since snp.efi seems to cover all of the devices I end up imaging.

  snponly.efi for uefi is roughly equivalent to what undionly.kpxe is to bios. Both of these ipxe boot loaders use the network adapter’s built in firmware driver. For bios, the undi firmware interface is very mature and stable. For uefi the snp firmware interface has been historically very flaky until the last few years where it has matured a bit and become more stable. For both the undi and snp firmware drivers, its up to the nic manufacturer to make sure the firmware driver conforms to the strict standards. This doesn’t always happen.

  Now ipxe.kpxe is to bios what ipxe.efi is to uefi. In the case of these boot loaders these are more like a linux kernel than not. These boot loaders have one of every known driver installed. The complete network and disk drivers are part of this boot loader kernel. The benefits are that ipxe has a very stable and known network and disk controller communication. The down side is that its sometimes difficult to keep up with emerging hardware. That is where undi and snp firmware drivers have helped since they are created by the hardware manufacturer when the new hardware is released. If the developers find that many people are having success with the snponly.efi drivers, they may change their default recommendations.

  If that doesn’t work, I’d recommend updating the kernel version.

  Don’t confuse the ipxe menu and the boot loader from the FOS Linux kernel. They are two different systems that work together. iPXE gets you to the FOG menu on the target computer. Once you select a menu item and bzImage is loaded then its FOS linux in charge. If you are having network issues and don’t get to the FOG iPXE menu then its a ipxe boot loader issue, if you get to the menu but when you select a menu item then see a network issue then its FOS Linux with the problem. I said all of that to say, if iPXE will not initalize then updating your {FOS Linux} kernel will not help you.

• X

  FOG Client 0.12 Error Could not parse data
  • xseth

  3
  0
  Votes
  3
  Posts
  37
  Views

  X

  @sebastian-roth
  indeed, I switched the fog server on the same network it works now
  thank you

• B

  21H1 imaging issue-variables do not populate
  • bruce.stewart

  2
  0
  Votes
  2
  Posts
  30
  Views

  

  @bruce-stewart The postinstall scripts execute under FOS Linux bash shell. FOS Linux doesn’t know/care about the target computer’s OS. When the script runs windows is not involved. So it kind of makes me think the issue is elsewhere.

  Are you using these instructions for the postinstall script? https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed

• T

  /bin/fog.upload Partition failed
  • tallier

  1
  0
  Votes
  1
  Posts
  8
  Views

  No one has replied