philroussel

Just a quick follow up. After failing using Docker for Plex (unable to find the proper path for the Plex libraries), I have decided to install a dual 250 GB SSD as cache and to have Plex installed on it. On the bright sight side, Plex restarts automatically after a reboot, the main problem have been the necessity to rebuilt the whole Plex database. But now the Plex database is protected against loss by a Raid1 cache (if I understand the documentation right).

PhAzE, I followed the instructions by the letter, and still does not work. I am sorry

Before doing things with unattended (bad) consequences, please tell me how to do that: - Turn off auto mount of the array Don't be afraid to treat me like a retarded 5 years old

>>Can you please post the output of mount at the console? ********* root@Tower:/# mount proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) tmpfs on /var/log type tmpfs (rw,size=128m,mode=0755) /dev/sdb1 on /boot type vfat (rw,noatime,nodiratime,umask=0,shortname=mixed) /mnt on /mnt type none (rw,bind) /dev/md1 on /mnt/disk1 type xfs (rw,noatime,nodiratime) /dev/md2 on /mnt/disk2 type xfs (rw,noatime,nodiratime) /dev/md3 on /mnt/disk3 type xfs (rw,noatime,nodiratime) /dev/md4 on /mnt/disk4 type xfs (rw,noatime,nodiratime) /dev/md5 on /mnt/disk5 type xfs (rw,noatime,nodiratime) /dev/md6 on /mnt/disk6 type xfs (rw,noatime,nodiratime) /dev/md7 on /mnt/disk7 type xfs (rw,noatime,nodiratime) /dev/md8 on /mnt/disk8 type xfs (rw,noatime,nodiratime) /dev/md9 on /mnt/disk9 type xfs (rw,noatime,nodiratime) /dev/sdn1 on /mnt/cache type btrfs (rw,noatime,nodiratime) shfs on /mnt/user0 type fuse.shfs (rw,nosuid,nodev,noatime,allow_other) shfs on /mnt/user type fuse.shfs (rw,nosuid,nodev,noatime,allow_other) /dev/sdj1 on /mnt/appdisk type xfs (rw,noatime,nodiratime,discard)

Let's get back on tracks... I need a reliable way to get PLEX back and running after a power outage, without me being around. I see currently three possibilities to get this solved: - A modification in PhAzE brilliant plugin - Some command lines to be inserted in some files being run at the end of the boot sequence - Switching to Docker (still to be seen if this would solve the issue)

If this helps... root@Tower:/mnt/disk1# cd / root@Tower:/# ls mnt appdisk/ disk1/ disk3/ disk5/ disk7/ disk9/ user/ cache/ disk2/ disk4/ disk6/ disk8/ disks/ user0/ My system was built from scratch over the years exclusively for hosting a Plex Media Server. And it works remarkably well. With my new internet provider (Spectrum replacing TWC) with upstream at 23 Mbps, I can deliver from San Diego to my kids in Texas, NY and Washington DC. So I will explore other routes before starting breaking up such a remarkable application.

>>I would recommend setting "show storage memory usage" to 'no' Done >>Is /mnt/appdisk a share on your cache drive or array? No, it is a PLEX dedicated 240 GB SSD (see HC) >>When you run the app as user 'nobody', does it have the same problem? It seems that when it initially starts it can't read the Plex configuration XML file and starts fresh. Then when you restart the plugin it corrects the permissions. Done. Then reboot. No change.

PhAzE, I am running the latest versions of your plugin and UnRAID (always). Plug-ins in packages are: root@Tower:/boot/packages# pwd /boot/packages root@Tower:/boot/packages# ls -lt total 14304 -rwxrwxrwx 1 root root 14596988 Oct 11 2015 perl-5.18.1-x86_64-1.txz* -rwxrwxrwx 1 root root 41768 May 8 2010 inotify-tools-3.14-i486-1.txz* >>When it starts up, what url are you using to connect to when you see the welcome page? I don't know how to answer this question and where to look at. >>Also can you post an image of your settings page so i can check out where you're pointing the directories to? 3 screen-shots in attachment Thank you a thousand for not letting me down. You can send me a PM to avoid filling your thread with my garbage.

PhAze, First let me congratulate you for you excellent work maintaining the plugins, specially Plex. I still don't see any reason to look toward Docker, which is good since I am a bit lazy, and when not broken, don't fix it. I have an issue though. Plex is my sole plugin. When I have to reboot the server, everything restarts fine, except Plex which displays the standard welcome page, not directing me to the PMS of the server. The remedy is simple, I have to go to Settings> PlexMediaServer>Stop then Start (on UnRAID GUI). How can I fix this? Even by inserting some command line in some files.... The matter is more important that it seems, as I don't know how long I will be around to maintain the family's PMS (small cell cancer, stage 4). Thank you for your help

