dchamb

I'd like to roll back to 6.8.3. That was a stable OS version. This one is crashing on me. I can't get diagnostics to run, it invokes a non-correcting parity check which cannot be stopped. This 6.9.2 version is a disaster!

I have seen posts from others about the same problem I am experiencing, i.e. dockers shutdown during a parity check. It does look like there is an interaction between the appdata backup running at the same time as the parity check. Other posts suggest moving the docker.img to cache along with appdata but I'm not sure how to do that properly.

My parity check runs monthly at the end of the month. It runs for more than 24 hours due to the size of the array. I also have an appdata backup that runs each day around 2am. However, the only time the docker servers are stopped are monthly at the end of the month. Once the parity check completes, the dockers resume automatically.

That is correct. The containers restart after the parity check finishes. But I also have an appdata backup that runs during the time the parity check runs. My parity checks run a little more than 24 hours.

Is there a way to prevent my docker apps from being stopped during a parity check? All of them including Plex are in a stopped state every month when the parity check runs.

Thanks. I removed the orphan, went back a few hours later and Plex came back. Any insight as to the cause of why unRaid did not shutdown cleanly?

Thanks!

Update: I forced an update to the stopped Plex container and it allowed me to start the Plex docker. However, the Plex clients do not see the server, even though it shows started. I am using the linuxserver/plex container. In addition, there is an (orphan image) that is stopped. I am not sure if it is interfering in any way or what is the best way to remove it other than remove it. Here is the Plex log: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 10-adduser: executing... ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 45-plex-claim: executing... [cont-init.d] 45-plex-claim: exited 0. [cont-init.d] 50-gid-video: executing... [cont-init.d] 50-gid-video: exited 0. [cont-init.d] 60-plex-update: executing... Atempting to upgrade to: 1.25.0.5246-cb2507e4d 2021-11-27 15:43:02 URL:https://downloads.plex.tv/plex-media-server-new/1.25.0.5246-cb2507e4d/debian/plexmediaserver_1.25.0.5246-cb2507e4d_amd64.deb [76591506/76591506] -> "/tmp/plexmediaserver_1.25.0.5246-cb2507e4d_amd64.deb" [1] (Reading database ... 10560 files and directories currently installed.) Preparing to unpack .../plexmediaserver_1.25.0.5246-cb2507e4d_amd64.deb ... PlexMediaServer install: Pre-installation Validation. PlexMediaServer install: Docker detected. Preinstallation validation not required. Unpacking plexmediaserver (1.25.0.5246-cb2507e4d) over (1.24.5.5173-8dcc73a59) ... Setting up plexmediaserver (1.25.0.5246-cb2507e4d) ... PlexMediaServer install: Docker detected. Postinstallation tasks not required. Continuing. [cont-init.d] 60-plex-update: exited 0. [cont-init.d] 90-custom-folders: executing... [cont-init.d] 90-custom-folders: exited 0. [cont-init.d] 99-custom-scripts: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-scripts: exited 0. [cont-init.d] done. [services.d] starting services Starting Plex Media Server. [services.d] done. Critical: libusb_init failed connect: Operation timed out

I upgraded to 6.9.2 recently after being up for 462 days 7 hours on 6.8.3. Initial impressions are that 6.8.3 was more stable. I just ran into a problem where my Plex docker seemed to be hung up (never had this problem before) and I tried to restart with clean shutdown with no success. I then tried shutting down the array and had no success with that either. Eventually I was forced to shutdown the system hard which caused a Parity Check to start. My Plex docker will not start and shows it is stopped. Any help will be most welcome! Dale tower-diagnostics-20211127-1421.zip

What should the Disk Settings be set to if you do not have VM Manager enabled?

I have the same issue. Whenever my monthly parity check starts or if I need to do a parity rebuild, all my docker apps are stopped automatically. As soon as the parity check/rebuild is complete, the docker apps are restarted automatically. I still have access to the array, just not the docker apps. Plex is one of them. My diagnositic logs are attached. Please note I took these logs during a parity rebuild. I had tried to start Plex from the Docker tab but it would not work. Dale tower-diagnostics-20211122-1525.zip

462 days 7 hours

Something is definitely wrong with transcoding. When I playback video on my big screen connected to my Roku, I get choppiness and buffering when set to auto. It goes away when I set it to direct. However, my smartphone over wifi will only work if I select transcoding. Not sure what to make of this but it didn't happen before the last container update.

I was thinking the transcoder performance was worse. I'm getting stuttering and stalls, but when I set quality to original everything plays fine.

Frank1940, Thanks! It is now set if this happens again. I've attached the syslog from the first and only time it failed. Not sure what to make of it except I see a general protection fault (which to me usually indicates a memory leak) and an error on the SSD drive, but nothing further shows up on the SSD. Ran SMART tests and it shows fine. Dale tower-diagnostics-20190712-1413.zip

That's the problem. This has been the only time it happened so I have no basis to determine when it might happen again. If it does, I believe there is close to a zero chance that getting a Diagnostics file saved since everything appeared to be down before the reboot. There was a syslog from before and after the crash though.

I upgraded to 6.7.2 from 6.6.6 about a week ago and all seems well. Before that I replaced the Marvell SATA controllers with an LSI Broadcom SAS HBA. Disk access times are better too. I did have one anomaly. Sometime during the early morning I could not access shared from any computer on my network. The webgui was still running but show zero CPU utilization. I tried to shutdown, but all I got were the standard shutdown warnings and nothing happened. After about 45 minutes I forced it down and restarted. Everything came back up but it had to do a parity check. I've never had this happen before. Dale

Here is one I am looking at currently LSI Broadcom SAS 9300-8i 8-port 12Gb/s SATA+SAS PCI-Express 3.0 Low Profile Host Bus Adapter https://www.amazon.com/dp/B00DSURZYS/ref=cm_sw_r_cp_apa_i_3c3fDbFCRSQST

Thanks johnnie.black. I still am uncertain if I should scrap this controller card for a non-Marvell based one. I see SAS controllers out there but I'm not familiar with them. And if I change my controller will all the existing drive assignments be preserved?

Where would I find it?

I have an unRAID version 6.6.6 system with an I/O Crest 4 Port SATA III PCI-e 2.0 x1 Controller Card Marvell 9215 (based on the Marvell 88SE9215). When I tried to upgrade to version 6.7.0 I lost 3 drives which were attached to this controller card. I reverted back to version 6.6.6 and the drives reappeared on the array. I am reluctant to try going to 6.7.2 because I don't know if this problem still exists, plus I've been aware of the posts on database corruption issues. My question is this: should I replace the controller with a non-Marvell based controller and try again? If so, what are the recommended controllers for SATA drives that should not have this problem with 6.7.x? Thanks Dale

Do you have any Marvell SATA controllers? I have one where two of my array disks are attached and had the same problem going from 6.6.6 to 6.7.0. I rolled back and had no problems. I'm guessing based on your experience the problem did not go away with 6.7.2.

I agree 100%. It is impossible for anyone to test for every condition and they have responded very quickly to address problems as they surfaced. unRAID OS is the best thing going!

Are you using a Marvell controller? I upgraded my system from 6.6.6 to 6.7.0 and two of my array drives went missing. They are attached to a Marvell controller. I reverted back to 6.6.6 and everything was fine. I'm waiting to see if 6.7.2 resolves this problem.

Does 6.7.2 solve the Marvell missing disks problem?