Partclone failed, imaging failed

[robza]

Hello,
my svn version 7953
I created image from pc with win10. Here is image config:

I’m trying send image to a client but got error:

I can’t find partclone.log in /var/log
In debug mode I received error about mismatch partition size.

Target partition size (103MB) is smaller then source (104MB). Use option -C to disable size checking (Dangerous).

Regards

[Tom Elliott]

I don’t know how many times I have to say it. When you see the “Partclone fail, please check /var/log/partclone.log” it’s not referring to the FOG Server’s LOG directory. It’s referring to the client machine as that’s the “environment” it is working from. Trying to manage and collect logs from all systems during imaging sounds like it would be a good idea, but would become a management nightmare.

Can you edit the /images/20160601/d1.fixed_size_partitions and put in it, if it doesn’t already exist, the number 1 and retry the image?

[robza]

@Tom-Elliott there was “1” in this file. File edited and task restarted but same error.

Target partition size (103MB) is smaller then source (104MB). Use option -C to disable size checking (Dangerous).```

[Sebastian Roth]

@robza To me this sounds like the exact same issue as in this post. Can you please show us what you have in the files /images/20160601/d1.minimum.partitions and /images/20160601/d1.original.partitions, /images/20160601/d1.original.fstypes and if you have /images/20160601/d1.partitions!

If I am right you can fix this by putting 1:2 into the file Tom mentioned. This is caused by the recovery partition being the first in the partition table. Detection of this kind of partition layout is not yet implemented.

[robza]

@Sebastian-Roth here is ls -la output. All files created when image was uploaded from client to fog server:

[root@v1fog 20160601]# ls -la
total 9945900
drwxrwxrwx 2 root root       4096 Jun  1 12:25 .
drwxrwxrwx 9 root root       4096 Jun  1 09:21 ..
-rwxrwxrwx 1 root root          1 Jun  1 12:25 d1.fixed_size_partitions
-rwxrwxrwx 1 root root    1048576 Jun  1 09:11 d1.grub.mbr
-rwxrwxrwx 1 root root      17920 Jun  1 09:11 d1.mbr
-rwxrwxrwx 1 root root        795 Jun  1 09:11 d1.minimum.partitions
-rwxrwxrwx 1 root root         46 Jun  1 09:07 d1.original.fstypes
-rwxrwxrwx 1 root root          0 Jun  1 09:07 d1.original.swapuuids
-rwxrwxrwx 1 root root        283 Jun  1 09:07 d1.original.uuids
-rwxrwxrwx 1 root root  332676204 Jun  1 09:11 d1p1.img
-rwxrwxrwx 1 root root   12702527 Jun  1 09:11 d1p2.img
-rwxrwxrwx 1 root root     254129 Jun  1 09:11 d1p3.img
-rwxrwxrwx 1 root root 9837860640 Jun  1 09:20 d1p4.img
-rwxrwxrwx 1 root root        793 Jun  1 09:07 d1.partitions

d1.minimum.partitions

[root@v1fog 20160601]# cat d1.minimum.partitions 
label: gpt
label-id: 3D725169-FAF4-4384-8DDF-356A64413AE9
device: /dev/sda
unit: sectors
first-lba: 2048
last-lba: 1953525134

/dev/sda1 : start=        2048, size=      921600, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=1D7C64E5-7879-4714-B88A-3949F693ADAC, name="Basic data partition"
/dev/sda2 : start=      923648, size=      202752, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=4B8253DB-FD06-489B-9D2D-A1B0D34BD037, name="EFI system partition"
/dev/sda3 : start=     1126400, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=B6192BD1-21F7-471B-8EA7-3843E50AB17D, name="Microsoft reserved partition"
/dev/sda4 : start=     1159168, size=    45334286, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=7B18A30C-AA7A-406D-AA7E-B62FF7A5C8C2, name="Basic data partition"

I don’t see d1.original.partitions.
d1.original.fstypes

[root@v1fog 20160601]# cat d1.original.fstypes 
/dev/sda2 fat
/dev/sda3 imager
/dev/sda4 ntfs

d1.partitions

[root@v1fog 20160601]# cat d1.partitions 
label: gpt
label-id: 3D725169-FAF4-4384-8DDF-356A64413AE9
device: /dev/sda
unit: sectors
first-lba: 34
last-lba: 1953525134

/dev/sda1 : start=        2048, size=      921600, type=DE94BBA4-06D1-4D40-A16A-BFD50179D6AC, uuid=1D7C64E5-7879-4714-B88A-3949F693ADAC, name="Basic data partition"
/dev/sda2 : start=      923648, size=      202752, type=C12A7328-F81F-11D2-BA4B-00A0C93EC93B, uuid=4B8253DB-FD06-489B-9D2D-A1B0D34BD037, name="EFI system partition"
/dev/sda3 : start=     1126400, size=       32768, type=E3C9E316-0B5C-4DB8-817D-F92DF00215AE, uuid=B6192BD1-21F7-471B-8EA7-3843E50AB17D, name="Microsoft reserved partition"
/dev/sda4 : start=     1159168, size=  1952364544, type=EBD0A0A2-B9E5-4433-87C0-68B6B72699C7, uuid=7B18A30C-AA7A-406D-AA7E-B62FF7A5C8C2, name="Basic data partition"

Sebastian after changing to 1:2 in d1.fixed_size_partitions imaging works fine.
Thanks a lot.

[Sebastian Roth]

@robza Well this is an interesting partition layout. As I don’t do much windows stuff lately I don’t know much about how they do this.

So you didn’t re-capture/-upload? Just changed d1.fixed_size_partitions and deploy is going fine?

[robza]

@Sebastian-Roth yes, I just changed d1.fixed_size_partitions
Regards

[Sebastian Roth]

@robza As I said in the other thread your issue is a very different one although the error message is pretty much the same.

Your partition layout is not one of these easy straight forward ones that we got pretty good at but a more advanced one. We fail(ed) to detect that sda2 needs to be fixed size in your case. Tom has added some new code to the inits to hopefully get some better detection. So can you please upgrade to the very latest version and do a fresh upload (maybe just create a new image definition so you don’t mess with your working one) and then try deploying again. The d1.fixed_size_partitions file should be correct this time. Please let us know if it is working for you with the latest FOG version or not.