Did you build your answer file with WSIM or manually?
What pass did you put the ExtendOSPartition in?
Have you tried without
[CODE]<Extend>false</Extend>[/CODE]
?

[quote=“mkstreet, post: 30796, member: 24215”]

3. It seems to be the case that the target computer’s partition table entries need to exactly match the image creator’s partition table…or the deploy won’t start. I think there have been some cases where the target computers partitions are larger and that seems to work. I thought that as long as the data of the partition was smaller than the defined partition that it would deploy? I’d read some comments to the effect that Windows 7 would work this way even with not resizable images (that Windows 7 would resize even though the image type is not resizable).

4. I’d like to make an image that is more hardware independent as far as HDD partition sizes… how can this be done (if it can be) with Windows 7 and the image types available?

Thanks![/quote]

This is where sysprep can be useful-- we use a master image with a ~40GB Windows install partition and then use ExtendOSPartiiton in the answer file to extend the C:\ drive to fill the remaining space in whatever drive the image is deployed to. The same answer file can also be used to make partitions, but that seems a bit riskier.
Sysprep’s generalize flag could also help with other hardware issues-- I’ve spent a few months working with Fog 0.32, Ubuntu 12.04, and W7 Pro x64 clients, and I’ve been able to get away without sysprep on occasion while testing, but, in my experience, sysprep /generalize really helped us deal with varying hardware, including things as trivial as getting an image from a 120GB drive to a 128GB drive.

That sounds really odd. It’s almost like the sysprep process runs on its own (in the first case).

Is this the windows installation HP shipped you the PCs with, or have you reinstalled Windows 7 yourself since receiving the laptops?

Tom, thanks for the debug info.
I double-checked the message I received from FOG. I searched the forums for the ioctl error, and I eventually realized that the ioctl error could mean that the client couldn’t find the device it was trying to mount (thanks to one of your posts). After a lot of double checking, I found some data entry errors where the FOG server was given the wrong IP address.
Thanks for your help and for the prompt reply. I’ve now successfully uploaded an image to the server and added a few hosts.

Thanks for the prompt reply!

If I run fog.sysinfo from the root command line in debug mode, FOG tells me that the computer appears to be compatible with FOG. Disk and network both pass.

Hi guys,
I’m pretty new to FOG, so I might be missing something obvious, but I’m having trouble getting a client (running Ubuntu 12.04 server) to either add itself to invertory or successfully boot into debug mode. My FOG server is also running Ubuntu 12.04 server.

The client will succesfully PXE boot and load the FOG menu. I’m using the Kitchen Sink kernel to be safe w/hardware support. When I boot to the debug mode, I get the FOG ASCII graphic, then an “Error Detected!” message, and the client sits at a root command line interface. When I attempt to add to inventory, I get a message about an inappopriate ioctl device, then FOG continues, and ultimately gives “Attempting to send image …” and then hangs indefinitely.

Any thoughts as to what my problem could be? Is there any way I could get more debug info from the client or the server on the client’s activity?

Thanks–