Data corruption following a thunderstorm

hello,

as mentioned, I’m dealing with data corruption caused by a thunderstorm (on my NAS).

I’m currently deleting my corrupted Borg archive (irrecoverable BTRFS errors).

This is shaping up to be a particularly long process (at least an hour for a 1 TB archive).

I wanted to delete the archive using rm -rf, but both Claude and ChatGPT advised against it.

I don’t know what to do to delete this archive and recreate it from scratch later.

What is your advice?

Docker Borg-Web-UI on Zima OS and

Vorta on Debian Testing (functional)

i had to supress my borg archive .
i also rewrote 2 multimedia files which were damaged .

now , making a scrub .
hope il will end ggod …

Every 10.0s: sudo btrfs scrub status /DATA/.media/Dany-Main-Storage ZimaOS: Sat 18 Jul 2026 10:40:31 PM CES
in 0.027s (0
UUID: a327f5d4-f069-7380-ae4d-51fab01a4ab2
Scrub started: Sat Jul 18 16:45:56 2026
Status: running
Duration: 5:54:35
Time left: 1:00:09
ETA: Sat Jul 18 23:40:40 2026
Total to scrub: 14.26TiB
Bytes scrubbed: 12.19TiB (85.50%)
Rate: 600.91MiB/s
Error summary: csum=896
Corrected: 0
Uncorrectable: 896
Unverified: 0

For now, strangely enough, I haven’t been able to fix the problem.

All right, problems solved.
Still, I think I need a UPS.
Which one (how many VA?) would you recommend for
a 650-watt power supply? (My NAS, Zima OS)

thinking to this one :
onduleur eaton 1200VA

What do Btrfs errors mean in the case of file corruption caused by a thunderstorm?
It seems I’ve had a lot of checksum errors.

Can someone explain how Btrfs works in this situation?