When the failed RESTORATION (The image file is corrupted. <0x1779013400000005>) is done in the previous post, I don't know what criteria is used to determine the corruption. If the Devs are just using the image chain sequence #s (there's one missing now), the same check could be made when the image is actually done, giving the user a real heads-up on the state of their imaging chain at the earliest time after the actual break in the chain.
Edit: a quick check shows that FileName sequences are NOT USED for chain integrity testing.
Edit: a quick check shows that FileName sequences are NOT USED for chain integrity testing.