mbezzo

Members
  • Posts

    70
  • Joined

  • Last visited

Everything posted by mbezzo

  1. Hey, I've got that board (no wifi version) with a placeholder (3200G) CPU until I can track down a 3950x - only have Windows on it right now, but if you can tell me how to list the groups from Windows - happy to post em later!
  2. yeah, I'm aware of the massive Nest changes - but none of them have hit yet. That's all happening later this year (and now they've sort of rescinded and are saying existing API use will not be disabled - you just can't make any new ones) So... that doesn't quite explain it. Curious if anyone else using this docker still has Nest working?
  3. And while I'm at it, has anybody figured out how to configure the Homebridge docker to see the log from the Homebridge gui?
  4. I've narrowed it down to the Nest plugin. No changes whatsoever related to my Nest config - anybody have any ideas? I've completely removed the docker/nuked its appdata folder and completely rebuilt. Same issue - if I remove nest it works great. WTF! lol I've even issued a new api token! Anybody hear of any issues with Nest? I can't seem to find much... thanks all!
  5. these are the 3 errors. the one from my OP just reads as text (not colored). thanks!
  6. is this what you're looking for? the error would be the last line - takes awhile to show up so it's not in this one. thanks! homebridge.log
  7. I'm getting this after updating homebridge: terminate called after throwing an instance of 'std::bad_alloc' Any ideas? Thanks!
  8. and... it was a bad flash drive! Transferred the config folder and I'm all back up and running.
  9. It's not coming back up after rebooting sadly. Not home at the moment, so can't see what's happening. Will update when I can see what's happening.
  10. But now, I'm getting a bunch of errors and the array is offline. Just rebooted, but got some diags before I did. Anybody see anything interesting? got a bunch of emails with this in it: /bin/sh: line 1: 25882 Bus error /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null unraid-diagnostics-20190515-2106.zip Thank you!
  11. Hi all, I've got a Marvell controller on my mobo (88SE9128) what're the chances when I upgrade to 6.7 it won't work? Is there a running list of known good and/or bad Marvell controllers, or is it JUST the 88SE9230? (Bad in that they don't work with unRAID ) thanks!
  12. Thanks, @peteknot - shoulda looked there first! Yup - just deleted/re-added (copied all my settings and re-entered them) and all is well. Thanks again!
  13. Hey all, just updated this evening to the latest release, and I'm getting this in my logs. Any ideas? ::: Starting docker specific setup for docker pihole/pihole WARNING Misconfigured DNS in /etc/resolv.conf: Two DNS servers are recommended, 127.0.0.1 and any backup server WARNING Misconfigured DNS in /etc/resolv.conf: Primary DNS should be 127.0.0.1 (found 127.0.0.11) nameserver 127.0.0.11 It quickly just fails and stops after this error. Didn't have any issues with it prior to the update (and no config changes either).
  14. Well shoot... hahah. YUP! that did the trick. Thank you!!! Matt
  15. Hi All, Just got a new 8TB drive, ran it through a preclear cycle without issue. Added it to array (Disk 9/sdj), and it shows up as needing to be formatted, check the box, hit format and after a few secs, it just pops back up as "Unmountable: Unsupported partition layout" Any ideas? See attached logs. Thank you!! Matt unraid-diagnostics-20181204-1357.zip
  16. Hi All, I've been trying to get the mastodon dockerhub docker running, but no luck. Anyone willing to unRAIDify this one? https://hub.docker.com/r/tootsuite/mastodon/ https://github.com/tootsuite/documentation/blob/master/Running-Mastodon/Docker-Guide.md Much appreciated! Matt
  17. FWIW, I'd be interested in this too!
  18. THANKS @Tyler! This did the trick for me. I can't quite remember if I changed that to br0 or not - seems like that was default... Appreciate the reply!
  19. Thanks! And yes, the more the merrier to get this issue resolved
  20. Submitted this if others with the issue want to add on/comment: https://github.com/pi-hole/docker-pi-hole/issues/321
  21. Glad to hear I'm not alone - I was really pulling my hair out on this one!
  22. V4.0 works great for me for awhile, then it completely stops resolving DNS. I think it seems to be after the first reboot. Anybody else figure out how to fix this? If I nuke it all and reinstall - samething. Works great for awhile, then no DNS resolution...
  23. Thanks, John - that's exactly the info I was looking for. The issue definitely seems to be much better in my case, but I've seen it several times over the past 1.5 months. It always recovers and usually never last for more than 10 mins. I'm going to try moving things to /mnt/cache and see how it goes. Thanks again!