Linux Problems

• U

  SOLVED GParted Live from FOG
  gpartet • • user435

  12
  0
  Votes
  12
  Posts
  609
  Views

  

  @alireza2n May I include your configuration in this tutorial? https://forums.fogproject.org/topic/10944/using-fog-to-pxe-boot-into-your-favorite-installer-images

• Z

  How to made a new kernel
  • Zaqen

  6
  0
  Votes
  6
  Posts
  18
  Views

  

  @zaqen The way I build the one off kernels are a bit different than the FOG Devs do it but it works. On your linux distro you need to install the buildessentials package. You can probably google building kernel on your linux distro to get all of the required packages.

  Now download the linux kernel from kernel.org to a working directory and extract it. From the git hub site https://github.com/FOGProject/fos/tree/master/configs Download kernelx64.config and save it into your home directory.

  Copy kernelx64.config from your home directory and save it as .config in the base directory of the kernel you extracted.

  Issue the make config or make nconfig command from a linux command prompt to build and load the kernel config editor. Once the editor load look for any warning messages about legacy/old settings or configs. If the menu loads cleanly then save the settings even if you haven’t changed anything and exit the menu config.

  The last bit is to just issue the make command to build bzImage. (the kernel).

• D

  Fog not loading after ubuntu updates
  • dejv

  9
  0
  Votes
  9
  Posts
  54
  Views

  D

  @sebastian-roth you have a point there a good way to learn linux

• B

  GRUB Config Lost After Imaging
  • bramen

  2
  0
  Votes
  2
  Posts
  19
  Views

  

  @bramen I can’t speak so much to the grub stuff.

  What I can tell you is that FOG has the ability to run a bash script after the image has been pushed to the target computer and before the computer reboots after completing the deployment. You can use this feature to tweak settings on the target computer before the computer is first booted into the target OS. This is used commonly with the windows environment to place hardware specific drivers onto the target computer that is used during the OOBE/WinSetup phase of windows. In linux we’ve used these scripts to rename linux computer and do some post install activities.

  The FOG imaging agent is Linux based so it can’t directly interact with ms windows, but it can leave bread crumbs behind for windows to act upon. For linux target computers it can do more things. I can’t say if it can run grub commands though.

  The concept of the fog post install script is that the script will need to mount the target computer media/file system, do whatever is needed then disconnect from the target media.

  For windows I have a tutorial here: https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed While this is windows specific the setup program would be very similar for linux.

• T

  Update CentOS 7
  • Technolust

  3
  0
  Votes
  3
  Posts
  22
  Views

  T

  @sebastian-roth Thank you for the response! I’m assuming I should keep EXT4. I haven’t updated this thing in a while. I was planning to take a snapshot first but wanted to have a little better clarity. I’m running 1.58 so I will also update to 1.5.9 as well.

• W

  FOG Post Deploy Script Rename Host (Linux)
  • WT_101

  3
  0
  Votes
  3
  Posts
  24
  Views

  

  @wt_101 If I can suggest you look at this post: https://forums.fogproject.org/topic/11126/using-fog-postinstall-scripts-for-windows-driver-injection-2017-ed

  it gives you an idea how to do this with windows. You can use the same concept, except for maybe look for the partition that has an /etc directory.

  Here is a bit older script that shows a few different techniques. https://forums.fogproject.org/topic/7740/the-magical-mystical-fog-post-download-script

• V

  Running both CloneDeploy and FOG?
  • vertimyst

  2
  0
  Votes
  2
  Posts
  37
  Views

  

  @vertimyst said in Running both CloneDeploy and FOG?:

  but since I have CD on our server already I can’t get anything to boot to FOG over our network - it all defaults to CD.

  Its not clear exactly what you are doing here. FOG doesn’t use a CD/DVD it boots over the network. FOG is similar to CloneDeploy or Clonezilla but different.

  For FOG you will set dhcp options 66 to the IP address of your fog server and dhcp option 67 to the boot file name. The boot file name depends on what format your computer’s firmware is in. For a BIOS computer, dhcp option 67 is undionly.kpxe and for a UEFI computer the boot file name is ipxe.efi.

  Once those values are set in your dhcp server then you pxe boot your target computer into the FOG iPXE menu.

  I have a feeling since you referenced CD several times you might be doing something non-standard with FOG. Can you explain a bit more of what you are trying to do?

• M

  Unable to login as root
  • michaeloberg

  6
  0
  Votes
  6
  Posts
  53
  Views

  M

  @george1421 Hello! I fired up a new VM and installed Debian 10.11 (buster). I did a modified installation from the YouTube video you shared, I did partitioning based on this video - https://wiki.fogproject.org/wiki/index.php?title=Debian_8

  I installed 1.5.9 and setup the DB and changed the fog default password.

  My next question is - can I export my settings off of my old FOG server into the new one? Currently I have both VMs fired up so I can simply toggle between the two IPs in a tabbed browser.

  Once I get the new server setup, I am going to change my DHCP and PXE settings on my Windows network to test PXE booting my new computers that use the USB dongle. I am going to be beyond thrilled if this works as I have several hundred of these machines that need imaged.

  Thank you so much for your help and look forward to your response!

  Gratefully,

  Michael

• F

  SOLVED Dual Images windows 10 and Ubuntu 16 with UEFI
  • Fernando Gietz

  35
  0
  Votes
  35
  Posts
  6258
  Views

  R

  Hello, I came to this topic because I was having this same issue with some new Dell computers that arrived here where I work, in my case I didn’t needed to repair the grub, but I could solve this by changing some bios configuration where there’s a option to add uefi boot option and there appears the .efi file of the grub and mark it to boot first. Hope it helps!

