• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login
    1. Home
    2. Quazz
    3. Posts
    Q
    • Profile
    • Following 3
    • Followers 2
    • Topics 27
    • Posts 1,977
    • Groups 3

    Posts

    Recent Best Controversial
    • RE: The future of partclone and therefore FOG as it is

      The error I was getting seems to be originating from zstdmt, it doesn’t have an rsyncable option in the included version. Would have thought that would be bundled by now, grrr.

      posted in General
      Q
      Quazz
    • RE: The future of partclone and therefore FOG as it is

      Okay, so I can’t believe I never noticed this, but -aX0 is an invalid parameter, it should be -a0

      Source: https://github.com/Thomas-Tsai/partclone/blob/master/src/partclone.c

      		"    -aX  --checksum-mode=X  Checksum formula to use to add error detection\n"
      		"                            where X:\n"
      		"                            0: No checksum (no slowdown, smallest image)\n"
      		"                            1: CRC32 (Fast to compute, basic detection)\n"
      

      Hopefully the source of the funky problem I was having, rebuilding now.

      posted in General
      Q
      Quazz
    • RE: The future of partclone and therefore FOG as it is

      @george1421 Thanks, I had already done some of that, got all of it in there now.

      posted in General
      Q
      Quazz
    • RE: The future of partclone and therefore FOG as it is

      I’m preparing a build with Buildroot version 2019.02.4 and one with that Buildroot version + partclone 3.12, will test and post them on Monday probably.

      posted in General
      Q
      Quazz
    • RE: Problem capturing image - " no space left on device"?

      @Sebastian-Roth Looking over the shrinkPartition function, it looks like the new size is calculated as the theoretical minimum size as given by ntfsresize + 5% of that size. (for safety and consistency I believe).

      However, I can foresee situations where the theoretical minimum is small enough that the 5% of “safety space” isn’t enough to accomodate everything. I don’t think this will happen under every circumstance, only when there’s certain kinds of fragmentations that it can’t resolve.

      Perhaps a preset minimum should be added to ensure a minimum safety boundry (like say 200MB)

      Ntfsresize man page mentions you don’t require defragmentating the drive prior to using it since it kind of does that itself, but obviously on an SSD that logic doesn’t really make sense anyway!

      Those are my current thoughts on this, but quite honestly I could be completely wrong.

      posted in FOG Problems
      Q
      Quazz
    • RE: Problem capturing image - " no space left on device"?

      @Stepa I could be wrong, but don’t notice anything wrong so far.

      Something goes wrong with ntfsresize or the size it’s ordered to try.

      Perhaps try a debug capture (under advanced tasks of a host) (type enter until you’re at command line after loading and then type in fog and press enter, then press enter for each step)

      Does it say * Possible resize partition size: (size here) a few steps before the error?

      Just want to see if the numbers make sense.

      posted in FOG Problems
      Q
      Quazz
    • RE: Problems with Solid State Drives?

      There were some issues with NVME drives in the past that have since been resolved. I do recommend updating to the latest version for best results.

      If it’s just SATA SSDs then it will function just as if it’s a spinning disk in how it’s treated in terms of image capture and deployment.

      posted in General
      Q
      Quazz
    • RE: rcu_sched Error on Host Registration - PC Tablet w/ Dock

      There might be some odd BIOS setting that causes this, worth checking out. (or perhaps a BIOS update)

      Might also be worth trying a Ubuntu live USB or something to see if that will work.

      posted in FOG Problems
      Q
      Quazz
    • RE: Problem capturing image - " no space left on device"?

      @Stepa Looks like an MBR layout.

      Fixed size partition seems to be correct as well.

      I’m not 100% sure what would cause this at this point.

      Can you post the contents of the text files in /images/dev/000cd615c141 (from the FOG server) here? That way we should be able to see what kind of results the FOS logic came up with and try and reverse engineer what happened.

      posted in FOG Problems
      Q
      Quazz
    • RE: PXE-T01: File Not Found Error

      Do note that if your main DHCP server is already sending out PXE boot options then it will still cause issues as far as I’m aware.

      posted in Windows Problems
      Q
      Quazz
    • RE: Problem capturing image - " no space left on device"?

      Is this on FOG 1.5.7?

      When using resizable image type, FOG will try to resize the partitions it thinks should be resized. Something appears to go wrong in this case however. The space attributed is not enough to do even very basic operations.

      Is this a GPT partition layout?

      Can you share a picture of diskmanagement?

      posted in FOG Problems
      Q
      Quazz
    • RE: Laptop with 2 nvme drives randomly selected so selecting one drive to capture not working

      @Sebastian-Roth I think relying on size isn’t the right approach.

      Problematic scenario: Two nvme disks of the exact same size and model number. You only wish to deploy to a specific drive, the other shouldn’t be touched. How do we guarantee we get the right one?

      Problematic scenario 2: Two nvme disks of different sizes. You wish to deploy to the smaller drive, so both drives can fit the image, how do you guarantee the correct drive?

      The only thing unique to a drive is the serial number as far as I know. On the other hand, that would only work on system to system basis, so that’s not really that appealing.

      What George brings up is probably a better way if it works, disks should be recognized in a specific order by their controller and could be identifiable in that way.

      posted in FOG Problems
      Q
      Quazz
    • RE: Image Capture/Deploy issues 1.5.7

      @fallenhero234 said in Image Capture/Deploy issues 1.5.7:

      Permissions on image files set:
      ls - laR /images
      chmod -R fog:root /images

      I assume you mean chown -R fog:root /images

      It should be chown -R fogproject:root /images for 1.5.7, so run that command to fix ownership.

      After that we can see if more steps are needed.

      posted in FOG Problems
      Q
      Quazz
    • RE: When i boot via pxe the client, nothing is happening after download files

      @Sebastian-Roth Actually, on the latest VirtualBox it seems that there is a way to UEFI PXE boot now. (chipset ICH9 and network adapter type to virtio-net), but I haven’t really tested it any significant amount. It gets to the FOG menu at any rate.

      posted in FOG Problems
      Q
      Quazz
    • RE: Corrupt file in image?

      There’s definitely been a lot of improvements for nvme drives since then 1.4.4 as George mentioned.

      Other than that, if the file seems to work fine on other devices, then it could also potentially be something far more silly such as a faulty ethernet cable.

      posted in FOG Problems
      Q
      Quazz
    • RE: tftp server issue

      Not entirely sure what’s going on here, but I’m guessing you can’t reach the tftp server given that subnet configuration which I’m guessing is passed along by the wrong DHCP server.

      If we can see which DHCP communication those clients get, then it will likely lead to the correct answer.

      posted in FOG Problems
      Q
      Quazz
    • RE: FOG 1.5.6: Auto resize is unpredictable

      @Sebastian-Roth As far as I understand, any tool that uses BLKRRPART could be prevented access because of udev event handling.

      It’s usually very fast and therefore unlikely to cause issues, but since it is executed parallel to everything else it can potentially get in the way from time to time.

      As far as I know, other programs that interact with the storage device act in the same way and also use BLKRRPART (such as fdisk and hdparm)

      For now, I’d say, leave it as is and monitor for reported problems. This problem is rare enough on its own already (personally haven’t come across it at all) that it doesn’t really warrant changing everything with the possibility of the affecting something else. (doesn’t look like it should, but never know)

      edit: Important to note that Kernel version could affect how BLKRRPART functions and what not plus the udev events would be handled by the kernel as well afaik, so perhaps it’s as simple as the kernel versions?

      posted in Bug Reports
      Q
      Quazz
    • RE: Windows 10 temp file clean up - Error(5) shrinkPartition - Capture fail

      @duanekaeb One other thing I had to do once upon a time was run

      dism /online /cleanup-image /startcomponentcleanup
      

      in command prompt before sysprep and capture

      posted in Windows Problems
      Q
      Quazz
    • RE: The future of partclone and therefore FOG as it is

      @george1421 I don’t believe FOS github has the fix included yet at this point, though shouldn’t be too long.

      Still trying to figure out if/when/where the problem exactly started.

      As far as I could find it’s supposedly been around for ages (sfdisk - udev conflict), but isn’t necessarily triggered usually.

      posted in General
      Q
      Quazz
    • RE: Fog image size too big (500 GB/takes around 2hours to capture and deploy)

      @azra Interesting, not sure why it still tries to capture in raw.

      Though I do recommend moving the 300MB partition to be the first one (as that will give trouble with resizing), we should probably hold off on that until the first partition is seen as NTFS by partclone.

      posted in FOG Problems
      Q
      Quazz
    • 1
    • 2
    • 13
    • 14
    • 15
    • 16
    • 17
    • 98
    • 99
    • 15 / 99