Jump to content

Cessquill

Members
  • Posts

    789
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by Cessquill

  1. 1 minute ago, deltaexray said:

    I've got a couple of questions regarding Part 3 of the very first post of this Thread:

    Where do you get the number from, to complete the info command? more specific, x86-64-linux-gnu isn't even in the files, let alone they are not ubunut ones, they are centos, at least in the most recent download of SeaChest Utilities.

    I feel like that I have either a completely different download of the software or I'm to stupid to work it out, but none of the commands work.

     

    The downloads have changed since I first wrote it - they had numbers in.  At the top of part 3 there is the text...

     

    Quote

    EDIT: When this guide was written, there was what looked like a version number at the end of each file, represented by XXXX below.  Now each file has "_x86_64-linux-gnu" so where it mentions XXXX you need to replace with that.

     

     

    1 minute ago, deltaexray said:

    Then the cd/tmp/seachest chmod .... to make them executable isn't working, u need to do them in 2 steps, bc if you are not in the directory first, those commands will not find anything to work with. If they even worked, in the first place because I'm not sure if they worked when I did the command.

     

    It may not be clear, but they are intended to be run as two separate commands (hence the line break).  I'll edit the post to clarify that.

  2. 3 hours ago, Anym001 said:

    @knex666

    Is it possible to run a script as root when starting the container?

    I would like to install ffmpeg to get previews for my videos.

    Currently I have solved this via the post arguments. 

     

    EDIT: 

    &&  docker exec -u 0 Nextcloud /bin/sh -c "apt update && apt install -y ffmpeg"

     

    Have you tried enabling/installing the video player app from within Nextcloud? (or  have I misunderstood)

  3. On 7/19/2021 at 10:06 AM, Maticks said:

     i issued both commands EPC disable and the lowcurrentspinup. on my ST8000VN004 rebooted, but after a spin down event i got errors again a few days later.

    If there another setting that needs to be disabled, i have forced the drive to stay spun up for the time being.

    But i do operate a system with 3xLSI 9211-8i Controllers. Not had any issues with my other disks.

     

    I do have 2xST8000VN004 additional drives but they are Parity Drives so never spin down.

    Any suggestions?

    The original issue that this is for was that drives were being disabled by Unraid and had to be rebuilt.  Is one of your drives exhibiting this behavior, or are you getting different errors?  And if so, what?

     

    Also, parity drives can spin down if there is no other activity on the array, no?

  4. 55 minutes ago, kri kri said:

    I am looking for a script to clone a github repo to a folder in my appdata folder. Can someone help me? 

    This script was used for a while when Plex encoding needed patching from a github script.  Whilst it's not exactly what you're after it might get you going...

     

    #!/bin/bash
    
    ############################### DISCLAIMER ################################
    # This script now uses someone elses work!                                #
    # Please visit https://github.com/revr3nd/plex-nvdec/                     #
    # for the author of the new transcode wrapper, and show them your support!#
    # Any issues using this script should be reported at:                     #
    # https://github.com/Xaero252/unraid-plex-nvdec/issues/                   #
    ###########################################################################
    
    # This is the download location for the raw script off github. If the location changes, change it here
    plex_nvdec_url="https://raw.githubusercontent.com/revr3nd/plex-nvdec/master/plex-nvdec-patch.sh"
    patch_container_path="/usr/lib/plexmediaserver/plex-nvdec-patch.sh"
    
    # This should always return the name of the docker container running plex - assuming a single plex docker on the system.
    con="$(docker ps --format "{{.Names}}" | grep -i plex)"
    
    # Verify plex container is running
    if [ -z $con ]; then
    	echo -n "<font color='red'><b>Error: Cannot find Plex container. Make sure it's running and has "plex" in the name.</b></font>"
            exit 1
    fi
    
    # Uncomment and change the variable below if you wish to edit which codecs are decoded:
    #CODECS=("h264" "hevc" "mpeg2video" "mpeg4" "vc1" "vp8" "vp9")
    
    # Turn the CODECS array into a string of arguments for the wrapper script:
    if [ "$CODECS" ]; then
    	codec_arguments=""
    	for format in "${CODECS[@]}"; do
    		codec_arguments+=" -c ${format}"
    	done
    fi
    
    echo "Applying hardware decode patch..."
    	
    # Grab the latest version of the plex-nvdec-patch.sh from github:
    echo -n 'Downloading patch script...'
    wget -qO- --show-progress --progress=bar:force:noscroll "${plex_nvdec_url}" | docker exec -i "$con"  /bin/sh -c "cat > ${patch_container_path}" 
    
    # Verify that wget was successful
    if [[ $? -ne 0 ]]; then
        echo -n "<font color='red'><b>Error: wget download failed, non-zero exit code.</b></font>"
        exit 1; 
    fi
    
    # Make the patch script executable.
    docker exec -i "$con" chmod +x "${patch_container_path}"
    
    # Run the script, with arguments for codecs, if present.
    
    if [ "$codec_arguments" ]; then
    	docker exec -i "$con" /bin/sh -c "${patch_container_path}${codec_arguments}"
    else
    	docker exec -i "$con" /bin/sh -c "${patch_container_path}"
    fi

     

  5. 8 hours ago, RifleJock said:

    I had a use case before, when I used 6x 8TB drives. This was on my Media share, where I had used "most-free" and changed the directories split such that each 30 minute GoPro video would be placed among these drives evenly. I would do this so that when reading videos from these drives whilst doing video editing that would reference 4 or 5 videos from the trip of the day, I could get full sequential reads from the Array disks per video. In order to prevent spin-downs, my work around would be to set the disk spin down delay to that of 45 minutes, that way, it was harder for the drive to spin down, while reading from all the drives.

    If all of the videos from one day were in the same folder, you'd be better off setting the split level of the share to make sure they all stayed together.  That way you're only spinning up one disk.  More economical.

  6. 7 hours ago, superrio said:

     I've been running into problems with my server locking up, every 8-9 days or so. To eliminate that until I can figure out what's wrong I want it to reboot itself in an effort to keep my dockers up and running. 

    I'd concentrate on solving the real problem first, but your cron schedule has WED in it.  Use a number to signify the day of the week.

  7. 4 hours ago, TangoEchoAlpha said:

    At some point today I will connect it up and preclear, but wondered if there were any checks I could do/useful info I could gather before running the SeaChest tools as per your original post?

    Maybe somebody else could help with this part - I just collated other people's findings.  Personally I don't think there's anything else needed.  Whilst the instructions look long, it's actually a quick and simple job.

     

    I didn't find a way to 100% trigger the symptoms, so I don't know whether there's any way of testing the Pro drive prior to adding it to the away.

  8. 3 minutes ago, TangoEchoAlpha said:

    Scan Computers in the UK. The Pro is £10 more than the non-Pro, for the extra warranty etc I'll take that.

     

    https://www.scan.co.uk/products/8tb-seagate-ironwolf-pro-st8000ne001-nas-hard-drive-35-hdd-sata-iii-6gb-s-7200rpm-256mb-cache-oem

     

    I've ordered the drive and downloaded the SeaChest tools. Might be inclined to make the changes from a Live install of Ubuntu elsewhere, or caddy the drive up to my Raspberry Pi. Looks like there's even a Windows version now?

    Cheers.  Some of my Ironwolf's are from there - just depends who's cheaper on the day.  That's a good price for the Pro - could swap my parity with it.

     

    If you've got a spare machine you could use the standalone USB version.  Haven't tried Windows for this.

  9. 56 minutes ago, spl147 said:


    Yea, I always felt it should be installed automatically as it is required by the plugin

    To be fair, it's a system-wide thing.  If you had several plugins using PERL (say, Speedtest), and you uninstalled one of them, would you expect PERL to still be there?

  10. 18 hours ago, tmeuze said:

    Mind sharing your raw config?

    The redacted conf file that NPM creates is below.  Not sure of the ssl and proxy files - will need to dig around...

     

    server {
      set $forward_scheme http;
      set $server         "192.168.1.10";
      set $port           8088;
    
      listen 8080;
    listen [::]:8080;
    
    listen 4443 ssl http2;
    listen [::]:4443;
    
    
      server_name my.domain.com
    
    
      # Let's Encrypt SSL
      include conf.d/include/letsencrypt-acme-challenge.conf;
      include conf.d/include/ssl-ciphers.conf;
      ssl_certificate /etc/letsencrypt/live/npm-8/fullchain.pem;
      ssl_certificate_key /etc/letsencrypt/live/npm-8/privkey.pem;
    
    
    
    
    # Asset Caching
      include conf.d/include/assets.conf;
    
    
      # Block Exploits
      include conf.d/include/block-exploits.conf;
    
    
    
      # HSTS (ngx_http_headers_module is required) (31536000 seconds = 1 year)
      add_header Strict-Transport-Security "max-age=31536000;includeSubDomains; preload" always;
    
    
    
    
      access_log /config/log/proxy_host-18.log proxy;
    
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header X-Real-IP $remote_addr;
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_max_temp_file_size 16384m;
    client_max_body_size 0;
    
    
    
    
    
      location / {
    
        
    
    
        # Force SSL
        include conf.d/include/force-ssl.conf;
    
    
    
    
      # HSTS (ngx_http_headers_module is required) (31536000 seconds = 1 year)
      add_header Strict-Transport-Security "max-age=31536000;includeSubDomains; preload" always;
    
    
    
    
        
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection $http_connection;
        proxy_http_version 1.1;
        
    
        # Proxy!
        include conf.d/include/proxy.conf;
      }
    
    
      # Custom
      include /data/nginx/custom/server_proxy[.]conf;
    }

     

    • Thanks 1
  11. 2 hours ago, knex666 said:

    I was wondering why so i setup a reverse proxy with nginx and it sucks so hard. it takes a very long time.

    Just had a friend check my URL remotely and it took just under a second to load.  I'm using Nginx Proxy Manager with my advanced settings at the top of this page.  Using the URL locally quick too.  Occasionally use it to deliver/transfer work files and have had no issues.

    • Like 1
  12. Hi - woke up this morning to a "500 Internal Server Error" on the Unraid web UI.

     

    I was able to access my file shares and some of my dockers (didn't try all, but Plex was not available).  My dockers are backed up Monday nights - not sure if that went awry.

     

    Could putty onto the server and get a diagnostics file (attached).  Could not run a powerdown though.  After 10 minutes tried an orderly shutdown via IPMI, which failed.  Performed an unclean shutdown, powered back up and all appears OK and it's parity checking now.

     

    Any idea what caused it?

     

  13. 8 hours ago, edrohler said:

    WOW! Thank you for this thread. I have been scratching my head about this all week. I posted here. Instead of tweaking the drives, I am just going to disable the spin down delay for any drives in the enclosure and hope for an update to the driver. 

    Just saw your post in the unbalance thread, and was about to suggest you check here.  No need now :)

    • Thanks 1
  14. 16 minutes ago, itimpi said:

    I would be interested to know if this is considered sufficient in the short term or more detail is needed?

    Looks good to me.  Would "docker start <name of container>" work, rather than docker run...?

     

    I was thinking of writing a generic user script which ran every 5 minutes (say).  At the top you fill in an array of all the start/stop events you want to happen, each entry having container name, start time and stop time (or array of time ranges).  Then when the script was run it would decide whether it needed to do anything by comparing the current state of a docker against its schedule.  Puts it all into a single script then, but prevents the user from overriding the schedule by manual start/stop.  Parked it until I could think of better logic.

  15. 1 hour ago, optiman said:

    Even if the fix works today, how do you know it will be ok in the next release?

    Because it was a fault with either the drive or the controller, and the fix was a change to the drives settings.  I understand that other systems have also had problems with this drive/controller combo.  Any future upgrade could theoretically break a previously unfound issue with anything.

     

    If the manufacturers don't step up then I'd reconsider whether to use their hardware for server work in future.  Just as I wouldn't set up a pfSense box using Realtek NICs.

     

    If it helps, I've had zero issues since reining in the drive's settings.

  16. 15 hours ago, optiman said:

    I was thinking of using the Seagate provided usb linux bootable flash builder and boot to that and run the commands outside of unraid.  Given I only have seagate drives, I will need to do them all.  Has anyone tried this with success?

    I haven't tried the bootable Seagate utility, but I was assuming it would just load to a command prompt with the tools preinstalled.  For me it was easier to go via Unraid (plus no downtime).

     

    In other news, I haven't had a single issue since applying the above (before I had three issues in about a week).

  17. 1 hour ago, ProphetSe7en said:

    Clearly the "docker pause/unpause rtorrentvpn" wont work like this, but what format should it be in to work?

    I'm not at my machine at the moment, but somebody else would know better.  Your script would pause the docker (assuming that's the correct name), but I'm guessing it would unpause it straight away.

     

    You'd need a second part to the script in an else block that checks if docker is paused and whether the mover is running.  If the mover has finished, unpause.  Something like...

     

    if ( $percent > $moveAt ) {
      docker pause rtorrentvpn;
      exec("/usr/local/sbin/mover");
    } else {
      if (!moverRunning && dockerIsPaused) {
        docker unpause rtorrentvpn;
      }
    }

    ...although without researching I don't know how to check if the mover is running and a docker is paused - this is just to illustrate the concept.

×
×
  • Create New...