ljm42

I don't think that is accurate. There are really only two reasons to care about where the transcode directory is located: [*]To transcode to ram [*]To make sure transcoding doesn't happen in the docker.img Since: [*]the option to transcode to ram hasn't worked since Plex 0.9.14 [*]and as of Plex 0.9.16.3, the default transcode location is in the /config directory rather than /tmp there is no longer a need for 99.9% of people to specify a transcode directory. Pretty sure that's why LS.IO removed it. For the 0.1% of people that can still think of a reason to change their transcoding directory given the two points above, they could always do it manually: https://lime-technology.com/forum/index.php?topic=40937.msg419495#msg419495

Ah you're right, it must have been the bmc update that changed everything, I did both at the same time. Can definitely see how that would be a problem. I didn't know valid sensors would go n/a (!) I would have expected them to drop to 0 rpm instead. It seems like this would have the same problem as the --ignore n/a setting? I'm happy with the ability to ignore individual sensors. The screenshot looks great! Could we add the current sensor value next to the sensor name? Something like this: CPU_FAN1_1 (192.168.69.50) - 1200.00 RPM CPU_FAN2_2 (192.168.69.50) - N/A That would make it easier to know which sensors to ignore.

Thank you Impressive! Wow!

Can you telnet into your system and type "ipmi-sensors", then copy/paste the output here?

The plugin is working great. I do have a request though After my last bios update, ipmi-sensors added a bunch of useless entries (everything below with a reading of N/A, plus CPU_AP1 temp): root@Tower:/# ipmi-sensors ID | Name | Type | Reading | Units | Event 3 | ATX+5VSB | Voltage | 4.95 | V | 'OK' 4 | +3VSB | Voltage | 3.44 | V | 'OK' 5 | Vcore1 | Voltage | 1.79 | V | 'OK' 6 | Vcore2 | Voltage | N/A | V | N/A 7 | VCCM1 | Voltage | 1.51 | V | 'OK' 8 | VCCM2 | Voltage | N/A | V | N/A 9 | +1.10_PCH | Voltage | 1.07 | V | 'OK' 10 | +1.50_PCH | Voltage | N/A | V | N/A 11 | CPU VTT1 | Voltage | 1.00 | V | 'OK' 12 | CPU VTT2 | Voltage | N/A | V | N/A 13 | BAT | Voltage | 3.26 | V | 'OK' 14 | +3V | Voltage | 3.38 | V | 'OK' 15 | +5V | Voltage | 5.10 | V | 'OK' 16 | +12V | Voltage | 12.00 | V | 'OK' 17 | CPU_FAN1_1 | Fan | 1200.00 | RPM | 'OK' 18 | CPU_FAN2_1 | Fan | N/A | RPM | N/A 19 | REAR_FAN1 | Fan | 500.00 | RPM | 'OK' 20 | REAR_FAN2 | Fan | N/A | RPM | N/A 21 | FRNT_FAN1 | Fan | 500.00 | RPM | 'OK' 22 | FRNT_FAN2 | Fan | N/A | RPM | N/A 23 | FRNT_FAN3 | Fan | N/A | RPM | N/A 24 | FRNT_FAN4 | Fan | N/A | RPM | N/A 25 | CPU_FAN1_2 | Fan | N/A | RPM | N/A 26 | CPU_FAN2_2 | Fan | N/A | RPM | N/A 27 | MB Temperature | Temperature | 39.00 | C | 'OK' 28 | TR1 Temperature | Temperature | N/A | C | N/A 30 | CPU_BSP1 Temp | Temperature | 40.00 | C | 'OK' 31 | CPU_AP1 Temp | Temperature | 0.00 | C | 'OK' This clutters the readings and all the dropdowns with useless information. Adding "--ignore-not-available-sensors" to the command gets rid of everything N/A, and "-R 31" gets rid of the useless temperature: root@Tower:/# /usr/sbin/ipmi-sensors --ignore-not-available-sensors -R 31 ID | Name | Type | Reading | Units | Event 3 | ATX+5VSB | Voltage | 4.95 | V | 'OK' 4 | +3VSB | Voltage | 3.44 | V | 'OK' 5 | Vcore1 | Voltage | 1.79 | V | 'OK' 7 | VCCM1 | Voltage | 1.51 | V | 'OK' 9 | +1.10_PCH | Voltage | 1.07 | V | 'OK' 11 | CPU VTT1 | Voltage | 1.01 | V | 'OK' 13 | BAT | Voltage | 3.26 | V | 'OK' 14 | +3V | Voltage | 3.38 | V | 'OK' 15 | +5V | Voltage | 5.10 | V | 'OK' 16 | +12V | Voltage | 12.00 | V | 'OK' 17 | CPU_FAN1_1 | Fan | 1200.00 | RPM | 'OK' 19 | REAR_FAN1 | Fan | 500.00 | RPM | 'OK' 21 | FRNT_FAN1 | Fan | 500.00 | RPM | 'OK' 27 | MB Temperature | Temperature | 39.00 | C | 'OK' 30 | CPU_BSP1 Temp | Temperature | 40.00 | C | 'OK' So I was wondering if we could add an IGNORE entry to ipmi.cfg, for me it would look like this: IGNORE="--ignore-not-available-sensors -R 31" and then every time you call ipmi-sensors you would add the $IGNORE variable to the call. I'd be ok if I had to add/edit that line in ipmi.cfg manually. Or if you think everyone would benefit from --ignore-not-available-sensors (I think they would), then include that by default everywhere, meaning my file ipmi.cfg would just have: IGNORE="-R 31" What do you think?

