Dmtalon

Members
  • Posts

    160
  • Joined

  • Last visited

Everything posted by Dmtalon

  1. Someone more knowledgeable than me would need to answer that. Anything in the logs giving you a clue?
  2. I'm glad these helped for sure! They are likely both there because we both struggled too :-) I look at those simply as network maps. I mounted mine to how it was originaly so I could keep the configuration the same so I only just added /mnt to /mnt/ That way if the container method (aka docker) didn't work out for me, I could swap back using the same configuration file. I tried a few iterations. Initially I couldn't get any media listed because I didn't have those filled out. I don't remember how/where I figured it out but I'm sure someone here pointed me straight!
  3. I'm glad it helped! I was in the same boat as you for sure... Decided to just try it. had a couple little issues, but made it through fairly clean but I certainly understand the confusion and/or worry about just trying it :-)
  4. I wrote it a while ago, but should have linked to it. Its not titled as a how too create a docker. I modified my post above, but here it is also. http://lime-technology.com/forum/index.php?topic=35531.msg330955#msg330955
  5. Not sure what would have been accessing it. I stopped my VM and Docker. Nothing was running. I was trying to get it unmounted to run a fsck on it. Wouldn't the manual way fail if it was busy as well? /etc/rc.d/rc.snap stop ?
  6. I cannot stop webvirtman (KVM Manager) via Gui I cannot unmount/stop SNAP via gui. I was able to stop both via /etc/rc.d/rc.webvirtman stop | rc.snap stop
  7. I get one telling me SNAP started. That's the the only one other than the test one I've gotten
  8. You might already know this by now but a few posts down I ask the same question, and the answer is "Yes" it is the same. Be prepared to reboot after, because the docker page will be messed up until a reboot.
  9. Ok, stopped my docker, my VM uninstalled snap, then reinstalled, and added the share the same name. Seems all is well! Thanks for the tip. I guess I updated to b12 before SNAP was updated.
  10. This isn't going to loose the data is it? I did run the plugin-check and updated anything needing it before unraid. (Just FYI)
  11. Anyone running SNAP getting anything to come up under settings/Snap?
  12. Reboot cleaned up my docker page also... Thanks!
  13. That is what I did, I no longer have the docker plugin installed I can click on those 'missing button images' above to see the normal layout but it defaults to that image I posted earlier. Before removing the docker manager, it looked fine, and autostarted fine.
  14. This messed up my docker tab... http://i.imgur.com/Aj0RpWm.png
  15. Are you referring to the "Docker Manager" (by gfjardim) listed in Plugins?
  16. all I did was just add the from email(s) at the top, then changed the gmail pull down to gmail-TLS and entered in my login/password at the bottom. Ran the test and it sent me an email.
  17. Regarding the available ram... the Dashboard's (mine shows 97% full) is useless as is. If we're going to have a ram reporting section, is would be nice if it took that info from the second line of free to get a more accurate reading. That 97% scared me when I first upgraded and started looking at things. I jumped into SSH and looked at free/htop to see what was going on.
  18. I've now got three lines under "Docker Images" from previous updates of Plex Media Server. Can I just click on the ones not associated with PlexMediaServer and remove them once I know plex is working ok? Just select the box and click remove? Anything special need to be done outside that?
  19. That is very slick looking... And the change you made today fixed my issue.
  20. If I click on the running green icon in settings/kvm Manager it works which takes me to http://192.168.0.100:8000/servers/ If I click on the link in unraid gui (KVM across the top) it won't allow me to log in. edit: If I use http://192.168.0.100/KVM it does work. But everything i do in unraid is with my dns name nas1
  21. With the latest plug-in update it's not allowing me to log in. If I goto unraid:8000/servers/ I can log in and it works.
  22. No problem. I hope this helps someone at least! I just added a little blurb at the bottom, I have since rebooted now and ran into a wrinkle but not one most are likely to hit. It was a silly mistake.
  23. If I remember correctly it was a Redhat scsi driver that was needed for virtio not anything AMD.
  24. Of course... Panic is bad. My main scenario is this, you have a red ball. Go down, open the case to see 'whats up' and have a Red Ball Check Cables/Power Supply Check syslog Order to do stuff if it's determined the drive is bad etc.. I've got a spare drive precleared and ready to go, but I'm not sure I know the exact order to do things, so I'd be on here searching for the steps. Having that taped to the inside of my case seems like a good idea.
  25. I was thinking, it would probably be a good idea to print out a paper that has "what to do if x happens" and tape it to the inside of my unRAID case. Obviously it would need to be fairly short/easy to read. Something that had information on steps after a failed drive would be the primary information. Possibly some important console commands (how to start/stop things) or basic troubleshooting ideas for common issues. Does anyone already have something like this, if so mind sharing it? It would be nice to not have to scramble to look up the procedures of swapping out a bad drive when in that situation. Just a thought...