Failed to decode sector contents map: Checksum mismatch

Issue Report

I started to observe such errors:

Sep 27 14:29:30 ironfish2 subspace-farmer[2569349]: 2023-09-27T07:29:30.871044Z ERROR single_disk_farm{disk_farm_index=8}: subspace_farmer::single_disk_farm::piece_reader: Failed to read piece from sector sector_index=62 piece_offset=767 sector_count=93 error=Failed to decode sector contents map: Checksum mismatch
Sep 27 14:29:54 ironfish2 subspace-farmer[2569349]: 2023-09-27T07:29:54.706432Z ERROR single_disk_farm{disk_farm_index=8}: subspace_farmer::single_disk_farm::piece_reader: Failed to read piece from sector sector_index=62 piece_offset=767 sector_count=93 error=Failed to decode sector contents map: Checksum mismatch
Sep 27 14:30:18 ironfish2 subspace-farmer[2569349]: 2023-09-27T07:30:18.070572Z ERROR single_disk_farm{disk_farm_index=8}: subspace_farmer::single_disk_farm::piece_reader: Failed to read piece from sector sector_index=65 piece_offset=916 sector_count=93 error=Failed to decode sector contents map: Checksum mismatch
Sep 27 14:31:48 ironfish2 subspace-farmer[2569349]: 2023-09-27T07:31:48.954185Z ERROR single_disk_farm{disk_farm_index=8}: subspace_farmer::single_disk_farm::piece_reader: Failed to read piece from sector sector_index=58 piece_offset=564 sector_count=93 error=Failed to decode sector contents map: Checksum mismatch
Sep 27 14:32:37 ironfish2 subspace-farmer[2569349]: 2023-09-27T07:32:37.503175Z ERROR single_disk_farm{disk_farm_index=8}: subspace_farmer::single_disk_farm::piece_reader: Failed to read piece from sector sector_index=60 piece_offset=893 sector_count=93 error=Failed to decode sector contents map: Checksum mismatch

If a farmer sees that the plot is not OK, or rather, a specific sector in it, why does it not replot it?
I ran scrub on all the plots, and the check was successfully completed.

Environment

  • Operating System: Ubuntu 22.04.3 LTS
  • Pulsar/Advanced CLI/Docker: gemini-3f-2023-sep-25

Interesting, so you’re saying that scrub didn’t find any issues, but errors still happen? Did you do anything special or anything happened to the machine that might have caused this?

Replotting such sectors would be a good idea indeed, but it is a bit tricky to implement since these kinds of errors can happen for various things in various places. Scrub corrections should result in sectors being replotted after restart.

Exactly. :man_shrugging:

Nothing at all.

Would you be able to upload farm’s data somewhere (except identity.bin, you should keep that one private)?
It may help with debugging.

Scrub doesn’t check this particular aspect individually, but it does check things on a bit higher level. The only explanation I see so far why scrub wouldn’t see the error is if there was in-memory data corruption during plotting, so might be worth checking memory for errors, but otherwise having a copy of the farm files would be helpful in debugging.

magnet:?xt=urn:btih:78633cfa9c16b754f54feba23e201c62477cbd67&dn=plot8&tr=http%3a%2f%2fp4p.arenabg.com%3a1337%2fannounce&tr=udp%3a%2f%2f9.rarbg.com%3a2810%2fannounce&tr=udp%3a%2f%2ftracker.openbittorrent.com%3a6969%2fannounce&tr=http%3a%2f%2ftracker.openbittorrent.com%3a80%2fannounce&tr=udp%3a%2f%2fwww.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2ftracker.torrent.eu.org%3a451%2fannounce&tr=udp%3a%2f%2fopen.stealth.si%3a80%2fannounce&tr=udp%3a%2f%2fexodus.desync.com%3a6969%2fannounce&tr=udp%3a%2f%2fipv4.tracker.harry.lu%3a80%2fannounce&tr=http%3a%2f%2ftracker.hiyj.cn%3a80%2fannounce&tr=udp%3a%2f%2ftracker.tiny-vps.com%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.moeking.me%3a6969%2fannounce&tr=udp%3a%2f%2fopentracker.i2p.rocks%3a6969%2fannounce&tr=udp%3a%2f%2fexplodie.org%3a6969%2fannounce&tr=https%3a%2f%2fopentracker.i2p.rocks%3a443%2fannounce&tr=http%3a%2f%2ftracker4.itzmx.com%3a2710%2fannounce&tr=udp%3a%2f%2ftracker.dler.org%3a6969%2fannounce&tr=udp%3a%2f%2fbt2.archive.org%3a6969%2fannounce&tr=udp%3a%2f%2ftracker.opentrackr.org%3a1337%2fannounce&tr=udp%3a%2f%2fopen.tracker.cl%3a1337%2fannounce

1 Like

Pulling (although very slowly)

Since I created this torrent, the problem described above has not been repeated. Apparently, this is the "effect of the master ".

I’m still pulling the file, it is at 97.3% now. I’ll check it either way after download completes.

1 Like