urbanracer34

Members
  • Posts

    166
  • Joined

  • Last visited

Everything posted by urbanracer34

  1. Upgrade successful. Had to do the command line thing with docker, but otherwise went off without a hitch.
  2. I can't find them. I've looked everywhere. I must be missing something. Do you happen to have a direct link?
  3. What is in the newest build of the container? I hope there isn't an update to qbittorrent as I have to use specific versions.
  4. This is exactly what I did. All checked OK but I'm not getting the speeds I usually got with rutorrent.
  5. I fixed this by manually assigning my ports on my docker. I hope that's it
  6. Hello, I was wondering how I can modify the port the Qbittorrent instance uses for connecting to other peers. I am listed as unconnectable. I'm currently using port 15276. I port forwarded on my router but the connection is refused. Thanks! GIBSON_UpdateContainer2.pdf
  7. @eske Thanks for the advice. I am a horrible coder so I really can't use scripts in my environment. Would just adding the original torrents from rutorrent's session folder, and not the "libtorrent_resume or "rutorrent" ones, to an new instance of an torrent client suffice? EDIT1: I have all 641 current torrent files ready to go to a new client.
  8. Hello. I updated my unraid server to 6.12 and I am unable to access my instance of rutorrent. It has been deprecated by the developer. It used to give me a prompt for webgui but it is no longer there. Every other docker has a webgui option. How can I bring over everything from rutorrent to qbittorrent? EDIT: Solved for now! Can access rutorrent after trying all the ports. Still need to know how to convert from rutorrent to qbittorrent.
  9. It's a WD BLACK 1TB NVME SSD on a daughterboard. Usually it reaches 45-46 C and gives off the warning, but this time it was 48C. AFAIK I haven't touched the temp alert thresholds. Info sheet here: https://documents.westerndigital.com/content/dam/doc-library/en_us/assets/public/western-digital/product/internal-drives/wd-black-ssd/data-sheet-wd-black-nvme-ssd-2879-810008.pdf I also looked at the rest of my drive's infosheets and the operational max temp is 60 or 70 C depending on the drive.
  10. So I have my server set up so at 12:20 and 6:20 AM and PM it will give me a status report via Pushover. Most of the time it's [PASS] but sometimes it's [FAIL] When I see it say FAIL, my stomach drops, my anxiety rises and I try to get access to my server to check. Most of the time it's a disk overheating (by 1-2 C) but I want the server to tell me that in the notification: Don't leave me hanging! How can I tell my server to send me this info in notifications?
  11. FYI there has been some movement on this WD finally allowed users to check drive warranties. All the WD drives in my server are out of warranty. I did a parity check and the parity drive had zero errors come up this time.
  12. Hello, I have an instance of binhex-rutorrentvpn that has over 600 torrents. I just realized today that the rutorrent docker was discontinued. How can I convert from rutorrent to qbittorrent without risk of data loss? We're talking terabytes of data. And how do I get the torrent files themselves out of rtorrent? Most of my Torrent files are in there.
  13. I may have figured this part out: The tool for warranty check is under maintenance right now. https://support-en.wd.com/app/systemmaintenance Maybe that is why my drives kept coming back with no records?
  14. Thanks. How do I tell the notifications my server sends to me to say array pass instead of fail because of the read errors?
  15. I got these from a reputable shop as far as I know. They were local to my area of town.
  16. OK. The SMART test is 70%. I only have the information on the unraid UI to find the serial number. Every serial number I try to find for warranty says it's invalid or no results. It's a Western digital drive. I heard the command "hdparm -I /dev/sdc" would help but it did not. Is there a command I can run from the terminal to somehow extract it? The store that I bought the drives from no longer exists.
  17. No errors were found during the parity check, but the errors I'm talking about were counted on the array DURING the parity check. I hope I'm making sense.
  18. OK! Thanks for the info. Here's the diagnostics post-check. gibson-diagnostics-20230403-1011.zip