bOt

The original post: /r/torrents by /u/tcollins317 on 2025-07-16 21:21:13.

I was using Xirvik and it worked great. Then I was trying torrent2box, but I keep getting an "unauthorized" error.

I can use a Firefox option as well, but I read that Xirvik will spam you to buy their seedbox service.

Any ideas?

* I meant magnet link.

The original post: /r/torrents by /u/317seref on 2025-07-16 20:09:37.

Hello,

I'm trying to use the search engine feature in qBittorrent, and I've added plugins from this page:

https://github.com/qbittorrent/search-plugins/wiki/Unofficial-search-plugins

However, when I perform a search, no results appear. I suspect this might be due to DDoS protection or something similar on the websites.

Is there a way to bypass or fix this issue?

Thank you in advance.

The original post: /r/mullvadvpn by /u/LilithLamm on 2025-07-13 20:52:22.

Is it actually possible to use Adguard and Mullvad apps together on Android? I have spent the past 2 hours trying all the different methods described on Reddit, Github, the Adguard website, and the Mullvad website. Nothing has worked. Some posts say you can use the Apps together, some say you can only use the Adguard DNS with Mullvad. Which is the correct answer? I like using Adguard because of it's features besides DNS filtering, but it seems to be impossible to get the two to work together.

I have a Pixel 9 pro xl with Android version 15. Both Adguard and Mullvad apps are up to date as well.

The original post: /r/datahoarder by /u/masturbaiter696969 on 2025-07-12 04:44:12.

I am currently using two 1.5tb hard drives from 2009. They are very slow and starting to grow in bad sector count. Running sha256sum on these takes forever and I feel like running that also wears them out quicker.

I am thinking about buying some bx500 ssds or western digital blue hard drives.

The computers will be on almost all the time. While the drives are not going to be mounted all the time, I think the power supply will still supply them with power, so I don't have to worry about ssd data retention, is that correct?

I will be running sha256sum frequently, and from my understanding ssds are not really worn out by reads while hard drives are, is that correct?

I don't have money issues so i'm leaning towards ssds. Is there any downsides to ssds in my situation?

The original post: /r/datahoarder by /u/SUCK-PIT on 2025-07-12 00:21:07.

The original post: /r/datahoarder by /u/First_Musician6260 on 2025-07-12 00:13:59.

The original post: /r/datahoarder by /u/zilexa on 2025-07-11 23:59:00.

Just wondering, I live Prowlarr + Sonarr + Radarr + QB. But is there a more simplified, potential all-in-one app ? Where you can simply add shows/movies you want to watch. And don't need to go find public trackers on Prowlarr first, integrate the apps with each other through their API keys and with their local IP addresses etc.

I love the NZB360 app for Android (a very friendly umbrella GUI over all *arr + QB) and I was just wondering why an app like that doesn't exist that does it all..

The original post: /r/datahoarder by /u/Ciapekq on 2025-07-11 22:27:59.

.

The original post: /r/datahoarder by /u/jaycenprogress on 2025-07-11 20:52:03.

It is Amazon Prime Day. I have the Synology in my cart for $354 and 2 16TB IronWolf Pro HDDs $269/each in my cart. I'd like advice on whether or not to pull the trigger. I'd love if all my data scattered across mutliple 1tb micro sd cards was just a central library in one place. I have up to or around 10TB worth of data that isn't backed up but would ensure to, to cloud services once I decide to purchase or not purchase the NAS. I've lots of media files ranging from movies, tv, anime, photos, music, etc. Has any one ever felt regret buying one? Did it improve data hoarding for you?

The original post: /r/datahoarder by /u/DiodeInc on 2025-07-11 20:46:05.

The original post: /r/datahoarder by /u/tryingtobecheeky on 2025-07-11 20:24:04.

I'm just genuinely curious if many people are gathering their data on paper.

The original post: /r/datahoarder by /u/abyssea on 2025-07-11 20:23:46.

One of the disks in my Unraid server is giving off these types of errors, meaning that portion of the drive is not accessible:

Jul 9 21:13:30 Tower kernel: sd 1:0:16:0: [sdr] tag#239 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=DRIVER_OK cmd_age=7s

Jul 9 21:13:30 Tower kernel: sd 1:0:16:0: [sdr] tag#239 Sense Key : 0x3 [current] [descriptor]

Jul 9 21:13:30 Tower kernel: sd 1:0:16:0: [sdr] tag#239 ASC=0x11 ASCQ=0x0

Jul 9 21:13:30 Tower kernel: sd 1:0:16:0: [sdr] tag#239 CDB: opcode=0x88 88 00 00 00 00 03 7f 2f 26 10 00 00 02 00 00 00

