W7 Image: Disk read Error after imaging
-
This may be off base but are the drive settings in BIOS the same on both machines I have had similar issues when ahci is enabled on one but not the other.
RTFM
-
Where exactly does this `Disk Read Error’ occur?
What did you create your image on?
If you created the image on a physical machine, did you zero the HDD first?
Have you zeroed the destination machine’s HDD?
Have you pushed the image onto any other hardware?
-
@Joseph-Hales said in W7 Image: Disk read Error after imaging:
have had similar issues when ahci is enabled
You may be on to something here. I remember that someone had an issue with a dell, it was in uefi mode and the drive configuration was “raid-on” In that setup it would have issues imaging. I can’t remember the exact details (I read way too many threads) but moving the firmware setting from raid-on to achi resolved that specific issue.
-
@Joseph-Hales Both BIOS Configurations are identical and both drives are on AHCI mode.
-
Then I think you need to try what @sudburr suggested and wipe the drive fully before imaging.
-
This post is deleted! -
We were having a read error also, changed to the 2nd image type and it worked but created a large file. So, we then changed it back to 1st image type and selected Partclone GZip as the Image Manager, everything worked fine for us after doing this.
-
Got a little more info:
Partitions are swapped. The 100 MB partition for system usage is being read as C:.
And the C:\ is now the D\ drive.
-
@roger-jsf Can you please post a screenshot of the disk managment (partition layout) of your reference system. As well, please post the content of
d1.partitions,d1.minimum.partitionsandd1.fixed_size_partitions(all text files!) for this image on your FOG server (find those in /images/<IMAGENAME>/…). -
Here you go!
CONTENT OF PARTITION FILES:
-------d1.partitions----------
label: dos label-id: 0x55366f1b device: /dev/sda unit: sectors /dev/sda1 : start= 63, size= 80262, type=de /dev/sda2 : start= 81920, size= 204800, type=7, bootable /dev/sda3 : start= 286720, size= 976484352, type=7-------d1.minimum.partitions----------
label: dos label-id: 0x55366f1b device: /dev/sda unit: sectors /dev/sda1 : start= 63, size= 80262, type=de /dev/sda2 : start= 81920, size= 204800, type=7, bootable /dev/sda3 : start= 286720, size= 57298684, type=7-------d1.fixed_size_partitions--------
:1:2
-
@roger-jsf Thanks for posting the picture and listings. To me this looks pretty good. Nothing out of the ordinary as far as I can see. We were fighting with
type=departitions about a year ago but FOG should handle those properly since then!Can you please boot up this client that you deployed to with a debug deploy task again (normal deploy in FOG web GUI but check the debug checkbox in the view just before scheduling the task). Let the client boot and it will ask you to hit ENTER twice and drop you to a command shell. Run
sfdisk -d /dev/sdathere, take a picture and post it here.By the way: Which setting for “Operating System” is set for this image in the FOG web GUI? Is it “Windows 7 - (5)”?
-
@Sebastian-Roth Yes, “Windows 7 - (5)” is selected. Thanks!
I don’t know why but I can’t upload the image, so I have posted here: https://s2.postimg.org/djnk4qzvt/fog.jpg
-
@roger-jsf Ok, now I see why things go wrong. The start of the partitions are being moved. See the different numbers in the picture you posted.
Re-reading your initial post I just saw that you are using FOG 1.4.0. Sorry but I didn’t notice this earlier. Could you please upgrade to the very latest version. Tom has worked on this stuff and we need to see if the issue is still persistent in the current code. So please upgrade and re-deploy that same image to one of your clients.
-
@Sebastian-Roth Following Goeorge’s advice I updated to 1.4.2, created a new image , redeployed the image and it didn’t work.
-
@roger-jsf Forgive me if I already asked this. What hard drive is in the 3020? Is it a nvme or sata disk?
The reason I ask, for nvme you need to have 2 fixes for Win7 installed in the reference image or Win7 will not see the nvme disk.
-
@george1421 It’s a sata disk.
-
@roger-jsf Is this a new install of fog, meaning you haven’t used fog before for imaging? This is your first system or do you have history imaging with FOG?
-
@george1421 I’ve always used clonezilla for imaging, and wanted to try out FOG because I’ll have to image a large quantity of computers shortly.
In behalf of the FOG installation itself, it was a clean install in 1.4.0 and then I upgraded to 1.4.2 .
-
@roger-jsf Could you please upload /images/<IMAGENAME>/d1.mbr somewhere and post a download link here. Plus run
ls -al /images/<IMAGENAME>/and post the output here. I’ll try to replicate this issue then. -
@roger-jsf OK, I just wanted to know if this was a new problem (as compared to a previous version of fog).
So if you use clonezilla to copy the same master reference image it works correctly? Or did you use a new reference image for FOG too?
I’m trying to rule out the reference image being at fault here. There are some drivers that must be embedded into reference image before capture.
