Jump to content

tjb_altf4

Members
  • Content Count

    367
  • Joined

  • Last visited

Community Reputation

43 Good

About tjb_altf4

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

1283 profile views
  1. Seems to be same issue looking at your logs @Pducharme Further discussion with some possible solutions: https://forum.level1techs.com/t/devops-workstation-fixing-nvme-trim-on-linux/148354
  2. Acording to intel's spec, that cpu only has 28 pcie lanes note: some of the higher tier cpus will unlock more lanes (44) on X299. https://ark.intel.com/content/www/us/en/ark/products/123589/intel-core-i7-7800x-x-series-processor-8-25m-cache-up-to-4-00-ghz.html You're probably near the limit and most certainly won't have another 16 lanes up your sleeve (probably only 4 spare).
  3. Good chance it's a pcie lane sharing issue... that is a common culprit. Check your mobo manual to see if your m.2 slots share lanes with other devices you may be using.
  4. Type docker stats into you terminal (ctrl+c to exit). You can also follow a specific docker, e.g. docker stats jackett
  5. You could also look at Jackett, which moves that logic to a separate application that is accessible by multiple applications and is well maintained
  6. Happy Unraid user of about 3 years or so, and I'm on my second build now (with build #3 in the next 12 months). Unraid allowed me to consolidate a bunch of separate machines with separate storage into a single more easily managed system. It also lowered the barrier to entry to technologies like virtualisation, docker and just linux in general.
  7. Basically I started from scratch. I removed MB docker via docker page, then deleted its app data. I then reinstalled from community apps. Make a copy of your musicbrainz token as a precaution, but your docker template should still have info from previous install. I had issues with current latest version of Picard, 2.1.3 (even after fixing MB docker), so I rolled back to 2.1 I happen to still have and it doesn't crash anymore.
  8. Fixed the problem with another nuke and pave
  9. Won't OP hit the problem of trying to open privileged ports with a non-privileged user (non-root)?
  10. Another path for investigation, all of the apps I've heard mentioned experiencing corruption are running mono/dotnetcore.
  11. Wow, just had a look, I've got this issue too. Investigating further it seems to be symbolic link in the recycle folder, causing it to loop to infinity. NFI how that was created, but emptying the recycle bin removed the link and all is normal again.
  12. Hopefully he is kind enough to create an updated v1 based image/tag should the non-deluge components need major updating. Otherwise sitting on the most recent v1 tag works just fine IMO as deluge v1 hasn't been updated in 2 years.
  13. What is it you are using VPN for? PIA has been flawless for me for torrent traffic, but someone else may have better suggestions for say avoiding Netflix geoblocking as an example.
  14. Same issue as above 2 posts, seeing inter page hyperlink errors on docker MB that have no issues on the public MB. All searches on docker MB page find desired results, but all links fail with either Release Not Found or Internal Server Error. API calls from Headphones/Beets are also failing.
  15. I don't think the old client supports v2, and win/mac doesn't have an updated client, only linux so far. V2 users are stuck with webUI for now.