arombo

Anyone else having an issue with Mark as Played? I'm receiving an error when attempting to do it from the gui website, and with remote sessions the video just remains in unplayed status. limetech plex Version 1.15.4.994

cybrnook, I've been able to adjust by simply logging out every time from the local webui page before closing the browser tab. If I stay logged in and close the page, and then attempt to reopen the webui, that's where I see the odd hangups and doubling of all active streams/unable to open any pages other than the landing home page. At least I don't have to restart the docker. Something funny with Chrome I guess.

I'm also on that release on chrome. I've disabled my adblockers and video blockers, but the web interface is still not functioning correctly. If I restart the plex docker it works fine on first connection. If I then leave the page and come back it will be in the buggy state. Thinking about moving to a different plex repo to see if it's isolated to the docker or just to me.

Anyone else having issues with accessing anything other than the home page of the Plex media server on chrome browser after the latest update? I can login to the homepage, but then can't actually open any thing else directory, settings, etc. I'm also seeing double the amount of current streams?

Just double checked my connections. Don't think anything is off still. It appears that I've lost my network interfaces. Any idea how to re-add them, or get them detected again? Latest diagnostics log attached. monolith-iii-diagnostics-20180114-1142.zip

Ok. Diagnostics ran successfully. Here's the file. monolith-iii-diagnostics-20180114-1037.zip

I made the upgrade from 6.3.5 to 6.4.0 this morning, and upon reboot I'm getting nothing from my server. I can login as root with my password ok. The command line terminal and GUI load up, but the gui web browser states it can't connect to localhost. I can't ping anything in the terminal window either. I've tried safe mode and there is no change. Please help. I'm very confused, and not sure what to try next.

@s_mason16 I've already sold it to a coworker who was interested.

I have a new in the box Rosewill RSV-L4500 I'm thinking of selling. Was gifted to me, but I don't think it will work for my needs. I'm located in the mid-west geographically.

So far so good on new SATA cables. Still showing no errors, and everything has been running just fine. (knocks on all the wood) Here's the latest Log just for records sake. I feel pretty confident that this issue can now be marked solved. monolith-iii-diagnostics-20170726-1131.zip

The Cables definitely are a little suspect to me, I noticed they weren't aligning 100% square to the SATA port when I moved them last night because of the tight squeeze from the drive cage to the motherboard. The cables are only nine months old though. I was already googling last night for some thinner\more flexible SATA cables to make things fit better and without putting stress on the motherboard ports.

After safely shutting down the server last night and moving the SATA cables over to the Intel ports, everything appeared to be back up and functioning with no issues. However, after checking it this morning I'm still getting disk read errors on my disk2. I've attached the diagnostics file freshly pulled from this morning. monolith-iii-diagnostics-20170712-0555.zip

Awesomesauce! Thanks again Johnnie.black!!!

Thank you again Johnnie.black! So even though the driver is different, the ports on the board that are labeled SAS will function like regular SATA ports when a SATA drive is attached to them? There is still room in the case I'm using for 2 more 3.5" hard drives, and I'm just trying to be certain that I can still do that in the the future.

Thank you Johnnie.black, I thought I had all the drives on the Intel controlled SATA ports. I will move some cables this evening and then restart the server to see if the issue resolves. Unrelated question, the ASRock EP2C602 motherboard I'm using has a group of 4 SAS ports on it. Are they not worthwhile over an LSI add in card?

Hello All, So during a parity check yesterday my Disk2 started reporting back read errors, over 20k. This system has never had any read errors before,and has been nice and rock solid for months. Poked around on the forums for some troubleshooting ideas and went into maintenance mode for the array, and ran the file system check on all of the drives, nothing came back stating there were errors, or that I needed to take additional steps. Restarted the array normally, no issues, but today again I'm starting to get read errors. The only changes made to the system before were the addition of the Plug-ins: CA Auto Turbo Write Mode, Dynamix Cache Directories, and Tips and Tweaks. Please find below my diagnostics. Right now I'm just looking for guidance on either repairing the drive with errors, or if it's too late to salvage and I should go out and get a replacement drive. I appreciate any and all help that can be provided. monolith-iii-diagnostics-20170711-0850.zip