[closed] Plex Docker stops working after Unraid restart

[DJay]

Hi Community,

This is my second time trying Unraid. First time I decided against, for time reasons. Since I have a little more time now, I decided to give it a shot again.

But until now it has been a hard time.

 

----------------------------------

My System:

M/B: ASRock - H270M-ITX/ac

CPU: Intel® Pentium® CPU G4560 @ 3.50GHz

HVM: Enabled

IOMMU: Enabled

Cache: 128 kB, 512 kB, 3072 kB

Memory: 8 GB (max. installable capacity 32 GB)

Network: bond0: fault-tolerance (active-backup), mtu 1500 
 eth0: 1000 Mb/s, full duplex, mtu 1500 
 eth1: not connected

Kernel: Linux 4.18.17-unRAID x86_64

 

8 GB DDR4 RAM

3x HGST 4TB HDD (2x ext4, 1x XFS)

1x WD 4TB HDD (ext4)

1x 128GB intel nvme ssd

1x 500 GB Samsung 840 pro (current workaround)

-----------------------------------

 

Before coming to my problem itself, a quick summary what I did.

I created a unraid stick, like the normal procedure.

Then I booted unraid, installed the community plugins, unassigned devices plugin and installed the plex docker container.

I wanted to use the filled HDDs as unassigned devices until I know all works fine, before I migrate them to XFS.

One HDD was free, which I placed into the first array slot.

The intel SSD was the only ssd in the system at the start and was used as cache (newly formatted as XFS).

So far so good, plex ran and worked. The problems begun after the first (intentional) reboot/ shutdown.

 

After the next start up the intel ssd was not mounted. I saw the error message that a unkown FS was on the ssd.

I thought, well i didnt too much yet, so I started again, formatted the ssd and it was running fine as cache. Re-setted up all. 

Sleep with the Dynamix plugin worked(s) fine. Until again, I shut the system down. And all was gone again.

 

Next try, quick and fast setup but then I installed the backup plugin from Dynamix and made a backup. Of course it happened again.

I was able to restore all, but it seemed to be a systematic problem. So I went ahead and placed the 500GB Samsung SSD into the system. As stated above as workaround, to test, since this SSD is planned for smth else. Restore didn't work, to be precise, physically it worked but the plex docker didn't start anymore.

Now we come to my problem. I was seeing the exact same error message as I have now.

 

So what I did, again formatted the cache drive (samsung ssd) and started from scratch. This time on the plus side, (fingers crossed) the ssd didn't "loose" it's FS. I was already suspecting a HW error on the ssd side. But before it worked fine with OpenMediaVault. Anyway, once all works I would take care of the intel ssd.

I shut down the system at some point and after the reboot I see this log in the docker container:

 

Quote

ErrorWarningSystemArrayLogin

[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] 40-plex-first-run: executing...
Plex Media Server first run setup complete
[cont-init.d] 40-plex-first-run: exited 0.
[cont-init.d] 50-plex-update: executing...
Attempting to upgrade to: 1.14.0.5465-425e4ac90
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
Attempting to upgrade to: 1.14.0.5465-425e4ac90
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
Selecting previously unselected package plexmediaserver.
(Reading database ... 7553 files and directories currently installed.)
Preparing to unpack /tmp/plexmediaserver.deb ...
Selecting previously unselected package plexmediaserver.
(Reading database ... 7553 files and directories currently installed.)
Preparing to unpack /tmp/plexmediaserver.deb ...
Unpacking plexmediaserver (1.14.0.5465-425e4ac90) ...
Setting up plexmediaserver (1.14.0.5465-425e4ac90) ...
Setting up plexmediaserver (1.14.0.5465-425e4ac90) ...

##################################################################
# NOTE: Your system does not have udev installed. Without udev #
# you won't be able to use DVBLogic's TVButler for DVR #
# or for LiveTV #
# #
# Please install udev and reinstall Plex Media Server to #
# to enable TV Butler support in Plex Media Server. #
# #
# To install udev run: sudo apt-get install udev #
# #
##################################################################

Processing triggers for systemd (229-4ubuntu21.4) ...
[cont-init.d] 50-plex-update: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
...

Starting Plex Media Server.
Starting Plex Media Server.
Starting Plex Media Server.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] syncing disks.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

 

