• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. benc
    3. Topics
    B
    • Profile
    • Following 0
    • Followers 0
    • Topics 7
    • Posts 43
    • Groups 0

    Topics

    • B

      Error at beginning of capture--Could not fix partition layout (runFixparts)

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved FOG Problems
      8
      0 Votes
      8 Posts
      948 Views
      B

      Side note, it appears that the KEA DHCP server in pfSense 2.7.2 does not properly support serving the correct boot file to BIOS vs EFI systems. It all works fine with Windows DHCP. This had nothing to do with my original issue.

    • B

      Details of image_export.csv

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems
      2
      0 Votes
      2 Posts
      299 Views
      george1421G

      @benc If its only one image, it probably easier to recreate the metadata by hand in the new fog server. As long as you remember the path part of the image definition is case sensitive you probably can make an educated guess at the rest of the settings You will see the image size being zero bytes after you manually create the image definition but that is OK since that value is only created on an upload and is only used for display purposes.

    • B

      Add setting for amount of free space on resizable images

      Watching Ignoring Scheduled Pinned Locked Moved FOG Problems
      3
      0 Votes
      3 Posts
      1k Views
      B

      Cool! I didn’t know that option was there. Thanks.

    • B

      Mounting and extracting files from an image

      Watching Ignoring Scheduled Pinned Locked Moved Feature Request
      7
      0 Votes
      7 Posts
      2k Views
      B

      Ran this from the Ubuntu 18 box:

      root@ubuntu18:~# zstdmt -dc </images/_Windows10Prox641909/d1p4.img | partclone.info -s - Partclone v0.3.11 http://partclone.org Showing info of image (-) File system: NTFS Device size: 9.9 GB = 2412369 Blocks Space in use: 9.6 GB = 2351625 Blocks Free Space: 248.8 MB = 60744 Blocks Block size: 4096 Byte image format: 0002 created on a: 64 bits platform with partclone: v0.3.13 bitmap mode: BIT checksum algo: NONE checksum size: n/a blocks/checksum: n/a reseed checksum: n/a
    • B

      Seems like you are trying to restore to an empty disk. Be aware this will most probably cause trouble.

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      13
      0 Votes
      13 Posts
      2k Views
      B

      @Quazz Nice explanation of the issues regarding the order of the partitions and the starting positions. I think that’s exactly what was going on. Since the actual usage of the original 1TB drive was only ~150GB, I went with a 240GB SSD which has always worked for me before. It gave me that “Seems like you are trying to restore to an empty disk…” error every time I tried to deploy that image to anything smaller than 2TB. Now that the two little partitions at the end of the original drive are gone, I recaptured it and it deployed just fine to a 240GB SSD.

    • B

      Multicast randomly hangs around 70-90% on last partition

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      20
      0 Votes
      20 Posts
      2k Views
      F

      I think that is interesant see this post:

      Multicast data address not change from one task to another one

    • B

      rEFInd reboot loop when booting from the network

      Watching Ignoring Scheduled Pinned Locked Moved Solved FOG Problems
      8
      0 Votes
      8 Posts
      2k Views
      S

      @benc Good to hear that you could make it work. I still suggest you should read up more about UEFI and think about moving all your systems that direction.

    • 1 / 1