hi there, anyone can help please?
i apologize for the trouble.
hi there, anyone can help please?
i apologize for the trouble.
Hi guys, happy new year. i am so sorry to bother.
i have tried everything i could in my knowledge. i cannot create new folder in the network drive that i map to windows.
i have put
docker,root,sambashare,ssh,sudo,users to my user
read/write to user
read/write/execute to root/user
i am not sure if i miss out anything
See: Plex Claim Token how to get your claim token.
hi mate, I have try following the step. but this is a fresh install of plex. there is nothing in the library folder. i am not sure how to view the XML for the token
https://hub.docker.com/r/linuxserver/plex
I thought it required a token number? (I don't use Plex) rather than just claim there? Instructions for using claim are on that link.
hi mate, merry xmas, yep I have follow that and get the claim key to insert in the code. it doesn't seem to work. when I go into plex it still ask me to claim the server
You could try putting a claim token in the PLEX_CLAIM= variable and redeploy the container. see:
Is the server logged in with your user credentials? See the icon with a letter in it in the upper right corner of the screen and click on the down arrow and sign in if needed.
i have tried this. but it doesn't seem to work.
btw it is PLEX_CLAIM= claim_ or PLEX_CLAIM=claim_
do I need a space after = ?
version: "2.1"
services:
plex:
image: ghcr.io/linuxserver/plex:latest
container_name: plex
network_mode: host
environment:
- PUID=998 #insert correct PUID
- PGID=100 #insert correct PGID
- PLEX_CLAIM= #optional, see https://hub.docker.com/r/linuxserver/plex for details
- UMASK=022 #optional, see https://hub.docker.com/r/linuxserver/plex for details
- VERSION=latest #see https://hub.docker.com/r/linuxserver/plex for details
volumes:
- /srv/dev-disk-by-uuid-97b70c21-d99e-47fd-9424-1dda54bf7763/docker_drive/plex_config:/config
- /srv/mergerfs/data_drive/data_drive/dramas:/dramas
- /srv/mergerfs/data_drive/data_drive/movies:/movies
- /srv/mergerfs/data_drive/data_drive/music:/music
- /srv/mergerfs/data_drive/data_drive/musicvideos:/musicvideos
- /srv/mergerfs/data_drive/data_drive/photos:/photos
restart: unless-stopped
Alles anzeigen
Codedocker: Let Docker handle the Plex Version, we keep our Dockerhub Endpoint up to date with the latest public builds. This is the same as leaving this setting out of your create command. latest: will update plex to the latest version available that you are entitled to. public: will update plexpass users to the latest public version, useful for plexpass users that don't want to be on the bleeding edge but still want the latest public updates. <specific-version>: will select a specific version (eg 0.9.12.4.1192-9a47d21) of plex to install, note you cannot use this to access plexpass versions if you do not have plexpass.
latest... I assume from the description.. that means you need to be a plexpass member. Are you a plexpass member?
You might also try redeploying the stack and see if it updates (and if it does, in the future consider watchtower to keep containers up to date automatically)
I'd also agree w/ gderf on using 998 as your PUID. Stop watching DBtech videos.
yes I am plexpass member for long time. i use to be on qnap. but it is spoiled. so I am building my own now. haha
oh ok. but what should I use?
Please use a code box when posting a compose file.
Poor choice of PUID=998.
What are you doing to claim the server?
i am sorry, what are you meaning by what are you doing to claim the server?
Post the docker-compose file you used.
Are the machine Plex is running on and the machine you are using to connect to it on the same network?
version: "2.1"
services:
plex:
image: ghcr.io/linuxserver/plex:latest #check at https://hub.docker.com/r/linuxserver/plex for available tags if needed
container_name: plex
network_mode: host
environment:
- PUID=998 #insert correct PUID
- PGID=100 #insert correct PGID
- PLEX_CLAIM= #optional, see https://hub.docker.com/r/linuxserver/plex for details
- UMASK=022 #optional, see https://hub.docker.com/r/linuxserver/plex for details
- VERSION=latest #see https://hub.docker.com/r/linuxserver/plex for details
volumes:
- /srv/dev-disk-by-uuid-97b70c21-d99e-47fd-9424-1dda54bf7763/docker_drive/plex_config:/config #adjust /srv/dev-disk-by-label-disk1 (mounted 'exec')
- /srv/mergerfs/data_drive/data_drive/dramas:/dramas #adjust according your setup; add more volumes if needed
- /srv/mergerfs/data_drive/data_drive/movies:/movies #adjust according your setup; add more volumes if needed
- /srv/mergerfs/data_drive/data_drive/music:/music #adjust according your setup; add more volumes if needed
- /srv/mergerfs/data_drive/data_drive/musicvideos:/musicvideos #adjust according your setup; add more volumes if needed
- /srv/mergerfs/data_drive/data_drive/photos:/photos #adjust according your setup; add more volumes if needed
restart: unless-stopped
yes it is on the same network
Which Plex container are you using? Do you have your version set?
version is latest in the env variable
Hi i have recently installed plex thru docker-compose following the step from the guide here.
i cannot seem to claim the server.
i have tried
reinstalling over again the plex.
restarting of docker & portainer
restarting of the whole nas
changing the DNS to 8.8.8.8 in OMV network interface & also my computer
the only thing I have not/unable is the hosts file which I do not know where is it.
I am still unable to claim the server. am I missing out anything.
Alles anzeigenBTW: I'm using a Dell HBA as well, in an Intel commercial server. It's a Dell Perc H200 that I flashed to JBOD. I haven't had any problems with it.
It matters. If drive device names are changing frequently (after a reboot), there may be an impact on setting up drives and related tasks.. I'm not sure if SNAPRAID converts to UUID, after the initial configuration, but it would make sense to use the mounted (UUID) path. (When you mentioned "parity" and "data" I'm assuming SNAPRAID.)
If that's the case, are you having problems with SNAPRAID when you run a scrub?Well, I'm guessing it's a used card. Did it come inside of a used server? If not, if it was bought separately, was the card handled properly? (Did it come in an anti-stat bag?) Have you ever heard of ESD? (Electrostatic Discharge Damage.) ESD damage can cause maddening intermittent problems.
Easy to do items to check off the list of possibilities are:
-Reseat the HBA.-Reseat SATA/SAS cables (both ends) and power connections.
- Look at SMART stat's to see if one of the drives are going south. (Any one drive can cause problems, especially with reordered device names.)
Look at the following:
SMART 5 – Reallocated_Sector_Count.SMART 187 – Reported_Uncorrectable_Errors.
SMART 188 – Command_Timeout.
SMART 197 – Current_Pending_Sector_Count.
SMART 198 – Offline_Uncorrectable.
And the following:SMART 199 - UltraDMA CRC errors
(Usually hardware or cable related)
___________________________________________________________________________
I'm curious as to, whether or not, the drives that are changing are attached to the HBA.
Storage, Disks will provide you with drive serial numbers versus device names. See if the changing drive devices are attached to the HBA.
Realize that I'm going out on a limb with these guesses. (They were made with very up front little information.)
thanks for all the info. i would check it one by one.
Alles anzeigenThat's not the drive path. You're talking about the device name. (/dev/sda is a device name.)
Drive absolute paths, as they are used in OMV, can be displayed under:
Storage, File Systems.
Click on the table Icon on the right and check the box for Mount Point.
You'll see drives mounted under their UUID's.
__________________________________________________________________
Why are your device names changing? If I were to guess, one of your many drives may have a bad cable or power connection. Maybe, if you have one of the cheaper HBA adapters, to attach additional drives beyond what the MOBO can handle, the card is not consistently reporting port numbers versus drive assignments to BIOS. (In that scenario, again if I were to guess, the drive(s) that are changing device names might be attached to that card.)
In any case, your scenario is one of the reasons why OMV mounts drives using UUID's in the mount point. UUID's don't change.
oh so it doesn't matter? coz I got so confused when scheduling tasks. coz I see the device name keep changing with the parity & data device name. ( the drive path uuid itself doesn't change right?)
yes I am using hba to connect all the drive. it is a dell hba bought from "the art of server"