Navigation

    FOG Project

    • Register
    • Login
    • Search
    • Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    1. Home
    2. geardog
    G
    • Profile
    • Following
    • Followers
    • Topics
    • Posts
    • Best
    • Groups

    geardog

    @geardog

    4
    Reputation
    57
    Posts
    427
    Profile views
    0
    Followers
    0
    Following
    Joined Last Online

    geardog Follow

    Best posts made by geardog

    • RE: NVME boot drive not found after image capture .. doh !

      So the trouble I’ve had with this box is that it falls in the middle of the bios/UEFI game. I’m dealing with Win7 (doesn’t play UEFI) and an i210 NIC (doesn’t seem to play Legacy). Upping to Win10, and booting fully UEFI would be the fix for this last quibble with this box.

      posted in Hardware Compatibility
      G
      geardog
    • RE: A couple images won't shrink/resize on capture..

      @george1421

      I feel like a bit of a dummy. It works now, and I suspect I just needed to run the “chkdsk /f” from prompt instead of what I figure is the less thorough one from disk properties. For completeness I’ve included what didn’t work.

      Nice thought, but the thread you note doesn’t hold my solution.
      https://forums.fogproject.org/topic/10824/image-upload-deploy-taking-a-long-time/43
      Bit locker is off as evidenced by the encryption control commands.
      manage-bde -off 😄
      manage-bde -status 😄

      “Way 1” from the FOG wiki made no change either.
      https://wiki.fogproject.org/wiki/index.php?title=Windows_Dirty_Bit

      I believe command prompt “chkdsk /F” corrected the issue. I had previously just used disk check from disk properties, which doesn’t lock the drive. This was, however, in conjunction with a bios setting dealing with power saving that was causing hangs.

      posted in Windows Problems
      G
      geardog
    • RE: Cannot find disk on system, NVMe, RAID mode, Intel RST

      @Sebastian-Roth

      lspci -nn showed the drive to be in raid mode

      using a tutorial on bcdedit via cmd for safemode boot I was able to change the setting without reinstalling windows

      now the machine is imaged

      resolved and thankyou

      coming back to this with a fresh mind and some new info helped

      posted in Hardware Compatibility
      G
      geardog
    • RE: No configuration methods succeeded (I210 NIC) HP-Z240

      @george1421

      Tried disabling Spanning tree with no effect.

      It turned out to be a bios/UEFI setting “option rom launch policies.” New to me. In my defense, this box’s bios is pretty massive and clumsy to navigate through, but works now!
      I feel stupid, but my issue appears resolved! Thank you very much George. I might not have ever stumbled through those screens again if it weren’t for you.

      As an aside, the MAC address cloning is a little odd as fog find and tries to get an IP on the wrong NIC first, before it gives up and tries the next NIC.

      posted in Hardware Compatibility
      G
      geardog

    Latest posts made by geardog

    • RE: connection timed out chainloading failed

      @sebastian-roth
      No adjustments have been made. I was waiting for this to play out.

      posted in FOG Problems
      G
      geardog
    • RE: connection timed out chainloading failed

      @sebastian-roth said in connection timed out chainloading failed:

      tcpdump -i enp5s0 port 67 or port 68 -e -n -vv

      No mention of next server.

      [root@Clear0 etc]# tcpdump -i enp17s0f0 port 67 or port 68 -e -n -vv
      tcpdump: listening on enp17s0f0, link-type EN10MB (Ethernet), capture size 262144 bytes
      11:24:14.566873 1c:6f:65:83:a0:95 > Broadcast, ethertype IPv4 (0x0800), length 590: (tos 0x0, ttl 20, id 1, offset 0, flags [none], proto                                                                                                    UDP (17), length 576)
          0.0.0.0.bootpc > 255.255.255.255.bootps: [udp sum ok] BOOTP/DHCP, Request from 1c:6f:65:83:a0:95, length 548, xid 0x6783a095, secs 8,                                                                                                    Flags [Broadcast] (0x8000)
                Client-Ethernet-Address 1c:6f:65:83:a0:95
                Vendor-rfc1048 Extensions
                  Magic Cookie 0x63825363
                  DHCP-Message Option 53, length 1: Discover
                  Parameter-Request Option 55, length 36:
                    Subnet-Mask, Time-Zone, Default-Gateway, Time-Server
                    IEN-Name-Server, Domain-Name-Server, RL, Hostname
                    BS, Domain-Name, SS, RP
                    EP, RSZ, TTL, BR
                    YD, YS, NTP, Vendor-Option
                    Requested-IP, Lease-Time, Server-ID, RN
                    RB, Vendor-Class, TFTP, BF
                    Option 128, Option 129, Option 130, Option 131
                    Option 132, Option 133, Option 134, Option 135
                  MSZ Option 57, length 2: 1260
                  GUID Option 97, length 17: 0.49.67.54.70.54.53.56.51.65.48.57.53.255.255.255.255
                  ARCH Option 93, length 2: 0
                  NDI Option 94, length 3: 1.2.1
                  Vendor-Class Option 60, length 32: "PXEClient:Arch:00000:UNDI:002001"
      11:24:14.567192 00:15:17:c4:a9:92 > Broadcast, ethertype IPv4 (0x0800), length 366: (tos 0xc0, ttl 64, id 2182, offset 0, flags [none], pr                                                                                                   oto UDP (17), length 352)
          172.17.17.1.bootps > 255.255.255.255.bootpc: [bad udp cksum 0xbe6f -> 0x1006!] BOOTP/DHCP, Reply, length 324, xid 0x6783a095, secs 8,                                                                                                    Flags [Broadcast] (0x8000)
                Your-IP 172.17.17.191
                Server-IP 172.17.17.1
                Client-Ethernet-Address 1c:6f:65:83:a0:95
                Vendor-rfc1048 Extensions
                  Magic Cookie 0x63825363
                  DHCP-Message Option 53, length 1: Offer
                  Server-ID Option 54, length 4: 172.17.17.1
                  Lease-Time Option 51, length 4: 43200
                  RN Option 58, length 4: 21600
                  RB Option 59, length 4: 37800
                  Domain-Name Option 15, length 22: "xxx"
                  Domain-Name-Server Option 6, length 12: 172.17.17.16,172.17.17.17,172.17.17.1
                  Default-Gateway Option 3, length 4: 172.17.17.1
                  BR Option 28, length 4: 172.17.17.255
                  Subnet-Mask Option 1, length 4: 255.255.255.0
      11:24:14.574606 00:15:5d:02:0a:16 > Broadcast, ethertype IPv4 (0x0800), length 374: (tos 0xc0, ttl 64, id 10347, offset 0, flags [none], p                                                                                                   roto UDP (17), length 360)
          172.17.17.82.bootps > 255.255.255.255.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length 332, xid 0x6783a095, secs 8, Flags [Broadcast] (0                                                                                                   x8000)
                Server-IP 172.17.17.82
                Client-Ethernet-Address 1c:6f:65:83:a0:95
                file "undionly.kpxe"[|bootp]
      11:24:14.575555 00:15:5d:02:0a:16 > Broadcast, ethertype IPv4 (0x0800), length 374: (tos 0xc0, ttl 64, id 10348, offset 0, flags [none], p                                                                                                   roto UDP (17), length 360)
          172.17.17.82.bootps > 255.255.255.255.bootpc: [udp sum ok] BOOTP/DHCP, Reply, length 332, xid 0x6783a095, secs 8, Flags [Broadcast] (0                                                                                                   x8000)
                Server-IP 172.17.17.82
                Client-Ethernet-Address 1c:6f:65:83:a0:95
                file "undionly.kpxe"[|bootp]
      11:24:22.585346 1c:6f:65:83:a0:95 > Broadcast, ethertype IPv4 (0x0800), length 590: (tos 0x0, ttl 20, id 2, offset 0, flags [none], proto                                                                                                    UDP (17), length 576)
      
      
      posted in FOG Problems
      G
      geardog
    • RE: connection timed out chainloading failed

      While it was discussed that fog may be the issue, talking to Sebastian had me thinking there was some debate.

      Here is the clearOS side.
      https://www.clearos.com/clearfoundation/social/community/clearos-dnsmasq-seems-to-step-on-other-nextserver-broadcasts

      His tcp dump isn’t showing a next server broadcast. I’m feeling like I may have done something wrong. hmm

      posted in FOG Problems
      G
      geardog
    • RE: connection timed out chainloading failed

      Thank you guys. If there is anything I can do to facilitate the big brains, let me know.
      George, should I email you the PCAP?

      posted in FOG Problems
      G
      geardog
    • RE: connection timed out chainloading failed

      @sebastian-roth Ah, I’m using clearOS, but I’ve left the tftp line blank, thinking it would be disabled.

      I tried pointing it at fog, at one point, but it didn’t seem to behave so I cleared the line.

      Just now I entered fog ip in the router’s tftp direction field. The client instead of attempting to boot from fog immediately gives a “media test failure” when trying to pxe boot.

      clearOS dhcp.conf (the quotes are surely wrong, but it’s in the api)
      61a7b803-e0c8-48cd-a938-a7b9a01e100b-image.png

      Clearing the field again takes me back to the start of the post and gives me the posted error. I’m not seeing anything screwy in the clearOS router, as running.

      clearOS dhcp.conf
      4369cbef-b33d-4602-be4f-b1bd881cf45a-image.png

      clearOS dnsmasq.conf
      d9e22649-4ea2-4750-8f52-1a6746b8442d-image.png

      posted in FOG Problems
      G
      geardog
    • connection timed out chainloading failed

      Fog 1.5.9 on ubu 20.04.1 VM not handling dhcp, using dnsmasq

      I feel like the flaw is the tftp:// ip address showing the gateway, but fog settings shows the correct ip of fog.

      I’m close to having it up again, but … any help would be great !

      d0360782-6df0-46d2-a310-b1c21c90d047-image.png

      38e78eef-72f5-46c4-ae6a-9fd91d8d404d-image.png

      fog-service-output.txt

      posted in FOG Problems
      G
      geardog
    • RE: ClearOS-DHCP, Fog, PXE, & dnsmasq

      @sebastian-roth

      Thanks for that. I’m using the linked tutorial in the correct context!

      Fog 1.5.9 on Ubuntu 18 (sorry) spit back an error on systemctl restart dnsmasq “Bad dhcp-range at line 38” which was caused by including the <> around the IP. wow …

      posted in FOG Problems
      G
      geardog
    • ClearOS-DHCP, Fog, PXE, & dnsmasq

      I’ve been poking around the links dealing with this, and I’m bleary-eyed.

      Keeping ClearOS in control of dhcp, how do I address PXE bios & uefi boots? I did this fine with windows 66/67 direction, but the guides don’t quite align with what I’m doing, perhaps partly because ClearOS uses dnsmasq for this, and overwrites dhcp.conf with what it finds in dnsmasq configs.

      First, am I correct in understanding that I could run dnsmasq on clear or fog box with the same effect?

      Second, if I can run dnsmasq on fog leaving dhcp to ClearOS, what modification do I need to make to the outlined ltsp.conf file found at the following link work? I’m assuming the linked tutorial fails because it is with the expectation dhcp is on fog. Commenting the last line out lets the service start without errors, but I’m not getting boot files yet.
      https://forums.fogproject.org/topic/12796/installing-dnsmasq-on-your-fog-server,

      posted in FOG Problems
      G
      geardog
    • RE: Resize failure?

      @Sebastian-Roth

      I’ve typically just restarted, but Fast start was enabled too.

      A cold boot with fast-start disabled allowed a good capture.

      Thanks so much.

      posted in General Problems
      G
      geardog
    • Resize failure?

      Running FOG 1.5.6

      Error(5): Could not map attribute 0x80 in inode 24291: Input/output error

      This is a follow up to
      https://forums.fogproject.org/topic/13334/mismatched-drive-sizes-in-win10-after-incomplete-capture-with-1-5-5

      After correcting the FS size, I ran Windows DISM clean and chkdsk /f which completed succesfully; they gave no errors. I then captured a raw image of the box which completed succesfully.

      Attempting to capture a resized image of this computer gave me this error

      f47dd505-ed4d-49bc-ada4-9c605c579ba0-image.png

      I ran chkdsk /f on the box, which completed clean before and after the imaging attempt.

      Any thoughts on cause or resolution to the error?

      Checking file system on 😄
      The type of the file system is NTFS.
      Volume label is HP.

      A disk check has been scheduled.
      Windows will now check the disk.

      Stage 1: Examining basic file system structure …
      576000 file records processed.
      File verification completed.
      12848 large file records processed.
      0 bad file records processed.

      Stage 2: Examining file name linkage …
      26147 reparse records processed.
      657814 index entries processed.
      Index verification completed.
      0 unindexed files scanned.
      0 unindexed files recovered to lost and found.
      26147 reparse records processed.

      Stage 3: Examining security descriptors …
      Cleaning up 5 unused index entries from index $SII of file 0x9.
      Cleaning up 5 unused index entries from index $SDH of file 0x9.
      Cleaning up 5 unused security descriptors.
      Security descriptor verification completed.
      40908 data files processed.
      CHKDSK is verifying Usn Journal…
      36582096 USN bytes processed.
      Usn Journal verification completed.

      Windows has scanned the file system and found no problems.
      No further action is required.

      223223172 KB total disk space.
      66502968 KB in 158976 files.
      128652 KB in 40909 indexes.
      0 KB in bad sectors.
      698964 KB in use by the system.
      65536 KB occupied by the log file.
      155892588 KB available on disk.

        4096 bytes in each allocation unit.
      

      55805793 total allocation units on disk.
      38973147 allocation units available on disk.

      Internal Info:
      00 ca 08 00 d8 0c 03 00 63 aa 05 00 00 00 00 00 …c…
      76 01 00 00 ad 64 00 00 00 00 00 00 00 00 00 00 v…d…

      Windows has finished checking your disk.
      Please wait while your computer restarts.

      posted in General Problems
      G
      geardog