Find Corrupted Torrents

Take care while deleting files within your torrent session state. We do not take any responsibility for accidental data deletion and cannot restore deleted data. The below procedures are provided for our clients to use at their own risk.

This guide will cover how to find and remove a corrupted torrent in your torrent client. Occasionally, a torrent can become corrupted and cause your torrent client to crash. This can be somewhat complicated to troubleshoot and diagnose, as there are many reasons for why a torrent client might crash.

Before we begin, let's introduce the available torrent clients, their strengths, and weaknesses. The information below will help you decide what torrent client to use. Please note that the below characteristics are highly subjective and may not align with your specific use case. The number of torrents listed is are soft limits.

These torrent clients are running in a shared environment on We do not recommend nor officially support torrent clients with torrent sessions above these limits.


If your qBittorrent instance is able to start up, but immediately becomes unreachable, it is possible that you have torrent files that are corrupted. To locate a corrupt torrent file in qBittorrent, you need to monitor the log output. Logging is enabled by default in qBittorrent and no further action is needed to get started.

If the qBittorrent log file throws torrent file errors without the hash string included, you need to locate the torrent hash from someplace else. A possible solution is to upgrade your qBittorrent instance to a newer version (if you aren't already on the newest version) and restore your torrent session. Then, restart qBittorrent and fetch the torrent hash from the webUI before qBittorrent crashes. This is not always possible, but will work in some cases. See our Torrent Session Migration guide for instructions on how to restore a torrent session.

tail -f ~/.local/share/qBittorrent/logs/qbittorrent.log
cat ~/.local/qbittorrent/logs/qbittorrent* | grep -i unable
rm ~/.local/share/qBittorrent/BT_BACKUP/fe44aede868a38dab52263da06e1e1bddc693136.torrent


To locate a corrupt torrent file in rTorrent, you need to monitor the log output during the crash of rTorrent. By default, rTorrent logging is disabled and needs to be enabled.

Enabling logging of rTorrent should only be done temporarily. Leaving logging enabled for a prolonged time will create very large log files, and could lead to your storage being filled up.

mkdir ~/.config/rtorrent/logs && cp -r ~/.config/rtorrent/session ~/.config/rtorrent/session.bak
nano ~/.rtorrent.rc
log.open_file = "rtorrent", ~/.config/rtorrent/logs/rtorrent.log
log.open_file = "tracker", ~/.config/rtorrent/logs/tracker.log
log.open_file = "storage", ~/.config/rtorrent/logs/storage.log
log.open_file = "network", ~/.config/rtorrent/logs/network.log
log.add_output = "info", "rtorrent"
log.add_output = "critical", "rtorrent"
log.add_output = "error", "rtorrent"
log.add_output = "warn", "rtorrent"
log.add_output = "notice", "rtorrent"
log.add_output = "debug", "rtorrent"
log.add_output = "dht_debug", "tracker"
log.add_output = "tracker_debug", "tracker"
log.add_output = "storage_debug", "storage"
tail ~/.config/rtorrent/logs/storage.log
rm ~/.config/rtorrent/session/TORRENTID*

Revision #7
Created 14 January 2024 12:06:02 by varg
Updated 26 April 2024 11:04:50 by varg