Can't have partition outside the disk
-
[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
-
Yet more testing…
FOG 0.32 on Ubuntu 8.04
Machine I am testing for the image is
HP D530 USD
P4, 2gb, 40gbStarted with a base Win 7 install with 2 partitions, 100mb + 20gb image upload and deployed to original disk and another 40, 120 and 160gb drives with out issues.
Next I followed the [URL=‘http://www.fogproject.org/wiki/index.php?title=Client_Setup#Dual_boot_Images’]guide[/URL] for linux
So now the setup was Win 7 100mb + 20gb + 1gb swap + 6gb Ubuntu
This would image up and down fine with the 3 test drives
Next I re-imaged with the base Win 7 Install added a 9gb data partition + 1gb swap + 6gb Ubuntu
The image uploads fine, but I end up with the cant have partition outside disk error on deployment to any of the test drives.
Next test was to revert to base Win 7 image, then create a 1gb swap + 6gb in linux as logical partitions and leave the rest for the windows data partition to be created post install.
Again the image uploads fine, but deployment ends with the same error.
So that leads me to conclude that the issue lies with logical partitions.
-
[quote=“Tangerine, post: 1628, member: 376”]Yet more testing…
FOG 0.32 on Ubuntu 8.04
Machine I am testing for the image is
HP D530 USD
P4, 2gb, 40gbStarted with a base Win 7 install with 2 partitions, 100mb + 20gb image upload and deployed to original disk and another 40, 120 and 160gb drives with out issues.
Next I followed the [URL=‘http://www.fogproject.org/wiki/index.php?title=Client_Setup#Dual_boot_Images’]guide[/URL] for linux
So now the setup was Win 7 100mb + 20gb + 1gb swap + 6gb Ubuntu
This would image up and down fine with the 3 test drives
Next I re-imaged with the base Win 7 Install added a 9gb data partition + 1gb swap + 6gb Ubuntu
The image uploads fine, but I end up with the cant have partition outside disk error on deployment to any of the test drives.
Next test was to revert to base Win 7 image, then create a 1gb swap + 6gb in linux as logical partitions and leave the rest for the windows data partition to be created post install.
Again the image uploads fine, but deployment ends with the same error.
So that leads me to conclude that the issue lies with logical partitions.[/quote]
If you have something to test on try [URL=‘http://sourceforge.net/projects/freeghost/files/Kernels/Kernel-3.2.4.core/Kernel-3.2.4.core/download’]kernel 3.2.4[/URL] i’m going to try it on my problem child and see if it fixes this or not
-
I
[quote=“Tangerine, post: 1628, member: 376”]Yet more testing…FOG 0.32 on Ubuntu 8.04
Machine I am testing for the image is
HP D530 USD
P4, 2gb, 40gbStarted with a base Win 7 install with 2 partitions, 100mb + 20gb image upload and deployed to original disk and another 40, 120 and 160gb drives with out issues.
Next I followed the [URL=‘http://www.fogproject.org/wiki/index.php?title=Client_Setup#Dual_boot_Images’]guide[/URL] for linux
So now the setup was Win 7 100mb + 20gb + 1gb swap + 6gb Ubuntu
This would image up and down fine with the 3 test drives
Next I re-imaged with the base Win 7 Install added a 9gb data partition + 1gb swap + 6gb Ubuntu
The image uploads fine, but I end up with the cant have partition outside disk error on deployment to any of the test drives.
Next test was to revert to base Win 7 image, then create a 1gb swap + 6gb in linux as logical partitions and leave the rest for the windows data partition to be created post install.
Again the image uploads fine, but deployment ends with the same error.
So that leads me to conclude that the issue lies with logical partitions.[/quote]
I tried that new Kernel and no dice i got the same error along with a new error that said something like unable to open read only file system
-
After doing some more testing i found that i get this error on Seagate Barracuda ST3250312AS drives which have the 4k advance format (Note: there is something also called Western Digital Advanced Format and Dell Advanced Format) From my testing it seems Windows Vista or Windows 7, disk alignment is correctly forced by the OS and for windows xp you will need to create an image on for this drive type Align the disk with an alignment tool (For example the Paragon Alignment Tool, a third party product, has been used by many) then Sysprep the image. The release of 0.33 fog should resolve this when ever released. Microsoft has also developed a patch for this [URL=‘http://support.microsoft.com/kb/982018’]here http://support.microsoft.com/kb/982018 [/URL]
