Leaderboard

Yea i haven't had time to push the fix (simple as it is). I'll see if I can get it done tonight.

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

No, random is fine

99% of LSIO's apps will update to the latest version if you install the container update that comes out every Friday @ 2300 GMT

If the device is totally unreadable, even via windows, then obtain a new high-quality name-brand usb flash device and reinstall Unraid OS onto it, boot your server and get a new Trial key. You will need to reassign all your storage devices to parity-array and cache as you can remember. In this situation there are three rules: Don't assign any device to Parity or Parity 2 unless you know that device does not contain valid data. Don't assign any device to Cache or Cache pool until after you have your parity-array reconfigured. Don't click any Format button. For step 1, you can leave Parity/Parity 2 unassigned, reassign your data disks, and then Start array and you should see all the shares there. Later after you've figured out what devices were for parity you can go back and assign them. Step 2 can be trickier, especially if you had a multi-device pool. In this case, going to command line and typing this may help with identification: blkid Once you have re-configured the storage devices correctly, all your shares should be ok, but if you changed any settings off their default, then you will need to go fix that.

Monthly on both of my servers as well...

Monthly here too. I schedule it for the first of the month and I know not to schedule any other events for the server from 12am-2pm because it normally takes that long.

The change in RC2 is for the dashboard. VMS page will have support for longer VM names in the next RC.

Monthly is a good choice. Doing a parity check verifies that all of the disks can be read and has often detected minor issues which can be easily corrected before they become major ones which might result in data loss. (Think of it like finding high blood pressure during a routine physical as opposed to a heart attack!)

I and many others have monthly parity check scheduled.

Please note that there is distinction between a direct write to array disks vs cache disks. When a write to array disk occurs, Unraid needs to read the parity disk + target array disk, then using that compute the new parity value, and then write to the target array disk and the parity disk. If you try to read from any drive during this time, you'll have disk I/O contention at a 4:1 ratio. It won't be a problem just yet, but you will encounter stuttering and pauses which depends on your hardware and the speed the download is ocurring. As for the CPU, your i3 is more than enough to do the parity computation. I only use a Pentium G4620. Upgrading CPU won't make a difference. You didn't provide your complete specs or the diagnostics file, so you'll only get general tips If you have a spare HDD (or SSD which is even better), you can add it and assign it as a cache drive. This speeds up your download as it will only need to write to cache drive like in any normal system. But files on the cache will only get moved to array on a schedule You also didn't consider the state of your network, is Unraid connected via gigabit?

I just copied my whole sonarr appdata directory as a backup and upgraded in place. Been working great. My guess is it changes the database, so I wouldn't assume going back to stable will be possible. But if you try running it for a few days and don't like it, you can always just restore your backed up folder and won't be too far out of date.

Seems extremely unlikely the plugin is to blame. As mentioned it is deprecated anyway. Just remove the plugin.

2 Factor authentication via youbikey or google authenticator would also be nice.

Well, this was easier than I thought. This is a pretty basic script that runs the 'tree' command against each of your array disks, creating a txt of their contents. My primary purpose for this is to serve as an archive of my array contents in case I have a catastrophic failure, then I can easily discern what I'm missing and start rebuilding from backups/etc. Default save directory goes to your flash drive in a subfolder called indexTree, with subfolders named for each disk containing a date stamped txt file. #!/bin/sh # Tree Index Array #description=Creates an inventory tree of all mounted disks (not cache) #arrayStarted=true SAVEPATH=/boot/config/indexTree for f in /mnt/disk* do echo "Scanning tree for $f" mkdir -p $SAVEPATH/$(basename $f) tree -o $SAVEPATH/$(basename $f)/$(date +%Y%m%d).txt "$f" done echo "indexTree complete!" exit 0 tree_index_array_drives.zip