Imagin Fails Every time
-
On one machine we are having the image constantly fail.
However, I just sued that image on another machine (and did it again to test). I have another nvme coming overnight. But this one passed the extended self test, but not sure that means much.
Strange that it says “read error” but I am guessing that was a read of a verification. But I have no clue.
I will report back if the new nvme fixes it. In the mean time any thoughts?
Thanks.
-
@Flyer The read error is misleading. The FOS scripts spin up a FIFO to uncompress the image data on the fly for partclone to write on disk. So a read error means the FIFO died. Mostly this is caused due to a corrupted image (not in your case as it deploys well to another machine) or faulty hardware - usually RAM - in the client machine.
-
@Flyer Is this indeed a real failure? Like can you boot the machine? Is the image you sent to it complete?
As Sebastian has stated, this error can be due to a proper read error, but it can also be due to an error on the FIFO closing before Partclone has finished it’s process verification.
FIFO is very memory sensitive and once no more data is to be read will be immediately discarded.
I suppose the rm statement we have might need to wait for partclone to exit first, though I don’t know 100% how to approach that, just thinking out text.
-
Thanks for the feedback, everyone.
You are absolutely correct! The new nvme had no effect
Memtest revealed a bad ram stick. Going to RMA that.
Thank you. Now I will try the imaging again after memtest passes a few times on the remaining RAM.
-
With the bad RAM removed the system imaged just fine with the same image. Thanks again.
