Unable to Deploy Image

[Jeff Findley]

[quote=“Just10, post: 41992, member: 28415”]ls -al /images/DellAllinOne8GBWIN764 shows:
d1.mbr
d1p1.img
d1p2.img
The image is multiple partition - single disk.

Any more on this? I am in exactly the same situation. Win7 image that is multiple partition - single disk. TFTP is verified working. When I run a debug and look at my disk and partition(s) it looks fine. I run a debug deploy and everything is fine except it never actually downloads anything. As I step through the steps everything appears okay and then it says it’s finished.[/quote]

[Jeff Findley]

Oh, and another thing I can add is that if I let the download (either via debug or normally) run it creates the correct partition table and MBR on the disk. Once it reboots if I check it it has done exactly what I’d expect. Just no file download.

[Sebastian Roth]

[quote=“Just10, post: 41995, member: 28415”]after typing that… I realize the image is probably larger than 40gb. If our techs put 40gb drives in these machines - I have a bigger problem.[/quote]
So is this causing the problem in your case??

Maybe we have another weird issue with partprobe again. Please run another debug download session. Type ‘fog’ and hit Enter till you see ‘Mounting File System . . .’ then press Ctrl+C to get back to the console.
[CODE]# dd if=/images/d1.mbr of=/dev/sda
…

fogpartinfo --list-parts /dev/sda

…

ls -al /dev/sda*

…

partprobe /dev/sda

fogpartinfo --list-parts /dev/sda

…

ls -al /dev/sda*

…
hdparm -z /dev/sda

fogpartinfo --list-parts /dev/sda

…

ls -al /dev/sda*

…[/CODE]
Sounds weird but I had a disk where device files were “missing” after running partprobe…

[B]By the way, which version of FOG are you running, Jeff??[/B]

[Jeff Findley]

[quote=“Uncle Frank, post: 42045, member: 28116”]So is this causing the problem in your case??

[B]By the way, which version of FOG are you running, Jeff??[/B][/quote]

Uhh, I hate to admit it, but yes, my target disk was just slightly smaller than my original image. Interestingly, one reason I was confused and having issues after attempting to deploy an image was because FOG partitioned the disk with the desired size for the image. So when I ran a disk partitioning utility to check it the first thing I saw was an error because a partition was created beyond the limits of the disk. Weird it is even able to do that and not just error out.

So, replacing the target disk with a larger one resolved the issue for me. I need to go back and recreate my original image using a much smaller disk.

Running FOG 1.2.0

My suggestion for an added feature would be to do some sanity check for disk size and give some sort of feedback to the user if a target disk is too small.

Thanks for the help and the excellent cloning solution!

JF

[Junkhacker]

is there a reason you can’t use a resizeable image type?

[Just10]

I just wanted to chime in - my issue was the target disk was slightly smaller than the original as well (physical to ssd and assuming, without double-checking).