S
@Sebastian-Roth said in Development FOG not capturing image - PartClone update:
@shruggy Would you mind telling us which version of partclone this is?
It’s the latest git shapshot:
https://github.com/Thomas-Tsai/partclone/tree/58d138da6e0f473acd80a7c9b8544d104377d50f
with the fix you suggested:
$ cd git/fos/Buildroot/package/partclone
$ ls
Config.in partclone-0.3.12.patch partclone.imager.patch partclone.mk
$ cat partclone.imager.patch
diff --git a/src/ddclone.c b/src/ddclone.c
index 04f8775..cab5386 100644
--- a/src/ddclone.c
+++ b/src/ddclone.c
@@ -30,7 +30,9 @@ void read_super_blocks(char* device, file_system_info* fs_info)
}
strncpy(fs_info->fs, raw_MAGIC, FS_MAGIC_SIZE);
fs_info->block_size = PART_SECTOR_SIZE;
- //fs_info->device_size = get_partition_size(&src);
+#ifdef IMG
+ fs_info->device_size = get_partition_size(&src);
+#endif
fs_info->totalblock = fs_info->device_size / PART_SECTOR_SIZE;
fs_info->usedblocks = fs_info->device_size / PART_SECTOR_SIZE;
close(src);
I haven’t yet pulled the latest FOS, however. So it doesn’t contain the changes to func.sh by @Tom-Elliott i.e. no special case for partclone.imager.
On the other note, when using unpatched Partclone 0.3.12 I also sometimes got segmentation fault, but didn’t report it. The case when Partclone finished successfully, but actually didn’t capture the partition was the more common outcome. I’d say, somewhere in the relation of 4 (empty) successes to 1 segfault, IIRC. And I didn’t notice any pattern to segfaults then (e.g. it could happen with or without compression).
