error when deploy

[pmonstad]

Running svn 7567 I cannot deploy an image to a computer. One computer with an image works but another with a different image does not. The client says An error has been detected!

Image failed to restore and exited with exit code 0 (writeImage)
Args Passed: /images/r61/d1p1.img* /dev/sda1

This path is not correct as the image is located in /home/images/r61 which is also the path found if I edit the Image in FOG gui.

It even says I can check log at /var/log/partclone.log There is no such log available (running Centos 6)

Any idea what is wrong?

[Tom Elliott]

@Quazz True, I didn’t look up part numbers, just trying to understand.

Guess I’m trying to see if it ALL hdd’s of the same part number or maybe just a bad batch of HDD’s that were created, or something on the drives is actually stopping things from happening.

[Quazz]

@Tom-Elliott He posted the part numbers earlier, they’re regular HDDs.

[Tom Elliott]

@TheKoR Just a guess, but they’re ssd, possibly with a protected NAND?

[TheKoR]

The HDD works well if you make a cd install. just this 3 type don’t accept imaging

[Tom Elliott]

@TheKoR I don’t understand what you mean. The error is happening because of the HDD having an issue or is there a workaround?

[Sebastian Roth]

@pmonstad said in error when deploy:

Image failed to restore and exited with exit code 0 (writeImage)

There should be an error in the blue partclone screen before you see this. Please take a short video of the partclone stuff and upload here. Try setting the camera/smartphone on a couple of books on your desk so you have a steady picture and we can read/see the error clearly.

[TheKoR]

Hi,

i have this problem with some Dell optiplex 380 - windows 7.

Running Version: 8088

But it’s not the machine in cause, it’s the Hard drive.

Error come with
Seagate p/n : 9W2854-001 (5 of it)
Samsung p/n HD083GJ/D (3 of it)
Western Digital p/n 0NR694

[Tom Elliott]

Moved to FOG Problems as the information described is NOT a bug. There’s a viable issue somewhere, but not one that is directly caused by what FOG is doing during the imaging process.

[Tom Elliott]

The path IS correct. /var/log/partclone.log is on the client machine (viewable if you have the tasking in debug.)

The Path you see on the client is 100% correct because we create /images on the client, and the NFS get’s mounted to /images on the CLIENT machine. So, /images/r61/d1p1.img* is respective of the client, not the full mount point.

The issue, as it seems to me, is it’s failing to image using that file, although it is finding that file.