• L

  SOLVED New User "fogproject" on ubuntu
  • lerne-nie-aus

  3
  0
  Votes
  3
  Posts
  16
  Views

  L

  @george1421 Ok, thanks.

  If so, i will not touch it:)

• L

  Is there a way to make FOG compatible with LUKS encryption?
  • LuisTemporal

  15
  0
  Votes
  15
  Posts
  109
  Views

  S

  @luistemporal said in Is there a way to make FOG compatible with LUKS encryption?:

  The problem I have now is that the original machine is 34 GB and the cloned machine is 54 GB and there is unallocated disk space left. How could I extend the encrypted partition to fill the entire disk?

  Now that part will definitely take some more work on the inits as we’d need to rework the resize functions and add LVM support. @Wayne-Workman said her might look into this but will take time.

• T

  The initial storage node is much smaller than the disk space I gave my VM?
  • tomslick

  9
  0
  Votes
  9
  Posts
  62
  Views

  T

  @sebastian-roth said in The initial storage node is much smaller than the disk space I gave my VM?:

  sudo resize2fs -p /dev/mapper/ubuntu–vg-ubuntu–lv

  That all did the trick, VM is now showing the full allocated disk space!

  Thank you so, so much for your help, and also for giving me a little homework! I’ll read up on LVM as you said.

  Thank you again for your help, I can’t thank you enough!

• C

  Controlling exit
  • chris_unit

  3
  0
  Votes
  3
  Posts
  21
  Views

  

  @chris_unit said in Controlling exit:

  That way we can book to windows using exit to refind, and exit to GRUB UEFI for ubuntu.

  You are on the right track on the other thread. The two refind options are what you need. This way you can target where refind looks for the boot files. You can include and exclude file paths to get what you need.

  The grub4win implementation inside fog is bios only. BUT that’s not to say you couldn’t use a similar concept to the dual refind hack to leverage grub too. There are a few ways to go about it. I don’t have to deal with dual boot so I’ve never looked into streamlining that flow.

• F

  FOG client under Kubuntu 20.04
  • Fernando Gietz

  3
  0
  Votes
  3
  Posts
  29
  Views

  F

  Hi @Sebastian-Roth,

  Now works fine the FOG client

  Thanks for your fast reply

• K

  The client won't install
  • koni

  6
  0
  Votes
  6
  Posts
  63
  Views

  K

  @sebastian-roth The error with chkconfig is still here and I dnd’t found any topic about it in the forum, is any alternativ possible to this package ?

• O

  SOLVED Ubuntu Image with both - UEFI and Legacy support
  • Oleg

  12
  0
  Votes
  12
  Posts
  153
  Views

  J

  @jc35
  mount /dev/sda1 /mnt
  mount --bind /sys /mnt/sys
  mount --bind /proc /mnt/proc
  mount --bind /dev /mnt/dev
  mount --bind /dev/pts /mnt/dev/pts

  chroot /mnt ./usr/sbin/grub-install /dev/sda

• C

  Intel NUC UEFI PXE menu
  • chris_unit

  10
  0
  Votes
  10
  Posts
  100
  Views

  

  @chris_unit said in Intel NUC UEFI PXE menu:

  and set the vendor class to PXEClient:Arch:00007
  is that the right vendor class for an intel nuc?

  I can’t answer that. I can tell you it will either be type 7 or 9 for 64 bit uefi computers.

  If you want to find out what type the nucs are setup wireshark on a witness computer (second computer on the same subnet). Run a capture filter of port 67 or port 68 PXE boot the target computer. In the Discover packet sent out by the target computer, in the dhcp option 93 or 94 (sorry can’t remember at the moment) the target computer tells the dhcp server what type it is.

• P

  Upgrade Debian to bullseye
  • plegrand

  3
  0
  Votes
  3
  Posts
  84
  Views

  P

  @sebastian-roth
  I completed the upgrade without any major problems.
  I had to reinstall some php packages that had been removed during the upgrade
  (the comparison between the packages installed on the old version and the new one allowed me to reinstall them easily)

  I also had to re-run installfog.sh because I had the same problem as here:
  https://forums.fogproject.org/topic/15254/503-service-unavailable-after-debian-upgrade.

  Also, unrelated to fog, I had to review the configuration of mariadb and more particularly the authentication mode of the “root@localhost” user.
  Indeed the user “root@localhost” was still using authentication with a password, but the new method is to use auth_socket :

  +-----------+------------------+-----------------------+-------------------------------------------+ | Host | User | plugin | authentication_string | +-----------+------------------+-----------------------+-------------------------------------------+ | localhost | root | mysql_native_password | XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX | +-----------+------------------+-----------------------+-------------------------------------------+ | Host | User | plugin | authentication_string | +-----------+------------------+-----------------------+-------------------------------------------+ | localhost | root | unix_socket |

  this is all I can say

• C

  PHP problem after FOG update
  • Captain_Adam

  5
  0
  Votes
  5
  Posts
  69
  Views

  

  @george1421 Well I’m kind of answering my own question here.

  php -m | grep -e gettext -e mysqli

  If they are installed on the OPs system then they should be visible with the php -m command.

• J

  Resize CentOS7 fails e2fsck
  • JasonNaughton

  6
  0
  Votes
  6
  Posts
  255
  Views

  S

  @JasonNaughton As we had another person run into a similar looking issue I had a closer look at the code and might have found why this happens. Please find all the details here: https://forums.fogproject.org/post/144691