tdunks

Members
  • Posts

    13
  • Joined

  • Last visited

tdunks's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Did anyone manage to find a fix for the timeout issues with SWAG? I am still getting timeouts on large files or updates
  2. I cant seem to get three containers to proxy through no matter what I do - these are my secondary sonarr/radarr containers and my plex container. On the dashboard all three state that they are unavailable and that SWAG can not reach them at http://[containername]:[port]. I have tried manually editing the configs to direct at the ip and port without any variables with no luck. I can't figure out what is going on here. All of the dockers except plex are on the dockerlocal network with plex having a host network. The normal sonarr and radarr containers work flawlessly.
  3. I changed the controller to a 9311 and no longer have errors with spindown on. It seems so be an issue only with the older controllers.
  4. Is it likely to be fixed by switching to a newer SAS3 HBA?
  5. It seems to have worked - I have attached both Diagnostics from after the EPC fix with errors and after disabling spindown to see if a cause can be identified. tower-diagnostics-20210415-1343.zip tower-diagnostics-20210413-1711.zip
  6. Will test next, but a basic feature line this as part of unraid shouldn't cause these issues, that's a lot of wasted power keeping them spin up all the time
  7. I have three St8000as002 drives that have started having this issue too but this fix did not work. All three have the exact same number of read errors only during parity checks and always near the end. I am not sure if there is another issue at work as well.
  8. I just did this fix and tried a parity check again with the same results. I'm not sure what else to try at this point.
  9. A few weeks ago I started getting read errors on three new-to-me drives that I recently picked up. These drives are all older 8tb Seagate Archive drives which I picked up off of someone in an unused state - they only have <2 months of power-on hours. I am only getting these read errors near the end of parity checks and only on these drives. The drives were pre-cleared without issue before having them be put in. I am currently using a supermicro SC846 case with a SAS2-EL1 backplane and an LSI 9205-8i HBA with both cables plugged into the backplane. I thought the added drives might be stressing the HBA so I added a 40mm fan to it with no change. I have also tried reseating the HBA and the cables, as well as changing the slots the drives are in. The odd thing is that all 3 usually have identical levels of read errors, sometimes only a few and sometimes tens or hundreds of thousands. The drives all pass extended SMART tests and don't seem to have any other issues. I have no idea what the issue could be here - I really doubt all 3 drives are failing in the same way at the same time but I don't see another issue? Could it be the HBA? if so, why only these drives? tower-diagnostics-20210411-1628.zip
  10. Both letsencrypt and Organizr updated today and one of which broke the organizr auth included in letsencrypt (SWAG). It just gives a 500 error now on any page that has auth enabled. Does anyone have a potential fix?
  11. Both letsencrypt and Organizr updated today and one of which broke the organizr auth included in letsencrypt (SWAG). It just gives a 500 error now on any page that has auth enabled. Does anyone have a potential fix?
  12. I cant seem to get the performance to where I want it. sabnzbd will level out at 30-50MB/s where it should be able to easily push 90-105MB/s. Currently running on a gigabit connection and have followed everything under the sabnzbd high speed downloading guide. Both the incomplete and complete are on my cache which is 4x400gb SSD in BTRFS raid0. Not sure where else to go to try to raise the speed. I am able to get 80+MB/s on nzbget but much prefer sabnzbd.