• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. HSD3Tech
    3. Posts
    H
    • Profile
    • Following 0
    • Followers 0
    • Topics 4
    • Posts 16
    • Best 1
    • Controversial 0
    • Groups 0

    Posts made by HSD3Tech

    • RE: Storage Node Disk Storage not showing extended volume

      @george1421 Thanks for the info george1421! I’ll give it a try! Thanks again!

      posted in FOG Problems
      H
      HSD3Tech
    • RE: Storage Node Disk Storage not showing extended volume

      @george1421 Thanks, it is currently booted onto GParted (ISO on VM CD/DVD). Now that I am on Gparted, what next? I extended the Volume successfully, but now I need to grow the filesystem to match? How do I do that?

      posted in FOG Problems
      H
      HSD3Tech
    • RE: Storage Node Disk Storage not showing extended volume

      @george1421 I can’t see where GParted would be able extend the volume.

      posted in FOG Problems
      H
      HSD3Tech
    • RE: Storage Node Disk Storage not showing extended volume

      @sebastian-roth I forgot to answer your second question: I didn’t knowingly “grow the filesystem” so, I’m guessing that’s where the problem is?

      posted in FOG Problems
      H
      HSD3Tech
    • RE: Storage Node Disk Storage not showing extended volume

      @sebastian-roth

      0_1516215958087_41f3be05-bb38-4b3b-a3c9-7d44f7e595b9-image.png

      posted in FOG Problems
      H
      HSD3Tech
    • RE: Storage Node Disk Storage not showing extended volume

      @george1421 Sorry for the late response. I’m not getting notifications through email anymore (will have to check that issue out).

      This is the screenshot of df -h
      0_1516215737785_80e504d9-ece3-4004-a04f-a233ded0ff31-image.png

      posted in FOG Problems
      H
      HSD3Tech
    • Storage Node Disk Storage not showing extended volume

      I have a FOG (Ver. 1.3.0-RC-11) VM that I recently extended the volume through Gparted and it’s showing (in System Settings>Details>Overview) that it has the correct Disk amount (after I added/extended the volume) but it’s not showing under Storage Node Disk Usage (FOG - Dashboard) that I have more free. Am I missing another step I need to perform? I’ve Restarted/Re-set a few time, but same results. Any help/guidance would be much appreciated! Thanks in advance! Seth

      posted in FOG Problems
      H
      HSD3Tech
    • RE: FOG clone IP address issue (holding onto cloned IP)

      Glad to help 🙂

      posted in FOG Problems
      H
      HSD3Tech
    • RE: FOG clone IP address issue (holding onto cloned IP)

      @wayne-workman I found the file default.ipxe, edited it in nano, saved it and it worked.

      posted in FOG Problems
      H
      HSD3Tech
    • RE: FOG clone IP address issue (holding onto cloned IP)

      @sebastian-roth I got it figured out, thanks.

      posted in FOG Problems
      H
      HSD3Tech
    • RE: FOG clone IP address issue (holding onto cloned IP)

      @sebastian-roth Thanks for the reply Sebatian! Can you please guide me on how to “check in the file /tftpboot/default.ipxe” on my FOG server? I’m am a Microsoft guy and kind of light on the Linux knowledge. Thanks!

      posted in FOG Problems
      H
      HSD3Tech
    • RE: FOG clone IP address issue (holding onto cloned IP)

      Yeah, I was too quick on the “Ask a Question” 🙂 I was typing the details when you replied. See above. Here is the Copy/Paste.
      I failed to add the description. OK, so I cloned my FOG Beta 1.3 server onto another VM and it is still holding onto the IP address from the cloned FOG server. Of course, the new FOG server has another IP address (different DG, etc) and I have gone through all of the FOG Configuration Settings and replaced the old IP with the new. It still is trying to go to the old IP (when I boot to PXE, it appears in the boot process, then times out. Originally, when I attempted to image from the newly cloned FOG server, it complted the imaging, but shows up as the Task on the old FOG Beta 1.3 server and not the new one. Where is the old IP hiding in the newly cloned FOG server?
      Thanks in advance!

      posted in FOG Problems
      H
      HSD3Tech
    • RE: FOG clone IP address issue (holding onto cloned IP)

      @hsd3tech I failed to add the description. OK, so I cloned my FOG Beta 1.3 server onto another VM and it is still holding onto the IP address from the cloned FOG server. Of course, the new FOG server has another IP address (different DG, etc) and I have gone through all of the FOG Configuration Settings and replaced the old IP with the new. It still is trying to go to the old IP (when I boot to PXE, it appears in the boot process, then times out. Originally, when I attempted to image from the newly cloned FOG server, it complted the imaging, but shows up as the Task on the old FOG Beta 1.3 server and not the new one. Where is the old IP hiding in the newly cloned FOG server?
      Thanks in advance1

      posted in FOG Problems
      H
      HSD3Tech
    • FOG clone IP address issue (holding onto cloned IP)
      Server
      • FOG Version: Beta1.3
      • OS: ubuntu 14.04 LTS
      Client
      • Service Version:
      • OS:
      Description
      posted in FOG Problems
      H
      HSD3Tech
    • FOG Host doesn't re-join Domain after being imaged
      Server
      • FOG Version: Beta 1.3
      • OS: Ubuntu 4.04
      Client
      • Service Version:
      • OS: Windows 10
      Description

      After re-imaging the Host/Client, it doesn’t re-join our Domain anymore. Hosts/Clients used to re-join our Domain automatically and they don’t anymore. We thought it was my other FOG server (1.1) VM but my new FOG Beta 1.3 VM does the same thing (no auto re-join domain after imaging) Any assistance would be greatly appreciated.

      Thanks in advance!

      Seth

      posted in FOG Problems
      H
      HSD3Tech
    • Windows 10 image upload lockup on FOG beta v1.3 - take 2
      Server
      • FOG Version: Beta 1.3
      • OS: Ubuntu 14.4
      Client
      • Service Version: ?
      • OS: Windows 10
      Description

      I just recently got my FOG beta v1.3 (on Ubuntu 14.4) VM setup and on my first attempt to upload a Windows 10 image it locked up on the “Saving original partitions…” step on the preparation screen. I started it twice (thinking it was a fluke the first time) and also changed the Image Type from Single Disk - Resizable to Multiple Partition Image - Single Disk and it hung in the same spot. Any suggestions on what I should try or the cause?

      Thanks in advance!

      posted in FOG Problems
      H
      HSD3Tech
    • 1 / 1