Leaderboard

Popular Content

Showing content with the highest reputation on 12/29/19 in all areas

  1. Introduction I recently modified the Corsair PSU plugin and made it easier to add to applications that can use REST such as Home Assistant, this got me thinking what i if i wrap the ini files used by emhttp in to JSON so i can get WAY WAY more statistics in Home Assistant from Unraid and so this plugin was created. super simple at only about 6 lines of PHP code. https://community.home-assistant.io/t/unraid-json-api/158652 This plugin is a wrapper for reading the files used by Unraid / emhttpd for displaying various statistics, the files are read from /var/local/emhttp/*.ini and are converted to JSON for easy access by services/applications like Home Assistant This plugin has no 'frontend' and is only accessible directly via http://TOWER/plugins/jsonapi/api.php?file=XXX.ini for example to get the disks.ini file you would do http://TOWER/plugins/jsonapi/api.php?file=disks.ini currently the following files exist that can be used but it's dynamic so if new files are added in new versions of Unraid in the same folder then these will be usable also. cpuload.ini devs.ini diskload.ini disks.ini monitor.ini network.ini sec.ini sec_afp.ini sec_nfs.ini shares.ini users.ini var.ini Usage Plugins > Install Plugin https://raw.githubusercontent.com/Cyanlabs/jsonapi-unraid/master/jsonapi.plg Source: https://github.com/Cyanlabs/jsonapi-unraid I will add some Home Assistant examples once i determine the best way. NOTE: please note that this currently is a raw json output, a custom HA component would be the best way to access this data but it is possible without a custom component (HA has a 255 character REST sensor state limit) - platform: rest name: Unraid resource: "http://192.168.1.3:965/plugins/jsonapi/api.php?file=disks.ini" username: root json_attributes: - disk1 - disk2 password: !secret unraid_password authentication: basic value_template: '{{ value_json["disk1"]["status"] }}' headers: User-Agent: Home Assistant Content-Type: application/json despite it not being able to do more than 255 you can work around it with the attributes, the above code will show something like this and you can access specific values with like this My python isn't great but i believe this is a good starting point - https://github.com/home-assistant/home-assistant/blob/dev/homeassistant/components/pvoutput/sensor.py Things like CPU load are easy though sensor: - platform: rest name: Unraid CPU resource: "http://192.168.1.3:965/plugins/jsonapi/api.php?file=cpuload.ini" username: root password: !secret unraid_password authentication: basic value_template: '{{ value_json["cpu"]["host"] }}' headers: User-Agent: Home Assistant Content-Type: application/json @LintHart thanks for the idea of integrating the PSU statistics in to Home Assistant and therefore making this an idea for me to create
    1 point
  2. Thanks, my friend is going to look in to a companion custom home assistant component but he is super busy currently so not sure when he will get it done. In the meantime the workaround sensor attributes works. It's possible there are other files used by unraid that might be usable in different folders so I'm happy to add others if they are relevant.
    1 point
  3. I've updated the Docker to Phusion 0.11 (Ubuntu 18.04). One of the changes is you'll have to change PATH_FFMPEG to /usr/bin/ffmpeg. Avconf has been removed.
    1 point
  4. Install UD+ and format the drives as necessary. The feature has not been removed, it's just optional. I never format drives on my main server.
    1 point
  5. You'd have to add in appropriate tests to determine that in your scripts The plugin can handle that for you https://forums.unraid.net/topic/48286-plugin-ca-user-scripts/?tab=comments#comment-475625 All scripts are executed as root. Either start a sub-script running as a particular user, or issue the appropriate chmod / chown commands after you're done. Should be noted however that on occasion you may need to specify full paths to commands that you may not have to when executing from the shell. IE: environment variables that are set in the shell aren't utilized in the plugin.
    1 point
  6. Haha sorry binhex, noob here. Thank you for the help 🙏🏽
    1 point
  7. I see "Member" thinks you are named "unPaid". I've certainly had a lot of users think I am named "Constructor".😉
    1 point
  8. It is also the only way you can re-order drives! In the special case of only having parity1 (not parity2) you can re-order drives without breaking parity. You can therefore use the New Config tool, re-arrange the drives into the order you want, and then tick the ‘Parity is Valid’ box before starting the array to commit the new order of drives and the array will start without needing to rebuild parity.
    1 point
  9. I was moderately surprised that the CSS changes didn't mess up CA at all. Personally I would submit a PR with the changes to LT to create a new theme say "Black(dim)", but I suppose that you should also create an appropriately modified white theme as that's like staring into a MagLight at night.
    1 point
  10. If you are referring to #1 in the text you quoted, it does not apply to your scenario since you are not mixing disks and user shares. When you might encounter the problem is if you were moving or copying from /mnt/disk1/share1 to /mnt/user/share1 or /mnt/user/share1 to /mnt/disk1/share1.
    1 point
  11. Check that arch link again, you are wrong Sent from my CLT-L09 using Tapatalk
    1 point
  12. Make sure you are aware of these 2 "surprises" that can happen with regard to moving or copying files directly on the server: https://forums.unraid.net/topic/61985-file-browser-in-webui/?do=findComment&comment=723474
    1 point
  13. What is the output from zpool list ? It should force import with zpool import -f Red8tb Sent from my iPhone using Tapatalk
    1 point
  14. No. UD Plus is just an add on plugin that installs the packages needed for the additional features. It is not an alternative to the base UD.
    1 point
  15. In the next release of UD, I am separating out all the packages loaded currently by UD into a separate plugin called 'Unassigned Devices Plus'. The packages removed from the base UD affect mounting of HFS+ and extFAT disks. If you need to mount these formats, install the UD plus Plugin. The other package not installed any more in the base UD s 'parted'. Parted is used for formatting and partition delete on disks. If you need to do any formatting or deleting of partitions, install the UD Plus plugin. All disk formats supported by Unraid are supported in the base UD plugin. The idea behind all this is the installation of packages into Unraid that are not used by the majority of users. I am not a fan of installing a lot of packages into Unraid, especially packages that are not being used. This also cuts down on the UD plugin installation time by not downloading and installing all those packages. The UD Settings page will indicate which features can not be enabled without the UD Plus plugin being installed. Check the 'Help' on that page for further information.
    1 point
  16. Just click on the 'ServerFiles' and put it wherever you want eg: '/mnt/user/MySuperspecialGames/Hurtworld1', '/mnt/user/MySuperspecialGames/Hurtworld2'... You don't need a cache drive it's recommended... You can also make it like this: '/mnt/disk1/Hurtworld1', '/mnt/disk1/Hurtworld2'... But keep in mind that each folder that you create will create a share directly to a disk so i would recommend you to do it like in the example above change 'MySuperspecialGames' to 'Hurtworldservers' or whatever you want.
    1 point
  17. Looks like there is a new BIOS/IPMI Firmware out very recently: BIOS: 1.1 IPMI: 01.23.04 No real release notes unfortunately. Currently I'm running unRAID 6.8.0, have a VGA display, IPMI/LOM console, and Quick Sync with my Plex docker all working great. My BIOS setting are the same as above, except there no longer seems to be a "Primary PCIE" option since I did the BIOS upgrade. I have "i915.disable_display=1" in syslinux.cfg and the following in my "go" file modprobe i915 chown -R nobody:users /dev/dri chmod -R 777 /dev/dri Happy to have been the guinea pig here. Aside from the "Primary PCIE" option disappearing I'd be curious to know if anyone else notices any other differences with the upgrades.
    1 point
  18. I updated the post to say that it does now have granularity. You have full granularity of cron schedules but you can also pick dummy proof schedules like - run at array start - run daily - run hourly Etc
    1 point
  19. You need to format the new data drive before you can start putting files on it. when you do that is up to you. It is possible to format the drive while the parity sync is running and the system will handle it correctly although the format and sync will run slower than normal if both are active at the same time so waiting until the sync finishes is not a bad idea.
    1 point
  20. 1 point
  21. I would love to see silent corruption detection natively integrated with parity checking for automatic repairing of the corruption. BTRFS only supports determining if there is corruption with a single drive, but the data exists in parity. Shouldn't have to go dig up a backup for this. Same with the Dynamix File Integrity plugin, from what I understand.
    1 point
  22. I 'll share my couple of cents on the assumption that cost is an issue. You 're not mentioning if you need transcoding. If you need up to 1 or 2 transcoding streams, then it 'd be safe to go with the 1600 w/out any GPU... If not for transcoding, the GPU is only needed to enter/configure the BIOS. Unraid itself does not need it. Unless you plan on passing a GPU through to a VM... As for the RAM, I 'd say use your existing sticks and only upgrade later if you feel the need to. For reference, my main Unraid server uses a Ryzen 2600 with 16G@3200 RAM and no GPU (I did put one just to configure the BIOS and then removed it). Emby can transcode one 4K stream on the CPU, no problem. Could possibly do two simultaneous 4K streams, didn't need it, didn't check for it That's what my needs are. YMMV
    1 point
  23. YESS! Now I got to figure out how to use these dockers.
    1 point
  24. I love the peace of mind Unraid gives me with my data. It’s hard to narrow it down to just 1 thing I want to see in 2020 so I won’t: 1. User shares spanning multiple servers (ideally docker-swarm-like capabilities as well) 2. VPN support baked in with a toggle on a per container/VM basis
    1 point
  25. Thanks for doing the giveaway. My favorite thing has always been the flexibility, being able to mix and match different disk sizes and easily being able to add/remove disks from the pool. I would love to see multiple cache pools, IE a cache pool for only my vm's and dockers and then another cache pool for just acting as a write cache
    1 point
  26. I love knowing my data is protected. I would like to see options for multiple servers and high availability. Starting with VM and containers. I’d love to replace my Proxmox boxes with Unraid.
    1 point
  27. Just as an aside for those of you that use Transdroid for connecting to your qbt client: You may have noticed that version 2.5.16 ceased to work due to the changes in qbt 4.20. There is an interim version to be found here - which unfortunately still produces an "Internal error building request" on my phone but it seems to work for others. Just saying. Edit: It works on my phones without a hitch, it just cannot be installed as an upgrade of V. 2.15.6.
    1 point
  28. "Fine people" and "on facebook" do not compute :P
    1 point
  29. you need to edit the nginx configuration file nginx.conf and look for these lines:- change this:- location / { index index.html index.htm index.php; auth_basic "Restricted Content"; auth_basic_user_file /config/nginx/security/auth; } to this:- location / { index index.html index.htm index.php; } make sure you do this for http and https, save and restart the container.
    1 point
  30. 1 point
  31. set the variable to / it's what i do
    1 point
  32. I run airsonic on a subdomain and with Lets Encrypt reverse proxy I have to use airsonic.domain.com/airsonic to access the login page. Removing the context path in the template solves this problem, but it returns after every update. Is there something I can do to fix this permanently?
    1 point
  33. Raising this old thread from the dead. After looking at this, there are a few options for managing Cron jobs: 1. Manually using crontab. Not really recommended given other better options. 2. Manually add in scripts into /etc/cron.hourly, /etc/cron.daily, /etc/cron.weekly or /etc/cron.monthly. Not recommended, this is not easier than other options. 3. Put cron scripts into /boot/config somethere (e.g. /boot/config/plugins/custom_cron/). These scripts are all automatically loaded on system start into /etc/cron.d/root/. If you make changes and want them applied, just run the command update_cron which reloads all the custom crons in /boot/config/plugins/custom_cron/). 4. Use the User Scripts plugin. This creates a folder /boot/config/plugins/user.scripts/ with a sub-folder called scripts. For each script, you create a sub-folder in /boot/config/plugins/user.scripts/scripts/, containing 2 files: Description and Script. Description is the 1 line description of the script that shows in the UI. The Script is the actual script. There is then a UI in the Unraid WebUI that allows you to run it one-off in foreground or background and supports custom scheduling using cron syntax. Best of every world. This is the best option and works even for the latest version of unraid (6.8.0 as of my last edit)
    1 point