I have no idea how to fix this.

The "Starting Plex Media Server." comes for several minutes until it end as displayed above.

 

I tried adding into the plex preferences.xml

EnableIPv6="0"

Which I found here:

https://github.com/linuxserver/docker-plex/issues/96

 

No change.

I am out of ideas and I don't feel like setting up everything again.

Interestingly the Handbrake and Krusader docker images continue to work.

 

I like the unraid approach, I would really appreciate help to make this fly.

I welcome any help.

 

 

 

 

 

 

 

 

 

unraid-nas-diagnostics-20181116-1456.zip

[trurl]

Which plex container is this? There are a few different ones to choose from here.

[trurl]

Are you running any other containers? I suspect one or more are misconfigured since you are already using more space in docker image than is typical for correctly configured dockers.

[trurl]

And your docker image is corrupt. The usual fix is to delete, recreate it then reinstall containers from Apps - Previous Apps. But I am wondering if you don't have some hardware problem that is leading to these issues.

 

Have you done a memtest?

[JorgeB]

4 minutes ago, trurl said:

But I am wondering if you don't have some hardware problem that is leading to these issues.

There is, one of the cache devices dropped offline:

 

Nov 14 00:34:02 Tower kernel: mpt2sas_cm0: removing handle(0x000f), sas_addr(0x4433221106000000)
Nov 14 00:34:02 Tower kernel: mpt2sas_cm0: enclosure logical id(0x5000000080000000), slot(1)
Nov 14 00:34:02 Tower kernel: sd 3:0:6:0: [sdk] Synchronizing SCSI cache
Nov 14 00:34:02 Tower kernel: sd 3:0:6:0: [sdk] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
Nov 14 00:34:02 Tower kernel: mpt2sas_cm0: removing handle(0x0010), sas_addr(0x4433221105000000)
Nov 14 00:34:02 Tower kernel: mpt2sas_cm0: enclosure logical id(0x5000000080000000), slot(2)
Nov 14 00:34:02 Tower kernel: sd 3:0:7:0: [sdl] Synchronizing SCSI cache
Nov 14 00:34:02 Tower kernel: sd 3:0:7:0: [sdl] Synchronize Cache(10) failed: Result: hostbyte=0x01 driverbyte=0x00
Nov 14 00:34:02 Tower kernel: mpt2sas_cm0: removing handle(0x0011), sas_addr(0x4433221107000000)
Nov 14 00:34:02 Tower kernel: mpt2sas_cm0: enclosure logical id(0x5000000080000000), slot(0)
Nov 14 00:34:02 Tower kernel: mpt2sas_cm0: sending diag reset !!
Nov 14 00:34:02 Tower kernel: mpt2sas_cm0: diag reset: FAILED
Nov 14 00:34:02 Tower kernel: iommu: Removing device 0000:02:00.0 from group 15
Nov 14 00:34:16 Tower kernel: BTRFS error (device sdg1): bdev /dev/sdf1 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0
Nov 14 00:34:16 Tower kernel: BTRFS error (device sdg1): bdev /dev/sdg1 errs: wr 1, rd 0, flush 0, corrupt 0, gen 0
Nov 14 00:34:16 Tower kernel: BTRFS error (device sdg1): bdev /dev/sdg1 errs: wr 1, rd 1, flush 0, corrupt 0, gen 0
Nov 14 00:34:16 Tower kernel: BTRFS error (device sdg1): bdev /dev/sdf1 errs: wr 1, rd 1, flush 0, corrupt 0, gen 0
Nov 14 00:34:16 Tower kernel: BTRFS error (device sdg1): bdev /dev/sdg1 errs: wr 1, rd 2, flush 0, corrupt 0, gen 0
Nov 14 00:34:16 Tower kernel: BTRFS error (device sdg1): bdev /dev/sdf1 errs: wr 1, rd 2, flush 0, corrupt 0, gen 0

 

[trurl]

Since he was having similar issues with nvme cache I didn't look further up the log for device problems.

[DJay]

Wow thanks for all that replies.

 

The docker container, sorry for forgetting to mention that:

plexinc/pms-docker:plexpass

Additionally I installed yesterday evening Krusader and Handbrake.

But I had the issues already while I had only plex as a container.

 

I could delete the docker image and do it from scratch. But I suspected that this is what happened when i used a new cache drive.

32 minutes ago, trurl said:

And your docker image is corrupt. The usual fix is to delete, recreate it then reinstall containers from Apps - Previous Apps. But I am wondering if you don't have some hardware problem that is leading to these issues.

 

Have you done a memtest?

Haven't done a memtest yet. But I could certainly do that.

I didn't expect a RAM issue, since OMV was fine. 

 

With HW issues you talk about deffective RAM right?

 

Since I will leave until tomorrow, i will let a memtest run. Just in case.

30 minutes ago, johnnie.black said:

There is, one of the cache devices dropped offline:

 

Nov 14 00:34:02 Tower kernel: mpt2sas_cm0: removing handle(0x000f), sas_addr(0x4433221106000000)
Nov 14 00:34:02 Tower kernel: mpt2sas_cm0: enclosure logical id(0x5000000080000000), slot(1)
...
Nov 14 00:34:16 Tower kernel: BTRFS error (device sdg1): bdev /dev/sdf1 errs: wr 1, rd 2, flush 0, corrupt 0, gen 0

 

 

What does it mean?

I have the intel ssd still inside, but not assigned.

It was the cache drive before. Right now only the Samsung one is assigned.

 

Btw. thanks guys, I had heared and read that the unraid community is strong. This was one of the things, why I wanted to give it a try.

 

Cheers,

Daniel

[JorgeB]

2 minutes ago, DJay said:

What does it mean?

In this case it appears to be the HBA stopped responding and since both cache devices are there problems with both, try reseating the controller, or using another slot if available, you should also update the firmware since it's very old:

 

Nov 12 06:11:03 Tower kernel: mpt2sas_cm0: LSISAS2008: FWVersion(07.15.08.00), ChipRevision(0x03), BiosVersion(00.00.00.00)

 

Current one is 20.00.007.00

[DJay]

4 hours ago, johnnie.black said:

In this case it appears to be the HBA stopped responding and since both cache devices are there problems with both, try reseating the controller, or using another slot if available, you should also update the firmware since it's very old:

 

Nov 12 06:11:03 Tower kernel: mpt2sas_cm0: LSISAS2008: FWVersion(07.15.08.00), ChipRevision(0x03), BiosVersion(00.00.00.00)

 

Current one is 20.00.007.00

 

FW of what? 

Bios i had just updated with the success of not finding the WoL settings anymore. And it stopped working too 😅

 

Anyway, if tell me of what, I'll do my best to do so. 

Currently the memtest is running until tomorrow late afternoon. 

[Hoopster]

1 hour ago, DJay said:

FW of what? 

The firmware of your LSI HBA.  Latest revision is 20.00.07.00 as johnnie.black indicated

[DJay]

I was googling this topic a bit. Unfortunately I have to tell that I didn't even know that I can update smth on the LSI HBA.

 

I found only this:

https://kb.sandisk.com/app/answers/detail/a_id/11192/~/lsi-sas2008-firmware%2Fbios-download-for-lightning-pcie-enterprise-ssa

 

Which looks also outdated? 

Where do I find the FW you guys mentioned? 

 

As mentioned I updated the BIOS in advance. But didn't know about any other FW. 

 

I'd appreciate a point into the right direction

[JorgeB]

You can find it on Broadcom's support site, under legacy

 

 

[DJay]

Hi again, 

i was searching for a new FW quite a while. 

Unfortunately I don't find any new one for a LSI SAS2008. 

 

With the version you mentioned I found only:

Quote

9202-16e_Package_P20_IT_Firmware_BIOS_for_MSDOS_Windows

Package_P20_Firmware_BIOS_for_MSDOS_Windows

Version: 20.00.07.00

and

Quote

9205-8e_Package_P20_IT_Firmware_BIOS_for_MSDOS_Windows

Package_P20_Firmware_BIOS_for_MSDOS_Windows

Version: 20.00.07.00

 

 

I even went through the manual of the MB and tried to find a hint on a model number or smth. 

I am not sure what to take here. I don't want to break stuff. 

 

If any of u has the time to guide me close through it, it would be very helpful. 

 

 

 

On 11/16/2018 at 4:13 PM, trurl said:

