Nov 14 00:34:02 Tower kernel: sd 3:0:6:0: Synchronizing SCSI cache There is, one of the cache devices dropped offline: Unraid-nas-diagnostics-20181116-1456.zip Edited Novemby DJayīut I am wondering if you don't have some hardware problem that is leading to these issues. I like the unraid approach, I would really appreciate help to make this fly. Interestingly the Handbrake and Krusader docker images continue to work. I am out of ideas and I don't feel like setting up everything again. I tried adding into the plex preferences.xml The "Starting Plex Media Server." comes for several minutes until it end as displayed above. sending all processes the KILL signal and exiting. Processing triggers for systemd (229-4ubuntu21.4). # To install udev run: sudo apt-get install udev # # to enable TV Butler support in Plex Media Server. # Please install udev and reinstall Plex Media Server to # # you won't be able to use DVBLogic's TVButler for DVR # # NOTE: Your system does not have udev installed. Setting up plexmediaserver (1.-425e4ac90). Unpacking plexmediaserver (1.-425e4ac90). 7553 files and directories currently installed.) Selecting previously unselected package plexmediaserver. % Total % Received % Xferd Average Speed Time Time Time Current Plex Media Server first run setup complete ![]() ![]() executing container initialization scripts. ensuring user provided files have correct perms.exited 0. making user provided files available at /var/run/s6/etc.exited 0. I shut down the system at some point and after the reboot I see this log in the docker container: Anyway, once all works I would take care of the intel ssd. But before it worked fine with OpenMediaVault. I was already suspecting a HW error on the ssd side. This time on the plus side, (fingers crossed) the ssd didn't "loose" it's FS. So what I did, again formatted the cache drive (samsung ssd) and started from scratch. I was seeing the exact same error message as I have now. Restore didn't work, to be precise, physically it worked but the plex docker didn't start anymore. As stated above as workaround, to test, since this SSD is planned for smth else. So I went ahead and placed the 500GB Samsung SSD into the system. I was able to restore all, but it seemed to be a systematic problem. Next try, quick and fast setup but then I installed the backup plugin from Dynamix and made a backup. Sleep with the Dynamix plugin worked(s) fine. I thought, well i didnt too much yet, so I started again, formatted the ssd and it was running fine as cache. I saw the error message that a unkown FS was on the ssd. ![]() The problems begun after the first (intentional) reboot/ shutdown.Īfter the next start up the intel ssd was not mounted. The intel SSD was the only ssd in the system at the start and was used as cache (newly formatted as XFS). One HDD was free, which I placed into the first array slot. I wanted to use the filled HDDs as unassigned devices until I know all works fine, before I migrate them to XFS. Then I booted unraid, installed the community plugins, unassigned devices plugin and installed the plex docker container. I created a unraid stick, like the normal procedure. Network: bond0: fault-tolerance (active-backup), mtu 1500ġx 500 GB Samsung 840 pro (current workaround)īefore coming to my problem itself, a quick summary what I did. Since I have a little more time now, I decided to give it a shot again. First time I decided against, for time reasons.
0 Comments
Leave a Reply. |