Posts made by Sebastian M.

I had the same problem after I removed the HP partition + 100MB partition and merged the free space with the other hdd space. HP images are making a lot of trouble and I am searching for solutions for a long time and I hope that 0.33 will fix some problems.

I think this solution works fine. Tried and worked.
But where can I see, wich Kernel-Version I am using?

I am using Version 0.32 with Kernel 3.2.4 Core.

It slows down at exactly 33%.

We have a problem with FOG and image deployment.

The image is Windows 7, x64, ~ 121GB, Multi Partition - Single Disk

It starts fine and but at ~ 1/3 of the progress the speed slows down about 100mb per second.

The progress goes on, but it slows down the hole time and needs hours for deployment.

I tried several times but the problem appears with every try.

[QUOTE]I would agree. Buffer I/O error is telling you that the hard drive has hardware problems.

Toss it and start a new image, do not start go, do not try to save this image. [/QUOTE]

The hard drive is ok. Tested and replaced it. Tested another PC.

The image works fine, only the imge size is wrong and therefore it needs a lot of more time to deploy.

[QUOTE]Because the data has been scattered around the disk and FOG needs to read all of the empty data between the real data. Defrag before uploading and this will be fixed (as long as all data can be moved to the front of the disk)[/QUOTE]
We have defragmented the PC several times and the problem is still there.

[QUOTE]A good tradesman never blames his tools.[/QUOTE]
I don’t want to blame the tool, but after working and trying for hours and days it could be a problem with the tool.

[QUOTE]Your problem looks like a failing hard drive. [/QUOTE]
I don’t think so, because it was a factory new PC and we tested it on more than that one machine. The error postet in [url]http://fogproject.org/forum/threads/fog-converts-hdd-in-raw-format.132/[/url] appears after I deleted the 100mb-Windows-Recovery/Boot-Partition. And I tried that only because the image size was wrong.

Okay, if you say that, but I tried this steps only because I tried to solve the problem: [url]http://www.fogproject.org/forum/threads/win7-x64-wrong-image-size.37/[/url]

Nothing to do, to solve that. Thanks. Maybe someone will find an solution.

It might be the problem.

I tried it other ways before removing the 100mb partition, described in the named thread, but there was the problem with the image size and so I tried to fix the problem with removing the partition. I only have one partition now and the Windows works perfect. Only after FOG wants to start the upload the bootloader is destroyed.

The raw problem seams to not appear at the moment, the image size is correct when I start a new upload, but after ~3% and ~1,27GB from 41,35GB I got the hole display full of error messages including ‘Buffer I/O Error’, ‘on device sda1’, ‘DRDY Error’, ‘ata1.00’, ‘logical block error’ and so on.

That errors also appear if I startet defrag and ‘chkdsk /f /r’ as written in the error message.

I am about to despair. No one can help. I’ve been reading for hours at this forum and at sites linked from Google, but it seems that nobody has an answer or a part of an solution.

Hello again.

After having the big problem of the wrong image size ([url]http://www.fogproject.org/forum/threads/win7-x64-wrong-image-size.37/[/url]) there is a new problem.

I tried to follow a new way of creating the image to solve the problem, but now there is a new one.

[LIST=1]
[]Updated and configured windows to the end.
[]Run defrag and chkdsk
[]Removed the 100mb Windows Recovery Partition
[]Windows started with an error
[]Repaired the error with the Windows Installation Disk
[]Merged the partitions so I had the hole HDD as one partition
[*]Restartet to test for function a couple of times
[/LIST]
Everything worked good and I startet imaging with setting the image type to ‘Single Disk, NTFS, resizable’

FOG displays: ‘Imagesize ~250GB, raw format’

I can’t understand why FOG says it is raw format. After that error I looked up the HDD with Parted Magic and it shows, that it is RAW format. I repaired the bootloader and everything worked fine.

So, why FOG destroyed my bootloader and how can I fix this?

Hi, I did the folowing:
Using VMware with appliance: [url]http://www.vmware.com/appliances/directory/246903[/url] and updated it to Version 0.32, it was an process of ~30min, without problems and working for me.

This steps worked for me under Ubuntu:
[INDENT=1][FONT=courier new]cd /opt[/FONT][/INDENT]
[INDENT=1][FONT=courier new]sudo wget [url]http://downloads.sourceforge.net/freeghost/fog_0.32.tar.gz[/url][/FONT][/INDENT]
[INDENT=1][FONT=courier new]sudo tar -xvzf fog_0.32.tar.gz[/FONT][/INDENT]
[INDENT=1][FONT=courier new]cd fog_0.32/[/FONT][/INDENT]
[INDENT=1][FONT=courier new]cd bin[/FONT][/INDENT]
[INDENT=1][FONT=courier new]sudo ./installfog.sh[/FONT][/INDENT]

Good morning!

I am a [COLOR=#000000][URL=‘http://dict.leo.org/ende?lp=ende&p=ziiQA&search=colleague&trestr=0x8001’][COLOR=#000000]colleague[/COLOR][/URL][/COLOR] of Florian and I answer for him, because we have the same problem and we are not able to solve it at the moment.

As written in the first post we are using ‘multiple partitions, single disk’, we removed all other partitions and tried again redeploying the machine.

As written it worked good and without problems until we updated the Novell Client, but how could it be, that the simple process of updating a software increases the image size from ~40GB to ~120GB?

We also tried to use defrag and chkdsk to solve the problem but it is still present.

I can’t understand why it is so complicated to clone a system with the same infrastructure (DC8100 from HP) and same settings.

Sadly the thread postet by Blackout has nothing to do with our problem or can’t even give us a hint how to solve it

Hope someone can help.