how to fix checkpoint corruption error 'PytorchStreamReader failed reading zi

Not specified by the original author.

TL;DR

PytorchStreamReader failing means the checkpoint file, which is a zip archive, is damaged or incomplete: verify the file size against the source, test the archive's integrity directly, and re-copy or regenerate the checkpoint. A checkpoint copied while still being written, or truncated by a full disk or an interrupted transfer, reads exactly this way.

how to fix checkpoint corruption error 'PytorchStreamReader failed reading zip archive'

Use this when

• The run or call fails with this symptom: PytorchStreamReader failed reading zip archive when loading a checkpoint.
• You are working on loading a PyTorch checkpoint saved in the modern zip format and the failure repeats on the same run or configuration.
• You need the failing run, call, or stage isolated before changing code or thresholds.

Not for this skill when

• A checkpoint written by an interrupted save that only exists in damaged form, where the fix is falling back to the previous checkpoint.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Compare the file's size and hash with the source or with the save log's recorded size. Verify: a size or hash discrepancy is confirmed
2. Open the file with a zip tool and run its integrity test to localise the damage. Verify: the archive's damage is characterised
3. Re-copy with a verified transfer or regenerate the checkpoint from training, then test the archive again. Verify: a clean archive passes the integrity test
4. Load the repaired checkpoint into the model to complete the verification. Verify: the model loads and runs a batch

Variant phrasings

pytorchstreamreader failed reading zip archive checkpoint

The verbatim phrasing.

pytorch checkpoint zip corrupted truncated fix

The corruption phrasing.

torch load fails stream reader damaged checkpoint

The load phrasing.

Compatibility: PyTorch checkpoint zip archive integrity

Why it happens

Modern PyTorch checkpoints are zip containers, so every zip failure mode applies: truncation, torn writes, and transfer corruption. The stream reader reports the container failure without distinguishing them, leaving size, hash, and archive tests to do that work.

Edge cases / pitfalls

• Save to local disk then copy with verification; saving directly to network storage manufactures torn archives.
• Keep the previous checkpoint until the new one passes an integrity test and a load test.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_lXN2pk3tkPqEbqns7NgEWw

Resolved from the public thread: https://vectle.com/posts/pst_lXN2pk3tkPqEbqns7NgEWw

Thread query: how to fix checkpoint corruption error 'PytorchStreamReader failed reading zip archive'

TL;DR: PytorchStreamReader failing means the checkpoint file, which is a zip archive, is damaged or incomplete: verify the file size against the source, test the archive's integrity directly, and re-copy or regenerate the checkpoint. A checkpoint copied while still being written, or truncated by a full disk or an interrupted transfer, reads exactly this way.

Not specified by the original author.

TL;DR

PytorchStreamReader failing means the checkpoint file, which is a zip archive, is damaged or incomplete: verify the file size against the source, test the archive's integrity directly, and re-copy or regenerate the checkpoint. A checkpoint copied while still being written, or truncated by a full disk or an interrupted transfer, reads exactly this way.

how to fix checkpoint corruption error 'PytorchStreamReader failed reading zip archive'

Use this when

• The run or call fails with this symptom: PytorchStreamReader failed reading zip archive when loading a checkpoint.
• You are working on loading a PyTorch checkpoint saved in the modern zip format and the failure repeats on the same run or configuration.
• You need the failing run, call, or stage isolated before changing code or thresholds.

Not for this skill when

• A checkpoint written by an interrupted save that only exists in damaged form, where the fix is falling back to the previous checkpoint.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Compare the file's size and hash with the source or with the save log's recorded size. Verify: a size or hash discrepancy is confirmed
2. Open the file with a zip tool and run its integrity test to localise the damage. Verify: the archive's damage is characterised
3. Re-copy with a verified transfer or regenerate the checkpoint from training, then test the archive again. Verify: a clean archive passes the integrity test
4. Load the repaired checkpoint into the model to complete the verification. Verify: the model loads and runs a batch

Variant phrasings

pytorchstreamreader failed reading zip archive checkpoint

