How big is the HDD you made the image on, the client that works? If it’s bigger than the others, you’re gonna have a bad time. Find the smallest HDD you can build your image on, and use that; I had similar issues where fog didn’t say anything about it being too big, but just whooshing by the imaging part of the deployment. That was 0.32, though, so ¯_(--)/¯
Best of luck, and welcome!
[quote=“cr31, post: 33511, member: 25150”]Was this a New HDD?
I came accross this when we purchased a pallet full of refurbished machines, and got the same message…because the HD wasn’t initialised.
I removed the drive, put it into an external caddy, used disk management to initialise the disk, put disk back into PC, re-tried with Fog, and it worked!
Alternatively you can use Diskpart or similar
i may be off the mark here, but just check[/quote]
it is definitely initialized - it’s currently got XP on it. Also, it imaged fine with the 0.32 fog server when I spun it back up. The issue is somewhere in the update, unfortunately 
Tom, after updating the initrd and booting, it still errors out - it goes by so fast and then restarts, I don’t have time to read the error messages. In my attempt to find a debug system I booted the compatibility menu entry and got a kernel panic. I might just spin back up my 0.32 and re-upload all the images to a new 1.1.2 box. I can hold off on that for about another week, if you’d like to continue troubleshooting.
also, is the advanced menu menu entry syntax different? I tried to load the advanced menu to see if the debug option was there, but it just cycles back to the basic menu, and restarts the timer.
it just feels longer, watching the pxe load up, then having to wait for ipxe to ‘initalize devices’. It could just be the client device I’m using too. And, upon further reading elsewhere in the forums, I have also realized that it’s just future-proofing for uefi (which is also a stupid technology, but that’s besides the point 
Junkhacker: in-place upgrade from 0.32 to 1.1.2.
Tom Elliot: weird question, but why did we move away from pxelinux.0 to undionly.kpxe? It definitely seems to take longer, and feels like an extra unnecessary step. Is there a large change in the menu system?
I updated, and everything worked out of the box, except actually writing the image to the host.
I searched everywhere to get an actual text copy of the error, but seeing as it occurs on the client, I couldn’t get one for you
Server: openvz squeeze with unfs3 instead of nfs-kernel. worked perfectly fine with .32; backup available if needed, and I might have to spin it back up if I can’t figure this out.
client: dell optiplex gx520 - no frill, just a HDD, tested to be working before upgrade
[url]http://imgur.com/doIXejR[/url] < link to the actual error message. Transcripted as follows:
[CODE]/usr/share/fog/lib/funcs.sh: line 84: 2522 Aborted partimage restore $2 $1 -f3 -b 2> /tmp/status.fog
short of unpacking the boot image and reading the script, it appears to be an un-fixable bug.
help?