# Missing blobs detected by 100% verify

**URL:** <https://kopia.discourse.group/t/missing-blobs-detected-by-100-verify/3319>\
**Category:** General Topics\
**Created:** [October 1, 2024, 12:51am UTC](https://kopia.discourse.group/t/missing-blobs-detected-by-100-verify/3319 "2024-10-01T00:51:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MFX](https://avatars.discourse-cdn.com/v4/letter/m/df788c/32.png) [@MFX](https://kopia.discourse.group/u/MFX)\
**Post date:** [October 1, 2024, 12:51am UTC](https://kopia.discourse.group/t/missing-blobs-detected-by-100-verify/3319/1 "2024-10-01T00:51:24Z")

</div>

I’m still testing but am struggling to understand what happens when Kopia verify detects problems and how to recover from those problems (Write a replacement blob?).

Making things worse? Any time Kopia hickups like this - it immediately dismounts all teh Diskcryptor drives on this system. I’ve used Diskcryptor for years, perhaps over a decade - and not once has it ever glitched on me except when running Kopia. Very surprising stuff.

Strangely, a “restore to a new disk while ignoring any errors” seems to work smoothly with no lockups.

The repository here is 2ea unencrypted USB 3 disks mounted as a Raid 0 equivalent.

---

<div class="post-metadata">

**Author:** ![kapitainsky](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/kapitainsky/32/535_2.png) [@kapitainsky](https://kopia.discourse.group/u/kapitainsky)\
**Post date:** [October 1, 2024, 5:25am UTC](https://kopia.discourse.group/t/missing-blobs-detected-by-100-verify/3319/2 "2024-10-01T05:25:21Z")

</div>

> **[Verifying Validity of Snapshots/Repositories and Trying to Repair Any Corruption](https://kopia.io/docs/advanced/consistency/#repairing-corruption)**
>
> Fast and Secure Open-Source Backup Software for Windows, Mac, and Linux