---
id: data-transfers.pieces-didnt-survive-the-interruption
url: https://storagestudio.us/faq/data-transfers/pieces-didnt-survive-the-interruption
category: "Data Transfers"
subcategory: "Downloads and large files"
question: "Why does a resumed download say some pieces “didn't survive the interruption”?"
alt_questions:
  - "pieces didn't survive the interruption"
  - "resuming pieces already here"
  - "download resumed but refetching pieces"
  - "Checked what had already downloaded"
short_answer: "On resume, pieces that were mid-write when the interruption hit are re-checked and fetched again. It's normal: only those few pieces are re-downloaded, and the log shows how many were already kept."
tags: ["download", "resume", "log messages"]
related: ["https://storagestudio.us/faq/data-transfers/large-downloads-resume-where-they-left-off", "https://storagestudio.us/faq/data-transfers/a-piece-couldnt-be-downloaded"]
applies_to: "app>=4.16"
last_reviewed: 2026-10-01
---

# Why does a resumed download say some pieces “didn't survive the interruption”?

When a large download resumes, Storage Studio first checks the pieces it already has. Any piece that was being written when the interruption happened — a crash, a power cut, the lid closing — may be incomplete, so it's set aside and fetched again. The log tells you how many.

That's normal and safe: only those few pieces are downloaded again, and everything else is kept. The log also shows a line like *"Resuming — N of M pieces already here"* so you can see how much was saved.

Related: [Large downloads that resume](https://storagestudio.us/faq/data-transfers/large-downloads-resume-where-they-left-off)