• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Gordon Taylor
    3. Posts
    • Profile
    • Following 0
    • Followers 0
    • Topics 7
    • Posts 35
    • Best 2
    • Controversial 0
    • Groups 0

    Posts made by Gordon Taylor

    • RE: rEFInd reboots instead of loading windows

      ok i did have a 1703 image but it does similar now it reboots then drops through to automatic repair blue screen in this case (but then its a sealed sysprep image - rather than a image that has been through the whole process) - if i pull the lan out to let it finish the windows setup then the behaviour is the same as 1709 - reboot then next time sat on preparing automatic repair splash screen.

      i also have slightly different behaviour from NUC6i5SYK which doesn’t reboot but just sits with the windows logo on the screen and doesn’t boot up (no disk activity) again saying preparing automatic repair

      i think there is a message from rEFInd but it flashes to quickly is there a way to interactively watch that step by step by editing refind.conf?

      of course if you pull the LAN cable out so it doesn’t network boot they all boot fine.

      posted in FOG Problems
      Gordon TaylorG
      Gordon Taylor
    • RE: rEFInd reboots instead of loading windows

      ok there isn’t anything in the apache log (/var/log/apache2/error.log) unless i change it to debug then there is lots but nothing that looks bad

      [Mon Mar 19 15:58:22.168627 2018] [authz_core:debug] [pid 45559] mod_authz_core.c(809): [client 192.168.4.31:54649] AH01626: authorization result of <RequireAny>: granted
      [Mon Mar 19 15:58:22.283609 2018] [authz_core:debug] [pid 45559] mod_authz_core.c(809): [client 192.168.4.31:54649] AH01626: authorization result of Require all granted: granted
      [Mon Mar 19 15:58:22.283653 2018] [authz_core:debug] [pid 45559] mod_authz_core.c(809): [client 192.168.4.31:54649] AH01626: authorization result of <RequireAny>: granted
      [Mon Mar 19 15:58:22.439171 2018] [authz_core:debug] [pid 45559] mod_authz_core.c(809): [client 192.168.4.31:54649] AH01626: authorization result of Require all granted: granted
      [Mon Mar 19 15:58:22.439192 2018] [authz_core:debug] [pid 45559] mod_authz_core.c(809): [client 192.168.4.31:54649] AH01626: authorization result of <RequireAny>: granted
      [Mon Mar 19 15:58:22.486550 2018] [authz_core:debug] [pid 45559] mod_authz_core.c(809): [client 192.168.4.31:54649] AH01626: authorization result of Require all granted: granted
      [Mon Mar 19 15:58:22.486570 2018] [authz_core:debug] [pid 45559] mod_authz_core.c(809): [client 192.168.4.31:54649] AH01626: authorization result of <RequireAny>: granted
      
      

      some of the workstations after rebooting once then get stuck with the windows boot splash screen and saying Perpairing Automatic Repair at the bottom… almost like its maybe booting the recovery partition… but its not doing anything no disk activity just stuck untill rebooted…

      the only os I’ve tried so far is Win10 1709 i think i might have a uefi 1607 or 1703 image i can try see if it happens across different host oses…

      posted in FOG Problems
      Gordon TaylorG
      Gordon Taylor
    • rEFInd reboots instead of loading windows

      on Friday i upgraded Fog to 1.5.0 from i think 1.5.0 RC12 and since then the Intel NUCs i have that are UEFI boot have now started rebooting instead of loading windows after rEFInd. i don’t know if its all my UEFI clients yet as i’ve disabled the Network booting on the main LAN whilst i troubleshoot it.

      I have tried from the backups that appear in the home/user folder replacing a few things, I’ve replaced /var/www/html/fog/service/ipxe both refind.conf and refind.efi
      i’ve also tried using the tftp.previous instead of tftp encase it was iPXE
      but it doesn’t make a difference.

      a couple of NUCs that are experiancing this D54250WYK and NUC5i5RYK

      posted in FOG Problems
      Gordon TaylorG
      Gordon Taylor
    • RE: FOG with UEFI - rEFInd Error: Failure booting legacy (BIOS) OS

      @sebastian-roth Thanks 🙂

      posted in General Problems
      Gordon TaylorG
      Gordon Taylor
    • RE: FOG with UEFI - rEFInd Error: Failure booting legacy (BIOS) OS

      where would i find the refind.conf file on the fog server?

      posted in General Problems
      Gordon TaylorG
      Gordon Taylor
    • RE: Organizations Using FOG

      Organization Name: The Crypt School

      Location: Gloucester, Gloucestershire, Great Britain

      Approximate Number of systems: Approx 400

      How long: i cant quite remember somewhere between 5 and 7 years. since XP was on our desktops anyways… ive had 3 Fog servers going back before 0.3x thats for sure…

      http://www.cryptschool.org/images/logo-crypt.jpg

      posted in General
      Gordon TaylorG
      Gordon Taylor
    • RE: Attempting to check in................... Failed

      @Tom-Elliott Thanks i did svn up and then re-installed and it looks like its all good again 🙂

      posted in Bug Reports
      Gordon TaylorG
      Gordon Taylor
    • RE: Attempting to check in................... Failed

      Thanks, ill give it ago tomorrow ive gone home now 🙂

      posted in Bug Reports
      Gordon TaylorG
      Gordon Taylor
    • Attempting to check in................... Failed
      Server
      • FOG Version: SVN 6047
      • OS: Ubuntu Linux 14.04.5
      Client
      • Service Version: 1.3.0-RC-36
      • OS: Windows 10
      Description

      When trying to deploy an image the it is stuck saying Attempting to check in… Failed
      (in line for X) where X starts at 5 and goes up in increments of 5 looks like seconds cause after 60 its 1:5

      The Apache Log has the lots of lines like this in it.

      [Tue Dec 13 18:28:38.228654 2016] [php7:error] [pid 1533] [client 192.168.19.14:54886] PHP Fatal error: Uncaught Error: Using $this when not in object context in /var/www/html/fog/lib/reg-task/taskingelement.class.php:206\nStack trace:\n#0 /var/www/html/fog/lib/reg-task/taskingelement.class.php(124): TaskingElement::checkStorageNodes(Object(StorageGroup))\n#1 [internal function]: TaskingElement->__construct()\n#2 /var/www/html/fog/lib/fog/fogbase.class.php(391): ReflectionClass->newInstanceArgs(Array)\n#3 /var/www/html/fog/service/Pre_Stage1.php(23): FOGBase::getClass(‘TaskQueue’)\n#4 {main}\n thrown in /var/www/html/fog/lib/reg-task/taskingelement.class.php on line 206

      posted in Bug Reports
      Gordon TaylorG
      Gordon Taylor
    • RE: Error fog booting from san device 0x80 after deploy

      I’ve swapped to grub and so far I’ve not seen anything fail 🙂 but it would be good if it could be per workstation configurable at some point 🙂

      posted in FOG Problems
      Gordon TaylorG
      Gordon Taylor
    • RE: Error fog booting from san device 0x80 after deploy

      is this possible to do on a per workstation basis? I only have a handful of workstations that don’t work with sanboot?

      posted in FOG Problems
      Gordon TaylorG
      Gordon Taylor
    • Chainload Fog 0.32 from Fog 1.1.2 menu

      I was wondering if i could add my old server into the advanced menu of my new server to make it easier to download images from the old server as i migrate workstations over to the new one?

      ive seen a thread or two about doing it the other way around but not this way… i wouldn’t know where to start with the ipxe menu item :-s i did get Clonezilla and Seatools successfully working with the following menu though 🙂

      menu
      item --gap – ---------------- iPXE boot menu ----------------
      item Clonezilla Clonezilla Network Boot
      item SeaTools Seatools 2.2
      item shell ipxe shell
      item ipxedemo ipxedemo
      item return return to previous menu
      choose --default Clonezilla --timeout 5000 target && goto ${target}

      :Clonezilla
      kernel http://${fog-ip}/pxetools/clonezilla/vmlinuz
      initrd http://${fog-ip}/pxetools/clonezilla/initrd.img
      imgargs vmlinuz boot=live config noswap nolocales edd=on nomodeset ocs_live_run=“ocs-live-general” ocs_live_extra_param=“” ocs_live_keymap=“” ocs_live_batch=“no” ocs_daemonon=“ssh” usercrypted=Kb/VNchPYhuf6 ocs_lang=“” vga=788 nosplash noprompt fetch=http://${fog-ip}/pxetools/clonezilla/filesystem.squashfs
      boot || goto MENU

      :SeaTools
      initrd http://${fog-ip}/pxetools/seatools/SeaToolsDOS223ALL.ISO || prompt
      chain http://${fog-ip}/${fog-webroot}/service/ipxe/memdisk iso raw || prompt
      boot || prompt
      goto MENU

      :ipxedemo
      chain http://boot.ipxe.org/demo/boot.php ||
      goto MENU

      :shell
      shell ||
      goto MENU

      :return
      chain http://${fog-ip}/${fog-webroot}/service/ipxe/boot.php?mac=${net0/mac} ||
      prompt
      goto MENU

      autoboot [/CODE]

      posted in General
      Gordon TaylorG
      Gordon Taylor
    • RE: Fog 1.1.1 and a UEFI only laptop

      Ok thanks for the Update… yes i had disabled secure boot 🙂 I’ll have to think about something a bit more complex with VLANs or something so i can UEFI boot some stuff and UNDI boot the others :s…

      posted in FOG Problems
      Gordon TaylorG
      Gordon Taylor
    • RE: TFTP Issues "File not Found"

      set option 67 to undionly.kpxe

      posted in FOG Problems
      Gordon TaylorG
      Gordon Taylor
    • Fog 1.1.1 and a UEFI only laptop

      Hi There, i’m in the process of building my Fog 1.1.1 server to replace my 0.32 server in due course. the Main reason is that we now have some laptops that are UEFI boot only (no legacy option)

      I can using undiony.kpxe get our older systems to boot and register in the new Fog server but the new laptops don’t boot.
      it starts booting over IPv4
      then it says Succeed to download NBP File.
      then it trys to boot over IPv6 then it eventually (we don’t have DHCP for IPv6) either tries to boot of the Local disk or if i pull the drive out just says no boot devices.

      if i change the bootfile to snponly.efi the UEFI laptop gets to the boot menu but if you choose register it loads init.xz then goes back to trying to IPv6 PXE boot. the old systems simply hang on network boot after displaying the IP address, GUID, gateway etc…

      is it possible to allow bot types UEFI and Legacy boot?

      posted in FOG Problems
      Gordon TaylorG
      Gordon Taylor
    • 1
    • 2
    • 2 / 2