bigsing

Members
  • Posts

    107
  • Joined

  • Last visited

Posts posted by bigsing

  1. Debug Log ID = 4049a95d-78bf-4065-b6d3-60dc5ed7ac89

     

    Error Message:

    [12.03.2024 04:01:09][][sabnzbd] tar verification failed! Tar said: tar: Removing leading `/' from member names; tar: /mnt/cache/appdata/downloads/inter: Not found in archive; tar: Exiting with failure status due to previous errors

     

    I'm not sure why it's expecting to find /mnt/cache/appdata/downloads/inter as I have /mnt/cache/appdata/downloads as an excluded folder

     

    I've disabled verification in the interim

    • Upvote 1
  2. I've been a user since the 4.x days and the OS has come a very long way. I've setup quite a few servers over the years for friends, and I will continue to recommend it. The community support and dedication from Tom and team is unmatched by any other company!

     

    I'd love to see built-in off-site backup support. Perhaps as a start, automated config backup to a specified cloud provider.

  3. Is your issue specific to VideoSort or Post Processing scripts in general? For the container to load the scripts your ScriptDir property (found under Settings > Paths) needs to be set to the location the scripts reside. For example my ScriptDir is set to /config/ppscripts which translates to /mnt/user/appdata/nzbget/ppscripts

  4. On 9/2/2018 at 5:16 PM, ccruzen said:

    I'm sure this is an easy fix but I'm not super proficient in linux.  I'm having a permissions issue I can't seem to figure out.  Any files I process with Beets I can't modify from my Windows machine.  I'm getting a "You need permission to perform this action" error.  I've tried changing the docker PUID and PGID to the values for nobody in the docker but that didn't work.  Any ideas?

    I fixed this by using the permissions plugin in the config.yaml file. Insure the permissions plugin is listed in the plugins section at the top and include a permissions section further down in the file similar to the below.

     

    permissions:
        file: 666
        dir: 777

     

  5. The array is not 100% unchanged, so that's not an option. I've reviewed the contents of the drive and was able to move the important files to another drive without issue.The items that remain i can replace if needed. 

     

    In this case, i think re-syncing parity with a new disk 4 and then copying everything over is the best approach. How do i add a new disk 4 without a rebuild occurring on it when i start the array? 

  6. Diagnostics File is attached. I was attempting to upgrade my parity drive from a 3TB to 8TB and encountered 384 errors on Disk 4. I ran an extended SMART test which subsequently failed, so i'm expecting I need to look at replacing the drive. The WebGUI shows that parity is valid, but will i be able to successfully rebuild the disk since the errors occurred during the parity rebuild? In retrospect i should have ran a check before upgrading the parity drive, but at least i know i won't make that mistake again.

     

    What should my next steps be?

    joey-diagnostics-20180330-0017.zip

  7. I recently purchased a LSI 9201-16i off eBay. The cards BIOS version is 8.00.00.00-IT would I gain anything from updating this? As far as testing the card, I plugged the card into my test bench and verified that each SAS port recognizes 4 drives when using a reverse breakout cable. The drives i tested with included 2x250GB, a 1TB HDD, and 1 SSD. I also ran a parity check and verified that an 8TB drive was recognized successfully after booting unraid.

     

     

  8. I recently purchased a LSI 9201-16i off eBay. I plugged the card into my test bench last night and verified that each SAS port recognizes 4 drives when using a reverse breakout cable. The drives i tested with included 2x250GB, a 1TB HDD, and 1 SSD. I was going to run a parity check as well, but is there any other testing I should do before I consider moving this card from my test bench into my main server? Also the cards BIOS version is 8.00.00.00 would I gain anything from updating this?

  9. Excellent! I've had mine for a year or so and it's the same config as yours. No issues with my backplanes. Now i just need to do a new build with new controller cards to fill it up :-)

  10. There is a script that the docker uses to pull the latest version number off the plex website. With the release of 1.0 Plex has also launched a new website, which probably involves a different URL location for downloads which breaks the updating process. Once the script is fixed the update should just happen as always.

  11. I tried changing some settings and nzbget wouldn't come back up. I just get

    Thu Apr 28 02:25:54 2016 INFO nzbget 16.4 daemon-mode
    Thu Apr 28 02:25:56 2016 INFO nzbget 16.4 daemon-mode
    Thu Apr 28 02:25:58 2016 INFO nzbget 16.4 daemon-mode
    Thu Apr 28 02:26:00 2016 INFO nzbget 16.4 daemon-mode
    Thu Apr 28 02:25:43 2016 INFO nzbget 16.4 daemon-mode
    Thu Apr 28 02:25:46 2016 INFO nzbget 16.4 daemon-mode
    Thu Apr 28 02:25:48 2016 INFO nzbget 16.4 daemon-mode
    Thu Apr 28 02:25:50 2016 INFO nzbget 16.4 daemon-mode

    Into infinity. I've tried renaming the config file, renaming the folder, restarting the image, stopping and starting the image, deleting and re-downloading the image. All yield the same result. Any ideas?

     

    Sounds like you've tried everything but a delete of the container and a restart of the server. I had a different issue several weeks ago and I tried everything you did as well and deleteing the container, restarting, and adding the container back was the only solution that worked for me.

  12. I'd probably remove the container and reinstall to start, preserving your appdata.  Also try clearing your browser cache/cookies or use a different browser.  If that fails try a reboot and remove then reinstall the container again.

     

    Sent from my LG-H815 using Tapatalk

     

    Thanks for the quick response!

     

    I tried deleting the container and reinstalling but they didn't change anything. I tried firefox instead of chrome and am still having the same issue. I'll try restarting the PC later and if it still fails i'll do the reboot and then remove/reinstall the container again.

     

    This is working now after a restart of the server, thanks!

  13. I'd probably remove the container and reinstall to start, preserving your appdata.  Also try clearing your browser cache/cookies or use a different browser.  If that fails try a reboot and remove then reinstall the container again.

     

    Sent from my LG-H815 using Tapatalk

     

    Thanks for the quick response!

     

    I tried deleting the container and reinstalling but they didn't change anything. I tried firefox instead of chrome and am still having the same issue. I'll try restarting the PC later and if it still fails i'll do the reboot and then remove/reinstall the container again.