Leaderboard

Popular Content

Showing content with the highest reputation on 03/18/19 in all areas

  1. Well I just bought a refurb R710 and it had a PERC6i raid controller and it cannot be flashed to IT mode from what I gathered so I put an LSI 9211 8i flashed to IT mode and it works flawlessly with unraid I did see there was some workaround but in the end its to much trouble and you would loose SMART info on your drives, also be aware that if you have SAS drives you will not be able to spin them down via unraid
    2 points
  2. NOTE: I do not have time to keep the table of contents up to date, so there are going to be other scripts within this thread that are not listed here. Just a thread to contain any/all additional scripts created by users for use within the user.scripts plugin. I'm going to be using this thread for anything that pops into my head that may be of use but is either too simple for a plugin format, or just not worth the time for something that may only get run once. Ideal format to post any contributed scripts would be a zip file containing the script and description (stored within an already named folder for ease of adding to the plugin, and additionally a code block of the script itself for complete openness. See the user.scripts thread for details on how to add these scripts (or any others) Default Scripts Included in the plugin Fix Files Stored on the Array for cache-only shares and the reverse Clean Docker Logs Backup MySQL Folder Run mover at a certain utilization automatically Record Disk Assignments Enable / Disable Turbo Write Mode Auto set turbo mode based on drives spun up Run Mover At A Threshhold, optional to skip moving if parity check in progress Clear An unRaid Data Drive A script to have a file with the folders containing movies and tvshows. Send Server Status To Phone Backup vm xml files and ovmf nvram files Automatically download from repo and install custom VM icons to vm manager Run A Custom Script At Parity Check / Rebuild Start And Stop Catalog Drive Contents Move a folder when disk utilization exceeded Very simple script which will resume paused/suspended vms or start shut off vms Scheduled Scrubs Scheduled checks for Out Of Memory Errors Play PacMan On Your Server USB Hotplug for Virtual Machines with no passthrough and a revision HERE Enable / Disable Nested VM https://forums.unraid.net/topic/48707-additional-scripts-for-userscripts-plugin/?page=4#comment-547492 RemoveSpacesFromFile FolderfromFilename Automatically save syslog onto flash drive Check Plugin Integrity Allow unRaid to utilize the full width of the browser instead of limited to 1920px Get size of running containers Script to spin up all drives at certain times of day unRaid GUI Bleeding Edge Toolkit Enable Hardware Decoding In Plex Convert files from dos to linux format
    1 point
  3. Parity Check Tuning plugin The Parity Check Tuning plugin is primarily designed to allow you to split a parity check into increments and then specify when those increments should be run. It will be of particular use to those who have large parity drives so that the parity check takes a long time and who leave their Unraid servers powered on 24x7. The idea is that you can specify time slots when the increments should be run and these can be chosen to be at times when the Unraid server is likely to be idle. The plugin also support running other long array operations (e.g. Clear, Rebuild) in increments if the user so desires. However since such operations are much rarer the user has to explicitly enable this in the plugin settings. Note that this plugin does not initiate a new parity check (or other array operation) - it only provides facilities for pausing/resuming/restarting them according to the criteria set in the plugin’s settings. If there is no array operation running during the timeslot specified for an increment then this plugin take no action. As an example on my system I have a 10TB Parity Disk and an uninterrupted Parity Check takes about 30 hours to complete. I have my normal scheduled parity checks set to run monthly. By using this plugin to run using 3 hour increments the elapsed time extends to 10 days (10 x 3 = 30) but I do not notice any impact on my normal use as the increments are run when I am not using the system. Once enough increments are run to complete the scheduled parity check then no further increments will be run until the time for the next scheduled check comes around. The plugin also allows other types of long-running array operations to be Paused or Resumed. These are Parity-Sync/Disk Rebuild and disk Clear operations. However since pausing these is less likely to be something the average user wants these can be individually controlled. For those who have problems with cooling on their Unraid systems it is also possible to set array operations to be Paused if the disks reach defined temperature thresholds and then Resumed when they cool down sufficiently. A much better solution is to have your Unraid system set up so that the cooling is sufficient to never let the disks overheat, but for some people this is not always practical. To avoid conflicts that can reduce overall performance you can set the plugin to automatically pause array operations if it detects that either the mover or the CA Backup processes are running and to then automatically resume the array operation when the process it question completes. The plugin will update the standard parity-check log to accurately reflect the duration and speed of parity checks to take into account that the check was run in increments as well as enhancing the information by also recording the number of increments, the total elapsed time and the type of check run. If you are running Unraid 6.9.0 (or later) array operations can be specified to be restated from the point they had reached at the point the reached when the system was shutdown or rebooted (or the array simply stopped/started) rather than from the beginning. This can be of particular use to those who do not want to keep their Unraid system powered on 24x7 (and power off overnight) as with modern large drives an array operation such as parity check can easily take more than 24 hours. The Settings page is added as an extra section to the Settings->Scheduler page (see the screenshot below) in the Unraid GUI as this seemed the most logical place for it to appear. Debug/Testing logging feature If you enable the option for debug logging then you will see additional entries appearing in the syslog about how this plugin is functioning internally. All these entries will include the word DEBUG so It is clear that they have been activated by turning on the Debug logging. This feature is primarily aimed at giving users a sense of what the plugin is doing under the covers for any users interested in such matters. In addition the logging level can be set to TESTING if trying to track down any suspected bugs in the plugin operation. This is primarily used during plugin development but can also help tracking down any issues that might be reported by users. It can be very verbose so users should not normally leave this option enabled. When this option is set to Testing then you are offered an additional option of Hourly for the frequency at which this plugin should pause/resume parity check increments. This was added primarily to help with testing and to help track down any issues that users might experience in using the plugin. Early feedback has suggested that users new to this plugin can use this feature as a way of getting a feel for how the plugin operates. Server Shutdown A feature has been included that allows users to set a temperature threshold for their array and cache drives that if exceeded will force the server to start its shutdown sequence. The prime Use Case for this is seen as protecting the disk drives in the event of the servers cooling failing for some reason. If activated this check runs even when there is no array or cache operation active. Command Line (CLI) options When this plugin is installed it adds the 'parity.check' command to the system which makes the following capabilities available from the command line: Usage: parity.check <action> where action is one of pause Pause a running parity check resume Resume a paused parity check check Start a parity check (as Settings->Scheduler) correct Start a correcting parity check nocorrect Start a non-correcting parity check status Show the status of a running parity check cancel Cancel a running parity check start Start the array stop Stop the array N Built-in Help The settings page for this plugin has very extensive built-in help to describe the meaning of the various settings. You can click on the description text for any particular setting to toggle it on-/off for that particular setting or you can turn it on/off at the page level by using the standard Help toggle in the Unraid GUI. Suggestions for improving the wording or expanding on the provided text are welcomed as it is not intended to produce any separate documentation. Parity Problems Assistant This is an additional option that appears under the Tools menu when the plug-in is installed. it implements Partial parity Checks which can be very helpful when trying to troubleshoot problems with parity after you have encountered errors when running the full parity check. It allows you to run a short check between specified start and end points. The current implementation is quite basic and feedback is welcomed on how it could be improved. Wish List This a holder for "blue sky" ideas that have been expressed for which there is no idea if it is even technically possible. They are kept here as a reminder and for others to perhaps expand on, and even perhaps come up with ideas for implementation.. Auto detect idle periods: The idea is that instead of the user having to specify specific start/stop times for running parity check increments the plugin should automatically detect periods when the system is idle to resume a parity check. This would need the complementary option of automatically detecting the system is no longer idle so that the check can be paused. Stop docker containers during a parity check. The ability to schedule the parity check to stop specified docker containers prior to check running and restart the docker containers after the check is paused or completed. A workaround for this would be to use the User Scripts plugin to do this although an integrated capability would be easier to use. Feedback Feedback from users on the facilities offered by this plugin is welcomed, and is likely to be used to guide the direction of any future enhancements. It will be interesting to hear how useful users find this plugin to be in the normal running of their system. Please feel free to suggest any changes that you think would enhance the experience even if it only rewording of text . Requirements Unraid 6.7.0 or later for the basic capability of running parity checks in increments. Unraid 6.9.0 or later for restarting array operations on next array start, and for using the Parity Problems assistant. Community Applications (CA) plugin. It is expected that this plugin will be installed via the Apps tab (i.e. the Community Applications plugin) and the appropriate template has been prepared to allow CA to handle it tidily. Installation The parity Check tuning plugin is available for installation by using the Community Applications plugin. If you navigate to the Apps tab and search for 'Parity Tuning' this plugin will show up and it can be installed from there. Once the plugin is installed then if you go to Settings->Scheduler in the Unraid GUI you will see an extra section has appeared that allows you to specify the settings you want to be used for this plugin.
    1 point
  4. Hi guys I am considering upgrading from a xeon to a 2950x. Im sure a lot of other members are considering the same. Could someone be so kind as to catalogue any outstanding issues with threadripper that have not got a solution. I know there is a @SpaceInvaderOne video on Ryzen, but I think it would aid a lot of people with this kind of decision if the current state of threadripper and VM is documented. Thanks for any assistance on this matter
    1 point
  5. Yeah, mine too really. I know how to set it up I think, but I don't know how to analyze the data. But I've not seen any leakage on delugevpn with privoxy enabled when testing on various leakage test sites so I'm choosing to trust it.
    1 point
  6. ok, being dumb here, have searched and tried configs for over 1 hr now... does anyone have a working bitwarden config for subdomain w/docker on a seperate proxeynet my others work just fine, but this one is making me pull out what hair i have left help pls Myk
    1 point
  7. The way you set up your a record and cnames is correct. You just need to make sure that the a record remains up to date. You can use a docker image like ddclient to update it, or some routers can also do it. If you're doing dns validation, look into getting a wildcard cert and then you only need to create one cname for "*" without the quotes and you'll be good. Between the a record and that wildcard cname, your domain and all subdomains will be covered.
    1 point
  8. I'd also suggest using the copy on the gist I linked: https://gist.github.com/Xaero252/9f81593e4a5e6825c045686d685e2428 It checks for a couple of things that could happen now. Like if you start a VM with the card passed through with the old version, all transcodes would stop working until the VM was stopped. Now it will simply fall back on CPU decoding. It also ignores files that use the mpeg4 AVI container, as they have problems with the ffmpeg build used by plex thus far. And yeah, force update, or changing any property of the docker will use a fresh copy of the docker, making this very easy to rollback from.
    1 point
  9. @Rick Sanchez - I just created a new Win10 VM for myself. I thought I was stuck at the same place. However, It's a super simple fix if it's the same issue. You need to connect to the VNC _REALLY FAST_ so you can catch the boot screen where it says "Press any button to boot into the CDROM...". It may take a couple of tries, but you'll see it if you have your VNC client ready to go as soon as you hit Start on the VM.
    1 point
  10. That's was going to be my next suggestion. I use it since all of my sites have their comodo ssl, I still run LEGlad you got it working Sent from my SM-N960U using Tapatalk
    1 point
  11. You absolutely must have another copy of anything important and irreplaceable. Parity is no subsititute for backups. You have a problem with your flash drive. Put it in your PC and let it checkdisk. Be sure you are using a USB2 port on your server for flash. While you have it in your PC make sure you get a backup of it. You must always have a current backup of flash, and for future reference you can get one from the webUI by going to Main - Boot Device - Flash - Flash Backup. Not the cause of your problem, but disk1 has more reallocated than I would be comfortable with.
    1 point
  12. Spent about an hour digging through their scripts and their post install of their package to see what could be missing. Wasted time. Openvpn pulled the 2.7.2 release. We pushed an update to set latest back to 2.6.1. If you updated to 2.7.2 today, update again to go back to 2.6.1 and things should go back to normal.
    1 point
  13. The Parity Check Tuning plugin is now available (as long as you are running the 6.7 rc4 release or later) which can automate pause/resume of parity checks to allow increments to be run when the system is likely to be idle. More details are available in the forum Support thread for this plugin.
    1 point
  14. Macvlan call traces are usually related to dockers with custom IPs.
    1 point
  15. Norco 4224 case 9x 6TB 6x 4TB 2x 500GB SSD 1x 1TB SSD Intel® Core™ i7-5820K Asus X99-DELUXE 32 GB DDR4 Nvidia P2000 3x LSI 9211-8i This has been updated a little since these pictures were taken. I'll update here when I take new pictures.
    1 point
  16. ...how to backup 42TB??? Backblaze takes $ 210/month - lel - i think its cheaper to buy a second server 🤣
    1 point
  17. Uploaded a short video on setting up the basics on Home Assistant with unRaid. I did it from start to show people how to quickly setup unRaid so most of you here can skip that part.
    1 point
  18. Did you make a directory inside your VM called /home/daylend/UbuntuServer and then reboot or mount -a to reload fstab? I did the following: Then I created the Directory "/unraid" not that the exact path matters could have used "/mnt/unraid" for instance and used that below instead of /unraid. Then I added the following to fstab and rebooted: unraid /unraid 9p trans=virtio,version=9p2000.L,_netdev,rw 0 0 And I got my user shares from my unRAID server listed when I "ls /unraid" Hope this helps.
    1 point
  19. For everyone still having problems installing Grafana, Telegraf and InfluxDB: I just released a tutorial on how to set everything up using atribe's docker containers on Reddit. Grafana, Telegraf and InfluxDB tutorial on Reddit Feel free to take a look and ask questions!
    1 point
  20. Clear an unRAID array data drive (for the Shrink array wiki page) Mod note: this script usually takes a much longer than normal time to clear a drive with newer Unraid releases, recommend using the "Remove Drives Then Rebuild Parity" Method or if you really want to clear the disk do it manually. This script is for use in clearing a drive that you want to remove from the array, while maintaining parity protection. I've added a set of instructions within the Shrink array wiki page for it. It is designed to be as safe as possible, and will not run unless specific conditions are met - - The drive must be a data drive that is a part of an unRAID array - It must be a good drive, mounted in the array, capable of every sector being zeroed (no bad sectors) - The drive must be completely empty, no data at all left on it. This is tested for! - The drive should have a single root folder named clear-me - exactly 8 characters, 7 lowercase and 1 hyphen. This is tested for! Because the User.Scripts plugin does not allow interactivity (yet!), some kludges had to be used, one being the clear-me folder, and the other being a 60 second wait before execution to allow the user to abort. I actually like the clear-me kludge, because it means the user cannot possibly make a mistake and lose data. The user *has* to empty the drive first, then add this odd folder. #!/bin/bash # A script to clear an unRAID array drive. It first checks the drive is completely empty, # except for a marker indicating that the user desires to clear the drive. The marker is # that the drive is completely empty except for a single folder named 'clear-me'. # # Array must be started, and drive mounted. There's no other way to verify it's empty. # Without knowing which file system it's formatted with, I can't mount it. # # Quick way to prep drive: format with ReiserFS, then add 'clear-me' folder. # # 1.0 first draft # 1.1 add logging, improve comments # 1.2 adapt for User.Scripts, extend wait to 60 seconds # 1.3 add progress display; confirm by key (no wait) if standalone; fix logger # 1.4 only add progress display if unRAID version >= 6.2 version="1.4" marker="clear-me" found=0 wait=60 p=${0%%$P} # dirname of program p=${p:0:18} q="/tmp/user.scripts/" echo -e "*** Clear an unRAID array data drive *** v$version\n" # Check if array is started ls /mnt/disk[1-9]* 1>/dev/null 2>/dev/null if [ $? -ne 0 ] then echo "ERROR: Array must be started before using this script" exit fi # Look for array drive to clear n=0 echo -n "Checking all array data drives (may need to spin them up) ... " if [ "$p" == "$q" ] # running in User.Scripts then echo -e "\n" c="<font color=blue>" c0="</font>" else #set color teal c="\x1b[36;01m" c0="\x1b[39;49;00m" fi for d in /mnt/disk[1-9]* do x=`ls -A $d` z=`du -s $d` y=${z:0:1} # echo -e "d:"$d "x:"${x:0:20} "y:"$y "z:"$z # the test for marker and emptiness if [ "$x" == "$marker" -a "$y" == "0" ] then found=1 break fi let n=n+1 done #echo -e "found:"$found "d:"$d "marker:"$marker "z:"$z "n:"$n # No drives found to clear if [ $found == "0" ] then echo -e "\rChecked $n drives, did not find an empty drive ready and marked for clearing!\n" echo "To use this script, the drive must be completely empty first, no files" echo "or folders left on it. Then a single folder should be created on it" echo "with the name 'clear-me', exactly 8 characters, 7 lowercase and 1 hyphen." echo "This script is only for clearing unRAID data drives, in preparation for" echo "removing them from the array. It does not add a Preclear signature." exit fi # check unRAID version v1=`cat /etc/unraid-version` # v1 is 'version="6.2.0-rc5"' (fixme if 6.10.* happens) v2="${v1:9:1}${v1:11:1}" if [[ $v2 -ge 62 ]] then v=" status=progress" else v="" fi #echo -e "v1=$v1 v2=$v2 v=$v\n" # First, warn about the clearing, and give them a chance to abort echo -e "\rFound a marked and empty drive to clear: $c Disk ${d:9} $c0 ( $d ) " echo -e "* Disk ${d:9} will be unmounted first." echo "* Then zeroes will be written to the entire drive." echo "* Parity will be preserved throughout." echo "* Clearing while updating Parity takes a VERY long time!" echo "* The progress of the clearing will not be visible until it's done!" echo "* When complete, Disk ${d:9} will be ready for removal from array." echo -e "* Commands to be executed:\n***** $c umount $d $c0\n***** $c dd bs=1M if=/dev/zero of=/dev/md${d:9} $v $c0\n" if [ "$p" == "$q" ] # running in User.Scripts then echo -e "You have $wait seconds to cancel this script (click the red X, top right)\n" sleep $wait else echo -n "Press ! to proceed. Any other key aborts, with no changes made. " ch="" read -n 1 ch echo -e -n "\r \r" if [ "$ch" != "!" ]; then exit fi fi # Perform the clearing logger -tclear_array_drive "Clear an unRAID array data drive v$version" echo -e "\rUnmounting Disk ${d:9} ..." logger -tclear_array_drive "Unmounting Disk ${d:9} (command: umount $d ) ..." umount $d echo -e "Clearing Disk ${d:9} ..." logger -tclear_array_drive "Clearing Disk ${d:9} (command: dd bs=1M if=/dev/zero of=/dev/md${d:9} $v ) ..." dd bs=1M if=/dev/zero of=/dev/md${d:9} $v #logger -tclear_array_drive "Clearing Disk ${d:9} (command: dd bs=1M if=/dev/zero of=/dev/md${d:9} status=progress count=1000 seek=1000 ) ..." #dd bs=1M if=/dev/zero of=/dev/md${d:9} status=progress count=1000 seek=1000 # Done logger -tclear_array_drive "Clearing Disk ${d:9} is complete" echo -e "\nA message saying \"error writing ... no space left\" is expected, NOT an error.\n" echo -e "Unless errors appeared, the drive is now cleared!" echo -e "Because the drive is now unmountable, the array should be stopped," echo -e "and the drive removed (or reformatted)." exit The attached zip is 'clear an array drive.zip', containing both the User.Scripts folder and files, but also the script named clear_array_drive (same script) for standalone use. Either extract the files for User.Scripts, or extract clear_array_drive into the root of the flash, and run it from there. Also attached is 'clear an array drive (test only).zip', for playing with this, testing it. It contains exactly the same scripts, but writing is turned off, so no changes at all will happen. It is designed for those afraid of clearing the wrong thing, or not trusting these scripts yet. You can try it in various conditions, and see what happens, and it will pretend to do the work, but no changes at all will be made. I do welcome examination by bash shell script experts, to ensure I made no mistakes. It's passed my own testing, but I'm not an expert. Rather, a very frustrated bash user, who lost many hours with the picky syntax! I really don't understand why people like type-less languages! It only *looks* easier. After a while, you'll be frustrated with the 60 second wait (when run in User Scripts). I did have it at 30 seconds, but decided 60 was better for new users, for now. I'll add interactivity later, for standalone command line use. It also really needs a way to provide progress info while it's clearing. I have ideas for that. The included 'clear_array_drive' script can now be run at the command line within any unRAID v6, and possibly unRAID v5, but is not tested there. (Procedures for removing a drive are different in v5.) Progress display is only available in 6.2 or later. In 6.1 or earlier, it's done when it's done. Update 1.3 - add display of progress; confirm by key '!' (no wait) if standalone; fix logger; add a bit of color Really appreciate the tip on 'status=progress', looks pretty good. Lots of numbers presented, the ones of interest are the second and the last. Update 1.4 - make progress display conditional for 6.2 or later; hopefully now, the script can be run in any v6, possibly v5 clear_an_array_drive.zip clear_an_array_drive_test_only.zip
    1 point
  21. Make a note of which ever folder that you went into that has the problem (which ever one starts windows in an infinite loop of empty folders) The log into the server using either the local console, or putty. Enter the following mc Navigate to /mnt/user/whatever share and folder have the problems Look for a file that has a rectangle in its name. Rename it to something normal. Its probably a messed up file from one of your downloads that didn't get renamed correctly.
    1 point