• Posts

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Viper359's Achievements


Newbie (1/14)



  1. For whatever reason, within a few days of a pihole update, my pihole stops working. Lost connection to API, all DNS stops working et. No amount of stop/starting fixes it. The first time it happened, I tried all the common troubleshooting tips. However, now, its just faster to remove the image, and the data, and reinstall since the only setting I change is the IP. Everything chugs along fine until the next update Pihole doesn't update enough for this to drive me mad, but next time, I would like to dig deeper. Any suggestions on where to start? Nothing jumps out other than DNS Service is not listening.....
  2. So just updated now and now it will not download new torrents. Checked the error log and I found the following...... (W) 2021-09-11T10:04:01 - File error alert. Torrent: "Torrentfilenamehere". File: "/downloads/Torrentfilenamehere". Reason: Torrentfilenamehere file_open (/downloads/torrentfilenamehere) error: No space left on device There is 50TB of space. It worked fine before upgrade. Now it doesn't. What changed? Oddly enough, the BT client is reporting 50TB free. URG
  3. Thanks for the tip of trying the new Speedtest app by henrywhitaker3. its working perfectly. Now I actually get my real speed test results. The other app never worked for me, only showed 30MB/s when I have 1.5Gbps connection.
  4. I am not using a VPN tunnel. I have it off.
  5. Ok, I for the life of me cannot figure out what is going on. The debug log shows no errors et Torrent is added, downloads at ISP speed. Then slowly comes to a stop, and peers drop off the peers list. After 1 minute, its stopped uploading and downloading. Zero peers show in the list If I hit update tracker, it will grab peers and wash rinse repeat
  6. Now I need to figure out how to access my Unraid Shares from within Synology
  7. We are just going to have to wait until @dmacias has time to update and finish his plugin.
  8. Yes, I switched and all my problems went away. Left my interposers in. Since all issues went away, I stopped trying to debug what the actual issue was.
  9. I too had this issue for the last few days. Used TOP to get process ID, then killed it, than typed WSDD Windows network locations showed back up after restarting typing just WSDD, or, that did nothing, and it automagically starts back up. Hopefully, it stays normal
  10. Had a different parity drive fail that night. Switched out the HBA to an LSI one. Rebuilt the parity drive. Ran 10hrs, no errors Started Rebuilding the other dropped drive. 21 drives running now, we shall see if this was the issue. Just waiting for rebuild to finish on the last drive.
  11. Alright, later tonight I will power down everything and make the switch and see what happens. I will also triple check the cables are seated properly. Those QSFP cables are thick and don't like to move.
  12. Yes, I believe that is the model I am using. I do have an LSI HBA card and a spare QSFP to whatever adapter cable. Maybe I should try this first. Do a rebuild, and see if it stays stable.
  13. I will have to downgrade and give it a go and see. Is it safe to downgrade now that its kicked a disk out of my array, and then rebuild it, and go from there?
  14. This is just the thing, this didn't happen on 6.7. Does this make any sense? Its a disk shelf, and everything seems to be working. The only thing I can thing of is the interposers, but, you would think I would have had this issue on 6.7 for the couple weeks I was running it? The other thing I cannot get, why do these errors only happen after a rebuild? Like I rebuilt the parity drive, nothing happen. Within an hour of it finishing, bam. Same when disk 11 was causing issues. Rebuilt the disk, nothing, hour or so later, boom.
  15. It has done it again. I am attaching my diagnostics. You will notice several disks report low amount of errors, and 1 drive has been kicked.