Wicked. I’m having the same issue. Although, I’m unsure if I’m creating the snap-in correctly (it does work if I run it manually). But, if I add/link the snap-in to a client (even in advanced tasks), nothing ever happens. Global snap-in is enabled, the client system is running the Fog client stuffs… I’m stumped.

Having the same problem with only one of our laptops. Using 0.33B rev. 899. Hopefully this will be fixed soon.

Hi Devs! Firstly, let me start by saying you’ve done a fantastic job with this project. I was introduced to it about 3 months ago and I’m totally in love with it! That being said, I recently decided to give 0.33B (rev 899) a shot to check out the ext4 support along with other perks that seem to be coming along nicely. But, when I attempt to upload a ext4 image, it is still seen as ‘raw’ and sometimes doesn’t upload the partition at all (only about 914 bytes, actually). However, if I’m uploading an LVM or encrypted partition (also ‘raw’) it seems to work fine. Is this something that should not be happening with 0.33B or did I somehow b0rk the install?

Again, great work on such such an awesome project! Thank you all very much for continuing the development.

I’m also having a strange issue with this. I have a triple-boot image that was working fine before, but now it will not boot into the Linux partition. The GRUB loader/MBR works perfectly fine, booting into both Windows 7 and Windows 8 works fine, but if I choose to boot into Linux (CentOS 6.4) it kernel panics as if the system isn’t actually there. The partition (d1p7) seemed to transfer just fine. Is there a way I can manually re-deploy just that image to partition 7 to see if there are errors? I’ve seen people mentioning PartImage for this, is there documentation?

So, doing a sector-by-sector worked perfectly. However, it did take 10.5 hours to deploy the image. Being as I need to deploy this same image to 25 other laptops, this method would be pretty painful. Going to try some more testing with multi-partition, single disk today.

Hrm. I’m having the same issue with a multi-boot using CentOS (grub 0.97). Although, I don’t get the errors during boot. The system just sits there with a blinking cursor. I’m attempting a sector-by-sector/raw deployment of the same system now to see if that does anything. Otherwise, I’m unsure as to why the MBR won’t deploy correctly. I’ll dig into the manual dd’ing if the raw image doesn’t work.