So does that mean that there is no way to set the transcode directory to memory (i.e. /tmp)? I have been debating switching from ESXi to bare metal, and that is something I'd love to keep since it reduces wear on my SSDs... It's forced by plex not by us. We just adapted our config lonix would it be possible to reinstate this mapping? From what I can see this hasn't been forced by plex - as there is still a setting within plex to set a custom location for transcoding. However without this mapping I am no longer able to use the setting within Plex itself to use unRAID root file system which is in the RAM. I have a large quantity of RAM (as in sure some others do too) and this change has essentially crippled the transcoding feature for me unless I'm misunderstanding something, if you can still tell Plex to transcode to a custom location, just add the appropriate mapping back in yourself (something like /transcode mapped to /tmp/plex) Like any other container, you can always add as many paths as your system requires without any changes from the template authors That's how I thought it worked too, but despite setting a mapping myself of /transcode/:/tmp/ and then setting it to /transcode/ in plex but it doesn't work anymore for some reason. If I try to transcode something it just doesn't play. I had it working perfectly prior to the recent change which is why I thought something had changed in the container itself. If I remove the custom location entirely in plex, transcoding works - albeit very slowly as my disk isn't very quick. When I had it running in RAM it was very quick which is why I'm so keen to try and get it working again, how it was before Transcoding to RAM has not worked since Plex version 0.9.14, which was released last November. This was a change that Plex made, and it affected all Dockers / plugins / installs. There isn't anything LS.IO can do to bring it back. Here is a post describing how to set your transcode directory manually, with a caveat that you should avoid transcoding to RAM: https://lime-technology.com/forum/index.php?topic=40937.msg419495#msg419495

Found the fix! In ipmi_options.php, change a few is_file() commands to file_exists(): $mod = (file_exists('/dev/ipmi0') || file_exists('/dev/ipmi/0') || file_exists('/dev/ipmidev/0')); Not sure why, but is_file() doesn't like this file: root@Tower:/# ls -al /dev/ipmi* crw------- 1 root root 247, 0 Apr 10 16:04 /dev/ipmi0 Thank you very much! I'm not sure I would have been able to figure that out until I got my new board. I'll push an update. Glad I could help! But mainly, thank *you* for this plugin!

Found the fix! In ipmi_options.php, change a few is_file() commands to file_exists(): $mod = (file_exists('/dev/ipmi0') || file_exists('/dev/ipmi/0') || file_exists('/dev/ipmidev/0')); Not sure why, but is_file() doesn't like this file: root@Tower:/# ls -al /dev/ipmi* crw------- 1 root root 247, 0 Apr 10 16:04 /dev/ipmi0

Thanks, that sounds perfect to me I wouldn't mind if it spun the drives up monthly or even weekly to do the full test, but right now I'm running it daily and would rather they not spin up. I suppose another option would be for me to run it less often