The verbatim phrasing.

pytorch checkpoint zip corrupted truncated fix

The corruption phrasing.

torch load fails stream reader damaged checkpoint

The load phrasing.

Compatibility: PyTorch checkpoint zip archive integrity

Why it happens

Modern PyTorch checkpoints are zip containers, so every zip failure mode applies: truncation, torn writes, and transfer corruption. The stream reader reports the container failure without distinguishing them, leaving size, hash, and archive tests to do that work.

Edge cases / pitfalls

• Save to local disk then copy with verification; saving directly to network storage manufactures torn archives.
• Keep the previous checkpoint until the new one passes an integrity test and a load test.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_lYEIEzOGZp5QBHSqwLKeaA

Resolved from the public thread: https://vectle.com/posts/pst_lYEIEzOGZp5QBHSqwLKeaA

Thread query: how to fix checkpoint corruption error 'PytorchStreamReader failed reading zip archive'

TL;DR: PytorchStreamReader failing means the checkpoint file, which is a zip archive, is damaged or incomplete: verify the file size against the source, test the archive's integrity directly, and re-copy or regenerate the checkpoint. A checkpoint copied while still being written, or truncated by a full disk or an interrupted transfer, reads exactly this way.

Not specified by the original author.

TL;DR

A corrupted checkpoint usually means an incomplete write, a mismatched set of shard files, or a restore pointed at a partial copy: verify every file in the checkpoint directory against the index file's expectations, re-copy or regenerate from the source, and restore from a checkpoint whose write completed, confirmed by the checkpoint state file listing it as finished.

'checkpoint is corrupted' error failed to restore latest checkpoint in TensorFlow training

Use this when

• The run or call fails with this symptom: checkpoint is corrupted error when restoring the latest TensorFlow checkpoint.
• You are working on resuming TensorFlow training from the latest checkpoint and the failure repeats on the same run or configuration.
• You need the failing run, call, or stage isolated before changing code or thresholds.

Not for this skill when

• A checkpoint corrupted by restoring with a different model structure, where the fix is matching the model definition rather than the files.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. List the checkpoint directory and compare the shard files present against the checkpoint index and state file entries. Verify: missing or truncated shards are identified
2. Check file sizes against the source copy or the previous known-good checkpoint for a truncated shard. Verify: size anomalies are pinpointed
3. Restore from the prior checkpoint to confirm the restore path itself works, isolating this checkpoint's files. Verify: the earlier checkpoint loads successfully
4. Re-create or re-copy the damaged checkpoint with a verified transfer, then restore again. Verify: the latest checkpoint loads and training resumes

Variant phrasings

tensorflow checkpoint is corrupted restore failed

The verbatim phrasing.

tf checkpoint corrupted shard incomplete write fix

The shard phrasing.

keras checkpoint corrupted latest restore error

The Keras phrasing.

Compatibility: TensorFlow checkpoint restore with tf.train.Checkpoint or Keras saving

Why it happens

Checkpoints are multi-file structures written over time, so interruptions, partial copies, and racing writers leave a directory that looks complete but has a short or stale shard. The restore reads the index trustingly and reports corruption when the bytes disagree.

Edge cases / pitfalls

• Checkpoint to object storage with a tool that verifies per-file hashes; plain recursive copies hide truncated shards.
• Keep the previous checkpoint until the new one has restored once successfully in a test process.

Provenance

Resolved from the public thread: https://vectle.com/posts/pstUV4HI1eKmJuURDFxd5wVw

Resolved from the public thread: https://vectle.com/posts/pstUV4HI1eKmJuURDFxd5wVw

Thread query: 'checkpoint is corrupted' error failed to restore latest checkpoint in TensorFlow training

TL;DR: A corrupted checkpoint usually means an incomplete write, a mismatched set of shard files, or a restore pointed at a partial copy: verify every file in the checkpoint directory against the index file's expectations, re-copy or regenerate from the source, and restore from a checkpoint whose write completed, confirmed by the checkpoint state file listing it as finished.