![]() This can be a bug in the binary (which is somehow unexpected with the ARMv8 image, using native Debian builds which are expected to be stable) or a limitation related to filesystem access, possibly related to NTFS, but not sure. Transmission runs into a segmentation fault, which generally means an unallowed memory access. Until then, NTFS with ntfs-3g driver (for emulated UNIX permissions and partial symlink support) implies high CPU load in I/O which may have an effect on download speeds. NTFS drive could be related indeed, since NTFS is not natively supported by Linux, but coming with next Linux LTS version: USB boot is generally unrelated, this is a pure userland issue. Hmm, DHT and PEX are enabled by default on qBittorrent, Deluge and Transmission, but should be about finding peers only, not about whether download really starts or not.Ĭurrently not sure what the percentage on connected peers mean, but I guess it is about how much of the file was downloaded from that peer, at least that would make sense. ![]() Would greatly appreciate any help around this.Įdit : On my router, I’ve opened the port 8096 on the static IP of my raspberry pi to user Jellyfin remotely. The main reason I got a pi was to use it with torrents but none of the clients seem to be working fine for me. I restart the service and it works for some time and then runs into the same problem. Jan 26 16:28:31 DietPi systemd: rvice: Failed with result 'signal'. Jan 26 16:28:31 DietPi systemd: rvice: Main process exited, code=killed, status=11/SEGV Based on one of the threads, I ranĪnd it gave me following at the bottom with one of the torrents : Jan 26 16:28:23 DietPi transmission-daemon: Attack on Titan S1 - S3+OVA IPv4 DHT announce failed (firewalled, 163 nodes): Success (tr-dht.c:737) I tried that as well and the transmission-daemon still fails. I went through some threads that suggest reducing the max cache to a smaller number. Under dietpi-services, it shows me “failed” for transmission-daemon. ![]() What could be causing the slow speeds ? Is it the USB boot ? NTFS harddrive ? Further, the biggest problem I face with transmission is that it randomly stops working. The speed wouldn’t go beyond 3.2 MBps but at least it could download a few files. Surprisingly, transmission could download the same torrent. Since qBittorrent and deluge weren’t working, I went to transmission. I see none of the connected peers at 100% though the same torrent downloads at around 13MBps on my windows laptop. ![]() The same happens with deluge.Īdditionally I’ve observed that all the peers listed under “peers” are at status 0%. I have provided permissions to the download directory using dietpi-explorer. It initially shows the peers connected like 3(500) but nothing actually downloads. I added the Ubuntu LTS torrent to test and it shows me the number of seeds and peers in the client. Suddenly after that it doesn’t download any other torrent. I managed to download one torrent using qBittorrent. With all this done, I am running into several problems with all the torrent clients Installed qbittorrent, deluge and transmission on it using dietpi-softwares.Mounted an external NTFS HDD using dietpi-drive_manager.Did a complete headless setup with a static IP and wireless connection.Installed the ARMv8 64-bit image on it using a USB boot.I have recently acquired a Raspberry Pi 4B (4GB) and I’ve done following to set it up :
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |