DJay

I had read that before, but thanks anyway Looked for it to understand the different modes. At start I had it to "cache only" but was a but unlucky with my intel ssd always "loosing" it's fs. Now with a samsung ssd all works fine.

I tried that, but as soon as I do this, the server is not reachable anymore. In the Plex settings itself, I didn't find anything to adjust. Therefore I reverted for now. You have an idea what I missed?

Thanks for the support guys! One last Q, if i have appdata on cache only, isn't the config implicitly on the cache drive?

I have news. After coming back from dinner, and I just let it run cont-init.d] 40-chown-files: exited 0. [cont-init.d] 50-plex-update: executing... Atempting to upgrade to: 1.14.0.5465-425e4ac90 At some point i got: Atempting to upgrade to: wget: unable to resolve host address ‘downloads.plex.tv’ And now it's just working even across reboots. I didn't change a thing, just a different docker container. To get the plexpass release I have to add the ":plexpass" to the repo ? Or is this different on this container? Does it work with the version string? That is strange. I don't understand I was trying since last tuesday to get it to run properly...

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='Plex-LinuxServer' --net='host' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -e 'VERSION'='latest' -v '/tmp/':'/transcode':'rw' -v '/mnt/disks/Movies/Movies/':'/media_movies1':'ro' -v '/mnt/disks/Series/Series/':'/media_series1':'ro' -v '/mnt/disks/SeriesMovies2/Series2/':'/media_series2':'ro' -v '/mnt/disks/SeriesMovies2/Plex Recordings/':'/media_plex-recordings':'rw' -v '/mnt/disks/SeriesMovies2/Videos new/':'/media_movies2':'rw' -v '/mnt/user/appdata/plex':'/config':'rw' 'linuxserver/plex' ee03ebce17e68142f480cd78858ab311edbaa955cb5c5ee4bb55c8e3ef39c479 Edit: you were right, the PUID and PGID were stated as PlexIUD and PlexGID. I adapted it. But it didn't show any difference. Edit2: To avoid smth funny with the config, I created a new container from scratch. Added only my folders. After a reboot of unraid i see the same behaviour. Any ideas?

Thanks, I tried to reuse the settings of the original plex docker container (copied the template and changed the repo) in order to not need to map all drives again. I will check if I missed smth there and report back this evening.

Hi guys, I have also some issues with my plex server. After sorting out in a different thread, that my docker is running normally and fine, i am trying to find why my plex server "dies" after a reboot. Before I was using Plex on OMV and all was fine so far. On Unraid, I can install the docker img and then use it normally. All good until I reboot. Once I do that, the docker container will be stuck at: Docker log In the Plex Server Log i found: Plex Server Log (from official plex inc docker) Currently: Details: Repository: linuxserver/plex Server Version#: 1.14.0.5465-425e4ac90 When I do turn off the plex docker container and overwrite the folloing folder, the docker plex server will start normally. /mnt/cache/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/Plug-in Support/Databases But it will break again after a restart. In the docker log i see after the reboot: [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] 10-adduser: executing... usermod: no changes ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io We gratefully accept donations at: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 911 User gid: 911 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-dbus: executing... [cont-init.d] 30-dbus: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 50-plex-update: executing... Atempting to upgrade to: 1.14.0.5465-425e4ac90 And i the web GUI never starts. Do you need anything else? I would seriously appreciate some advice.

Thanks. I just switched to the one of LinuxServer and have the same problem. Will look for the support thread now.

I had tried that But:

I didn't find it. I searched for all plex dockers here and came across this: Where they recommend the plex forums. I certainly would prefer feedback of you guys here, which seem to have deeper know-how (my impression from reads)

alright thanks. I am sorry for the confusion. I myself checking the correct logs and didn't notice I posted the wrong once. I just asked in the plex forums. Will see if they can help, or I try another repo. Even though I doubt another repo will help.

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

How can I do that? It's all onboard on the mainboard.

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?

unraid-nas-diagnostics-20181118-1150.zip Plex Media Server.log

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.

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. 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.

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: and 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. 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

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

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.

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. 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. 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

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: 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