puddleglum

Members
  • Posts

    30
  • Joined

  • Last visited

Everything posted by puddleglum

  1. Same error in FF, Chrome, Edge Ummm...it's Squeeze Ctrl
  2. Tried restarting the docker itself, same error. Tried restarting the server, same error. In the client, when you're selecting which LMS server to connect to...that shows the character string
  3. Just installed, tried to access settings: 403 Forbidden: settings/index.html Everything else appears to be fine...well, is there a way to edit the server name so it doesn't just show a string of randomly generated characters? Currently my "server" is 5c98e85133cf
  4. Does it not matter? I'd think AMD's drivers of today would be quite different than a generic MS driver from almost a decade ago.
  5. Hopefully this is my last forth-from-back-and-forth of unraid/bare metal! Going through and cleaning up the initial Win10 VM installation and I noticed the CPU driver is a MS driver from 4/21/2009. I can't seem to get anything else to install. How do you go about updating to AMD's most recent CPU driver? I've tried 3 different packages from AMD, they just seem to be GPU based (even one labeled "chipset". Went to the MB manufacturers website and downloaded the all-in-one. It too is the same. Tried the "have disk" option in windows, browsed to the extracted dirs and can't find an .inf to save my life.
  6. Before I switched to win on bare metal, I was using only one gpu for gaming on unraid. I didn't have to put anything in grub. Just boot up the machine and it displayed the host machine. go to the web interface, launch a vm, and the vm would take over the display. worked like a charm.
  7. I switched to a full install of Win-bare metal because games ran like a dog in the VM. Does the "fix" here https://lists.linuxfoundation.org/pipermail/iommu/2017-October/024823.html REALLY address the gpu issue? Are there pre and post benchmarks anywhere?
  8. @kizer That was it. Sorry (for my idiocy) and thanks (for your chill comment)! Sweet! Now, I can have my recorded television shows not take up ~6GB/hr and get it whittled down to about 1.5.
  9. I'm not getting any auto conversion from /watch. I checked /watch, and it does indeed match the share on the server. There were pre-populated videos in there. Nothing ever "kicked off" I copied a file from the share to my desktop, copied it back over, and still nothing. Suggestions?
  10. ASrock AB350 Fatal1ty Ryzen 1700x Radeon 480 8GB GSkill DDR4 32GB (3200 RAM, but can't get the board to work passed anything but 2133) Just set up a VM of Win10 last night then kicked off a bunch of games to DL. Haven't got to play them yet, but the OS is behaving fine. Everything seems to be dandy. I specifically went with the B350 board because I have no need for crossfire AND there were no X370 boards in stock. I just ordered a PCIE SATA card to offset the fewer ports. In my particular board, utilizing the M.2 port disables one of the SATA ports, and utilizing the M.2 ultra port disables one of the PCIE lanes. Not using a crossfire configuration, I can't see why there would be an issue running multiple vid cards.
  11. The server never automagically appeared. As soon as I remove it and install the official unraid one, it's there. Any other thoughts? I'd really like to use the DVR features. Wherever your appdata is stored. Ah, gotcha. Any other thoughts I might try when I get home? As I mentioned, I deleted the appdata dir (no biggie, my server isn't terribly populated at the moment) and recreated from scratch. Also, tried removing the docker and recreating with a capital Plex, so it wouldn't touch anything in the previously failed dir. No, I've already told you my thoughts... Try that first, then if that doesn't work, we can think again, but I don't have any other ideas tbh. Having said that, a screenshot of the docker setup might be helpful just to make sure you've got it configured appropriately. Didn't work. Still unavailable. I just had the same issue after I upgraded regular Plex to Plex Pass. I went into the web GUI and had to sign in, and it didn't find my local server. I logged out and back in without doing anything else, and it showed up. Not sure if you tried doing just that without anything else, but it might be worth a shot. I've tried logging out, removing the docker, deleting the dir from appdata, reinstalling/logging back in, etc. Just about every combination I can think of in order for plex to think it's "fresh". Odd. Maybe I just have to play the waiting game on this one? Hmph. The version string is in thre, i just blurred it out.
  12. My ini has "serverpassword=foo". I wouldn't use the register stuff. Just tell your friends to click "add server", and enter your fqdn, and the right port number. When they connect, it will prompt them for the password. If it doesn't then something's wrong with your port forwarding. Make sure you have it set up properly for your container in addition to your router. 'sall good. The error was router-side. I didn't have everything set up properly...now I do, and your docker works like a champ. Thank you.
  13. If you read the TOS, Amazon snoops EVERYTHING. And will delete at will. Doesn't stop me from utilizing it. Too good a bargain at the moment. As soon as they delete one of my files, I'm sure I'll turn to crashplan or some such. In the meantime, however, Amazon is da bomb.
  14. Not really. Perhaps I have a misunderstanding of how parity works though. As soon as a data drive receives a "write" it is immediately synced with parity? Ohhhhh (forgive me as I talk through my understanding of how unraid handles data)...I thought the parity portion didn't come into play until the scheduled sync (I have mine set for a weekly sync). So I thought parity should remain at rest until said scheduled action. But, perhaps that's just a check? If that's the case, then yes, if any drive is actively "waiting", as a good server should, then your statement makes absolute sense. Hence one of the reasons for a cache drive. Hmmmm. Thank you very much for your response.
  15. No, neither are SCSI drives, just regular drives plugged into the motherboard's SATA ports. No active reads or writes happening, yet other drives are active. I have Plex, Emby and Mumble servers installed, no cache drive. The docker .img is installed on one of the data drives. I'm assuming that's why it's active. What would you like from tools/diagnostics? The whole zip?
  16. Parity drive(s) never spin down? Why is this? The point of the parity drive is to be able to recover data in the event of a storage drive failure. Parity sync happens on a scheduled basis, it's not an "always, as soon and whenever a change is made" ideology, right? So why don't the parity drives spin down to rest until utilized? Is there a way to make them? I clicked on the down arrow next to one and it comes right back up. Or, am I incorrect in my thinking that a running drive will have a (potentially) shorter lifespan than one that is in a state of rest until called upon?
  17. Thanks. I'm not sure if this info is in some kind of "best practices" for unraid or not...honestly, i've only read a smidgen of what's available. But if it isn't...it should be. I certainly don't want my parity disc(s) constantly spinning for no good reason, lessening their longevity.
  18. Wherever your appdata is stored. Ah, gotcha. Any other thoughts I might try when I get home? As I mentioned, I deleted the appdata dir (no biggie, my server isn't terribly populated at the moment) and recreated from scratch. Also, tried removing the docker and recreating with a capital Plex, so it wouldn't touch anything in the previously failed dir. No, I've already told you my thoughts... Try that first, then if that doesn't work, we can think again, but I don't have any other ideas tbh. Having said that, a screenshot of the docker setup might be helpful just to make sure you've got it configured appropriately. Didn't work. Still unavailable. I just had the same issue after I upgraded regular Plex to Plex Pass. I went into the web GUI and had to sign in, and it didn't find my local server. I logged out and back in without doing anything else, and it showed up. Not sure if you tried doing just that without anything else, but it might be worth a shot. I've tried logging out, removing the docker, deleting the dir from appdata, reinstalling/logging back in, etc. Just about every combination I can think of in order for plex to think it's "fresh". Odd. Maybe I just have to play the waiting game on this one? Hmph. The version string is in thre, i just blurred it out.
  19. Wherever your appdata is stored. Ah, gotcha. Any other thoughts I might try when I get home? As I mentioned, I deleted the appdata dir (no biggie, my server isn't terribly populated at the moment) and recreated from scratch. Also, tried removing the docker and recreating with a capital Plex, so it wouldn't touch anything in the previously failed dir.
  20. I'm at work so can't check the box right now, however, I have no cache drive installed. Would that file be some other place?
  21. been wanting to try the dvr features so i uninstalled unraid's official and gave this one a shot. everything seems to install fine, but when going to web interface, it will not see itself as a server. my friends servers are there, my cloud sync is there, but no local server. i've removed the docker and reinstalled, changed the appdata dir, deleted the docker .img file and recreated, retried the whole shebang from scratch and nada. every time, same story, no local server.
  22. How do I allow external connections? I've set up my router to forward the default port to the server. I have edited the .ini file with the following #registerName=Mumble Server registerPassword=somegenericpassword #registerUrl=http://mumble.sourceforge.net/ registerHostname=thehostnameofmyserver When someone externally tries to connect, they put the fqdn in address field: hostname.mydomain.com and the default port, and a generic username They can't connect externally. I can connect internally. What do I need to do to allow anyone I provide the info to, to connect to my server?
  23. Thanks. The log still shows the same, but mythweb mysteriously populated data! Don't know how it works, bug glad it does. Now, let's see how the first recording turns out