FOG converts HDD in RAW-format
-
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?
-
Windows 7 really likes to have that 100MB partition at the start of the disk, and FOG has been built to handle that with the Single Partition image type, so there is no need to remove it (assuming we’re talking about a fresh install from the Windows 7 DVD and not an OEM install which generally contains other hidden partitions). Honestly it might be a stretch to call it Single Partition considering it’s handling of Windows 7. By selecting Windows 7 as the OS type in FOG it expects to find that 100MB partition, and this raw format issue might be what happens when the partition isn’t there.
-
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.
-
The bootloader issue is tied to the Windows 7 OS setting on the host in FOG. When you select Single Partition as the image type and upload an image FOG ignores the hosts MBR, so the actual MBR never gets uploaded. When deploying that image to a host FOG checks what the OS type is set to and applies a “generic” MBR. FOG’s Windows 7 generic MBR expects the 100MB partition to be there, which is why you’re having problems booting after imaging.
My first guess about the errors during upload would be that the HDD has problems, possibly a bad sector or failing controller board.
-
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.
-
I think BryceZ is correct with suspecting a HDD problem.
From my experience “Buffer I/O Error’, ‘on device sda1’, ‘DRDY Error’, ‘ata1.00’, ‘logical block error’” is among a number of error messages that occur when a drive can’t be read at a certain point. Since you’re getting the same error using FOG and chkdsk, I would tend to think there’s hardware issue.
First thing I’d do is reseat any connections to the HDD and/or motherboard and make sure you don’t have a loose cable (I suspect not, but it doesn’t hurt to be sure).
You can try moving the drive to another computer and upload the image from there. If that worked, I’d suspect the hard ware in the original machine as being the problem.
If you got the same error, then I’d believe there’s a problem with the hard drive. At that point, I’d try another very basic image from a different hard drive and see if you can upload an image then.
-
[quote=“Bobfrid, post: 559, member: 224”]I think BryceZ is correct with suspecting a HDD problem.
From my experience “Buffer I/O Error’, ‘on device sda1’, ‘DRDY Error’, ‘ata1.00’, ‘logical block error’” is among a number of error messages that occur when a drive can’t be read at a certain point. Since you’re getting the same error using FOG and chkdsk, I would tend to think there’s hardware issue.[/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]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.
-
Well, if it’s deploying RAW and you get a bootable image and want to use it… I guess I’d deploy it, verify the hidden 100mb partition was restored by Windows, sysprep it, then upload the image again as Single Partition/Single Drive, and it should be able to resize it as intended and save you a lot of space and deploy time.
Unless I’m missing something or not understanding something else, I think that might work.
If you wanted to be sure, I’d just start with a new image of a fresh Win7 install that had the 100mb partition and verify your fog setup is accepting the Single Partition/Single Drive upload before attempting anything else. It’ll save a lot of time down the road, in my opinion. Once you’ve verified that part is working as intended, it’ll be easier to find any other issues that might occur.
