Ah, didn’t realize there was an update. I’ll give that a try. We have 3 new models of laptops and tablets and this is the only one that gave us trouble that’s what’s so strange. Even our older models worked like a charm all the way back to v.32.

I’ll update more when I update.

Sorry, here’s the basics

FOG 1.1.2
OS Windows 7
Image Type Single Partition, resizable
Lenovo T440 laptop

This is a from scratch build, deleted all partitions, reformatted drive, installed windows on a single partition and went to upload.

Upload was successful and machine still boots, just now stuck with a 35 gig hard drive instead of 500 with no way to resize it lol.

Prepped a T440 image master device
Uploaded the image successfully
Booted the master device that the uploaded image was pulled form, disk size has been reduced to image size.

Diskpart.exe will not resize it, Disk management will not resize it, I’m not sure where to turn with this one, this is totally new, I’ve never had this problem before. Our school is 100% Lenovo so I’ve seen plenty of other issues with MBR’s that were screwy but this one is driving me nutty.

Hi Klaus, probably already too late here but for notifications sake, I’m able to do the X230’s no problem. I had to restructure the master to a single partition and make sure the boot flag is set to the primary OS after Windows 7 sets up it’s utility partition. I also changed the AHCI settings to compatibility mode. Other than those things it went smoothly.

I’m trying to image a Windows 2003 server running on a Dell Power Edge 860. I can successfully boot to the FOG PXE but it errors saying “Hard Drive Not Found” since this is a fully functional server, I’m assuming this is a RAID driver issue with FOG. Does anyone have any ideas where to go with this next, I’m not having any trouble with the rest of our workstations, a mixture of Lenovo tablets, laptops and workstations, just the Servers we have which are a mixture of 2003 and 2008 (14 in total ).

FOG Server:
Ubuntu 11.04
Fog Server .32

[B]UPDATE[/B]: Ok, so after a lot of struggling, and some physical and OS changes, here’s the final solution (at least I hope so). I rolled back the OS via complete reinstall of the OS to Ubuntu 11.04 as 10.04 didn’t include the NIC drivers for this new of a motherboard and I wasn’t going to try and compile drivers for the Network Card (I already have enough on my plate without that task).

I also physically moved the FOG server into a rack in the server room and am direct now into the Pro Curve which eliminates any in wall wiring or cabling issues with it in my office. So far I’ve uploaded 2 of the problem images in less than 12 minutes and downloaded and imaged 2 PC’s with the troublesome X201 image in less than 10 minutes each with no trouble on either one.

Unfortunately I was so exasperated with the issues I ran across I didn’t do this in stages to find out what the actual problem is so I’m not sure this post will be useful for anyone looking at the same issues.

One thing I wanted to ask, what does mounting the NFS volume actually indicate, since I was able to successfully mount it and copy down the image with a very respectable speed? Basically does that indicate network problems or FOG problems? I’m sorry I’m not following the diagnostic pattern on this test.

Regardless of all of this thank you both for your help with this, I’m pretty sure I’m back and imaging happily.

I actually haven’t tried reversing the install, but maybe that’s the way to go and I haven’t changed any of the Kernels, so far this is the first time I have had any trouble with our network or the FOG server. I’ll have to try and find the older versions of the Ubuntu downloads, as I’m pretty sure I don’t have a CD of it.

[B]UPDATE[/B]:
Started over with a completely new installation of FOG server, same IP address, did not migrate the images, used the master computers for each image to create new images. Uploaded a new image from the X201 master which went much faster and then attempted to download to 2 different X201 machines (all have the same hardware) and both of them bomb out at different points during the deployment. This is the only image that doesn’t complete and they stop at different points during the deployment. I tested the NFS setup again with the same results, took about 11 minutes to copy this image straight down to the desktop. These images were working like a charm from our initial temporary FOG server, so the only thing that’s new is the new FOG server.

Any ideas? Reloading our machines from scratch is a nightmare with all the additional software and I have to get a bunch of these machines knocked out soon.

[quote=“djm79, post: 8686, member: 1568”]Are you imaging from the same access layer switch all the time or are you moving between two different switches? I only ask because a had a very similar problem with one of our Cisco POE switches. I would take the laptop and move around and check the switches move outward from the FOG server until you get back to your access switch where you are having the slow imaging. Mine was a cheaply done uplink into a a 10/100 port instead of a gig uplink. Try that out and let us know how it goes.[/quote]

Actually the FOG server and I are in the same switch, basically our IT office is run off the main Pro Curve and both the FOG server and my imaging station are in the same office. At some point in the future I would like to be able to use the VPro chips and RDP over KVM and remote into a machine and image straight from the users location if there is a problem but for right now, I’m removing the machine, bringing it to the office and imaging from here.

An interesting thing to note here is we use primarily Lenovo workstations and laptops, I have 3 laptop images, an X230, and X200 and an X201. Both the X200 and the X230 both deploy pretty well and there’s generally no issues, it just seems to be the X201s that are the problem. This could be the image or the hardware or the fog server is my thought but not sure what to think anymore as I’ve gone round and around on this.

Ok, so the problematic image’s size on the hard drive was about 42 gigs, instead of 50. When I transferred down to my Macbook, it took about 11 minutes while uploading it through FOG took about an hour. The network is basically made up of HP Pro Curves with fiber run between the buildings (12), completely gigabit all the way throughout.

The FOG server is a brand new custom box with a 6 core AMD Chip and 4 Gigs of DDR III with a Terabyte SATA II hard drive in it.

So, does this mean that the FOG server is working correctly and I have a network problem or does this indicate a problem with the FOG Server?