Thank you PhAzE. I did copy the old version along with the new version in /boot/packages on the flash key. Renamed the old one with the new name, removed the new version, I have never found the md5 file so didn't do anything on this, then rebooted . I worked. This fooled the autoloading of the new version. Still I would wish that it was more simple and that the auto-install of new version could be disabled. Any way, you earned your beer Thanks. PS: it just proved that the new Plex version (0.9.12) is buggy. The old version (0.9.11.16) works fine.

I have installed the new Plex Media Server version yesterday (version 0.9.12.0) and it seems that there is a bug in the transcoder or whatever engine Plex uses to play movies. My latest Blu-Ray movie, Unbroken, ripped with Handbrake, is very pixelated in motion sequences. It's just an example, same thing for all my movies. I have no doubt there will be a patch in the future. Here comes my question: I am running the latest unRAID version 6.0.beta15, and the Plex plugin ( PhAzE) is updated automatically. How do I reverse to the previous Plex version? I have tried to re-install the previous version on the USB boot key in /boot/packages , but the new version automatically downloads and replaces it at boot.

Thank you for replying to the question I never dare to ask. I was afraid to be the dumb idiot of the village But thinking twice about it... This should be explained as a front page in the UnRaid functionality. And THERE SHOULD BE A DAMN MANUAL on about how to install container with the GUI, and description of the use of the various fields (undocumented). I was promised an up-to-date documentation 3 months ago by jonp, and obviously this has never happened until now. So I installed the Plex plugin

Thank you for not being dismissive or arrogant. I will put the switch toward V 6.0 for another time in the future, as I read that V 6.0 is ONLY 64 bits compatible and does not run 32 bits apps (like the current Plex non-plexpass version). Back to stable and documented V 5.0.5 now.

No Matt, you are not alone... I share the pain. The GUI in Unraid 6.0 B10a does not match the posted pics. I have tried to enter the command line, but I have a message "--net: invalid net mode: invalid --net: tower". I have tried to use the GUI, but could not find any explanation nor tutorial on how to use it.

Thank you guys for your posts. I did some research and went to the conclusion that XBMC and PleXBMC were the way to go. And there is no emergency to scrap everything for the sake of going 64 bits. I installed XBMC/PleXBMC and it works: I have DTS, 5.1 and faster loading. Still some minor little glitches, but, I consider this is it! To make life of other FireTV users easier... The solution for making FireTV working the way it should with your Home Theater as suggested in previous posts is XBMC and PleXBMC: XBMC (now renamed KODI) is a software which installs on the client side, ie FireTV. That means that the data received from the Media server is treated by a client or receiver (FireTV) executing a software program (XBMC) prior to be displayed on your TV and getting DTS sound from your AVR. Thus there is NO INSTALL of XBMC on your media server, just on the FireTV. To install XBMC follow the instructions there: http://wiki.xbmc.org/index.php?title=Amazon_Fire_TV This will install XBMC on you FireTV, but to use this program through the PLEX interface, you need to install an add-on: PleXBMC. http://wiki.xbmc.org/?title=Add-on:PleXBMC Life is good

