Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 01/11/19 in all areas

  1. 3 points
    There should be a new update available. This has quite a number of changes to how ffmpeg is executed. It should resolve some issues with inotify and library scanning. For those people who created issues on github you will see the ones that "should" be now fixed marked as closed. If I get time tomorrow I will make a push for adding some features. Perhaps some additional settings for file conversions.
  2. 3 points
    The price of Pro is so cheap I'm surprised anyone purchases less.
  3. 3 points
    Its a Jimmy Banner Bonanza! Enjoy!
  4. 2 points
  5. 2 points
    I'm taking a look now Edit: This may require a bit more investigation. I'm leaving some tests running while I head to bed. I'll let you know what I find in the morning.
  6. 2 points
    Add another digit to that and maybe viable. Interesting idea... thanks!
  7. 2 points
    ironic, because your hard drives are so outdated!
  8. 2 points
    Ah-ha! I may have found the problem: If I change the Primary vDisk Location from Auto to Manual, I can then Update the VM. But when I Edit it again, the Primary vDisk Location reverts to Auto.
  9. 1 point
    ETA? Because you know, we are OCD and that 'Update available' button does tend to bother us...
  10. 1 point
  11. 1 point
    Your screenshot shows appdata all on cache but system share has the same amount on cache and disk2, probably a duplicate of your docker image. Maybe I missed it in a previous post but which 2 config files?
  12. 1 point
    SSD was dropped from cache at some point in the past, likely dropped offline, you can re-add it but IMO not much point in running an hybrid SSD/HHD cache, I would use one or the other, depending on if you need speed or capacity.
  13. 1 point
    Your cache description isn't entirely clear, but in any case, however you have it configured, it is a pool with no way to specify the disks separately when accessing them. Most people would never consider mixing hdd and ssd in the cache pool. By "removing hdd from the array" I assume you actually mean removing it from the cache pool, not the parity array. People often use an Unassigned Device for dockers, etc. but an SSD is going to perform better with apps. I really don't have enough details about your system to make specific recommendations about how to proceed, and getting your configuration changed will probably take some detailed work, but it can be done. To give us a more complete idea of what you have and what might be happening, go to Tools - Diagnostics and attach the complete diagnostics zip file to your next post.
  14. 1 point
    I have got this all working, here is a guide. This will only work with intel iGPU on unraid. I have an E3-1275 V5 CPU. You need an Intel CPU with iGPU and quick sync video support. https://en.wikipedia.org/wiki/Intel_Quick_Sync_Video The assumption is that nothing else is using the integrated video from your CPU (no VM's) Mine is Skylake so I am limited to HEVC, (no 10 bit, that will be software transcode instead), If I upgrade to a Kaby Lake Xeon I would have full support for HEVC 10-BIT I grabbed info from this thread and info from the Emby docker page, if you run into trouble with below check out that thread. Any experts on this please feel free to chime in and I can update it. This is what I did to make it work: Step 1 Edit your go file with a text editor (I use EditPad Lite) You can share your flash file as hidden and give your self access. (Click on the flash drive in the main tab to find this setting) Locate the go file: flash\config\ Edit the go file with a text editor and add the following: (put this in below anything already in your go file) #Setup drivers for hardware transcoding in Emby modprobe i915 chown -R nobody:users /dev/dri chmod -R 777 /dev/dri Restart your unRaid system Step 2 Click on the terminal screen on unRAID on the top menu. and type / paste: getent group video | cut -d: -f3 Note what the output is (mine was 18) as seen below Step 3 I am using the official Emby Docker: https://hub.docker.com/r/emby/embyserver/ Here is the link to the templates. (I am using beta currently) you need to add this manually, this wont be found in Community Applications. https://github.com/MediaBrowser/Emby.Build/tree/master/unraid-templates/emby I am currently using the beta 4.0 it has a nice little logo to confirm hardware transcoding Here is what I have in my docker template, you will need to add extra parameters over the default. If you already have Emby, you will need to modify your template to add extra parameters. This is easy to do with the "+Add another Path, Port, Variable, Label or Device" when editing your install. My Settings: Repository: emby/embyserver:beta Network Type: Host Console shell command: Shell Privileged: Off Port 1: 8096 Container Port: 8096 (for htttp) Port 2: 8920 Container Port: 8920 (options if using https) Path 1: /mnt/user/appdata/emby/ Container Path: /config Path 2: /mnt/user (change as required to your media share, i leave it as user, makes it easier to add new shares with out remapping) Container Path: /mnt Variable 1: Key: APP_UID Value: 99 Variable 2: Key: APP_GID Value: 100 Variable 2: Key: GIDLIST Value: (Change to your output from Step 2) Here is an example of Variable 1 Now click on Advance View and under "Extra Parameters" add the following: --device /dev/dri/renderD128 I have also attached my template (my-EmbyServer.xml) that you can edit and add it your flash drive. I am not sure if unRAID will need a restart to find it. Place the template here: flash\config\plugins\dockerMan\templates-user my-EmbyServer.xml Step 4 Start Emby. As I am running Beta 4.0 (please note massive changes to your library so check out the forums first) you don't need to do anything. It will pick it up automatically. Give it a test. Checkout the transcode section just in chase, click advanced and it will show you what was detected. If using the current release (3.5.3) you need to use VAAPI and under device add the following: /dev/dri/renderD128 Then restart. You need to check the transcode logs to see if hardware transcodings was successful on 3.5.3
  15. 1 point
  16. 1 point
    Apps Tab - Enable DockerHub search results in it's settings. Search for powershell Install it, then (technically, the above isn't even required, but only lets you have unRaid allow you to uninstall it) Linux 4.18.20-unRAID. Last login: Tue Jan 1 20:53:05 -0500 2019 on pts/1 from 192.168.1.183. root@ServerA:~# docker run -it microsoft/powershell PowerShell 6.1.1 Copyright (c) Microsoft Corporation. All rights reserved. https://aka.ms/pscore6-docs Type 'help' to get help. PS /> Write-Host "Hello, World!" Hello, World!
  17. 1 point
    Pulseway is a great tool that allows you to remotely monitor servers from iOS, Android, and the web. I mainly use it on iOS for the notifications about loss of network, high CPU usage or my server being shutdown. It was one of the few things I missed when I switched my server to unRAID. Luckily, I figured out how to get it installed and working. Here's the steps I took: 1. Download the Pulseway Agent for Slackware from Pulseway's website 2. Copy the pulseway_x64.txz to /boot/extra (this is also the flash smb share so flash/extra) 3. Create a new folder,pulseway, in the /boot directory 4. Reboot unRAID 5. SSH into server and copy config.xml.sample to config.xml: cp /etc/pulseway/config.xml.sample /etc/pulseway/config.xml 6. Edit the config.xml file you just copied, you'll need to add your Pulseway username/password and setup any notifications you want to receive (change the Enabled flag from False to True). I enabled Network interface monitoring (change interface name to br0) as well as WhenOffline, HighCpuUsage and MemoryLow notifications. 7. Pulseway needs to be run to verify your config file works and to generate an id file. The Pulseway service looks for version 0.9.8 of libssl and libcrypto, unRAID includes version 1.0.0 so we need to create symlinks to the 1.0.0 files to trick Pulseway into using those: ln -s /lib64/libssl.so.1.0.0 /usr/lib64/libssl.so.0.9.8 ln -s /lib64/libcrypto.so.1.0.0 /usr/lib64/libcrypto.so.0.9.8 8. Start Pulseway service: /etc/rc.d/rc.pulseway start 9. Copy the id file generated by Pulseway to the /boot/pulseway directory (if you don't do this, the server will show up as a new machine in Pulseway every time unRAID boots): cp /var/pulseway/pulseway.id /boot/pulseway/pulseway.id 10. Copy your config file to /boot/pulseway cp /etc/pulseway/config.xml /boot/pulseway/config.xml 11. Add the following lines to /boot/config/go cp /boot/pulseway/config.xml /etc/pulseway/config.xml cp /boot/pulseway/pulseway.id /var/pulseway/pulseway.id ln -s /lib64/libssl.so.1.0.0 /usr/lib64/libssl.so.0.9.8 ln -s /lib64/libcrypto.so.1.0.0 /usr/lib64/libcrypto.so.0.9.8 # As of version 6.6, you also need one for libidn ln -s /usr/lib64/libidn.so.12 /usr/lib64/libidn.so.11 /etc/rc.d/rc.pulseway start 12. Reboot unRAID and make sure everything works! Explanation: unRAID's OS is stored in RAM so any changes you make do not persist after a reboot/shutdown. That's why we need to move everything to the /boot drive (the flash drive unRAID boots from). On startup, we're installing Pulseway, creating symlinks to libraries it needs, copying the config and id files to their respective locations and then starting the service. EDIT (9/26/2018): As of version 6.6, you also need to create a symlink for libidn like so: ln -s /usr/lib64/libidn.so.12 /usr/lib64/libidn.so.11
  18. 1 point
    Not sure I understand the question, but the numbers in your screenshot will reset on reboot.
  19. 1 point
    If you're on latest release it's much easier, just click on the flash drive and change it here:
  20. 1 point
    It was too much of a rabbit hole, so I built my own container. It aims to be fully fault-tolerant, self-healing and modular. And it's a bit smaller than the other leading brand, running on Alpine Linux rather than Ubuntu. I haven't figured out the unRAID template thing to make a Docker container work natively with unRAID yet, so please offer some tips on that. I read the docs on it a while back, and I need to go over them again. But here's how it works on the command line, for now. DISCLAIMER: This is a work-in-progress. It may have significant bugs, and lacks a certain level of fit and finish. I use it, but I have not exercised it very much to shake out more than obvious issues. docker run -d --rm \ --net='bridge' \ -p 1984:80/tcp \ -v '/mnt/cache/appdata/cacti/backups':'/var/backups':'rw' \ -v '/mnt/cache/appdata/cacti/mysql-data':'/var/lib/mysql':'rw' \ -v '/mnt/cache/appdata/cacti/mysql-conf':'/etc/mysql':'rw' \ -v '/mnt/cache/appdata/cacti/cacti-data':'/var/lib/cacti/rra':'rw' \ -v '/mnt/cache/appdata/cacti/apache-conf':'/etc/apache2':'rw' \ -v '/mnt/cache/appdata/cacti/php-conf':'/etc/php7':'rw' \ -e TZ="America/Los_Angeles" \ -e MYSQL='mysql root password' \ -e CACTI='cacti user db password' \ --name cacti \ chestersgarage/cacti:latest The settings are intentionally a little different from the QuantumObject container in order to avoid conflicts. Being able to easily maintain configs and data outside of the container are key improvements. The container will look for existing configs and data at each startup, and if some are missing or not recognized, it will initialize those elements of the application from defaults. What I like to do is let it start up fresh, then manipulate the configs after that point. The migration instructions take that approach as well. Take a look at the source here: https://github.com/ChestersGarage/cacti https://hub.docker.com/r/chestersgarage/cacti/ Migration instructions provided in the source repos linked above. I'm hoping to have the container fully compliant with the unRAID Docker implementation in a week or two. Enjoy!
  21. 1 point
    Thank you sir, I actually can now find this in the web assistant now although im getting a message of Failed to format the disk. (35) when trying to install from the PAT file. I cannot change the bus to 02 or the slot to 01 either comes up with an error although i have managed to chang ethe type to e1000 Confused as to why i cannot format the Vdisk tho ? This is my disk config <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/isos/New folder/synoboot.img'/> <target dev='hdc' bus='usb'/> <boot order='1'/> <address type='usb' bus='0' port='1'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Linux/vdisk2.img'/> <target dev='hdd' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk>
  22. 1 point
    I have one server that, although it isn't encrypted, may be an example of a work around for you. You will need: Dynamic DNS for the router (or know the WAN IP). This can be done in the router (usually). A local user (other than root) on the server setup with SSH access. (I recommend the SSH and denyhosts plugins by docgyver) Setup port forwarding on the router to forward SSH to the unRaid server. Using SSH tunnels and port forwarding on the router, I run ssh mysuser@mydynamic.host.com -CL 8080:localhost:80 -p 2020 from my remote location. Breaking this down: I have the router forward the external port 2020 to the internal port 22 of the unRaid server's IP. In the example above, mydynamic.host.com is a Dynamic DNS name of the router so outside machines can talk to the router. It could also be the WAN IP of the router. 'C' tells ssh to use compression (why not). 'L' tells ssh to tunnel the local machines port 8080 to localhost (from the point of view of the unRiad server) on port 80. You would need to change this port to the HTTPS port if you have a SSL cert setup. Once the connection is working, on my computer I open a browser to localhost and port 8080 (https://localhost:8080 if using SSL on the unRaid server.) Then I can start the array as usual in the browser. NB: the localhost you put in the local browser is from the point of view of your machine you are connecting from. I won't go into ssh tunnels here; there's plenty of info about that on the internet. You also may be interested in this video (https://www.youtube.com/watch?v=TSlHEBR1yfY ) showing how to automatically download the password file for the encrypted disks. I haven't tried it.
  23. 1 point
    How do I close some of them without restarting unraid?
  24. 1 point
    I wrote this script that I tell user.scripts to fire off every morning at 7AM-11AM to back up some stuff from my Mac #!/bin/bash #Start Docker docker start resilio-sync #Delay before issuing Stop sleep 4h #Stop Docker docker stop resilio-sync
  25. 1 point
    Is this likely to work on unRAID? ## Create an image file to your preferred size fallocate -l 50G /data/security/patio.img ## Format the image file as ext3 mkfs -t ext3 -q /data/security/patio.img -F ##Add the NFS mount to your FSTAB to mount the image at your NFS location (/etc/FSTAB) /data/security/patio.img /data/security/patio ext3 rw,loop,usrquota,grpquota 0 0