And your docker image is corrupt. The usual fix is to delete, recreate it then reinstall containers from Apps - Previous Apps. But I am wondering if you don't have some hardware problem that is leading to these issues.

 

Have you done a memtest?

About this, the memtest86 is running now since over 26h and no error. 

I guess it's fine so far. 

picture attached upload not working on the phone. I will do it in a sec. 

 

Picture link: https://imgur.com/a/jQuXHd6

[Hoopster]

46 minutes ago, DJay said:

Hi again, 

i was searching for a new FW quite a while. 

Unfortunately I don't find any new one for a LSI SAS2008

LSI SAS2008 is the controller chipset.  It is used on many HBAs from many manufacturers, such as LSI 9210-8i/9211-8i, IBM M2015, Dell Perc H200/H310 and others.

 

You should look for the latest firmware for your make and model of HBA.

 

Your motherboard manual will be no help since the HBA is a PCIe add-in card.  Your cache drive(s) are apparently connected to it.  What is it?

 

As @johnnie.black mentioned, you need to search for legacy drivers on on the Broadcom site.  For example I found the 9211-8i 20.00.07.00 firmware there.

 

 

The 20.00.07.00 firmware is available for flashing in Windows or DOS

 

 

20.00.00.00 firmware is available for installation via UEFI, Linux and various other OSes

 

You want to make sure you are flashing in IT mode.

 

IT mode firmware flashing instructions are available in these forums and various other websites.

 

[DJay]

23 minutes ago, Hoopster said:

LSI SAS2008 is the controller chipset.  It is used on many HBAs from many manufacturers, such as LSI 9210-8i/9211-8i, IBM M2015, Dell Perc H200/H310 and others.

 

You should look for the latest firmware for your make and model of HBA.

 

...

 

 

20.00.00.00 firmware is available for installation via UEFI, Linux and various other OSes

 

You want to make sure you are flashing in IT mode.

 

IT mode firmware flashing instructions are available in these forums and various other websites.

 

 

 

I am sorry for all this questions, this is all very new to me.

 

So what confuses me is this: "You should look for the latest firmware for your make and model of HBA."

 

I am reading in parallel these two threads, just to understand a bit more:

https://wiki.unraid.net/index.php/Crossflashing_Controllers#Tools

 

 

But I still feel puzzled. This means, I can just download the "unbranded" broadcom FW and flash it to my SAS2008 chipset.

Correct?

 

The IT mode, if boot support is disabled, will disable looking for boot devices on my harddrives. But if I enable it, I can use it normally again with any other OS. correct?

 

 

I found this:

00:17.0 SATA controller: Intel Corporation 200 Series PCH SATA controller [AHCI mode] (prog-if 01 [AHCI 1.0])
        Subsystem: ASRock Incorporation 200 Series PCH SATA controller [AHCI mode]
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 124
        Region 0: Memory at df348000 (32-bit, non-prefetchable) [size=8K]
        Region 1: Memory at df34c000 (32-bit, non-prefetchable) [size=256]
        Region 2: I/O ports at f090 [size=8]
        Region 3: I/O ports at f080 [size=4]
        Region 4: I/O ports at f060 [size=32]
        Region 5: Memory at df34b000 (32-bit, non-prefetchable) [size=2K]
        Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit-
                Address: fee00278  Data: 0000
        Capabilities: [70] Power Management version 3
                Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot+,D3cold-)
                Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [a8] SATA HBA v1.0 BAR4 Offset=00000004
        Kernel driver in use: ahci
        Kernel modules: ahci

 

If i look in the wiki page, under "SAS2008 chipsets" there is only one entry from intel.

Quote

This cards are rebranded LSI 9240-8i cards. They can be cross-flashed with the 9211-8i firmware.

Applies to

IBM ServeRAID M1015

Intel RS2WC080

Dell Perc H310 dedicated instructions will be included in the wiki later on

Dell Perc H200 dedicated instructions will be included in the wiki later on

Lenovo RAID 500 dedicated instructions will be included in the wiki later on

 

This doesn't make things exactly clearer to me.

I am wondering if I should just leave unraid, since i am not really understanding everything at this point.

 

Again, thanks for the patience.

 

[DJay]

Another update:

 

I deleted the docker image. 

Disabled it in the settings, deleted the image. 

Created a new one. 

 

Then I created a new plex container. 

Same result. It doesn't start and shows the same in the logs. 

[JorgeB]

2 hours ago, DJay said:

It doesn't start and shows the same in the logs. 

Post new diags.

[DJay]

10 hours ago, johnnie.black said:

Post new diags.

unraid-nas-diagnostics-20181118-1150.zip

 

 

Plex Media Server.log

Quote

Nov 18, 2018 12:04:55.966 [0x15393a3ff700] INFO - Plex Media Server v1.14.0.5465-425e4ac90 - Docker Docker Container x86_64 - build: linux-ubuntu-x86_64 ubuntu - GMT 01:00
Nov 18, 2018 12:04:55.966 [0x15393a3ff700] INFO - Linux version: 4.18.17-unRAID, language: C
Nov 18, 2018 12:04:55.966 [0x15393a3ff700] INFO - Processor Intel(R) Pentium(R) CPU G4560 @ 3.50GHz
Nov 18, 2018 12:04:55.967 [0x15393a3ff700] INFO - /usr/lib/plexmediaserver/Plex Media Server
Nov 18, 2018 12:04:55.966 [0x153945c98800] DEBUG - BPQ: [Idle] -> [Starting]
Nov 18, 2018 12:04:55.967 [0x153945c98800] DEBUG - FeatureManager: Using cached data for features list
Nov 18, 2018 12:04:55.967 [0x153945c98800] DEBUG - Opening 20 database sessions to library (com.plexapp.plugins.library), SQLite 3.13.0, threadsafe=1
Nov 18, 2018 12:04:55.969 [0x153945c98800] INFO - SQLITE3:0x10, 283, recovered 99 frames from WAL file /config/Library/Application Support/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db-wal
Nov 18, 2018 12:04:55.969 [0x153945c98800] ERROR - SQLITE3:0x10, 11, database corruption at line 60663 of [fc49f556e4]
Nov 18, 2018 12:04:55.969 [0x153945c98800] ERROR - SQLITE3:0x10, 11, database disk image is malformed
Nov 18, 2018 12:04:55.969 [0x153945c98800] ERROR - Database corruption: sqlite3_statement_backend::prepare: database disk image is malformed for SQL: PRAGMA cache_size=2000
Nov 18, 2018 12:04:55.969 [0x153945c98800] ERROR - Error: Unable to set up server: sqlite3_statement_backend::prepare: database disk image is malformed for SQL: PRAGMA cache_size=2000 (N4soci10soci_errorE)
 

 

[JorgeB]

16 minutes ago, DJay said:

unraid-nas-diagnostics-20181118-1150.zip

 

 

Plex Media Server.log

 

Docker service is starting correctly, if a docker isn't working you need to ask for support on that specific docker support thread.

[DJay]

6 minutes ago, johnnie.black said:

Docker service is starting correctly, if a docker isn't working you need to ask for support on that specific docker support thread.

 

hmm... alright thanks.

 

About the HBA, should I update there anyway or just leave it?

If yes, it wizld be helpful if someone could clarify my Qs from earlier.

 

 

And in the end, I mark the thread just as closed? or solved anyway?

[JorgeB]

You should, but no LSI controller is being detected currently, if you didn't remove it try reseating it.

[DJay]

20 minutes ago, johnnie.black said:

You should, but no LSI controller is being detected currently, if you didn't remove it try reseating it.

How can I do that?

It's all onboard on the mainboard.

[JorgeB]

OK..., some confusion going on here, maybe you posted the wrong diags on the first post? They are form a server with a Gigabyte X58A-UD3R/X58A-UD3R, with an LSI controller, not an Asrock H270M.

[DJay]

Ahm, no, i am using all the time the same machine.

 

Wow you are right. I was comparing logs before with others i found in the forums to understand better.

Maybe they stayed in the clipboard. I was convinced i had the right once. Sorry.

 

WIll remove it right away.

 

What should I do then?

 

Edit: replaced the wrong logs, with the correct zip. Sorry again

[JorgeB]

OK, all previous observations were based on the wrong logs, and like mentioned after you posted the new diags the docker service looks fine so you'll need to ask for help on that docker support thread.