Can't have partition outside the disk
-
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…
-
I am sort of in the same boat as the original poster, except we are using a 40gb drive to create an image and trying to deploy to a 40gb drive.
What we are trying to achieve is this. Windows 7 32bit (20gb) NTFS Data Partition (9gb) Ubuntu 11.04 (8gb) Swap (1-2gb).
We can create and upload the image with no problems, and it will deploy back to the machine it was created on correctly, trying to deploy to another machine causes the cant have partition outside disk error.We have tried doing just windows 7 and the data partition, and this will deploy to the other test machine as expected, even with the OS type set to linux. I have spent the last two afternoons trying to nail this one down, I have even made the partitions smaller to ensure there is blank space at the end of the drive, and it still will not deploy, I am clearly missing something, the question is what?
-
Hi Tangerine,
I’ve not played with dual boot, but the success you had capturing and deploying the image to the original machine leads me to believe you’ve got all of that set right.
Off the top of my head, I’d guess the two 40GB disks aren’t the exact same size. You can boot both into debug mode and check with “fdisk -l /dev/sda” to verify. However, doing just the Win7 + data partition (I’m assuming multiple partition - single disk image) and having that deploy correctly makes me think that isn’t the case. Do you have a larger capacity drive you can try deploying to, say a 60 or 80gb drive? If that also failed, that might give somebody more experienced than I an idea on what could be wrong.
Another guess would be the sata controller mode, could the “other” machine be set to something different in the bios?
If I come up with anything else, I’ll post.
Which OS and version of Fog are you using? I’ve only used 0.32, but if you’re on an older version, somebody who’s had experience on that version may be able to offer some advice.
-
[LEFT]The last time i worked on this 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. When i went to deploy it on a different pc with the same size hard drive it blue screened on me, i’m thinking that when i changed the image to the Single Drive / Single Partition option it did something to the image when it did that resizing during the upload?[/LEFT]
[LEFT] [/LEFT]
[LEFT] [/LEFT]
I had a previous backup of the images that i restored from…i also noticed that i get the can’t have partition outside the disk error on hard drives that have no partitions. So what i did was create a partition and boot the pc up in debug mode so i can run a fdisk -l and it shows disk /dev/sda doesnt contain a valid partition table -
[quote=“Blackout, post: 575, member: 1”]There is special code to deal with Winblows 7 partition structure. It will work with Single Disk, Single Partition (Re-sizable) as intended.
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.[/quote]
Something else i just saw was when i go to deploy an image and it gives that can’t have partition outside the disk error it says umount; can’t umount /ntfs: invaild argument
Donethen it updates the database then restarts
