• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. JGeear
    • Profile
    • Following 0
    • Followers 0
    • Topics 4
    • Posts 13
    • Best 1
    • Controversial 0
    • Groups 0

    JGeear

    @JGeear

    1
    Reputation
    442
    Profile views
    13
    Posts
    0
    Followers
    0
    Following
    Joined Last Online

    JGeear Unfollow Follow

    Best posts made by JGeear

    • RE: Moving FOG's /images files off the root partition 2017 edition

      @george1421 said in Moving FOG's /images files off the root partition 2017 edition:

      touch /opt/fog/snapin.chk

      Tutorial worked like a charm! The is some minor errors as follows:

      The following line needs bind bind 0 0 added
      /opt/fog/snapins /opt/fogdisk/snapins bind bind 0 0

      and the Snapin test file needs to be in the right directory!
      touch /opt/fog/snapins/snapin.chk

      posted in Tutorials
      JGeearJ
      JGeear

    Latest posts made by JGeear

    • RE: FOG Update errors

      @Tom-Elliott said in FOG Update errors:

      ./installfog.sh -y

      Thanks Tom! I am up and running again!

      posted in Linux Problems
      JGeearJ
      JGeear
    • RE: FOG Update errors

      @Tom-Elliott Awesome that worked I was able to complete the update. I did receive a error unable to update database. Apache error log.

      [Wed Aug 07 16:02:42.370052 2024] [proxy_fcgi:error] [pid 207214] [client 10.160.241.168:57856] AH01071: Got error 'PHP message: PHP Parse error:  syntax error, unexpected token "<<" in /var/www/fog/lib/fog/system.class.php on line 56'
      [Wed Aug 07 16:02:45.486205 2024] [proxy_fcgi:error] [pid 207210] [client 10.160.241.168:57855] AH01071: Got error 'PHP message: PHP Parse error:  syntax error, unexpected token "<<" in /var/www/fog/lib/fog/system.class.php on line 56'```
      posted in Linux Problems
      JGeearJ
      JGeear
    • RE: FOG Update errors

      @Fog_Newb
      I receive the following messages trying to do a dev-branch and git pull.
      FOG.png

      posted in Linux Problems
      JGeearJ
      JGeear
    • FOG Update errors

      I had install errors updating my Trunk version on Ubuntu 20.04 LTS. I updated Ubuntu to 22.04 LTS. Now I am receiving a GIT conflict on the git pull a install script error

      posted in Linux Problems
      JGeearJ
      JGeear
    • Image USB drive

      I have Dell OptiPlex 3070’s that we UEFI PXE Boot with a USB stick. The FOG server is running on Ubuntu 16.04 and the FOG version is 1.5.9.59. The Dell BIOS is set to RAID by default and when we try to image a PC it tries to image the USB drive and fails. The work around is to switch the SATA settings to AHCI. We are then able to image the PC and save the USB drive from being corrupted and repaired with Diskpart.

      posted in FOG Problems
      JGeearJ
      JGeear
    • RE: Moving FOG's /images files off the root partition 2017 edition

      @george1421 said in Moving FOG's /images files off the root partition 2017 edition:

      touch /opt/fog/snapin.chk

      Tutorial worked like a charm! The is some minor errors as follows:

      The following line needs bind bind 0 0 added
      /opt/fog/snapins /opt/fogdisk/snapins bind bind 0 0

      and the Snapin test file needs to be in the right directory!
      touch /opt/fog/snapins/snapin.chk

      posted in Tutorials
      JGeearJ
      JGeear
    • RE: Maybe the USB cable is bad

      @JGeear
      I purchased a Dell USB 3.0 to Ethernet adapter with PXE boot. It worked perfectly!

      posted in Hardware Compatibility
      JGeearJ
      JGeear
    • RE: Maybe the USB cable is bad

      @fry_p said in Maybe the USB cable is bad:

      has_usb_nic=1

      Yeah, it still displays the warnings!

      posted in Hardware Compatibility
      JGeearJ
      JGeear
    • RE: Maybe the USB cable is bad

      @Quazz

      This worked as well and still displayed the messages.

      posted in Hardware Compatibility
      JGeearJ
      JGeear
    • RE: Maybe the USB cable is bad

      @dylan123 said in Maybe the USB cable is bad:

      c
      That worked! It stills outputs the message. Cheers!

      0_1493855671484_IMG_0150.JPG

      posted in Hardware Compatibility
      JGeearJ
      JGeear