stdin corrupted crc32 mismatch
-
Hi
I’m using the latest trunk. I uploaded an image of a dell latitude E7470 laptop. It uploaded seemingly OK.I choose win 7 OS
Single Disk -Resizable (same as we used to in fog .32, although it also said NTFS only)
Parition - EverythingI tried to deploy to another E7470 but got the above error.
-
I tried to upload the image again, but now I get a warning that it thinks windows is corrupt and wants me to run check disk /f…
This is a brand new laptop from dell so it’s strange there could be corruption. Anyway I’ll run checkdisk and try again.
-
Still no good after a reupload after a check disk.
This is the disk of the laptop I’m trying to upload. It’s an OEM image.
-
@andyroo54 Have you another computer with that OEM image ? It would be interesting to test with another hard disk.
-
@andyroo54 I am sorry to say this but your partition layout is not very easy to handle for FOG. Not sure how FOG 0.32 handled this but the recovery partition in between boot and system partition might confuse FOG trunk. That said I wonder if you ever tries “Single Disk - Multiple Partitions” (non resizable)???
-
I’m still getting this error, but it’s inconsistent. It only happens sometimes… sometimes an image job will work perfectly, other times I get this CRC32 error. I’m using my standard SOE not the one I originally linked in this forum post. It just has normal 100Mb system reserved, then the rest is on one partition.
Its almost like an error from the partclone transfer?
-
Doesn’t CRC check for broken sectors? Is it possible the target HDD has a couple of broken sectors?
-
@Quazz It happens randomly though. It’s the same image being deployed every time, yet we randomly get these CRC errors. I think it’s maybe a glitch with partclone.
-
@andyroo54 when I was having the random crc issues it was related to my servers storage setup getting corrupt. I was using a glusterfs setup with was always problematic at best within my environment. In fact, it was the reason I added the --ignore_crc flag. In most cases the crc issue was fixed after adding the flag but if the data was corrupted enough I’d get partclone all the way to 100% then the same errors you’re seeing.
What is output on the server when this happens from the command
dmesg? -
@Tom-Elliott I just got another CRC32 this is the output Tom:[img]http://i.imgur.com/L2RtsT2.png[/img]
-
-
@andyroo54 What is your server disk where you have /images stored on? Maybe try
dmesg | grep sda(if /dev/sda is your disk…) -
@Sebastian-Roth It’s on a RAID 5 storage of sandisk SSD’s in a HP DL380 server.Do you think the SSD’s might be causing an issue?
-
@andyroo54 From the output you posted I am not sure if sda really is your system disk… Maybe show us the output of
lsblk…Soft RAID or real hardware RAID controller??
-
[img]http://i.imgur.com/VKHFXuc.png[/img]
It’s hardware RAID in a HP DL380 server running esxi 5.5
-
@andyroo54 I’m assuming it’s formatted as either ext3 or ext 4. Maybe run a full blown fsck on it?
-
@Tom-Elliott I booted into the live CD and ran this and this is the output. Not sure if I’m doing it right
[img]http://i.imgur.com/xxqdVop.png[/img] -
I ran gparted instead.
[img]http://i.imgur.com/dvR2ImK.png[/img]
[img]http://i.imgur.com/pUJgcwZ.png[/img]
[img]http://i.imgur.com/OP3hB69.png[/img]
FYI, after using gparted, I was able to deploy the image without a CRC32 error. I’ll do some more testing to be sure! Thanks guys
-
@andyroo54 Are you able to deploy do a differnent machine/disk?? Possibly the destination disk is the problem??
-
@Sebastian-Roth I don’t think it was destination disk. I think the raid has some corruption. But we wouldn’t have seen it directly as it was mounted as an individual disk. When he went into gparted, it found the corruptions and was able to take a course of action.