Jul 9 21:13:30 Tower kernel: critical medium error, dev sdr, sector 15018698736 op 0x0:(READ) flags 0x0 phys_seg 4 prio class 0

DiskSpeed reports back with:

|| || |Temperature Celsius||26| |Raw Read Error Rate||0| |Spin Up Time||9833| |Start Stop Count||903| |Reallocated Sector Ct||0| |Seek Error Rate||0| |Power On Hours||27295 [3 Years, 42 Days, 7 hours]| |Spin Retry Count||0| |Calibration Retry Count||0| |Power Cycle Count||20| |Power-Off Retract Count||17| |Load Cycle Count||897| |Reallocated Event Count||0| |Current Pending Sector||0| |Offline Uncorrectable||0| |UDMA CRC Error Count||0| |Multi Zone Error Rate||1094|

I know some data systems will mark bad sectors and avoid them, meaning less of the drive is useable but the drive isn't dead in the water. I've moved all the data from the drive on to another drive and performed an extended SMART test with Unraid, which came back without any issues.

Device Statistics (GP Log 0x04)

Page Offset Size Value Flags Description

0x01 ===== = = === == General Statistics (rev 1) ==

0x01 0x008 4 20

Lifetime Power-On Resets

0x01 0x010 4 27291

Power-on Hours

0x01 0x018 6 40039298553

Logical Sectors Written

0x01 0x020 6 42197995

Number of Write Commands

0x01 0x028 6 296149816379

Logical Sectors Read

0x01 0x030 6 417669825

Number of Read Commands

0x01 0x038 6 3758319488

Date and Time TimeStamp

0x03 ===== = = === == Rotating Media Statistics (rev 1) ==

0x03 0x008 4 21972

Spindle Motor Power-on Hours

0x03 0x010 4 21933

Head Flying Hours

0x03 0x018 4 914

Head Load Events

0x03 0x020 4 0

Number of Reallocated Logical Sectors

0x03 0x028 4 48008

Read Recovery Attempts

0x03 0x030 4 0

Number of Mechanical Start Failures

0x03 0x038 4 8

Number of Realloc. Candidate Logical Sectors

0x03 0x040 4 17

Number of High Priority Unload Events

0x04 ===== = = === == General Errors Statistics (rev 1) ==

0x04 0x008 4 7

Number of Reported Uncorrectable Errors

0x04 0x010 4 0

Resets Between Cmd Acceptance and Completion

0x05 ===== = = === == Temperature Statistics (rev 1) ==

0x05 0x008 1 34

Current Temperature

0x05 0x010 1 29

Average Short Term Temperature

0x05 0x018 1 24

Average Long Term Temperature

0x05 0x020 1 45

Highest Temperature

0x05 0x028 1 15

Lowest Temperature

0x05 0x030 1 40

Highest Average Short Term Temperature

0x05 0x038 1 18

Lowest Average Short Term Temperature

0x05 0x040 1 32

Highest Average Long Term Temperature

0x05 0x048 1 22

Lowest Average Long Term Temperature

0x05 0x050 4 0

Time in Over-Temperature

0x05 0x058 1 65

Specified Maximum Operating Temperature

0x05 0x060 4 0

Time in Under-Temperature

0x05 0x068 1 0

Specified Minimum Operating Temperature

0x06 ===== = = === == Transport Statistics (rev 1) ==

0x06 0x008 4 35

Number of Hardware Resets

0x06 0x010 4 0

Number of ASR Events

0x06 0x018 4 0

Number of Interface CRC Errors

And

SATA Phy Event Counters (GP Log 0x11)

ID Size Value Description

0x0001 2 0 Command failed due to ICRC error

0x0002 2 0 R_ERR response for data FIS

0x0003 2 0 R_ERR response for device-to-host data FIS

0x0004 2 0 R_ERR response for host-to-device data FIS

0x0005 2 0 R_ERR response for non-data FIS

0x0006 2 0 R_ERR response for device-to-host non-data FIS

0x0007 2 0 R_ERR response for host-to-device non-data FIS

0x0008 2 0 Device-to-host non-data FIS retries

0x0009 2 0 Transition from drive PhyRdy to drive PhyNRdy

0x000a 2 1 Device-to-host register FISes sent due to a COMRESET

0x000b 2 0 CRC errors within host-to-device FIS

0x000d 2 0 Non-CRC errors within host-to-device FIS

0x000f 2 0 R_ERR response for host-to-device data FIS, CRC

0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC

0x8000 4 908014 Vendor specific

Because the array is reporting 288 errors from the device, I'm not sure if the drive should be replaced, considering the other results. Looking for advice, thanks.