Here is a screenshot of that 2048th sector on my fresh install with the 100mb partition.
First print display in Bytes, second print in sectors.
[ATTACH]1053[/ATTACH]
edit : This will help by showing that fog debug load from pxe have parted.
[url=“/_imported_xf_attachments/1/1053_Windows 7 x64 2-2014-06-24-13-30-02.png?:”]Windows 7 x64 2-2014-06-24-13-30-02.png[/url]
Maybe i didn’t explained well.
Windows 7 (and all new OS maybe) use the 2048, not the 63 so, maybe put at 2048 is the solution.
To try this, you also need to make a backup to keep your system ready for the upload but now also need to get a live CD, USB or even PXE distribution with parted.
I used Gparted put in FOG pxe menu.
Boot on it then run “parted” in a terminal then use “print” to display the partition.
If it display “[SIZE=3]32,3kB” as starting sector, it’s the 63th sector.[/SIZE]
write “rm #” where you replace # by the number of the partition to remove, in your case it should be 1.
Then recreate a partition starting at 2048 using the all drive size with the command “mkpart primary ntfs 2048s 100%” and add boot label to with “toggle 1 boot”.
Check your partition with “print”.
Reboot and restore data on the new partition.
If you did well and if i explained well too (haha), you shouldn’t even need to boot windows and break your fogprep.
But as the first try, maybe it will help to check if windows is well loading then restore again the data that have been fogprep.
Maybe there is easier way like a using a gparted with an interface but i prefered used command line with easy and clear data to read.
So you probably have the same problem than the one i had.
If you don’t want to reinstall everything or maybe try this for nothing, you can make a backup of the current computer with a software (i used Acronis 2014 CD version) then make a “fresh” install with the 100mb partition then restore you the single partition without the MBR on the 2nd partition of the computer.
I has worked for me.
Yet, i didn’t tried to upload it because the computer was needed for work so only check if windows was starting well.
Thinking again of this, i haven’t check if it’s the 100mb partition or the first partition sector that block the upload.
I haven’t work on partitioning since few months and maybe more than a year.
If i remember well, i was using the sector 63 for all my image, like XP, instead of 2048 like the usual windows 7 installation.
Maybe try to this would be helpfull.
You can’t backup anymore with partimage so that’s why it always go back to partclone.
Do you have the “original” 100mb partition made by Windows during a normal installation ?
I have been working without these 100mb with partimage and now, it look to be a problem for partclone.
I think i had the same error when i was trying to upload an image with only one partition.
Hello,
when i tick “Join Domain after image task” it doesn’t fill domain details (name, user and password).
In a previous version, if i remember well, it was fill everything itself but when i tried under one of my current 0.32 version and my 1.1.x, text box wasn’t filling themselves.
Under 0.32, computer doesn’t seem to join domain without these data.
The second things is, when i save my homepage login account (fog / password by default) browser put it in most (if it’s not all pages) requesting for a accound (AD account, node account, etc.).
Even overwrite the saved account for nodes and possibly on others.
Is it possible to check webpage code to prevent this (box name) and avoid wrong account and password saving ?
[ATTACH]1052[/ATTACH]
[url=“/_imported_xf_attachments/1/1052_node.jpg?:”]node.jpg[/url]
It works with “GRUB”.
Thank you again.
I have link my 0.32 storage to my FOG 1.x server but on web interface it detect wrong disk space.
Should it work or i have to upgrade my storage to an 1.x version ?
[ATTACH]1049[/ATTACH]
[url=“/_imported_xf_attachments/1/1049_Dashboard Dashboard FOG Open Source Computer Cloning Solution.png?:”]Dashboard Dashboard FOG Open Source Computer Cloning Solution.png[/url]
Thank you for the explanation.
Since we work on the server and not on the client, it could also means that the server download the image from the client or the server upload it to the client and much when we read “image push” on the pxe interface, saying that’s the server that is working.
It doesn’t work better with partclone.
[ATTACH]1048[/ATTACH]
[url=“/_imported_xf_attachments/1/1048_Windows 7 x64-2014-06-23-13-30-03.png?:”]Windows 7 x64-2014-06-23-13-30-03.png[/url]
Sorry, i was meaning download (or deploy).
Since “deploy” has been change to “download”, i keep messing with the words.
It would have been better to have “deploy” and “backup” ! 
I have checked twice the image itself and the configuration on the web page (even update it twice and recreate it).
[ATTACH]1045[/ATTACH]
Is there a command line that i could use to have more details ?
And when i have this blue screen is very hard to read and i don’t even see what i write, is it from FOG or from the pxe module ?
[url=“/_imported_xf_attachments/1/1045_Edit 7GeneriqueOld Image Management FOG Open Source Computer Cloning Solution.png?:”]Edit 7GeneriqueOld Image Management FOG Open Source Computer Cloning Solution.png[/url]
Hello,
I have a message on all Acer M410 of a room under Windows XP at boot since i run FOG 1.x.
It says “PRESS A KEY TO REBOOT”.
Windows load fine if I ignore pxe boot.
It’s like FOG doesn’t handle well Windows XP boot or/and Acer M410.
This a big problem because it could make unusable all the Windows XP on my network.
Any idea ?
Thank you.
Hello,
i come back to find out if there is a way to deploy my old images.
I have a many (around 20 myself and i think around 150 for all my coworkers) Windows 7 single partition (without the 100mb partition).
Some one us have only a few so remake image isn’t a problem for them but many others have more that 30 to 40.
I have activated GUI for partimage support and proceed as always to import image to fog.
Yet, when i try to upload it, i have some messages and deploy doesn’t work.
Here is the screenshot :
[ATTACH]1037[/ATTACH]
[ATTACH]1036[/ATTACH]
Thank you for your help.
[url=“/_imported_xf_attachments/1/1036_Windows 7 x64-2014-06-20-10-53-03.png?:”]Windows 7 x64-2014-06-20-10-53-03.png[/url][url=“/_imported_xf_attachments/1/1037_Windows 7 x64-2014-06-23-09-00-06.png?:”]Windows 7 x64-2014-06-23-09-00-06.png[/url]
Sorry, I forgot to reply.
Upload works fine with the normal windows installation.
Now, i’ll look for the problem of downloading old image.
I have check with the creator of the image i used to build my VM.
He never created this strange partitions.
I’ll make a “fresh” install and keep the 100MB partition then try again to back it up as single partition.
From my memories, we don’t “remove” the 100MB after the install but we create the partition before installing Windows to avoid Windows handle it itself and create that 100MB.
We have remove the usual 100Mb partition to be able to upload it as single partition.
And the sector boo not made at the 63th sector by windows was already a problem to solve.
I’ll try use the fixmbr in windows since i work under a VM with snapshot, i can revert it at anytime if it doesn’t work.
I’ll also see with the old co-worker that made the original version to see if we find out something.
Could this GPT problem could also bring a problem for download ?
As said in the few first message, I have saved an edit of this image and after deploy using partimage, Windows doesn’t boot.
Thank you for your help and advises, i’ll look further on my side.