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.
Posts
-
RE: The future of partclone and therefore FOG as it isposted in General
-
RE: The future of partclone and therefore FOG as it isposted in General
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.
-
RE: The future of partclone and therefore FOG as it isposted in General
@george1421 Thanks, I had already done some of that, got all of it in there now.
-
RE: The future of partclone and therefore FOG as it isposted in General
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.
-
RE: Problem capturing image - " no space left on device"?posted in FOG Problems
@Sebastian-Roth Looking over the
shrinkPartitionfunction, 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.
-
RE: Problem capturing image - " no space left on device"?posted in FOG Problems
@Stepa I could be wrong, but don’t notice anything wrong so far.
Something goes wrong with
ntfsresizeor 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
fogand 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.
-
RE: Problems with Solid State Drives?posted in General
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.
-
RE: rcu_sched Error on Host Registration - PC Tablet w/ Dockposted in FOG Problems
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.
-
RE: Problem capturing image - " no space left on device"?posted in FOG Problems
@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.
-
RE: PXE-T01: File Not Found Errorposted in Windows Problems
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.
-
RE: Problem capturing image - " no space left on device"?posted in FOG Problems
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?
-
RE: Laptop with 2 nvme drives randomly selected so selecting one drive to capture not workingposted in FOG Problems
@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.
-
RE: Image Capture/Deploy issues 1.5.7posted in FOG Problems
@fallenhero234 said in Image Capture/Deploy issues 1.5.7:
Permissions on image files set:
ls - laR /images
chmod -R fog:root /imagesI assume you mean
chown -R fog:root /imagesIt should be
chown -R fogproject:root /imagesfor 1.5.7, so run that command to fix ownership.After that we can see if more steps are needed.
-
RE: When i boot via pxe the client, nothing is happening after download filesposted in FOG Problems
@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.
-
RE: Corrupt file in image?posted in FOG Problems
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.
-
RE: tftp server issueposted in FOG Problems
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.
-
RE: FOG 1.5.6: Auto resize is unpredictableposted in Bug Reports
@Sebastian-Roth As far as I understand, any tool that uses
BLKRRPARTcould 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 asfdiskandhdparm)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
BLKRRPARTfunctions and what not plus theudevevents would be handled by the kernel as well afaik, so perhaps it’s as simple as the kernel versions? -
RE: Windows 10 temp file clean up - Error(5) shrinkPartition - Capture failposted in Windows Problems
@duanekaeb One other thing I had to do once upon a time was run
dism /online /cleanup-image /startcomponentcleanupin command prompt before sysprep and capture
-
RE: The future of partclone and therefore FOG as it isposted in General
@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.
-
RE: Fog image size too big (500 GB/takes around 2hours to capture and deploy)posted in FOG Problems
@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.