Wow, that is an impresive change log! I upgraded both my main 6.1.9 system and my test 6.2b21 VM. The VM makes a network connection and works perfectly (well, I haven't tried the fan control yet), but the local install has problems. No sensors are available in the Display Settings dropdown and the fan says "Your board is not currently supported", although the Readings and Event Log do work. On the local system can you tell me if any of these files exist? /dev/ipmi0, /dev/ipmi/0 or /dev/ipmidev/0 root@Tower:/dev# ls /dev/ipmi* /dev/ipmi0

Wow, that is an impresive change log! I upgraded both my main 6.1.9 system and my test 6.2b21 VM. The VM makes a network connection and works perfectly (well, I haven't tried the fan control yet), but the local install has problems. No sensors are available in the Display Settings dropdown and the fan says "Your board is not currently supported", although the Readings and Event Log do work.

Very nice! I'd like to request another feature - can we have an option to disable any checks that cause disks to spin up? I like that this can run on a regular basis, but I'd rather not spin my drives up unnecessarily. Thanks!

How about warning if "Share Settings -> Min Free Space" is zero? This will help prevent confusing "No space left on device" errors if your cache drive is full but the array is not: https://lime-technology.com/forum/index.php?topic=48847.msg468604#msg468604

I hope you don't mean your unraid server is available directly on the internet? There are lots of threads here talking about how that is a bad idea. Regarding Plex specifically, for initial setup Plex requires that you access the Plex server using: http://ipaddress:32400/web from a computer that is on the same subnet as the Plex server. Once the server has been setup you should be able to manage it from any ip address. Also see: https://support.plex.tv/hc/en-us/articles/204604227-Why-can-t-the-Plex-app-find-or-connect-to-my-Plex-Media-Server- Thanks for the quick reply. They were always on the same subnet. My router groups my DHCP and Static IP's on the same subnet. But that didn't help. I was always able to hit the GUI but I was never able to see the Server settings page. I went and temporarily changed this unRaid box over to a DHCP IP and then was able to enable "Remote Access" on the Plex side. I then moved back over to one of my static IP's and can still edit my server via LAN and WAN. Your suggestion made my brain think outside the box for a work around. Thanks again! I also appreciate the security concern. This box is firewalled/proxied/and has VPN. There is nothing tied to me personally anyway on my Plex box. Very cool, glad you were able to get it working

I hope you don't mean your unraid server is available directly on the internet? There are lots of threads here talking about how that is a bad idea. Regarding Plex specifically, for initial setup Plex requires that you access the Plex server using: http://ipaddress:32400/web from a computer that is on the same subnet as the Plex server. Once the server has been setup you should be able to manage it from any ip address. Also see: https://support.plex.tv/hc/en-us/articles/204604227-Why-can-t-the-Plex-app-find-or-connect-to-my-Plex-Media-Server-

Agree 100%, this sort of diagnostic could prevent a lot of problems. Thanks for starting this Squid!

That sounds incredible dmacias, I really appreciate the work you are putting into this for us!

Thanks dmacias - I can confirm the 2016.04.28 version installs without any delays in an unRAID 6.2b21 VM. Works great! The only remaining VM issues I see are these repeated errors in the syslog: Apr 29 22:33:26 TowerVM kernel: IPMI System Interface driver. Apr 29 22:33:26 TowerVM kernel: ipmi_si: Unable to find any System Interface(s) Apr 29 22:33:37 TowerVM kernel: IPMI System Interface driver. Apr 29 22:33:37 TowerVM kernel: ipmi_si: Unable to find any System Interface(s) and that the readings are missing from the footer.

I had the same issue until I upgraded my bios. See my comment one page back.

Where aro those manuals? Are you referring to the CP site or are there any other? https://support.code42.com/CrashPlan/4 Thankyou Gus The OP is the "Original Post", i.e. the first post in this thread. The Q&A portion of that post contains a section titled "Q) Can another computer backup to my unRAID array?" which has the basics to get you started and then links you over to specific pages on the CrashPlan site for more details.

check out the OP (i.e. the "Original Post", the first post in this thread)

I would humbly suggest that the first post in this thread be updated with the above information. The current information mentions the /config and /mnt volumes (only the former seems to exist) with nothing on the others. I did not feel comfortable even starting the container until I ran across this post that describes each of the volumes. Thank you, Leifgg! Interesting, I didn't realize those default paths had been added to the XML. I'll suggest some updated text for the OP to gfjardim.

Please read the Q&A in the OP. You need to configure CrashPlan to use the /backup directory you passed in.

That sounds great! If you're looking for ideas I'd really like to see plugins take advantage of this new functionality that was added to 6.2b21: bonienl explained it here: https://lime-technology.com/forum/index.php?topic=47944.msg459607#msg459607

Cool, at least we are seeing the same things Do we have the option of not loading "modprobe ipmi_si" for network installs?