Random read or write errors to NAS stops downloads--"errors" seem to be "fake"

[Hammerhead]

I am getting random network read/write errors when saving torrents to a NAS. Those errors stops the torrent. But there's no actual problem. Restarting the torrent is 100% effective with no further errors for at least 30 minutes, but 60 minuts to 4 hours is more common before there is another error on some of these "slow" torrents. This seems to affect only random torrents though. Most torrents complete with no errors. Usually 1 torrent is active when this happens... and it is often a slow torrent (low speeds) that produces the random read/write errors. The log identifies whether it is a read or write error and says only that it is "an unexpected error." But clicking Start does restart the torrent again immediately as though there was no problem at all. I would estimate I can do 8 to 12 torrents (2 GB to 88 GB file-size range, and could be 1 file or 6 to 24 files in a group, no pattern to what torrents get this error. It's especially annoying if the torrent speed is not great and there was an error 20 minutes after I went to bed for the night with the download in progress... wake up next morning to no progress on the download due to a read or write error.

I never get random read/write errors on the network from any other software, nor from any other of the many devices in the house connected to the Ethernet network.

Windows 11 with qBit version 5.0.3 but this has happened randomly with older versions also. File sizes being saved over gigabit Ethernet from computer to NAS.

Is there a setting somewhere that will cause qBit to retry for a while after a read or write error before stopping the torrent? Nothing in the Options menu, including Advanced Options seems to have any settings related to this behavior. I do make a habit of doing "Recheck" at the end of torrent downloads where I have had these errors to make sure no data was lost, and every time, the Recheck is perfect and the download is completely fine.

[Gripweed107]

The only time I've gotten an error involving a NAS doesn't seem to fall into the same category as you describe. My error shows up occasionally when a certain torrent reaches its ratio limit and the torrent and files are removed. If the other torrenter(s) continues to try to get the files, it will sometimes throw an error, but not always. I have this happen, maybe, once a week. Most times there is only one notification, never more than two. It's not a biggie.