Is it possible you have a faulty disk?
this post was submitted on 31 Jul 2023
33 points (94.6% liked)
Selfhosted
40018 readers
830 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
I would second the bad disk. I thought bad permission but since since it seems intermittent, the bad disk is the better guess. It would be good to get more info like what’s it running on, is it an array, etc.
Maybe! I'd start checking dmesg logs and check the smart info provided you do regular tests. Otherwise do some SMART tests and check the results after.
it wouldn't be bad to know what the error says
If you're not working over a VPN, it may be your ISP trying to stop you from torrenting. Otherwise I have no guesses unfortunately.
...how can I see that? The torrent just goes "error" on the UI. Not sure where it saves logs on my container, or what to look for specifically.
Sadly I live in Asia where they couldn't care less about what I download. Torrent is not blocked, and I download consistently at very high speeds.
Deleted
I would look into either a permissions issue (the daemon having no permissions to write in your target folder), or a faulty disk issue. I’ve had a similar issue in the past and the former was the cause.
Your description seems coherent with the torrent downloading normally until the memory buffer is full, and then failing when the data is attempted to be written to the disk.
Thanks. Your last sentence really makes sense. It's writing to a NAS, and sometimes the download speed is clearly higher then the NAS max write speed.
have you updated deluge to the latest? many trackers block older versions so you have to keep it current.
Hmmm it's on 2.0.3. Took me some fiddling back in the day updating from v1.x to 2.x...But there's no further versions correct?
2.1.1 is the latest. I think that should be your next step. not sure how you installed it, but the process should be quick be it in windows. Docker or Linux.
In Linux with headless+specific libraries dependencies + remote client + remote client dependencies last time the upgrade was a royal pain in the butt... But I'll look into it