![image capture import error 28 image capture import error 28](https://www.wireshark.org/docs/wsug_html/wsug_graphics/ws-merge-qt5.png)
In the end I think it turned out to be a very strange partition start number issue that was only in the d1.mbr file but not in the text-based partition layout files. This one you just posted reminds me on a topic that we had some weeks ago.
Image capture import error 28 windows#
Boot it up and when you get to the shell run parted /dev/sda print, take a picture and post Beside the layout being a bit weird with the three partitions it actually looks very good for being properly re-sizable! The smaller unmovable partitions are in the front (sda1 and sda2) while the big Windows partition is last. Can you please schedule a debug upload task on the machine you usually capture the image from. To be able to fix this we would need to find out why FOG detects the fourth partitions as fixed. So at this point we don’t know how much data you have on that partition and can’t fix the d1.mbr. In that post mentioned we see that the partitions 2, 3 and 4 are detected as fixed size and therefore FOG does not shrink those when capturing the image. 233179648 * 512 KB sector size is roughly 112 GB and it won’t fit onto a 60 GB disk! Too bad I can’t fix this d1.mbr for you because I am missing some important information. Now that makes 234441216 the least amount of sectors you need on a disk to be able to deploy this image.
![image capture import error 28 image capture import error 28](https://softwaretested.com/wp-content/uploads/2020/09/Mac-Camera-Format.png)
The d1.mbr file you uploaded has four partitions and the last partitions starts at sector 1261568 and is 233179648 sectors in size (see numbers above). Ok, back to the partition layout from 27th of May. Every partition layout is different and there is no general answer or solution for all of them. So in any case you want support with this, make sure you give us all the details for each image you want us to help you with. I just say this because if we confuse things here we won’t be able to properly help you. I thought we were still discussing the other one with three partitions you mentioned on June 27, 2019, 3:32 PM. It’s very important exactly which image and partition layout we are talking about. The layout and UUIDs match the one you posted here on May 27, 2019, 7:29 PM. The d1.mbr file you posted shows the following partition table: label: gpt Sorry for the long delay but I have not found the time to look into this any ealier.