[quote=“Uncle Frank, post: 42420, member: 28116”]Hold on a second. I think you are mixing things up here. Let me explain. When you start deploying an image your client boots up via PXE and comes up with the FOG client. This small linux is made up of several shell scripts to do the magic and deploy an image from your server to that client. First it mounts the image directory from the FOG server via NFS into the local filesystem. So ‘/images’ on the client is essentially the same as ‘/images/<imagename>’ on the server. ‘/dev/sda’ is simply the first hard disk on the client and this is where the image will be restored to (aka destination disk).
From what I can see your ‘/images’ seams perfectly alright (we’d see other error messages if not!).
[B]BUT, are you sure that the disk you pulled the image from is NOT larger than the disk to be deployed to…[/B][/quote]
I am new to this but I understand that much. What I was saying is that my images are not on /images located on /dev/sda. They are on a seperate (sdb) internal drive and I have linked the location on there to the /images located on /dev/sda. I think you might be right about the problem though, I compared the two drives and didn’t realize that the drive I made the image on was bigger. Am I correct in thinking that if I were to shrink the partition on my master image before uploading then any drive I use that’s larger than that partition should work? Also, will FOG automatically expand the partition to take up the full space of the drive during deployment? Sorry if this is super basic stuff.