Thiels851

Thanks. I looked into this earlier, and at that time there wasn't any lines written to syslog when it failed. I tried both writing to a local syslog, and a remote syslog collector. I will try it again with the remote syslog, to see if it was a on-off. I was hoping that something would be in the diagnostics.

Hello there. Plex has been working for years without issue. Now, when I play videos it will quite often crash the server to the point where shuts down, and I have to physically start it up again. I figured it was a crashed hard drive, so I recently downloaded unBalance and tried moving everything off of the hard drive I thought was problematic. Still no luck. Could be one of the other drives, but I figured I'd ask the community for help. I don't really use it for much besides plex these days, so it's possible that any processor intensive app could crash it too. Many thanks to anyone who can point me in the right direction! tower-diagnostics-20230905-0723.zip

Hello fine people. I'm having one hell of a problem with my server as of late. Been using unraid for about a year without issues, until I installed the unifi video docker container. I think I had it was misconfigured upon installation, and somehow used the docker image as data storage. That locked up my whole system, and I was forced to hard shut down the server. Luckily everything appears to have come back. I then had to delete the docker image, and reinstall the containers. Thought life was great again, but alas I have been unable to play any of my plex media. The latest message I get from plex is "couldn't retrieve the play queue for this item". I have spent the last few days trying everything I can think of: installing just the (binhex-plexpass) plex container, try other plex containers, etc. To no avail. Anyone have any ideas? I created a diagnostics file to attach it here. I would like to get the binhex one working again, as that's been the best behaving one. Here's what I see over and over in the docker.log file: time="2018-06-23T21:15:16.787863181-04:00" level=error msg="Failed to log msg \"\" for logger json-file: error writing log entry: write /var/lib/docker/containers/bbf2c38464cfe96c007d8ba87e2d146d9e803e30c37effe63c3a4aa0d4e2c686/bbf2c38464cfe96c007d8ba87e2d146d9e803e30c37effe63c3a4aa0d4e2c686-json.log: read-only file system" Created by...___. .__ .__\_ |__ |__| ____ | |__ ____ ___ ___| __ \| |/ \| | \_/ __ \\ \/ /| \_\ \ | | \ Y \ ___/ > <|___ /__|___| /___| /\___ >__/\_ \\/ \/ \/ \/ \/https://hub.docker.com/u/binhex/2018-06-28 21:20:11.799736 [info] Host is running unRAID2018-06-28 21:20:11.830986 [info] System information Linux Tower 4.14.13-unRAID #1 SMP PREEMPT Wed Jan 10 10:27:09 PST 2018 x86_64 GNU/Linux2018-06-28 21:20:11.869858 [info] PUID defined as '99'2018-06-28 21:20:11.948700 [info] PGID defined as '100'2018-06-28 21:20:12.007213 [info] UMASK defined as '000'2018-06-28 21:20:12.042004 [info] Permissions already set for volume mappings2018-06-28 21:20:12.079929 [info] TRANS_DIR defined as '/config/transcode'2018-06-28 21:20:12.176819 [info] Starting Supervisor...2018-06-28 21:20:12,398 INFO Included extra file "/etc/supervisor/conf.d/plexmediaserver.conf" during parsing2018-06-28 21:20:12,399 INFO Set uid to user 0 succeeded2018-06-28 21:20:12,401 INFO supervisord started with pid 72018-06-28 21:20:13,405 INFO spawned: 'plexmediaserver' with pid 552018-06-28 21:20:13,405 INFO reaped unknown pid 82018-06-28 21:20:14,407 INFO success: plexmediaserver entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)2018-06-29 01:00:35,629 DEBG 'plexmediaserver' stderr output:Connection to 45.56.96.162 closed by remote host.2018-06-29 04:52:54,065 DEBG 'plexmediaserver' stderr output:Connection to 45.56.96.162 closed by remote host.2018-06-29 05:39:55,252 DEBG 'plexmediaserver' stderr output:Connection to 45.56.103.116 closed by remote host.2018-06-29 06:15:14,353 DEBG 'plexmediaserver' stderr output:Connection to 45.56.96.162 closed by remote host.2018-06-29 08:04:53,046 DEBG 'plexmediaserver' stderr output:Connection to 45.56.96.162 closed by remote host.2018-06-29 08:31:34,530 DEBG 'plexmediaserver' stderr output:Connection to 45.79.184.41 closed by remote host.

Thank you. So what would be lost, the drive or the data? I just don't want to be caught in a loop of the drive being unmountable after each array restart and having to reformat it to make it functional. And the file system on the rest of the drives in the array, should I be worried about them at all? Sent from my iPhone using Tapatalk

and...here's the updated Disk Check without the -n flag. After the repair, I spun up the array and the bad drive still shows as "unmountable". DIsk Check Repair.rtf

Thanks. Yeah I just used the GUI and clicked the Check button. I'll look into the command line options. Here are the details from Diagnostics. tower-diagnostics-20170614-1008.zip

I have a drive that overheated and was marked as disabled. I then performed the steps I found somewhere to stop the array, disconnect the drive, start the array, stop the array, connect the drive, and start the array. I was then able to see the drive and formatted it, then readded it to the array. I lost the data on that drive, which sucked, but that was my fault so it is what it is. A week later, after getting a bunch of my data back, I relocated my server and therefore had to spin down the array, and performed a clean shutdown. Ever since then, that specific drive is showing unmountable. In an effort to do things the right way, I'm going to take a moment to reach out for assistance on these great forums, as recommended by "Fix Common Problems". I put the array into Maintenance Mode, then went to the drive, and ran the filesystem checks. The results are attached. I have also run extended SMART checks, and it appeared to run successfully. Any ideas? Of course, I'd like to save the drive as well as the data, but if this is going to be an ongoing problem with this drive I would replace it to avoid future issues. Thanks for any help! Disk Check.rtf