• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Quazz
    3. Posts
    Q
    • Profile
    • Following 3
    • Followers 2
    • Topics 27
    • Posts 1,977
    • Groups 3

    Posts

    Recent Best Controversial
    • RE: [Solved] Migrated /images folder

      @Fimlore I don’t think the path is wrong. First one is the nfs path to the FOG server and second is the image name (you can see this in the kernel variables in your screenshot)

      192.168.68.14:/images/FOGImages/
      QAD-Teamwork
      

      You can schedule a deploy (debug) for a registered host (type fog then enter to start deployment process)

      Is this image non-resizable per chance?

      posted in General Problems
      Q
      Quazz
    • RE: [Solved] Migrated /images folder

      @Fimlore Yes, the FOS environment mounts your image location to /images on the client.

      You can actually see your image location in the kernel arguments, which seems to be correct.

      If I rename the folder to be like one of the working images

      What do you mean by that?

      What do the image settings look like? Are they different from the old ones?

      posted in General Problems
      Q
      Quazz
    • RE: Images are created with 777 (world writable file rights) and owner root on CentOS 7

      @aborn The files are never chowned. I suspect this is because the initial copy uses nfs which runs as a service under the root user on the server.

      You can try changing

      sed -i -e "s#chmod -R 777#chmod -R 774#gi" /usr/share/fog/lib/funcs.sh
      

      to

      sed -i -e 's#chmod -R 777#chown -R fog:root "$imagePath";chmod -R 774#gi' /usr/share/fog/lib/funcs.sh
      

      I fear this won’t work, but it’s the only quick hack that I can think of right now that might.

      posted in Linux Problems
      Q
      Quazz
    • RE: [Solved] Migrated /images folder

      @Fimlore You have to change the path in a couple of places

      The storage node image path has to be adjusted on the WebGUI of the server.

      Then on the server itself:

      /opt/fog/.fogsettings : storageLocation
      

      If you let FOG build exports automatically, then just rerun the installer after that change.

      If not, you have to edit /etc/exports

      Do be careful of ownership and permissions in a shared image location.

      posted in General Problems
      Q
      Quazz
    • RE: FOG Kernel panic at startup with some systems

      @mckayj That’s great news! I’m not sure why x2apic support wasn’t enabled. As far as I know, it’s typically only used for multi CPU systems which aren’t your typical usecase for FOG I suppose. It’s very strange that it would be enabled on a single CPU board to me, but there you go anyway.

      @Sebastian-Roth
      I don’t think it will harm anything if we enable x2apic support going forward, it can always be disabled with a kernel parameter on boot anyway.

      posted in FOG Problems
      Q
      Quazz
    • RE: Images are created with 777 (world writable file rights) and owner root on CentOS 7

      @aborn Only for /images

      Since you are reducing permissions for “everyone” (which is ok since FOG should connect with the fog user account), you need to ensure the folder structure where it places the images has the correct ownership.

      chown -R fog:root /images

      probably works fine too.

      New images should have fog as the owner as far as I’m aware.

      posted in Linux Problems
      Q
      Quazz
    • RE: Images are created with 777 (world writable file rights) and owner root on CentOS 7

      @aborn Postinit runs just after the kernel and init files load in on the client. (not on the server)

      It will work on the unpacked filesystem in memory on the client device before the capturing of the image takes place.

      It will work just fine.

      posted in Linux Problems
      Q
      Quazz
    • RE: FOG Kernel panic at startup with some systems

      @mckayj Okay, I think this one should have it enabled

      https://drive.google.com/open?id=1ZiRWrrN3dv26bLwW8GAEdLtzGw5xkyQI

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG Kernel panic at startup with some systems

      @mckayj I’m not a kernel guru, but I’d be interested to seeing what would happen if you were to boot using a kernel that has x2apic support. From some light googling, it seems to suggest a kernel panic is normal behavior if x2apic is enabled in BIOS (even if you can’t see the option), but the support isn’t in the kernel.

      Trying to compile said kernel now.

      posted in FOG Problems
      Q
      Quazz
    • RE: Image files and Snapin files not deleted

      Did you change any of those passwords or were they already correct?

      Do you use the fog user account at all? (don’t)

      Anything in the apache error logs?

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG Kernel panic at startup with some systems

      Would be interesting to see if they can boot a live USB of say Ubuntu 18.04.

      Additionally, I think you should be able to scroll up a bit using shift + pageup iirc, there might be some useful info up there.

      Also, does this happen on all the nodes?

      posted in FOG Problems
      Q
      Quazz
    • RE: Images are created with 777 (world writable file rights) and owner root on CentOS 7

      @aborn I am unsure if the FTP client would be able to move the images, but you can change the chmod comment using a postinit script.

      It might work fine if you chown -R fog:fog first, though.

      At any rate in /images/dev/postinitscripts/fog.postinit try adding the following:

      sed -i -e "s#chmod -R 777#chmod -R 774#gi" /usr/share/fog/lib/funcs.sh
      

      The permissions are set twice, once before imaging (so files can be put there) and once after imaging (in case the files are created with different permissions for some reason).

      You’ll have to test which permissions actually work yourself.

      posted in Linux Problems
      Q
      Quazz
    • RE: TFTP Server requires manual entry

      @neiliob1973 “The best solution” depends on your situation. In a perfect world, you shut down other DHCP servers and let FOG handle it all and it will work out of the box basically.

      However due to policies, preferences or certain restrictions sometimes you are stuck with another DHCP server, this is where dnsmasq comes in with proxy mode. (basically piggybacks the other DHCP server and sends only the PXE boot info)

      I do think this may struggle or not work as expected if the original DHCP server is also sending PXE boot info, from what I remember anyway. And certain clients for some reason don’t like it very much either.

      posted in Linux Problems
      Q
      Quazz
    • RE: upgraded to Ubuntu 18.04.1 LTS

      @Boyan-Biandov said in upgraded to Ubuntu 18.04.1 LTS:

      @Wayne-Workman Great link Wayne, I am actually going to do this myself very soon, one point of clarification if I may: section “Arranging Images”. Is it really necessary to copy the images to a folder, other than /images on the new fog server and then once they are copied there “rearrange” them by moving them again into the final destination of /images (assuming fog defaults)?

      Imagine scenario A: You are busy capturing a new version of your image and someone attempts to deploy that image. They will get an incomplete and broken image and the install has failed.

      Imagine scenario B: You are busy capturing a new version of your image but something goes wrong! The image is now in an incomplete/broken state and you have no way of knowing for how long that will be the case! Not very practical.

      So yeah, there are legitimate reasons for using a ‘temporary directory’ if you will.

      posted in FOG Problems
      Q
      Quazz
    • RE: Tablet PC hangs on bzImage

      @Zerpie Did you ever end up trying the has_usb_nic=1 kernel argument?

      posted in FOG Problems
      Q
      Quazz
    • RE: Erasing current MBR/GPT tables.... taking about 5-10 minutes

      @andreiv Use kernel 4.15.2 for now.

      A lot of work has gone into tracking down the source of the problem, which we believe we have found. Now it’s just a matter of formulating a fix for it and getting it pushed.

      People are quite busy though, so unsure when that’s going to be, but it is being worked on still.

      posted in FOG Problems
      Q
      Quazz
    • RE: problem ACPI error

      @WhiteNovaKnight Have you tried the kernel parameter?

      posted in FOG Problems
      Q
      Quazz
    • RE: Web Page Text Box Bigger

      You can grab and drag the bottom right corner of it to resize it

      posted in FOG Problems
      Q
      Quazz
    • RE: problem ACPI error

      @WhiteNovaKnight Set acpi=off under kernel parameters (or arguments) either on the host definition or under the General settings of FOG.

      It’s just a field on the WebUI

      posted in FOG Problems
      Q
      Quazz
    • RE: Dell Precision Tower 5820 - FlexBay MiniSAS PCIe NVMe SSD not recognized

      Because they’re marked as ODD, they might be on a different controller altogether and possibly with more limited functionality too.

      posted in Hardware Compatibility
      Q
      Quazz
    • 1 / 1