No, Unraid 5.x is 32 bit only. Unraid 6 is 64bit only. :( That's what I feared... This being said, does it worth to scrap a stable unRAID v5 to install the beta v6 just to get 64bit Plex? Does the 64bit version of Plex makes a noticeable difference? Please let me know your findings.

Does that mean I can install Plex new 64bit version on my UnRAID 5.05 instead of the 32 bit? And would be the advantage of doing so? Any down side? Thanks for any suggestion. BTW: I am using Plex with Amazon FireTV box and app. It works but has some severe limitations. The interface is great, but sound is just 2.0 (no DTS, no 5.1,...) the fast forward or rewind work more or less sporadically, some stutter... Any better solution?

Rebooting the router and switches? Been there, done that. No change. I have had the same issue with WiFi connection, that's why I have decided to go hard wired. The WiFi connection rules out the switches as the source of the problem, because they weren't in use in this configuration. The router is a TP-Link WDR3600 N600 dual band with the latest firmware (decent hardware).

Here is attached my syslog from tonight. The whole period where I was watching a movie through a hard wired 1GB connection I had the msg "Tower last message repeated 2 times" every 2 minutes. Just don't know what this is. Every once in a while the movie seems to jump or skip a few frames for no reason. I have used a KdLink and a Fire TV device with the same result. I have re-installed recently my whole system with just Dynamix and Plex, to get rid of any collateral issue. But in vain. My ethernet card is an Intel e1000 and the driver is an ancient Intel® PRO/1000 Network Driver - version 7.3.21-k8-NAPI (copyright 2006!). I am wondering if this could be the cause of this inconvenience. Other hardware possibility: the network goes through 1 router and 2 switches, but it has a very light load. syslog.txt

+1 It seems that the Intel network driver is quite old and I have some slight but noticeable issues with the data flow using my unRAID server as a video server. In my case, just keep the drivers up-to-date and I would be an happy (pay) camper. Virtualization is just another animal, for which I don't have currently the use.

PROBLEM SOLVED !!!! ;D Actually, when putting back the motherboard to default safe values, it changed the SATA type and SATA IDE values. The correct values must be SATA TYPE ---> AHCI SATA IDE combined mode ---> DISABLED All of a sudden the drives hdX became sdX. And everything went back to normal as described in this one-of-its-kind tutorial. Again, thank you Jumperalex for such a great piece of work!

First, thank you for not treating me as a moron I am running a very standard UnRAID v5.0.5 on a decent hardware CPU AMD A8-5500 APU on MB Biostar A85W with 8 GB RAM (I know it is not relevant but just to say I am doing it by the book). I am trying to install a brand new PNY 120 GB SSD XR8. I haven't done any firmware modification (yet). Here's what I get after a reboot. The SSD is recognized, even partially /dev/hdh1 Array Disk Status Status Disk Mounted Device Model/Serial Temp Reads Writes Errors Size Used %Used Free OK parity /dev/hdg TOSHIBA_DT01ACA300_23DES3ZGS 39°C 87 32 OK /dev/md1 /mnt/disk1 /dev/sdc TOSHIBA_DT01ACA200_13EDSNWGS 35°C 749 10 2.00T 1.45T 73% 553.00G OK /dev/md2 /mnt/disk2 /dev/hde TOSHIBA_DT01ACA300_23DES55GS 37°C 6449 10 3.00T 2.25T 76% 746.17G OK /dev/md3 /mnt/disk3 /dev/sde TOSHIBA_DT01ACA200_13E7689AS 39°C 856 10 2.00T 1.26T 64% 736.15G OK /dev/md4 /mnt/disk4 /dev/sdd TOSHIBA_DT01ACA200_23JMGDZAS 38°C 1246 9 2.00T 1.20T 60% 803.19G OK /dev/md5 /mnt/disk5 /dev/sdb TOSHIBA_DT01ACA200_Y2P4X60AS 37°C 984 10 2.00T 1.39T 70% 613.34G Total: 11.00T 7.55T 68% 3.45T UNRAID Drive Device Model/Serial Mounted File System Size Used %Used Free /dev/sda1 usb-Corsair_Flash_Voyager_4cb768f2227108-0:0 /boot 8.07G 235.23M 3% 7.83G Cache Drive Device Model/Serial Mounted File System Temp Size Used %Used Free /dev/hdf1 /mnt/cache 34°C 1.00T 8.26G 1% 991.92G Drive Partitions - Not In Protected Array Device Model/Serial Mounted File System Temp Size Used %Used Free /dev/hdf WDC_WD10EADS-11M2B1_WD-WCAV54129425 34°C 1.00T /dev/hdh SSD2SC120G3LC709B121-460I_PNY14130000471460570 30064771072°C 120.03G /dev/hdh1 30064771072°C I must have screwed up somewhere, but frankly I don't see where. I have started over the whole section 1, including erasing the partition before creating a new one. Same result.

First I would like to thank jumperalex for his remarkable tutorial. At the end of paragraph 1c, the process is validated by the following command: root@Tower:/dev/disk/by-id# fsck -N /dev/hd* fsck from util-linux-ng 2.17.2 [/sbin/fsck.ext2 (1) -- /dev/hde] fsck.ext2 /dev/hde [/sbin/fsck.reiserfs (2) -- /dev/hde1] fsck.reiserfs /dev/hde1 [/sbin/fsck.ext2 (3) -- /dev/hdf] fsck.ext2 /dev/hdf [/sbin/fsck.reiserfs (4) -- /dev/hdf1] fsck.reiserfs /dev/hdf1 [/sbin/fsck.ext2 (5) -- /dev/hdg] fsck.ext2 /dev/hdg [/sbin/fsck.reiserfs (6) -- /dev/hdg1] fsck.reiserfs /dev/hdg1 [/sbin/fsck.ext4 (7) -- /dev/hdh] fsck.ext4 /dev/hdh [/sbin/fsck.ext4 ( -- /dev/hdh1] fsck.ext4 /dev/hdh1 Everything looks normal so far, the SSD being /dev/hdh. But the next step shows the SSD device (first line), but not -part1 [quote]root@Tower:/dev/disk/by-id# ls ata-SSD2SC120G3LC709B121-460I_PNY14130000471460570@ ata-TOSHIBA_DT01ACA200_13E7689AS@ ata-TOSHIBA_DT01ACA200_13E7689AS-part1@ ata-TOSHIBA_DT01ACA200_13EDSNWGS@ ata-TOSHIBA_DT01ACA200_13EDSNWGS-part1@ ata-TOSHIBA_DT01ACA200_23JMGDZAS@ ata-TOSHIBA_DT01ACA200_23JMGDZAS-part1@ ata-TOSHIBA_DT01ACA200_Y2P4X60AS@ ata-TOSHIBA_DT01ACA200_Y2P4X60AS-part1@ ata-TOSHIBA_DT01ACA300_23DES3ZGS@ ata-TOSHIBA_DT01ACA300_23DES55GS@ ata-WDC_WD10EADS-11M2B1_WD-WCAV54129425@ scsi-SATA_TOSHIBA_DT01ACA_13E7689AS@ scsi-SATA_TOSHIBA_DT01ACA_13E7689AS-part1@ scsi-SATA_TOSHIBA_DT01ACA_13EDSNWGS@ scsi-SATA_TOSHIBA_DT01ACA_13EDSNWGS-part1@ scsi-SATA_TOSHIBA_DT01ACA_23JMGDZAS@ scsi-SATA_TOSHIBA_DT01ACA_23JMGDZAS-part1@ scsi-SATA_TOSHIBA_DT01ACA_Y2P4X60AS@ scsi-SATA_TOSHIBA_DT01ACA_Y2P4X60AS-part1@ usb-Corsair_Flash_Voyager_4cb768f2227108-0:0@ usb-Corsair_Flash_Voyager_4cb768f2227108-0:0-part1@ wwn-0x5000039ff3c23b52@ wwn-0x5000039ff3c23b52-part1@ wwn-0x5000039ff3c34620@ wwn-0x5000039ff3c34620-part1@ wwn-0x5000039ff3c5cd52@ wwn-0x5000039ff3c5cd52-part1@ wwn-0x5000039ff3c8d92d@ wwn-0x5000039ff3c8d92d-part1@ Of course, I tried the rest of the tutorial, but the mount cmd shows that the ext4 disk is not present root@Tower:/dev/disk/by-id# mount proc on /proc type proc (rw) sysfs on /sys type sysfs (rw) tmpfs on /var/log type tmpfs (rw,size=128m) /dev/sda1 on /boot type vfat (rw,noatime,nodiratime,umask=0,shortname=mixed) /dev/md1 on /mnt/disk1 type reiserfs (rw,noatime,nodiratime,user_xattr,acl) /dev/md2 on /mnt/disk2 type reiserfs (rw,noatime,nodiratime,user_xattr,acl) /dev/md3 on /mnt/disk3 type reiserfs (rw,noatime,nodiratime,user_xattr,acl) /dev/md4 on /mnt/disk4 type reiserfs (rw,noatime,nodiratime,user_xattr,acl) /dev/md5 on /mnt/disk5 type reiserfs (rw,noatime,nodiratime,user_xattr,acl) /dev/hdf1 on /mnt/cache type reiserfs (rw,noatime,nodiratime,user_xattr,acl) shfs on /mnt/user0 type fuse.shfs (rw,nosuid,nodev,noatime,allow_other) shfs on /mnt/user type fuse.shfs (rw,nosuid,nodev,noatime,allow_other) Where did I go wrong? ls_by-id.txt

Here is my syslog attached. I should have done that in the first place, sorry... syslog.txt

Description of my setup System: Gigabyte Technology Co., Ltd. - GA-MA785GM-US2H CPU: AMD Athlon 64 X2 Dual Core 6000+ - 3 GHz Cache: 128 kB, 128 kB, 1024 kB Memory: 8192 MB (max. 16 GB) Network: eth0: 1000Mb/s - Full Duplex TOSHIBA_DT01ACA300_23DES3ZGS (sde) 30 °C 3 TB TOSHIBA_DT01ACA200_13EDSNWGS (sdb) 28 °C 2 TB TOSHIBA_DT01ACA300_23DES55GS (sdf) 29 °C 3 TB TOSHIBA_DT01ACA200_13E7689AS (sdg) 30 °C 2 TB TOSHIBA_DT01ACA200_23JMGDZAS (sdd) 30 °C 2 TB TOSHIBA_DT01ACA200_Y2P4X60AS (sdc) 29 °C 2 TB System running Unraid v5.05 with Dynamix (great tool BTW) and used as a video server. I am experiencing the following: After a cycle of sleeps, the video stream shows some signs that frames drop out. The solution has been so far to reboot the server every 2 or 3 days. That seems to indicate that the issue does not come from the rest of the infrastructure but from my server. The syslog indicates that e1000: Intel® PRO/1000 Network Driver - version 7.3.21-k8-NAPI But I found that a new e1000 driver (v8.) exists, and there was a post saying that the Unraid v5 was now using a new e1000e driver. My question(s): I am right to think the driver is the culprit? How do I get the system to use a new driver for the NIC Intel e1000? Should I just wait for the latest v5 release praying that the problem would be solved? If you are kind enough to answer and help, please explain in details the commands .