puddleglum
-
Posts
30 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by puddleglum
-
-
6 minutes ago, dlandon said:
Try restarting the Docker.
I don't understand the server name issue. Where do you see this?
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
-
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
-
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.
-
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.
-
2 hours ago, ars92 said:
Woah are you saying that currently you have a ryzen system with only one GPU which is the 960 and yet you're passing through that GPU to the windows VM and unraid isn't giving any issue due to not having a GPU of its own?
this is great!!
Sent from my iPhone using TapatalkBefore 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.
-
10 hours ago, jayseejc said:
I've been running an r7 1700X since April. It works fine and now great with the npt bug fixed.
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?
-
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.
-
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?
-
Same error for me.
-
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.
7 hours ago, planetwilson said:So if you aren't planning on doing crossfire with gfx cards - is there any point in going for X370 over B350? large price difference in the boards. I am still not 100% clear on the PCI lane thing, will it be an issue running M.2 SSD cards and a couple of graphics cards in there (not crossfire, just hooked up to different VMs)
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.
-
Still nothing.Tried shutting down your plex container, logging into plex.tv, deleting old server, clearing browser cache and cookies, then setting up new server?
In that order.
But got to admit I'm shooting in the dark a bit with this one, I'm just assuming that as a different instance of Plex server is appearing on the same host that's what it causing the issue.
-
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.
Didn't work. Still unavailable.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?
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.
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.
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".
I had similar issues a few months ago with finding a local server. It was when I was messing about with different plug in and docker containers, testing the initial setup, then recreating the server in a different docker. Not sure what the cause was, but it seemed to sort itself out. My impression was that plex doesn't like recreating the same server with same name, owner and ip address. It's like it gets confused. I think internally it has a unique id and when there's two instances of the server with same name and ip address but different unique id it just fails to find it.
At times I could find it over wan, but not over lan. Also some pc's found it, eg hard wired into same router, whilst Wi-Fi didn't. It was very strange. It just fixed itself without any intervention from me. I did the management from the interfaces that could see it ie wan or the hard wired PC. Now it's behaved for ages. I assumed that plex forgets servers it hasn't seen for a while and thus sorted out its internal confusion. I'm just guessing. There are plex logs to be looked through, but they didn't add anything to help me at the time. YMMV.
Sent from my iPhone using Tapatalk
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.
-
What do I need to do to allow anyone I provide the info to, to connect to my server?
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.
-
I truly wonder how long unlimited will really mean unlimited. I know those of us with 100TB are not the majority and are more likely the minority but after the onedrive issues just make me wonder. Or even to the extent of how much snooping Amazon does to your files/data.
Sent from my iPhone using Tapatalk
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.
-
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.
-
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?
-
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?
-
The drive that contains your docker.img will probably not spin down while Docker is enabled. The docker.img should be on your cache drive, not an array drive.
The drive that contains your appdata folder will probably not spin down while Docker is enabled. The appdata share should be marked "cache only" so it stays on the cache drive.
Then assuming your individual dockers aren't accessing the drives (i.e. Crashplan isn't backing something up, Plex isn't creating index files) the array drives and parity drive should spin down.
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.
-
Didn't work. Still unavailable.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?
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.
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.
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".
I had similar issues a few months ago with finding a local server. It was when I was messing about with different plug in and docker containers, testing the initial setup, then recreating the server in a different docker. Not sure what the cause was, but it seemed to sort itself out. My impression was that plex doesn't like recreating the same server with same name, owner and ip address. It's like it gets confused. I think internally it has a unique id and when there's two instances of the server with same name and ip address but different unique id it just fails to find it.
At times I could find it over wan, but not over lan. Also some pc's found it, eg hard wired into same router, whilst Wi-Fi didn't. It was very strange. It just fixed itself without any intervention from me. I did the management from the interfaces that could see it ie wan or the hard wired PC. Now it's behaved for ages. I assumed that plex forgets servers it hasn't seen for a while and thus sorted out its internal confusion. I'm just guessing. There are plex logs to be looked through, but they didn't add anything to help me at the time. YMMV.
Sent from my iPhone using Tapatalk
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.
-
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?
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.
-
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?
-
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.
-
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?
-
Normal behavior, mine is the same and works perfectly
icon for kill switch is set default config file(s) appear to be in place .Xauthority file appears to in place kill switch is set setup desktop icon is set mythtv folders appear to be set Database(s) exists. Starting MariaDB... Checking whether database(s) are ready waiting..... waiting..... icon for kill switch is set default config file(s) appear to be in place .Xauthority file appears to in place kill switch is set setup desktop icon is set mythtv folders appear to be set Database(s) exists. Starting MariaDB... Checking whether database(s) are ready waiting..... waiting..... waiting..... icon for kill switch is set default config file(s) appear to be in place .Xauthority file appears to in place kill switch is set setup desktop icon is set mythtv folders appear to be set Database(s) exists. Starting MariaDB... Checking whether database(s) are ready waiting..... waiting..... icon for kill switch is set default config file(s) appear to be in place .Xauthority file appears to in place kill switch is set setup desktop icon is set mythtv folders appear to be set Database(s) exists. Starting MariaDB... Checking whether database(s) are ready waiting..... waiting..... icon for kill switch is set default config file(s) appear to be in place .Xauthority file appears to in place kill switch is set setup desktop icon is set mythtv folders appear to be set Database(s) exists. Starting MariaDB... Checking whether database(s) are ready waiting..... waiting.....
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
[support] dlandon - Logitech Media Server
in Docker Containers
Posted
Same error in FF, Chrome, Edge
Ummm...it's Squeeze Ctrl