danioj

Members
  • Content Count

    1438
  • Joined

  • Last visited

  • Days Won

    1

danioj last won the day on November 22 2020

danioj had the most liked content!

Community Reputation

77 Good

About danioj

  • Rank
    Advanced Member
  • Birthday 07/25/1980

Converted

  • Gender
    Male
  • URL
    https://www.danioj.net
  • Location
    Melbourne, Australia
  • Personal Text
    Your arrogance blinds you, Master Yoda ...

Recent Profile Visitors

2853 profile views
  1. No idea what happened. Had nothing to do with 6.9.2 as it was running fine after the upgrade. Plex just stopped responding and was dropping any connection being made to it. Nothing obvious in the Plex logs either. Life is too short to troubleshoot sometimes. I just deleted the whole thing, reinstalled, scanned the library again. All is up and working again. Easy. I seem to recall that sometimes Plex 'Databases'? can get corrupt? Who knows. Anyway, all is well again and family have their tv.
  2. Evening all, Not sure if this issue is localised to me but this evening Plex became suddenly unresponsive. No changes or amendments. Im on unRAID OS 6.9.2. Version tag set to latest. Normal practice for me is to restart the container. Safari now complains that the connection to the server was "dropped". I get this in the log: ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO p
  3. Hi All, I am experiencing an unknown issue with my server. Since I upgraded to 6.9.1 I have experienced 2 "freezes". The server (and dockers) is unreachable via any means over the network or via the console. The only solution is to hard reset. By that time, the log is empty and diagnostics are useless. Nothing from initial view of the log following the reset indicates an issue nor is there any obvious disk issue following review of SMART data. It would be really helpful if I could configure unRAID to grab diagnostic data periodically to hopefully grab some
  4. I noticed that after upgrading from 6.8.3 to 6.9.1 that one of my docker containers (which run's on the host) lost its connectivity to a docker container which runs on a user defined network with its own IP. I could not understand why, as all the settings - including the "Host Access to custom networks" option, were checked. After a little playing, I stopped the array, turned the option off - saved. Then turned the option on - saved. Started the array and communication between the docker containers was restored. I am not sure if I can replicate this now that it has been
  5. @comet424 here is my2c. Home assistant is in its purest sense is Home Assistant Core. This can typically be installed on any Linux OS (although the HA devs would love to stop supporting that method of installation AFAIK) but it seems to me that the most suggested installation is via Docker. Hass.io is an OS that comes pre packed with Home Assistant Core AND with Docker running as well as a Docker “Assistant” that can be accessed within Home Assistant Core to manage the containers. This allows you to install “Addons” like MQTT etc but in essence as it is a Docker
  6. This is a wonderful post, written with insight, sensitivity and purpose. Thank you for taking the time to write it. I read it a few times, I hope others do the same.
  7. This post represents my own personal musings and opinion. This thread (and the broader situation) interests me on a number of levels. We (Royal we) bang on (quite rightly) about our community and how supportive, inclusive, helpful and respectful it is. Values really that any organisation in the world would be lucky for its members to behave consistent with. Saying that, this situation has shown that there is an undercurrent of what I can only call bitterness and to some extent entitlement in some community members. I don’t feel that this is across the board by any
  8. Unhelpful, inflammatory, provoking and downright unnecessary. Also, if I was to define the set of values that makes this community group so strong I would say there isn’t a word in your post that would align with them.
  9. Acting uncharacteristically extreme sometimes when we get hurt is very human and understandable and my personal opinion is that is what a few of the fellas at @linuxserver.iodid after the exchanges on the previous thread. I have no reason to doubt the sincerity of this post by @limetech and therefore was hoping there would be some return comms from @linuxserver.io to do their part in repairing this bridge. It might be nice if those who “retired” or decided they were now “out” or were “quitting unRAID work” came back. It might also be nice that if some of the support threa
  10. As much as I felt I had to post on the beta release thread I felt the need again to post here for this very nice and sincere post. “An apology is the super glue of life. It can repair just about anything.” - Lynn Johnston A great point and note on which to pivot and move on. I appreciate you for making this post Tom @limetech.
  11. Following @CHBMB’s request to have the support thread locked (and that request being actioned) along with his comment that all development and support for it has now ceased following @limetech announcement it wouldn’t surprise me if that App has been removed from CA altogether. CA is also a community app and the developer AFAIK still has a close relationship with the @linuxserver.io team. It appears therefore that to use Nvidia drivers with any future release of unRAID you must use the stock build (which now has them in of course). How to configure your dockers to use those stock bui
  12. I’ve been around a little while. I always follow the boards even though I have very little life time to give to being active in the community anymore. I felt the need to post to say I can completely appreciate how the guys at @linuxserver.io feel. I was lucky enough to be apart of the team @linuxserver.iofor a short while and I can personally attest to how much personal time and effort they put into development, stress testing and supporting their developments. While @limetech has developed a great base product i think it’s right to acknowledge that much of the
  13. My understanding is that IDRAC ports are similar to SuperMicro (and others) dedicated ports for server management (ie you cannot use them on your server as an available interface for your OS - in this case unRAID). You “could” (I think) go down the route (if you have a managed switch) of using your spare RJ45 port as the port for PfSense (available to the VM as a bridge) and use VLANS for LAN and WAN. I won’t elaborate on that. I think the best bet though is to use your Intel SFP+ card. I’m making assumptions that you’re not going 10G here and you just want to use your SFP+ ports as additio
  14. I’d love the ability to assign multiple networks to a single Docker container. The simplest use case involves pihole. Currently I run seperate instances of a pihole container for each of my VLANS. It would be great if I could just attach one container to each network and configure pihole to listen on all assigned interfaces. I’m pretty sure you can do it via the cli using ‘docker network connect <network> <container>‘ or something but it would be excellent to be able to do it in the GUI.