• Dell Optiplex 7020: Multicast problem

    Unsolved
    1
    0 Votes
    1 Posts
    885 Views
    No one has replied
  • Help needed for multiple Ubuntu desktops deployment

    Unsolved
    4
    0 Votes
    4 Posts
    895 Views
    george1421G

    @uzee FOG doesn’t change or really step into the target system during deployment. You CAN do this if you write a post install script that will get called once the target image is deployed to the target computer. In the case of a linux computer you could potentially set the target computer’s name here by updating the /etc/hostname file or anything else you can do with a bash script. The FOG Client can also be configured to make changes to the target computer or install applications based on instructions from the fog server. Its really identifying what you want to do and how much automation you want to script. Its all possible with FOG and a little creativity on your end. Since you already know Ubuntu (linux) bending FOG to what you want will be easier than coming strictly from a MS Windows background.

  • multicast flow

    Unsolved
    2
    0 Votes
    2 Posts
    845 Views
    S

    version is 1.5.10

  • Image capture issue from VM

    Unsolved
    4
    0 Votes
    4 Posts
    867 Views
    U

    I was not able to figure out capturing the image from a VM, I decided to use an actual desktop as the master/golden image. It made more sense as it would include the right hardware type, drivers, etc. I have captured the image finally. Now on to deployment

  • FOGBackup.sh does not back up the database

    Unsolved
    1
    0 Votes
    1 Posts
    799 Views
    No one has replied
  • No Network Interfaces Found Error

    Unsolved
    4
    0 Votes
    4 Posts
    865 Views
    george1421G

    @Ryxn I checked and that nic has been in the linux kernel for several years.

    And secondly when you checked for missing firmware the kernel wasn’t complaining about missing something.

    Its a good thing you were able to get the error while in debug mode. Because that was going to be the next quest for you. To get the system when its behaving badly.

    So when you get it into debug mode and its complaining about no nic lets do the following.

    ip a s should show if the network interface has an ip address, I’m going to suspect no because it complained about it earlier in the boot process.

    lspci -k -nn | more Look through this list until you find the entry. The number in the square brackets will be what you posted earlier. [8086&1502]. See if the nic is visible to the kernel. AND if it is it should mention what kernel driver its using. I’ll give you a for example using my laptop.

    0000:00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection ( 13) I219-V [8086:15fc] (rev 20) Subsystem: Dell Ethernet Connection (13) I219-V [1028:0a22] Kernel driver in use: e1000e Kernel modules: e1000e

    lastly if everything looks good, kernel sees the nic, there is a kernel driver assigned. Lets see if time fixes your problem.

    When you ran the ip a s command it listed all of the network interfaces and if it has IP addresses. You will need to know the interface name for your network adapter. It may be something like eno1 or ens192, or something else. Get that device name.

    Now run this command /sbin/udhcpc -i $iface --now replacing the whole word $iface with the device name listed from the ip command. This will tell the network adapter to again poll for an IP address from your dhcp server. If it picks up an IP address this time, then time does solve your problem and you will need to look into your network configuration and make sure that port-fast or fast-stp is enabled on your network port.

  • FOG Dashboard showing wrong date of captured images?

    Unsolved
    1
    0 Votes
    1 Posts
    689 Views
    No one has replied
  • Literally cant even run ./installfog.sh -_-

    Unsolved
    5
    0 Votes
    5 Posts
    825 Views
    J

    @tacOS said in Literally cant even run ./installfog.sh -_-:

    I keep getting told to run “su -” or “sudo -i”, while and after having run one, the other, or BOTH. just the same error over and over.

    It’s a workaround but I managed to continue by editing installfog.sh and deleting the if-fi block that has this message. I think it’s using a very specific way of testing that might not work in every distro ( like the previous block that checks if the user ID is 0 to see if it’s root and it won’t work on distros that randomize the root’s ID). I’m working on Garuda Linux (Arch based), and I’ve hit another wall at the end with TFT but at least it’s installed.

  • Different distribution

    Unsolved
    1
    0 Votes
    1 Posts
    453 Views
    No one has replied
  • Resize Test Failed - Could not adjust bad sector list - But drive is clean

    Unsolved
    3
    0 Votes
    3 Posts
    548 Views
    F

    @Small0145 No, it’s not.

  • [BUG] iPXE Boot Loop & Menu Failure After FOG 1.5.10.1660 Upgrade

    Unsolved
    22
    0 Votes
    22 Posts
    3k Views
    S

    @george1421 said in [BUG] iPXE Boot Loop & Menu Failure After FOG 1.5.10.1660 Upgrade:

    If undionly.kpxe worked in bios mode then snp.efi should work in uefi mode

    Hi George, the BIOS claims its in UEFI mode but when booting it looks suspiciously like legacy (larger text etc). Its an old Viglin with a second generation i3 which is being retired this October so its not too much of a deal now I have a workaround.

  • Mellanox ConnectX 3 imaging issues.

    Unsolved
    6
    0 Votes
    6 Posts
    732 Views
    george1421G

    @aurfalien said in Mellanox ConnectX 3 imaging issues.:

    So all good here.

    Did FOS Linux have the driver enabled for that 10GbE card (i.e. were you able to image with FOG once you got past the iPXE menu)?

    FWIW: For uefi mode snp.efi or snponly.efi should work if undionly.kpxe worked in bios mode. I’m saying it should because ConnectX3 is a somewhat older card (circa 2017/2018).

  • Unable to install Fog successfully.

    Unsolved
    10
    0 Votes
    10 Posts
    2k Views
    george1421G

    @punch07 to view the /tftpboot use the command line terminal window. Now I do have to say that different distros have the directory in different locations like /var/lib/tftpboot.

  • ASUS NUC14MNK fos kernel no netwerk drivers

    Unsolved
    29
    0 Votes
    29 Posts
    5k Views
    R

    @Eazis I created an experimental kernel that includes the drivers to fix this issue. Would you be willing to test it and let us know how it goes?

  • Capture not finishing in NAT environment

    Unsolved
    1
    0 Votes
    1 Posts
    356 Views
    No one has replied
  • Localstorage randomly selected

    Unsolved
    1
    0 Votes
    1 Posts
    302 Views
    No one has replied
  • Issues with upgrading to FOG 1.5.10 from 1.5.4 on CentOS 7.5.1804

    Solved
    3
    0 Votes
    3 Posts
    274 Views
    M

    There is a BIOS update for the MiniX PCs that allows the PCs to be built from FOG 1.5.4 running on CentOS 7.5.2009.

    I do not know the technicalities but upgrading from verion 6 to 8, was mentioned.

  • Issues capturing image on Dell Pro 16+ Laptops

    Unsolved
    3
    0 Votes
    3 Posts
    452 Views
    W

    @george1421 This worked! Thank you so much for your help!

  • Replication Issues

    Unsolved
    1
    0 Votes
    1 Posts
    204 Views
    No one has replied
  • iPXE fog boot menu error Could not boot: Results too large

    Unsolved
    4
    0 Votes
    4 Posts
    406 Views
    george1421G

    @Jias94 Hey no worries, I’ve created that error a few times myself so I had a good idea where to look. I’m glad you have it sorted out and can get back to imaging.

115

Online

12.3k

Users

17.4k

Topics

155.6k

Posts