Need Help with qBittorrent Restart and all Files Missing #6569

Closed
opened 2026-02-21 18:29:28 -05:00 by deekerman · 2 comments
Owner

Originally created by @jeff15110168 on GitHub (Dec 14, 2017).

Please provide the following information

qBittorrent version and Operating System

3.3.11 x64 on Windows 10 x64

What is the problem

I restarted my computer after closing out of qBittorrent and when i rebooted the system, a list of nearly 500 torrents say "missing files" in red, ~8TB of seeding. The disks can all be reached normally and no errors are on any of the disks.

It would take FOREVER if i just click resume and make it force recheck all of these files (I did it for one torrent and it was able to be resume seeding after checking, so I know the file integrity is there).

Can anyone help me fix this without having to force recheck each and every single torrent? This is somewhat urgent as I have lots of private seeds that need to be seeded within an alotted time or they count as HnR.

Originally created by @jeff15110168 on GitHub (Dec 14, 2017). **Please provide the following information** ### qBittorrent version and Operating System 3.3.11 x64 on Windows 10 x64 ### What is the problem I restarted my computer after closing out of qBittorrent and when i rebooted the system, a list of nearly 500 torrents say "missing files" in red, ~8TB of seeding. The disks can all be reached normally and no errors are on any of the disks. It would take FOREVER if i just click resume and make it force recheck all of these files (I did it for one torrent and it was able to be resume seeding after checking, so I know the file integrity is there). Can anyone help me fix this without having to force recheck each and every single torrent? This is somewhat urgent as I have lots of private seeds that need to be seeded within an alotted time or they count as HnR.
deekerman 2026-02-21 18:29:28 -05:00
Author
Owner

@jeff15110168 commented on GitHub (Dec 14, 2017):

I checked the logs and it seems this has happened on the disk: (C) 2017-12-14 T20:58:51 - File sizes mismatch for torrent '[................].mkv', pausing it.

This has happened for over 500 torrents. It would take weeks for me to check each torrent's integrity again. I can't explain why this happened either....any ideas? Is there a backup I can restore to? Anything I can really do?

@jeff15110168 commented on GitHub (Dec 14, 2017): I checked the logs and it seems this has happened on the disk: (C) 2017-12-14 T20:58:51 - File sizes mismatch for torrent '[................].mkv', pausing it. This has happened for over 500 torrents. It would take weeks for me to check each torrent's integrity again. I can't explain why this happened either....any ideas? Is there a backup I can restore to? Anything I can really do?
Author
Owner

@sledgehammer999 commented on GitHub (Oct 29, 2020):

This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable.
If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.

A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.
Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.
Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.

Thank you for your contributions.

@sledgehammer999 commented on GitHub (Oct 29, 2020): This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable. If you experience the reported problem or similar in the **latest** version, please open a new issue report with the requested information in the issue template. A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression. Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar. Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression. Thank you for your contributions.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/qBittorrent#6569
No description provided.