• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. sami.blackkite
    3. Topics
    S
    • Profile
    • Following 0
    • Followers 0
    • Topics 4
    • Posts 8
    • Groups 0

    Topics

    • S

      FOG + PXE / SNPonly.efi + ipxe.efi

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      1
      0 Votes
      1 Posts
      324 Views
      No one has replied
    • S

      "Not shrinking (/dev/nvme0n1p1) as it is detected as fixed size

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Linux Problems
      8
      0 Votes
      8 Posts
      1k Views
      Tom ElliottT

      @J-Redshaw I suspect yours is likely related to Bitlocker encrypting the free space of your drive.

      https://forums.fogproject.org/post/134625

    • S

      [Resolved]

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Windows Problems
      1
      0 Votes
      1 Posts
      210 Views
      No one has replied
    • S

      Windows Images - Too large.

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Windows Problems
      7
      0 Votes
      7 Posts
      1k Views
      S

      @JJ-Fullmer said in Windows Images - Too large.:

      @sami-blackkite Looks like you’re on the dev branch, which is good. Updating is always a good first step in troubleshooting stuff like this in case it’s already fixed.
      I’m not seeing anything in the commits (https://github.com/FOGProject/fogproject/commits/dev-branch) that actually looks related since the version you’re on, but sometimes a refresh still helps.

      I took a look at the default settings of a new image and it’s close to what I use, only difference is I set compression to 11.

      Are you familiar with a debug capture/deploy task? If not, simply check the ‘debug task’ checkbox when queuing up the capture task. It allows you to step through the capture process and you can catch any messages that might be telling us why it’s behaving odd. Just use the command fog once it’s booted up and ready to start the image and you’ll hit enter for each step. You can also set it up to watch it and step through over ssh if you want by, before running the fog command, getting the ip address with ifconfig and then setting a password with passwd then you can ssh into the debug session from your workstation with ssh root@ip.add.re.ss then the password you set. The password will only exist for that session on that machine. SSH just makes screenshotting and or copying any error messages to share here a bit easier.

      Oh thank you so much, JJ.
      I’ll give those steps a go and report back.

    • 1 / 1