Can't have partition outside the disk
-
If it is the 2 partitions from Windows 7 (boot and C), it will still resize - its only when it gets beyond the base partitioning scheme of Win 7 (you used 3 partitions?) that resize will fail.
-
[quote=“totalimpact, post: 536, member: 217”]If it is the 2 partitions from Windows 7 (boot and C), it will still resize - its only when it gets beyond the base partitioning scheme of Win 7 (you used 3 partitions?) that resize will fail.[/quote]
It is those 2 default partitions but In the instructions i read it was suggested to use “Multiple Partition Image - Single Disk” for the image type when creating windows 7 images which doesn’t resize. Are you saying that it will ?
-
Yes - it will, not sure what instructions show that, but its mentioned all over the forum - use Single Disk/Single Partition for best performance - even on Win 7.
-
I am having a similiar issue with an XP multi-partition. The image was taken from a 160GB HDD, and I am getting the error trying to image to a 1TB HDD. Do I need to put a partition table on the drive first? It is a blank new drive with nothing on it.
-
Have you tried imaging the source drive as Single Drive / Single Partition?
FOG will create or delete partitions as it sees fit, you should not need to do any partitioning - but in multi partition scenarios, it will not resize the partitions on your new drive, only in single partition mode can it resize.
-
It is a multi partition drive that i am imaging from. I am not concerned with resizing it. We just had 1TB drives on the shelves. One of our computer labs, a drive died, so I was replacing it and using an image taken from another machine. I just cannot figure out who it says it is outside the disk when this drive is 7 times the size of the original host image drive.
-
I havent tried the scenario yet - but I know multi-partition to the same drive size works fine - hopefully development can chime in.
If its just a single failed system, Clonezilla would definitely work. In the future you might try changing your platform to single partition - it has saved me a ton of time and space.
-
[quote=“totalimpact, post: 539, member: 217”]Yes - it will, not sure what instructions show that, but its mentioned all over the forum - use Single Disk/Single Partition for best performance - even on Win 7.[/quote]
Fog says that in the image types in the description and that’s why i used it.
[B]Multiple Partition - Single Disk[/B]Multiple Partition - Single Disk will back up all the supported partitions on the first disk drive detected by FOG, but the partitions are [B]NOT[/B] resizable by FOG. This means that the image must be restored to a disk of the same or larger capacity.
[B]Overview[/B][LIST]
[]Single Disk Drive
[]Not Resizable
[]Supports: [B]NTFS, XFS. JFS, HPFS, FAT16, FAT32, Reiser3, EXT2, EXT3[/B]
[]Linux Support!
[/LIST]I don’t see how you can use Single Disk/Single Partition when there are 2 partitions?
-
The single disk/single partition does work for windows 7 as long as you don’t have a recovery partition in the mix also. I just uploaded a Win7 image this morning with the 100mb partition and the regular partition and have been deploying the image successfully.
I agree, it does seem logical to pick the Multiple Part/Single disk, but Single/Single accounts for the 100mb partition and has worked for me.
Try uploading it, worst case is that it won’t upload, but barring some other problem, it should.
-
The developers know that Windows 7 will always have a 100mb boot partition (many people dont even see it), and then some partition of random size, so this means there is only 1 partition FOG needs to manipulate, but if you add a 3rd partition in to the mix - how will Fog make the decision as to which needs resizing?? - this is why multi partitions cant be resized - and Win7 has 2 parts, but only 1 needing resizing - this is why Win 7 works as a “resizable single partition” scenario - the term doesnt fit, but it works.
-
h
[quote=“totalimpact, post: 563, member: 217”]The developers know that Windows 7 will always have a 100mb boot partition (many people dont even see it), and then some partition of random size, so this means there is only 1 partition FOG needs to manipulate, but if you add a 3rd partition in to the mix - how will Fog make the decision as to which needs resizing?? - this is why multi partitions cant be resized - and Win7 has 2 parts, but only 1 needing resizing - this is why Win 7 works as a “resizable single partition” scenario - the term doesnt fit, but it works.[/quote]hmmm…i may have tried that before not sure but it may have blue screened on me. i have one freshly done next to me ill give your suggestions a shot hopefully i dont lose all my effort i put into it to get it how i want it, let you guys know the outcomes. If it does work then someone needs to correct those image types descriptions:)
-
[quote=“The Dealman, post: 560, member: 53”]I don’t see how you can use Single Disk/Single Partition when there are 2 partitions?[/quote]
There is special code to deal with Winblows 7 partition structure. It will work with Single Disk, Single Partition (Re-sizable) as intended.
[quote=“totalimpact, post: 563, member: 217”]The developers know that Windows 7 will always have a 100mb boot partition[/quote]Not always. I remove it on my images personally.In the future, we are looking at offering a Mutli-Partition (Re-sizable) option that will resize the last partition to the remainder of the disk.
-
I changed the setting to the Single Drive / Single Partition option uploaded my image and i saw as it was going through the pre-checks it resized the partitions. i havent deployed it to a different model yet or checked to see what the partitions look like yet though but it may have worked…
-
Hi,
So I have a 30GB Virtual machine, windows 7 NTFS, If I Want to deploy this to every machine, and have
expand to use the additional space on the comptuers drives, which option should I select? It should be single disk (resizable) right? -
I believe so. I’ve not done any work using FOG and VMs, but I’d think a virtual Win7 image with a single partition (excluding the aforementioned system partition) ought to image in the same fashion. Maybe somebody’s who’s done this with VMs can reply and verify or offer tips.
As far as using the resizable single disk Win7 image for conventional machines, it works great! I’ve been deploying a roughly 20GB image to all sorts of different drive sizes and it’s done very well.
-
I am developing my Windows 7 image and am having a couple of problems. I posted in a separate post but this sounds like similar issues and seems to be an active post.
-
When I try to capture a Windows 7 Enterprise image with 1 partition it immediately fails when starting the partimage (blue screen).
-
I have successfully captured an image with 2 partitions (Includes the 100mb part) but when I try to deploy it I get a BOOTMGR is missing error.
As it is I cannot seem to either create or deploy a Windows 7 image in FOG. I have tried this on various hardware as well as in a virtual machine all with the same result. Others have commented in my post to having the same issue. Any ideas??
-
-
This post is deleted! -
Hi Dug,
I found this mentioned from this Fog guide: [URL=‘http://blog.ibuddy.info/index.php/2011/05/fog-29-my-windows-7-guide-3264-bit-docv1/’]http://blog.ibuddy.info/index.php/2011/05/fog-29-my-windows-7-guide-3264-bit-docv1/ [/URL]
[QUOTE]
[LIST=1]
[][LIST]
[]Scott S
[]June 14th, 2011
[/LIST]
[LIST]
[]REPLY
[*]QUOTE
[/LIST]
Kyle,
Just wanted to mention that building your W7 master image with VMWare Workstation works as well. I followed your guide and everything appears to be working just fine
Just one note of caution! If you are using VMWare, make sure you do not let VMWare Workstation do an “easy install” of your Windows 7 installation. If you do, the additional 100mb partition will not be created. Not allowing this partition to be created will cause issues when you try to upload your master image. Fog looks for that 100mb partition when you upload a W7 host. If it doesn’t exist, the upload will fail (blue upload screen flashes and restarts the system). Several hours of frustration until we figured that out!
[/LIST]
[/QUOTE]
When you’re doing the single partition/single disk upload, by 1 partition, do you mean that it’s just the primary partition without the 100mb partition? This might be the issue, but it’s odd. Blackout has said that he removes the 100mb partition and it works.I’ll keep thinking on it and see if I come up with anything better, but if anybody else has solved this or a similar issue, please post and help Dugjones out!
-
Oh, if you have specs on your Fog installation, flavor of linux, model(s) trying to image, etc, that might help in case there’s a specific issue with some combination of hardware/software.
-
Thanks for the reply Bobfrid. I am using an Autounattend.xml to create the single or double partition setup. I am using FOG .29 running on Ubuntu 10.04 server. I have been using this setup for awhile now with windows xp with no issues. I have created the image on physical machines (several types) but am currently working in a VirtualBox virtual machine running on Linux Mint 12.
Playing around this afternoon I was able to manually capture the image by using the commands in the /bin/fog script (partimage save …) but when I deployed it it wouldn’t boot. I’ll continue playing around next week…
