Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 05/20/19 in all areas

  1. 2 points
    Summary: Support Thread for ich777 Gameserver Dockers (CounterStrike: Source & ConterStrike: GO, TeamFortress 2, ArmA III,... - complete list in the second post) Application: SteamCMD DockerHub: https://hub.docker.com/r/ich777/steamcmd All dockers are easy to set up and are highly customizable, all dockers are tested with the standard configuration (port forwarding,...) if the are reachable and show up in the server list form the "outside". The standard password for the gameservers if enabled is: Docker Please read the discription of each docker and the variables that you install (some dockers need special variables to run).
  2. 2 points
    I don't know about you, but my wife does this all the time (usually in anger) and expects me to remember everything...
  3. 2 points
    AIRVPN.ORG best vpn i've had,
  4. 2 points
    Fixing a Malformed/Corrupted PLEX Database. Hi, all. I'm just here to update you on the "Starting Plex Media Server" issue. For me it was caused by a very malformed database file. I followed this guide which has worked perfectly. I've had a few more corruptions (brought about by failing hardware that I've replaced) but I've been able to bring my library back each time. I wrote this script to automate much of the process, and do some of the most basic backup management (creating backups if your database isn't corrupt/malformed and you agree to a prompt). PLEASE MAKE SURE YOUR TO SET THE TOP 2 VARIABLES! They're fairly self-explanatory, but here is what you set them to: appdata_directory > Your appdata directory plex_container_name > The name of your plex container (the defaults for those are "/mnt/user/appdata" and "plex" respectively) This script requires SQLite3 if you do not have it installed: 1. Go to Community Applications 2. Install the Dev Pack 3. Go to "Settings" in UNRAID 4. Open Dev Pack 5. Enable (install) SQLite3 6. Retry pmsDB.sh Also, please keep in mind that I wrote this script with this linuxserver.io image of plex in mind, it should(?) still work with other plex dockers if you edit the paths in the script, but I'm making no guarantees. Download Script: pmsDB.sh ***EDIT - 5/24/19*** I just updated the script to fix one of my checks (for sqlite3) and improved the error reporting (slightly).
  5. 2 points
    As many are aware, Intel has had some serious security vulnerabilities released over the past year. "Spectre", "Meltdown", and now one of the strongest dubbed "Zombieload" aka MDS. Intel seems to be having some skeletons coming out of the closet, which saw a CEO resign, and market share loss now to AMD. The mitigation's to these vulnerabilities have all individually come with a performance cost, Spectre/Meltdown in the range of ~%15, and now MDS rumored to need Hyperthreading disabled altogether to mitigate, costing upwards of %30-%40 (sources are based on the internet, so take with a grain of salt). So add them all together, and that's a pretty hefty penalty for users who may not even be a target for this kind of attack. Personally, I have nothing that sensitive at my home running in individual dockers or VM's that I would worry enough about if someone from one area could read data from the other. As well, my local users are myself and my wife 🙂 , so she could just TAKE the money from the bank in person 🙂 Not a threat to me. I don't care if someone is watching me play games on a vm, or is watching that I am encoding or decrypting a movie, big deal, not much going on at my house anyone would work hard enough to watch....... and if someone did make it that far to target me, I got bigger problems than speculative execution, like checking my firewall rules!! So, with that said, this is ALL AT YOUR OWN RISK, I or the community do not assume any responsibility of damage due to the disablement of these mitigation's. As of 6.7.0, we have kernel level 4.19.41 which marks the last kernel to NOT mitigate against MDS. To disable Spectre/Meltdown for release 6.7.0, adjust your syslinux.cfg file as follows (and reboot): pti=off spectre_v2=off l1tf=off nospec_store_bypass_disable no_stf_barrier As of 6.7.1 RC1, we have kernel level 4.19.43 which marks the first kernel TO mitigate against Spectre/Meltdown AND MDS. To disable Spectre/Meltdown/MDS for release 6.7.1 RC1+, adjust your syslinux.cfg as follows (and reboot): pti=off spectre_v2=off l1tf=off mds=off nospec_store_bypass_disable no_stf_barrier You can validate the mitigation's on the OS before/after by: cat /sys/devices/system/cpu/vulnerabilities/* BEFORE: Should look similar to (notice the Mitigation's): Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable Mitigation: Clear CPU buffers; SMT vulnerable Mitigation: PTI Mitigation: Speculative Store Bypass disabled via prctl and seccomp Mitigation: __user pointer sanitization Mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling AFTER: Should look similar to (notice the Vulnerable): Mitigation: PTE Inversion; VMX: vulnerable Vulnerable; SMT vulnerable Vulnerable Vulnerable Mitigation: __user pointer sanitization Vulnerable, IBPB: disabled, STIBP: disabled
  6. 2 points
    Might I suggest that those of you requesting games that ich777 doesn't currently own a license for should contribute by either obtaining a license or working together with other requesters to obtain a license for ich777? You are asking for a significant amount of work to be done on your behalf, the least you can do is make the work easier to accomplish and support.
  7. 2 points
    The unbalance plugin will do what you want, it's a graphical front end that utilizes rsync command line to do the work. There also is a procedure that takes some of the risk out of moving data off of one array member, emulated or not, where you exclude the drive from the global shares configuration. That will allow you to enable disk shares and "safely" copy from that disk to the user share system, which will allocate the data according to your split level and disk allocation strategy. If you don't GLOBALLY exclude the disk from user shares, not just the regular exclude, it's going to corrupt the data if you try to copy from disk to user share. Unbalance operates from disk to disk instead of user share, so it's not effected. Also, I'd recommend copying instead of moving. It will be faster, and have the same end result. You will have to rebuild parity without that disk after you get the data safe. In any case, I hope the rest of your drives are perfectly healthy, because you are relying on them to perform flawlessly for the entire duration of this procedure. You say you plan on upgrading, it would be safer to go ahead with the upgrade and rebuild on to a larger disk. You would be operating at risk for less time.
  8. 2 points
    You misunderstand parity protection as it applies to single disks. The mdX devices are protected by parity, so there is no difference in protection whether you use /mnt/user/appdata or /mnt/diskX/appdata. In either case a single disk failure is still emulated by parity. The only thing you are losing is the ability to automatically spread the ../appdata folder across multiple disks and use a single point of access, /mnt/user/appdata. BTW, parity doesn't provide a resilient filesystem, only device failure protection. Each disk has a separate independent file system. The /mnt/user fuse is just the combination of all the root folder paths on each separate disk.
  9. 2 points
    Update: Was able to install 6.2.2-24922 DSM as a VM. This is what I did: - Used bootloader 1.03b. - Used DS3615 - Installed DMS version 6.2.2-24922 (also tried DSM 6.2.1-23824 Update 6 and that worked too!) - Created VM as "CentOS". Used Seabios and highest version of machine (Q35-3.0) - After I configured the bootloader, I loaded the img as the first bootable primary vdisk first but set the type to "USB". (doing it this way, as "usb", DSM won't see the bootloader image file as a hard drive and will show only your other vdisks attached) - I created a vdisk, and used qcow (other type could be used, but I didn't try). Must be at least 5gb I found. (anything less it won't see and/or will fail during setup) - The main part!! -- manually go into the XML and change the nic to "e1000e". This worked for me on my Supermicro - X9SRH-7F E5-2690 v2. YMMV. Good luck.
  10. 1 point
    Try this one..... root@matrix:/mnt/disk1/dvb# check-config.sh .config-swarm info: reading kernel config from .config-swarm ... Generally Necessary: - cgroup hierarchy: properly mounted [/sys/fs/cgroup] - CONFIG_NAMESPACES: enabled - CONFIG_NET_NS: enabled - CONFIG_PID_NS: enabled - CONFIG_IPC_NS: enabled - CONFIG_UTS_NS: enabled - CONFIG_CGROUPS: enabled - CONFIG_CGROUP_CPUACCT: enabled - CONFIG_CGROUP_DEVICE: enabled - CONFIG_CGROUP_FREEZER: enabled - CONFIG_CGROUP_SCHED: enabled - CONFIG_CPUSETS: enabled - CONFIG_MEMCG: enabled - CONFIG_KEYS: enabled - CONFIG_VETH: enabled (as module) - CONFIG_BRIDGE: enabled - CONFIG_BRIDGE_NETFILTER: enabled - CONFIG_NF_NAT_IPV4: enabled (as module) - CONFIG_IP_NF_FILTER: enabled (as module) - CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module) - CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled - CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled - CONFIG_NETFILTER_XT_MATCH_IPVS: enabled (as module) - CONFIG_IP_NF_NAT: enabled (as module) - CONFIG_NF_NAT: enabled (as module) - CONFIG_NF_NAT_NEEDED: enabled - CONFIG_POSIX_MQUEUE: enabled Optional Features: - CONFIG_USER_NS: enabled - CONFIG_SECCOMP: enabled - CONFIG_CGROUP_PIDS: enabled - CONFIG_MEMCG_SWAP: enabled - CONFIG_MEMCG_SWAP_ENABLED: enabled (cgroup swap accounting is currently enabled) - CONFIG_LEGACY_VSYSCALL_EMULATE: enabled - CONFIG_BLK_CGROUP: enabled - CONFIG_BLK_DEV_THROTTLING: enabled - CONFIG_IOSCHED_CFQ: enabled - CONFIG_CFQ_GROUP_IOSCHED: enabled - CONFIG_CGROUP_PERF: enabled - CONFIG_CGROUP_HUGETLB: missing - CONFIG_NET_CLS_CGROUP: enabled (as module) - CONFIG_CGROUP_NET_PRIO: enabled - CONFIG_CFS_BANDWIDTH: enabled - CONFIG_FAIR_GROUP_SCHED: enabled - CONFIG_RT_GROUP_SCHED: enabled - CONFIG_IP_NF_TARGET_REDIRECT: enabled (as module) - CONFIG_IP_VS: enabled (as module) - CONFIG_IP_VS_NFCT: enabled - CONFIG_IP_VS_PROTO_TCP: enabled - CONFIG_IP_VS_PROTO_UDP: enabled - CONFIG_IP_VS_RR: enabled (as module) - CONFIG_EXT4_FS: enabled (as module) - CONFIG_EXT4_FS_POSIX_ACL: enabled - CONFIG_EXT4_FS_SECURITY: missing enable these ext4 configs if you are using ext3 or ext4 as backing filesystem - Network Drivers: - "overlay": - CONFIG_VXLAN: enabled (as module) Optional (for encrypted networks): - CONFIG_CRYPTO: enabled - CONFIG_CRYPTO_AEAD: enabled - CONFIG_CRYPTO_GCM: enabled (as module) - CONFIG_CRYPTO_SEQIV: enabled - CONFIG_CRYPTO_GHASH: enabled (as module) - CONFIG_XFRM: enabled - CONFIG_XFRM_USER: enabled - CONFIG_XFRM_ALGO: enabled - CONFIG_INET_ESP: enabled - CONFIG_INET_XFRM_MODE_TRANSPORT: enabled - "ipvlan": - CONFIG_IPVLAN: enabled (as module) - "macvlan": - CONFIG_MACVLAN: enabled (as module) - CONFIG_DUMMY: enabled (as module) - "ftp,tftp client in container": - CONFIG_NF_NAT_FTP: enabled (as module) - CONFIG_NF_CONNTRACK_FTP: enabled (as module) - CONFIG_NF_NAT_TFTP: enabled (as module) - CONFIG_NF_CONNTRACK_TFTP: enabled - Storage Drivers: - "aufs": - CONFIG_AUFS_FS: missing - "btrfs": - CONFIG_BTRFS_FS: enabled - CONFIG_BTRFS_FS_POSIX_ACL: enabled - "devicemapper": - CONFIG_BLK_DEV_DM: enabled (as module) - CONFIG_DM_THIN_PROVISIONING: enabled (as module) - "overlay": - CONFIG_OVERLAY_FS: enabled - "zfs": - /dev/zfs: missing - zfs command: missing - zpool command: missing Limits: - /proc/sys/kernel/keys/root_maxkeys: 1000000 Unraid-v6.7.1rc1-swarm-v2.zipswarm-v2.patch
  11. 1 point
    What you describe should work. however it is worth pointing out that for important data you normally you want a backup that is independent of the server in case the server itself has some sort of catastrophic failure.
  12. 1 point
    This plugin is designed to find and offer up suggestions to a multitude of configuration errors, outright problems, etc for numerous aspects of your unRaid server. To install this plugin, just head over to the Apps tab and search for Fix Common Problems. After installation, you will see a lifesaver within Settings / User Utilities which will launch a manual scan (and give you the option to set the background scan settings) For every error or warning that this plugin finds, a suggested course of action will also be displayed. Additionally, should you seek additional help for any error / warning, the errors are all logged into your syslog so that persons helping can easily find the issue when you post your diagnostics. Scans can be scheduled to run automatically in the background (you have the option of hourly, daily, weekly, and monthly). Additionally, if the background scans find an issue they will send out a notification (depending upon your notification settings in this plugin) The current list of tested items will be maintained in the second post of this thread. Any support for problems this plugin finds, should be posted in the General v6 section of these forums. Problems relating to false positives, suggestions for more checks, why I made the decisions I did, wording mistakes in suggestions, etc. should be posted here. As usual for anything written by me, updates are frequent as new ideas pop into my head. Highly recommended to turn on auto-updates for this plugin. Additionally, a special "Troubleshooting Mode" is available to assist with problems involving random crashes / shutdowns / lockups / etc A video with a basic run through of FCP can be found here: (at about 18:25)
  13. 1 point
    The decode script should become unnecessary here in the next couple of months. The Plex team has mentioned on their forum that they are working on adding the decode function.
  14. 1 point
    @RoderickBasinB The url for the beta plugin is different, as I didn't wanted it to show as update until 6.7.0 was officially released. The beta plugin looks for updates at the same github url as the normal version or CA. Once I pushed the beta version to github as new official release yesterday, it got made available as update in the plugin settings (no matter if old or beta) and it is now available in CA or for manually installing it from github https://github.com/SlrG/unRAID/raw/master/Plugins/ProFTPd.plg. The beta version link is now obsolete. It provides the now old beta version with old version number, which is essentially the same as the new official version with a new version number. I guess when you tried to install from CA it was before I pushed the beta version to github as new official release and so you got the old version still. I hope this explains what was happening.
  15. 1 point
    In my experience, @limetech are far more likely to respond to a request which clearly states the requirement, which, in this case is a kernel module, than just a plain "Can we get docker swarm?" Problem with the second question is it's an unknown quantity of what needs to be done and why this is important? Just remember Unraid can't be everything to everyone, and whilst some decisions might seem arbitrary, there may be good reasons why stuff isn't changed upstream. For instance if adding that kernel module breaks something else, it's a no go. As some useful information, here's the output of the above script. root@server:~# wget https://raw.githubusercontent.com/moby/moby/master/contrib/check-config.sh --2019-05-25 12:00:31-- https://raw.githubusercontent.com/moby/moby/master/contrib/check-config.sh Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 151.101.16.133 Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|151.101.16.133|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 10314 (10K) [text/plain] Saving to: ‘check-config.sh’ check-config.sh 100%[===================>] 10.07K --.-KB/s in 0s 2019-05-25 12:00:31 (208 MB/s) - ‘check-config.sh’ saved [10314/10314] root@server:~# chmod +x check-config.sh root@server:~# ./check-config.sh warning: /proc/config.gz does not exist, searching other paths for kernel config ... info: reading kernel config from /usr/src/linux-4.19.41-Unraid/.config ... Generally Necessary: - cgroup hierarchy: properly mounted [/sys/fs/cgroup] - CONFIG_NAMESPACES: enabled - CONFIG_NET_NS: enabled - CONFIG_PID_NS: enabled - CONFIG_IPC_NS: enabled - CONFIG_UTS_NS: enabled - CONFIG_CGROUPS: enabled - CONFIG_CGROUP_CPUACCT: enabled - CONFIG_CGROUP_DEVICE: enabled - CONFIG_CGROUP_FREEZER: enabled - CONFIG_CGROUP_SCHED: enabled - CONFIG_CPUSETS: enabled - CONFIG_MEMCG: enabled - CONFIG_KEYS: enabled - CONFIG_VETH: enabled (as module) - CONFIG_BRIDGE: enabled - CONFIG_BRIDGE_NETFILTER: enabled - CONFIG_NF_NAT_IPV4: enabled (as module) - CONFIG_IP_NF_FILTER: enabled (as module) - CONFIG_IP_NF_TARGET_MASQUERADE: enabled (as module) - CONFIG_NETFILTER_XT_MATCH_ADDRTYPE: enabled - CONFIG_NETFILTER_XT_MATCH_CONNTRACK: enabled - CONFIG_NETFILTER_XT_MATCH_IPVS: missing - CONFIG_IP_NF_NAT: enabled (as module) - CONFIG_NF_NAT: enabled (as module) - CONFIG_NF_NAT_NEEDED: enabled - CONFIG_POSIX_MQUEUE: enabled Optional Features: - CONFIG_USER_NS: enabled - CONFIG_SECCOMP: enabled - CONFIG_CGROUP_PIDS: enabled - CONFIG_MEMCG_SWAP: enabled - CONFIG_MEMCG_SWAP_ENABLED: enabled (cgroup swap accounting is currently enabled) - CONFIG_LEGACY_VSYSCALL_EMULATE: enabled - CONFIG_BLK_CGROUP: enabled - CONFIG_BLK_DEV_THROTTLING: enabled - CONFIG_IOSCHED_CFQ: enabled - CONFIG_CFQ_GROUP_IOSCHED: enabled - CONFIG_CGROUP_PERF: enabled - CONFIG_CGROUP_HUGETLB: missing - CONFIG_NET_CLS_CGROUP: missing - CONFIG_CGROUP_NET_PRIO: missing - CONFIG_CFS_BANDWIDTH: enabled - CONFIG_FAIR_GROUP_SCHED: enabled - CONFIG_RT_GROUP_SCHED: enabled - CONFIG_IP_NF_TARGET_REDIRECT: enabled (as module) - CONFIG_IP_VS: missing - CONFIG_IP_VS_NFCT: missing - CONFIG_IP_VS_PROTO_TCP: missing - CONFIG_IP_VS_PROTO_UDP: missing - CONFIG_IP_VS_RR: missing - CONFIG_EXT4_FS: enabled (as module) - CONFIG_EXT4_FS_POSIX_ACL: enabled - CONFIG_EXT4_FS_SECURITY: missing enable these ext4 configs if you are using ext3 or ext4 as backing filesystem - Network Drivers: - "overlay": - CONFIG_VXLAN: enabled (as module) Optional (for encrypted networks): - CONFIG_CRYPTO: enabled - CONFIG_CRYPTO_AEAD: enabled - CONFIG_CRYPTO_GCM: enabled (as module) - CONFIG_CRYPTO_SEQIV: enabled - CONFIG_CRYPTO_GHASH: enabled (as module) - CONFIG_XFRM: enabled - CONFIG_XFRM_USER: enabled - CONFIG_XFRM_ALGO: enabled - CONFIG_INET_ESP: enabled - CONFIG_INET_XFRM_MODE_TRANSPORT: enabled - "ipvlan": - CONFIG_IPVLAN: missing - "macvlan": - CONFIG_MACVLAN: enabled (as module) - CONFIG_DUMMY: missing - "ftp,tftp client in container": - CONFIG_NF_NAT_FTP: missing - CONFIG_NF_CONNTRACK_FTP: missing - CONFIG_NF_NAT_TFTP: enabled (as module) - CONFIG_NF_CONNTRACK_TFTP: enabled - Storage Drivers: - "aufs": - CONFIG_AUFS_FS: missing - "btrfs": - CONFIG_BTRFS_FS: enabled - CONFIG_BTRFS_FS_POSIX_ACL: enabled - "devicemapper": - CONFIG_BLK_DEV_DM: enabled (as module) - CONFIG_DM_THIN_PROVISIONING: enabled (as module) - "overlay": - CONFIG_OVERLAY_FS: enabled - "zfs": - /dev/zfs: missing - zfs command: missing - zpool command: missing Limits: - /proc/sys/kernel/keys/root_maxkeys: 1000000 root@server:~#
  16. 1 point
    It is in the config directory/folder. Before you modify it in any way, I would suggest that you do two things. First, make a backup copy of your entire flash drive. You can do this from the Main page. Click on Flash under the Device column. Under the 'Flash Device Settings', you will find the backup button. Second, make a copy of the network,cfg file in its folder. That will make it easy to recover if you need to revert back to your original configuration.
  17. 1 point
    I would love this to be added as well. Maybe the team building the NVIDIA kernel could add it if unraid is unwilling to add it though it would be great to know why they don't want to add it.
  18. 1 point
  19. 1 point
    mover will only move data when it runs at its scheduled time. You can install the Mover Tuning plugin to get finer grained control over when mover runs. The other thing you should do is make sure that the the Minimum Free Space setting under Settings->Global Share Settings is set to be larger than the biggest file you expect to write. When the free space on the cache drops below that value Unraid will automatically stop trying to write new files to cache, and will start bypassing cache and writing directly to the array until space is freed up on the cache drive.
  20. 1 point
    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
  21. 1 point
    SSD needs a new SATA cable, likely the same for the other disks with increasing CRC errors, but I just see errors for the SSD on the current syslog.
  22. 1 point
    I have split this into its own topic. Do you have any other working dockers? Please post your docker run command as already requested.
  23. 1 point
    Disk10 dropped offline and got reconnected with a different identifier, there's a SMART report on the diags, it's sdn now, rebooting will fix the GUI/SMART issue, though you'll still need to rebuild the disk, which looks fine so more likely a connection issue.
  24. 1 point
    I'm very new to this but learning, I am currently running 6.6.7 and not sure but when I first started with this program I had the nice colour icons on all my apps like docker and such and now I only have colour app on the new ones I download. Not sure how to start over and get back the colour icons for such things as Docker, network, pretty much any thing in system settings is black and white and very generic looking to say, unlike what it should be. Any help would be apprefciated as I like the other look with this.
  25. 1 point
    Whatever is using the integrated graphics will probably show up on the built-in display. An external display may be required to see the output of the dedicated GPU.
  26. 1 point
    If you have a non-GPU device that you wish to assign to a guest in KVM and are using the machine type of PC (not Q35), you can use this XML and skip the <qemu:cmd> arguments at the end. This goes in between the <devices> and </devices> tags in your domain XML. <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x02' slot='0x00' function='0x1'/> </source> </hostdev> For "bus", "slot", and "function", this should be your PCI device address. The above XML will pass through PCI device 02:00.1. Again, this only applies to non-graphics PCI devices (NICs, USB controllers, capture cards, tuners, etc.) Happy virtualizing!!
  27. 1 point
    Many thanks, saved me tons of space. will keep these safe as they come in very handy. I am pretty sure Radarr doesn't download smaller versions if you change profile or the cutoff.
  28. 1 point
    I know this is overkill, but it only took about 15 minutes. Here are 3 different scripts for different situations: Remove directories within a source directory over a certain size: #!/bin/bash limit=20G source="/mnt/user/Movies" limit=$(echo $limit | cut -d 'G' -f 1) for dir in "$source"/*/ do size=$(du -sBG "$dir" | cut -d 'G' -f 1) if (( $size > $limit )) then echo remove: $dir rm -rf "$dir" fi done removeDirOverSize.sh Remove files within a source directory over a certain size: #!/bin/bash limit=20G source="/mnt/user/Movies" find "$source" -type f -size +$limit -delete -print removeFilesOverSize.sh Remove files within a source directory over a certain size with specific extensions: #!/bin/bash limit=20G source="/mnt/user/Movies" find "$source" -regextype posix-extended -iregex '.*\.(mpg|mkv)' -size +$limit -delete -print To change extensions you could replace mpg|mkv with avi or mpg|mkv|avi etc... removeFilesOverSizeByExtension.sh
  29. 1 point
    You also need to know whether the VM can do a UEFI boot or not. If the vmdk is not set up for UEFI boot then you should be using the SeaBIOS option.
  30. 1 point
    Do you mean vmdk (rather than vmdf)? If so they are not supported by the Unraid GUI although the underlying KVM system can normally use them. Since the GUI does not support them you have to manually enter the full path. Also a vmdk File is not an iso image but the main vdisk that is used to run the VM. You also need to ensure the controller type is set correctly to match what the original VM was set up to use. This is probably not the vfio type that Unraid defaults to but something like SATA. There have to be appropriate drivers already loaded into the VM or it will not be able to use the vdisk.
  31. 1 point
    Thank you for this information!
  32. 1 point
    Yeah that's running in bridge mode, thus the ports should be and have been defined. Sent from my EML-L29 using Tapatalk
  33. 1 point
    Depending on what exactly you did, be aware that it's probably not the whole computer that is routed through the VPN, most likely it's only the specific browser you configured.
  34. 1 point
    In this inaugural blog in the New Users Blog Series, we talk about: Unraid and the USB flash drive Using the USB Flash Creator tool How drives are counted towards the license limit How to reset your root password How to rename your server (Tower) How to change banner images and themes Check it out and let us know what you think! Have ideas/questions about Unraid that you'd like to see a blog written about? Post them here or send me a DM. Cheers! https://unraid.net/blog/unraid-new-users-blog-series
  35. 1 point
    For the USB creator tool, please enable UEFI by default, it took a bit of head scratching to figure out why the BIOS shows UEFI as a boot option for USB device, but it does not boot. Once I recreated the USB drive and selected the UEFI option under advanced settings, it showed UEFI and booted UEFI. From what I understand about the boot format, adding the UEFI option will still allow legacy booting, but not having the UEFI option will break UEFI booting.
  36. 1 point
    This Docker is in BETA status. Some controllers may not be detected, there may be errors thrown. Please help in resolving these issues if this occurs if you use this beta version. Installation Via the Community Application: Search for "DiskSpeed" Manual Installation (The Community Applications plugin is having issues currently, here's a work around for now) Save the attached "my-DiskSpeed.xml" file to your NAS under \\tower\flash\config\plugins\dockerMan\templates-user View the Docker tab in your unRAID Administrator , click on "Add Container" Under "Select a template", pick "my-DiskSpeed" The defaults should work as-is unless you have port 18888 already in use. If so, change the Web Port & WebUI settings to a new port number. The Docker will create a directory called "DiskSpeed" in your appdata directory to hold persistent data. Note: Privileged mode is required so that the application can see the controllers & drives on the host OS. This docker will use up to 512MB of RAM. RAM optimization will happen in a later BETA. Running View the Docker tab in your unRAID Administrator and click on the icon next to "DiskSpeed" and select WebUI. A new window will open. On first time run (or after the Docker app is updated or you select to rescan hardware), the application will scan your system to locate drive controllers & the hard drives attached to them. Drive Images As of this post, the Hard Drive Database (HDDB) has 825 drive models in 20 brands. If you have one or more drives that do not have a predefined image in the HDDB, you have a couple options available - wait for me to add the image which will be displayed after you click "Rescan Controllers" or you can add the drive yourself by editing it and uploading a drive image for it. You can view drive images in the HDDB to see if there's an image that'll fit your drive and optionally upload it so others can benefit. Controller & Drive Identification Issues Some drives, notably SSD's, do not reveal the Vendor correctly or at all. If you view the Drive information and it has the same value for the vendor as the model or an incorrect or missing Vendor, please inform me so that I can manually add the drive to the database or add code to handle it. If you have a controller that is not detected, please notify me. Benchmarking Drives The current method of benchmarking the hard drives is to read the hard drive at certain percentages for 15 seconds and takes the average speed over each of those seconds except for the first 2 seconds which tend to trend high. Hard Drives report an optimal block size to use while reading but if not, a block size of 128K is used. Since Docker under unRAID requires the array to be running, SpeedGap detection was added to detect disk drive activity during the test by comparing the smallest & largest amount of bytes read over the 15 seconds. If a gap is detected over a given size which starts at 45MB, the gap allowed is increased by 5MB and the spot retested. If a drive keeps triggering the SpeedGap detection over each spot, you may need to disable the SpeedGap detection as the drive is very erratic in its read speeds. One drive per controller is tested at the same time. In the future, each drive will be tested to see it's maximum transfer rate and the system will be tested to see how much data each controller can transfer and how much data the entire system bus can handle. Then multiple drives over multiple controllers will be read simultaneously while keeping the overall bandwidth by controller & system under the maximum transfer rate. Contributing to the Hard Drive Database If you have a drive that doesn't have information in the Hard Drive Database other than the model or you've performed benchmark tests, a button will be displayed at the bottom of the page labeled "Upload Drive & Benchmark Data to the Hard Drive Database". The HDDB will display information given up by the OS for the drives and the average speed graphs for comparison. Application Errors If you get an error message, please post the error here and the steps you took to cause it to happen. There will be a long string of java diagnostics after the error message (java stack) that you do not need to include, just the error message details. If you can't get past the Scanning Hardware screen, change the URL from http://[ip]:[port]/ScanControllers.cfm to http://[ip]:[port]/isolated/CreateDebugInfo.cfm and hit enter. Note: The unRAID diagnostic file doesn't provide any help. If submitting a diagnostic file, please use the link at the bottom of the controllers in the Diskspeed GUI. Home Screen (click top label to return to this screen) Controller Information Drive Information Drive Editor my-DiskSpeed.xml
  37. 1 point
    @Eadword: I have a thread opened for Docker Isolation with no replies, but you should add Linux namespaces / subuids for Docker to your list, as well as not using root and 777 permissions everywhere in the OS would be some good changes. It's been this way for a long time, I doubt it will change because unraid has always been a "don't expose to outside world" kind of distro for a long time.
  38. 1 point
    Upgraded two servers from V6.6.7, went very smoothly, especially compared to 6.5 -> 6.6 in my case. Really like the new dashboard, looks great! Zero issues so far, been running stable for a few days. I still have the following error message in the syslog, but as it doesn't seem cause problems, I have given up trying to look for a fix: kernel: i40e 0000:b5:00.0: Error I40E_AQ_RC_EINVAL adding RX filters on PF, promiscuous mode forced on
  39. 1 point
    Seems that we will be getting a newer, more simplified, flag we can set to disable mitigation's called: mitigations=off Other options would be: - mitigations=off: Disable all mitigations. - mitigations=auto: [default] Enable all the default mitigations, but leave SMT enabled, even if it's vulnerable. - mitigations=auto,nosmt: Enable all the default mitigations, disabling SMT if needed by a mitigation. In the meantime, we can continue to use the options above until I can test the new options out on unraid with a newer kernel (future releases once unraid upgrades kernel). There seems to be validation of it working in 5.0.16 Kernel. However seems to be a release intended for Kernel 5.2. https://www.phoronix.com/scan.php?page=news_item&px=Spectre-Meltdown-Easy-Switch-52 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v4.19.43&id=8cb932aca5d6728661a24eaecead9a34329903ff
  40. 1 point
    I left my v2 docker alone, stopped it and created a new docker with the v3 preview with its own appdata folder. I started fresh and everything is working fine so far. I imagine you can copy the DB folders into the new appdata folder but I don't know that exact process. I have only been running v3 for a couple days but I have not come across any issues yet.
  41. 1 point
    Here is a script that will remove directories within a source directory less than a certain size limit. I used 100M, but you can change it to any size in MB. The script can be easily changed to KB, GB, TB etc... Don't forget to set your source directory. #!/bin/bash limit=100M source="/mnt/user/Movies" limit=$(echo $limit | cut -d 'M' -f 1) for dir in "$source"/*/ do size=$(du -sBM "$dir" | cut -d 'M' -f 1) if (( $limit > $size )) then echo remove: $dir rm -rf "$dir" fi done removeDirUnderSize.sh
  42. 1 point
    This makes me thinks is still related to the UUID issue, you can try changing it again, but even if it works probably best to backup and reformat the disk. If the UUID change doesn't help and you want to try and recover any data before formatting try the btrfs recovery options on the FAQ.
  43. 1 point
    @Squid I have updated the dockerfile so that uses the latest version of mono, and I also have updated the template to fix those issues.
  44. 1 point
    https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md https://www.privoxy.org/user-manual/quickstart.html Substitute 127.0.0.1:8118 with the IP of your unraid server and the privoxy port defined in the docker config.
  45. 1 point
    You can plug your USB flash device into a PC and then make a backup (just drag contents to a temp folder on your desktop). Next use the USB Creator Tool to re-install Unraid OS on your flash. You can put the last version you were running, or try 6.7 again. Then copy the contents of your 'config' folder backup to the USB flash 'config' folder. If you had any custom 'syslinux' settings, you could restore that too. Eject flash, reboot server and 'should work' 👍
  46. 1 point
    That SSD is dropping offline: Apr 30 12:18:33 Tower kernel: sd 1:0:8:0: Power-on or device reset occurred Apr 30 12:18:33 Tower kernel: sd 1:0:8:0: Device offlined - not ready after error recovery Apr 30 12:18:33 Tower kernel: sd 1:0:8:0: [sdj] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 Apr 30 12:18:33 Tower kernel: sd 1:0:8:0: [sdj] tag#0 Sense Key : 0x2 [current] Apr 30 12:18:33 Tower kernel: sd 1:0:8:0: [sdj] tag#0 ASC=0x4 ASCQ=0x2 Apr 30 12:18:33 Tower kernel: sd 1:0:8:0: [sdj] tag#0 CDB: opcode=0x28 28 00 15 d5 43 38 00 00 08 00 Apr 30 12:18:33 Tower kernel: print_req_error: I/O error, dev sdj, sector 366297912 Apr 30 12:18:33 Tower kernel: sd 1:0:8:0: rejecting I/O to offline device Apr 30 12:18:33 Tower kernel: sd 1:0:8:0: [sdj] killing request Apr 30 12:18:33 Tower kernel: sd 1:0:8:0: [sdj] UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 Apr 30 12:18:33 Tower kernel: sd 1:0:8:0: [sdj] CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00 Apr 30 12:18:33 Tower kernel: print_req_error: I/O error, dev sdj, sector 244198784 You can try replacing cables, though you should connect the SSDs to the onboard SATA controller (and set to AHCI) to be able to trim them.
  47. 1 point
    I asked a meeseeks and he said you should maybe try upgrading to current stable, see if that fixes it, then upgrade to 6.7 if you're feeling up to it. It's definitely easier than improving Jerry's golf game. Sent from my Pixel 3 XL using Tapatalk
  48. 1 point
    Hi Xioustic, I'm trying to get this working for my son, and while I've pulled the container and ostensibly run it, I can't get Webman to see any games. Any tips?
  49. 1 point
    See this thread for some insight into how this is supposed to work.
  50. 1 point
    To clear up a misconception you seem to have: Array disks are not cached, user shares are. Any writes made directly to a disk will go directly to that disk. It is only when you write to a user share that unRAID decides whether or not to cache that write and then move it to the array at the scheduled time. The "Use cache disk" for each user share can be set to Yes, No, or Only. This and other User share settings are explained in the Help on that settings page. You can get the help by toggling the Help button. Yes - writes to the user share are written first to cache then moved to array at the scheduled time. No - writes to the user share are not written to the cache disk, but to the array disk(s). Only - writes to the user share are written to the cache disk but not moved to the array. Here is some more information about user shares that may not be obvious but can have very important effects: A user share is actually a top level folder on cache or array disk(s). The folder has the same name as the user share. Conversely, any top level folder on cache or array disk(s) is a user share. The user share has the same name as the folder. If you don't make settings for a user share it will have default settings, which includes Use cache: No. When unRAID writes a file to a user share, it writes it in accordance with the Use cache settings for that share. But when unRAID reads a user share, it will read from any disks (including cache) that have a top level folder named for that share. So it is possible to have writes that go to the array and not to cache while the reads could include files on cache, or have writes that only go to cache while the reads could include files not on cache. Hope I haven't confused things even further.