Leaderboard

Popular Content

Showing content with the highest reputation on 10/10/18 in all areas

  1. Just wanted to updatea bit and say that the temperatures has decreased drastically since i did some modifications to my Silverstone DS380. I 3d printed a "cooling duct" that i found from someone who had similar problems. https://blog.briancmoses.com/2017/04/creating-a-cooling-duct-for-the-silverstone-ds380.html I also installed two Noctua NF-F12 Industrial 3000rpm fans. Loud af but as my server is in the basement, thats not an issue. Thanks for all the advice!
    2 points
  2. The limit is in the current size of super.dat, it can not hold more than 30 (=28+2) disk references. Limetech would need to invent a solution which can handle a bigger super.dat file, while maintaining backward compatilibty. And - as you mentioned - the second parity disk which is the highest number in the array would need to change. On top, several updates to the GUI need to be done to accommodate a larger array and a different parity2 assignment.
    2 points
  3. That's the proper solution except you probably want to use 'disks_mounted' and 'unmounting_disks' events.
    1 point
  4. If disk3 is really dead there's not much else you can do, and nothing to lose really, except time, do this: -Tools -> New Config -> Retain current configuration: All -> Apply -Assign any missing disk(s), including new disk3 -Important - After checking the assignments leave the browser on that page, the "Main" page. -Open an SSH session/use the console and type: mdcmd set invalidslot 3 29 -Back on the GUI and without refreshing the page, just start the array, do not check the "parity is already valid" box, disk3 will start rebuilding, if parity is valid disk should mount immediately but if it's unmountable don't format, wait for the rebuild to finish and then run a filesystem check
    1 point
  5. I'm on COX residential as well. Please refer to these posts as to how I was able to get it set up (per aptalca's excellent dockers and documentation!) and Hope it helps!
    1 point
  6. I had the same Problem day's ago .. After i reinstall the Network Status Plugin and reboot, unRAID Shares working like a charme again. Greetz
    1 point
  7. @tjb_altf4 Clocks back to 1.2 GHz when idle.In the picture core 8-16 cores are pinned to Plex and under load while others are idle.
    1 point
  8. It's all explained in the docker image description on both github and docker hub
    1 point
  9. If you had just SMB access to the shares, you would not lose that; but, because you have NFS access enabled, once /mnt/user is lost due to the NFS issues, it is not there for SMB access either.
    1 point
  10. I opened a merge request to bump the 'unstable' branch of this docker to (what UBNT says is stable) 5.9.29. https://github.com/linuxserver/docker-unifi/pull/81
    1 point
  11. I edited the config file as follows and it works! Thanks. cipher aes-128-gcm auth sha256 ncp-disable
    1 point
  12. If it moves and it shouldn't, duct tape it. If it should move and doesn't, WD-40.
    1 point
  13. We have an adage over here "If you can't fix it with duct tape, then you're not using enough" Sent from my LG-D852 using Tapatalk
    1 point
  14. Just a note that currently the application feed is having some weird problems. This has resulted in one entire existing repository being dropped, and a newly added one today not being added. Template maintainers may also on occasion see their templates not updating correctly. These problems have given me the impetus to finally take control of the appfeed and create a replacement, rather than relying upon a 3rd party to host and maintain it. The next revision of CA (due in a few days) will utilize the replacement as a default, with a fall-back to the existing one, and a final fall-back to legacy mode if necessary. As an aside, this also gives me the possibilities for future enhancements to CA that I've been thinking about for the longest time but have been unable to implement due to the design of the current feed. The upshot is that those users who due to their geographic location are blocked from utilizing the appfeed but are able to utilize legacy mode *should* have no problems connecting to the replacement. Downside is that it may take a second or two longer for CA to startup. In the meantime, if you notice that such-and-such application isn't appearing (or FCP is yelling at you), just ignore it (or yell back at FCP if it makes you feel better) - Andrew
    1 point
  15. Sound much like software development... You introduce 10 new features. Nobody notices those 9 features working fine, only this 1 feature which has issues 🤨
    1 point