FOG not imaging to new HD
-
Hi All,
Looking for a little help here. I have setup a Win 7 machine. I have syspreped the device and uploaded the image. I can redeploy the image to the same HD and it will boot and partclone just fine. If I try and deploy it to a different HD (either in a different chassis or in the same one) it will PXE boot and get right to the point where the partclone will kick in it just reboots. I am running 1.2.0. I have have tried multiple machines and this is what I have figured out so far. Thoughts? Am I missing something? -
Not without researching it.
-
do you know what commands to use for partclone?
-
I was trying to follow the directions in the debug of image download. Should I replace those commands with partclone instead?
-
Then why is it trying to image using partimage?
-
It is uploaded from 1.2.0.
-
Is the image uploaded from 1.2.0 or from 0.32?
-
I used a SLAX boot drive and formatted the HD to NTFS and still have the same result. I tried using the debug mode, but when I get to the part about using partimage it says aborted after clicking next. I am going to try and post a video of what I am seeing.
-
You can also use the debug mode to edit and create partitions with fdisk
[url]http://fogproject.org/forum/threads/quick-format-to-ntfs-with-fog-for-noobs.10349/[/url]
-
Could you please try booting a live CD, create one primary partition, format it (e.g. NTFS) and then try again…
I really hope that this does not fix the problem as FOG is capable of handling empty drives but hey, weird things can happen.
-
[quote=“Uncle Frank, post: 45061, member: 28116”]Is the other disk smaller or bigger? Same model, different one? Maybe try debug download and take a (slow motion) video. Maybe we see some error messages then. Hard to figure out with little information.[/quote]
Same size drive and exact same model machine, Dell Optiplex 760. I have taken a video and it doesn’t show any errors when trying to deploy. I will try the debug mode.
-
Is the other disk smaller or bigger? Same model, different one? Maybe try debug download and take a (slow motion) video. Maybe we see some error messages then. Hard to figure out with little information.
