Jump to content

xorinzor

Members
  • Content Count

    45
  • Joined

  • Last visited

Community Reputation

1 Neutral

About xorinzor

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. sorry for the confusion. The last entry in the FAQ did indeed answer my question, thanks.
  2. But how will creating a local file, help me in getting CA to recognize the template? This container should eventually be able to be installed on other unraid installations too.
  3. can someone please explain to me how I can get the custom template to be recognized / used by CA for both search and install of the container? This is my container: https://hub.docker.com/r/xorinzor/shoutz0r And I tried creating this template, but that didn't seem to do much. https://github.com/xorinzor/docker-templates/blob/master/xorinzor/shoutz0r.xml Haven't been able to find some kind of guide or tutorial either, so I'm pretty much guessing here based on what other people did.
  4. Using Unraid 6.6.7 I have 2 shares, "downloads" and "media". Files that have finished downloading are written to a directory, thats checked for changes by a FileBot container. It then renames and moves the files to their respective directory in the media share. I used to have caching enabled for the media share, but recently decided it was better to have these files written to the array directly. For some reason however, FileBot still leaves these files on the cache drive, instead of writing it to the array. At first I thought it was an error by me, because the path used was still set to "/mnt/cache", but after changing it to "/mnt/user", it still happened. Even when I removed the "Media" directory from the cache drive. When manually invoking the mover it doesn't move the files either oddly enough.
  5. Hi, I've installed the MotionEye Docker container and attached the USB webcam to it via the extra parameters via: --device=/dev/bus/usb/002/004 which shows up fine in the container. But MotionEye fails to detect it as a webcam. I've read around that a usb webcam is supposed to show up as an /dev/video* device, but it doesn't for me. Is there any way to get this working without using a VM? "lsusb" shows: Bus 002 Device 004: ID 046d:0823 Logitech, Inc. It's a Logitech C920 (I think). And it works totally fine on my Windows Desktop, so I can confirm it's not broken.
  6. Ah, I didn't realize they already counted towards the limit. Nevermind then.
  7. If the drive would be part of the array, either by extending it, or functioning as a cache drive, I would agree with you. However, I'm just using it as a separate drive to store my config files on because I want to prevent my HDD's spinning up unnecessarily. I feel like the device count only counts (and should stay that way) towards the array functionality, as that's what UnRaid is mainly all about. If this plugin would be integrated with unraid and they'd start counting towards the device limit, a lot of people of the community will get very unhappy. And reasonably so.
  8. I figured I'd post my results here since this is the first result in google to come up for this issue. If you have used "Community Applications" to install docker containers (ie: the Apps tab), it is safe to remove the docker image file. After you have deleted the docker image file and create a new one and start your docker service back up, you can head back to the Apps tab and click on the list icon in the top-left to go to previous installed apps as jonathanm explains. When these are installed, all settings as you had previously configured your containers will be restored. The only thing you may have to fix are custom made docker networks and properly configure the autostart for your containers, as these will all be turned on by default. Other then that, you lose absolutely nothing. EDIT: Worth noting, it looks like it doesn't use the "Post Arguments" when building the container. For these to be applied you will have to edit the container, and just press "apply" again.
  9. I created a post in the support thread for UD, referencing this post and asking if the same SMART attribute monitoring toggle config can be added. As long as it's a separate plugin it makes sense that this wouldn't be something Unraid could do anything about. Thanks for the help!
  10. Regarding: With the normal disks mounted within unraid itself you can enable/disable the monitoring of certain SMART values. The mounted disks via Unassigned Devices don't have this option, and seem to follow the default settings as set in "UnRaid: settings -> disk settings". Would it be possible to implement this same SMART attribute monitoring menu like in unraid where these can be toggled on/off ?
  11. Looks like that workaround will do for now! Of course a more proper way of doing this would be even better, but at the moment I'm no longer getting spammed warning notifications Thanks!
  12. I'll try that out, thanks. As long as it works, even as a workaround, I'll be happy. It's turning kind of into a situation where the server screams "wolf" at the moment
  13. Turns out, this doesn't work in my specific case, because I mounted the SSD using the "Unassigned Devices" plugin. When I click on the device name, it doesn't show the SMART attributes like the other drives do
  14. I would really like the ability to exclude devices from the notifications that unraid sends. For example, I have an SSD installed, and will (on every write operation) get emails about it having bad sectors, which I know, but don't prioritize as needing a replacement since it only contains config files and is working fine so far. The only option for me to stop unraid from sending me those emails right now however, is by disabling warnings entirely, which would prevent unraid from sending me "legitimate" warnings about my array disks. Having a dropdown list next to each notification entity where you could either whitelist, or blacklist, devices would really be a massive help in managing these notifications more specifically. Even though this might generally not be needed.