ich777 Posted July 6 Author Share Posted July 6 2 hours ago, meunraid said: anyone having python, pip issues after installing Unraid 7 grab this install: https://slackware.uk/slackware/slackware64-current/slackware64/n/openssl11-1.1.1w-x86_64-1.txz and drop it in /boot/extra and reboot. Please use Nerd Tools instead to install Python. Quote Link to comment
meunraid Posted July 6 Share Posted July 6 (edited) Nerd Tools doesnt work either, I am guessing openssl11 is missing from Unraid 7. Other applications are broken as well that require older openssl. Troubleshooting this lead me to this thread and un-get which is perfect for what I need. Thanks for creating it! Edited July 6 by meunraid 1 Quote Link to comment
bmartino1 Posted July 9 Share Posted July 9 Mainly had it installed for compabilty and use with other plugins as there notes at boot asked for this plugin or python to be avaible for there code to run. Not sure if this is needed anymore... Currently, on Beta 7. Plugin saying Incompatible. I can use a LTS version 6 unraid and copy the python plugin folder to beta 7 to update... when Unraid v7 release will this get an update to use python3 or should we use Slackware packages and a venv? Reviewing the log: Quote Jul 4 19:48:59 BMM-Unraid plugin-manager: skipping: /boot/config/plugins/python3/images/Python3.png already exists Jul 4 19:48:59 BMM-Unraid plugin-manager: running: 'anonymous' Jul 4 19:48:59 BMM-Unraid plugin-manager: Python3.plg installed Jul 4 19:48:59 BMM-Unraid rc.local: plugin: installing: Python3.plg Jul 4 19:48:59 BMM-Unraid rc.local: Executing hook script: pre_plugin_checks Jul 4 19:48:59 BMM-Unraid rc.local: +============================================================================== Jul 4 19:48:59 BMM-Unraid rc.local: | Installing new package /boot/config/plugins/python3/packages/python3-3.9.16-x86_64-1.txz Jul 4 19:48:59 BMM-Unraid rc.local: +============================================================================== Jul 4 19:48:59 BMM-Unraid rc.local: Verifying package python3-3.9.16-x86_64-1.txz. Jul 4 19:48:59 BMM-Unraid rc.local: Installing package python3-3.9.16-x86_64-1.txz: Jul 4 19:48:59 BMM-Unraid rc.local: PACKAGE DESCRIPTION: Jul 4 19:48:59 BMM-Unraid rc.local: # python3 (object-oriented interpreted programming language v3) Jul 4 19:48:59 BMM-Unraid rc.local: # Jul 4 19:48:59 BMM-Unraid rc.local: # Python is an interpreted, interactive, object-oriented programming Jul 4 19:48:59 BMM-Unraid rc.local: # language that combines remarkable power with very clear syntax. Jul 4 19:48:59 BMM-Unraid rc.local: # This is a new version of the language that is incompatible with the Jul 4 19:48:59 BMM-Unraid rc.local: # 2.x line of releases. The language is mostly the same, but many Jul 4 19:48:59 BMM-Unraid rc.local: # details, especially how built-in objects like dictionaries and strings Jul 4 19:48:59 BMM-Unraid rc.local: # work, have changed considerably, and a lot of deprecated features have Jul 4 19:48:59 BMM-Unraid rc.local: # finally been removed. Also, the standard library has been reorganized Jul 4 19:48:59 BMM-Unraid rc.local: # in a few prominent places. Jul 4 19:48:59 BMM-Unraid rc.local: # Jul 4 19:48:59 BMM-Unraid rc.local: Executing install script for python3-3.9.16-x86_64-1.txz. Jul 4 19:48:59 BMM-Unraid rc.local: Package python3-3.9.16-x86_64-1.txz installed. Jul 4 19:48:59 BMM-Unraid rc.local: +============================================================================== Jul 4 19:48:59 BMM-Unraid rc.local: | Installing new package /boot/config/plugins/python3/packages/python-pip-22.2.2-x86_64-1.txz Jul 4 19:48:59 BMM-Unraid rc.local: +============================================================================== Jul 4 19:48:59 BMM-Unraid rc.local: Verifying package python-pip-22.2.2-x86_64-1.txz. Jul 4 19:48:59 BMM-Unraid rc.local: Installing package python-pip-22.2.2-x86_64-1.txz: Jul 4 19:48:59 BMM-Unraid rc.local: PACKAGE DESCRIPTION: Jul 4 19:48:59 BMM-Unraid rc.local: # python-pip (tool for installing Python packages) Jul 4 19:48:59 BMM-Unraid rc.local: # Jul 4 19:48:59 BMM-Unraid rc.local: # The PyPA recommended tool for installing Python packages. Jul 4 19:48:59 BMM-Unraid rc.local: # Jul 4 19:48:59 BMM-Unraid rc.local: # Homepage: https://pip.pypa.io/ Jul 4 19:48:59 BMM-Unraid rc.local: # Jul 4 19:48:59 BMM-Unraid rc.local: Package python-pip-22.2.2-x86_64-1.txz installed. Jul 4 19:48:59 BMM-Unraid rc.local: +============================================================================== Jul 4 19:48:59 BMM-Unraid rc.local: | Installing new package /boot/config/plugins/python3/packages/python-setuptools-65.1.1-x86_64-1.txz Jul 4 19:48:59 BMM-Unraid rc.local: +============================================================================== Jul 4 19:48:59 BMM-Unraid rc.local: Verifying package python-setuptools-65.1.1-x86_64-1.txz. Jul 4 19:48:59 BMM-Unraid rc.local: Installing package python-setuptools-65.1.1-x86_64-1.txz: Jul 4 19:48:59 BMM-Unraid rc.local: PACKAGE DESCRIPTION: Jul 4 19:48:59 BMM-Unraid rc.local: # python-setuptools (a collection of enhancements to Python distutils) Jul 4 19:48:59 BMM-Unraid rc.local: # Jul 4 19:48:59 BMM-Unraid rc.local: # This is a full featured library designed to facilitate packaging Jul 4 19:48:59 BMM-Unraid rc.local: # Python projects. Features include Python package and module Jul 4 19:48:59 BMM-Unraid rc.local: # definitions, distribution package metadata, test hooks, project Jul 4 19:48:59 BMM-Unraid rc.local: # installation, and platform-specific details. Jul 4 19:48:59 BMM-Unraid rc.local: # Jul 4 19:48:59 BMM-Unraid rc.local: # Homepage: https://pypi.python.org/pypi/setuptools Jul 4 19:48:59 BMM-Unraid rc.local: # Jul 4 19:48:59 BMM-Unraid rc.local: Package python-setuptools-65.1.1-x86_64-1.txz installed. Jul 4 19:48:59 BMM-Unraid rc.local: ----------------------------------------------------------- Jul 4 19:48:59 BMM-Unraid rc.local: python3 has been installed. Jul 4 19:48:59 BMM-Unraid rc.local: Copyright 2022, dlandon Jul 4 19:48:59 BMM-Unraid rc.local: Version: 2023.08.01a Jul 4 19:48:59 BMM-Unraid rc.local: ----------------------------------------------------------- Jul 4 19:48:59 BMM-Unraid rc.local: plugin: Python3.plg installed From searching around, it looks like 3.10 is the last prepackaged version of python floating... Latest packages version of python is 3.12 nerdtools: 3.9.18 plugin: 3.9.16 or should we use nerd tools (extra) to install the python 3 and tools to maintain current projects and code before update? will work with unraid: comment from ich777: **REMOVED** These are the wrong files for Unraid 7.0.0, please don't post links to packages, this will cause trouble for inexperienced users and is nothing that I want to discuss in this thread, please start a new thread if you want to get help create a tutorial for others on that. and dependencies? https://slackbuilds.org/repository/15.0/python/ As nerd tool is not keep the python pacakge up-to-date nor running the lattest python. My weird issue is that on reboot I lost the python environment and started going into venv with python then used the python 3 plugins to have the tool to open the venv and run the update and scripts needed... This was one of my original post which is why I use a LXC environment now for python. Many Thx to ich777 on that. For my use case it more to satisfy any plugins that unraids needs to run that needed it before. I need to double-check to see if any are left or installed. Quote Link to comment
ich777 Posted July 9 Author Share Posted July 9 21 minutes ago, bmartino1 said: or should we use nerd tools (extra) to install the python 3 and tools to maintain current projects and code before update? You should use the version from Nerd Pack, the Python package is not compatible anymore with Unraid 7.0.0 21 minutes ago, bmartino1 said: Mainly had it installed for compabilty and use with other plugins as there notes at boot asked for this plugin or python to be avaible for there code to run. Not sure if this is needed anymore... Unraid itself never had any dependencies on Python, I'm not really sure if that is even true for other plugins (these can be only a hand full of plugins). 21 minutes ago, bmartino1 said: when Unraid v7 release will this get an update to use python3 or should we use Slackware packages and a venv? You shouldn't use Python on Unraid directly since it's not a general purpose Server, it's an application Server. 21 minutes ago, bmartino1 said: and dependencies? Please don't use any packages from Slackware 15.0 on Unraid 7.0.0 because Unraid 7.0.0 is based on Slackware current. I have removed the links form above because I'm not happy that you link packages directly, again you shouldn't need Python on Unraid anyways. Quote Link to comment
woobins Posted July 11 Share Posted July 11 (edited) It looks like the Unraid 7 beta update broke Mellanox-Firmware-Tools. Edited July 11 by woobins Quote Link to comment
ich777 Posted July 11 Author Share Posted July 11 4 hours ago, woobins said: It looks like the Unraid 7 beta update broke Mellanox-Firmware-Tools. I will look into that and will update the plugin, this ill take me a few days. 2 Quote Link to comment
ich777 Posted July 11 Author Share Posted July 11 @woobins & @Faceman please update the plugin to the latest version, reboot and see if everything is working as expected. 1 Quote Link to comment
woobins Posted July 11 Share Posted July 11 @ich777 it looks like it can find the libraries now. Thanks for fixing it! 1 Quote Link to comment
ich777 Posted July 11 Author Share Posted July 11 15 minutes ago, woobins said: @ich777 it looks like it can find the libraries now. Thanks for fixing it! Sure thing, the issue was caused because Unraid 6.12.x uses libssl1.1 and Unraid 7.x uses libssl3.3 1 Quote Link to comment
pOpYRaid Posted July 12 Share Posted July 12 On 7/6/2024 at 9:55 AM, meunraid said: anyone having python, pip issues after installing Unraid 7 grab this install: https://slackware.uk/slackware/slackware64-current/slackware64/n/openssl11-1.1.1w-x86_64-1.txz and drop it in /boot/extra and reboot. thx, that solved pip for me on unraid 7 beta. Quote Link to comment
ap-wtioit Posted July 17 Share Posted July 17 The python3 plugin 2024.07.06 does not support the latest unraid 6.12.11 release. I proposed a fix here: https://github.com/dlandon/python3/pull/2 For anybody also updated to 6.12.11 and missing python3 now, you can try to install the plugin from this url (until the PR is accepted, then you should use the official url again): https://raw.githubusercontent.com/ap-wtioit/python3/main/Python3.plg Quote Link to comment
ich777 Posted July 17 Author Share Posted July 17 32 minutes ago, ap-wtioit said: The python3 plugin 2024.07.06 does not support the latest unraid 6.12.11 release. I proposed a fix here: https://github.com/dlandon/python3/pull/2 For anybody also updated to 6.12.11 and missing python3 now, you can try to install the plugin from this url (until the PR is accepted, then you should use the official url again): https://raw.githubusercontent.com/ap-wtioit/python3/main/Python3.plg The plugin is now deprecated. Please use the Nerd Tools plugin to install Python. Quote Link to comment
ranova Posted July 20 Share Posted July 20 Thanks for the UGREEN LED Driver plugin. Was wondering if you could add options to it to: turn off LED if a hard drive is spun down in Unraid modify brightness level Change what the first LED does. Right now it just blinks bright blue, not sure what that means and would rather be static Quote Link to comment
ich777 Posted July 20 Author Share Posted July 20 44 minutes ago, ranova said: UGREEN LED Which unit do you have? 44 minutes ago, ranova said: turn off LED if a hard drive is spun down in Unraid Yes that‘s possible but needs more background processing as I explained here, for now it stays like it is, for more information read this post: 46 minutes ago, ranova said: modify brightness level That‘s already possible by editing the file: /boot/config/plugins/ugreen-leds/settings.cfg (you have to reboot so that the changes apply currently) 47 minutes ago, ranova said: Change what the first LED does. Right now it just blinks bright blue, not sure what that means and would rather be static Depending on your model the first led should be the network indicator. 1 Quote Link to comment
linuxdevil Posted July 31 Share Posted July 31 Thanks a lot for providing a plugin to handle LEDs on Ugreen NASync devices. I installed it the other day on my DXP4800+ and the network LED works correctly (blue=1GBit/s) The 4 LEDs for the drives are white and static, no reaction to HDD activity. Any ideas how to fix that? Can I provide any logs? Quote Link to comment
ich777 Posted July 31 Author Share Posted July 31 32 minutes ago, linuxdevil said: Thanks a lot for providing a plugin to handle LEDs on Ugreen NASync devices. I installed it the other day on my DXP4800+ and the network LED works correctly (blue=1GBit/s) The 4 LEDs for the drives are white and static, no reaction to HDD activity. Any ideas how to fix that? Can I provide any logs? Did you yet try to reboot? What filesystem are you using on the Disks? Is there actually some disk I/O happening? Quote Link to comment
linuxdevil Posted July 31 Share Posted July 31 HDDs are XFS. I have not rebooted yet, because I am copying data from an old slow NAS to the DXP4800+. I will reboot tomorrow, as soon as the copying is done, and report back. 1 Quote Link to comment
LemmingO Posted August 5 Share Posted August 5 Hi! Really appreciate your work @ich777! I've installed the QNAP-EC Plugin in the hopes it works with the TL-R400S. The TL-R400S is an expansion enclosure, powered by a QNAP HBA (QXP-400eS-A1164 Asmedia-powered PCIe 3.0 x2 card). I can't seem to get it to work, following the instructions on your Git repo. Any suggestions? Fixes? Thanks in advance! P. Quote Link to comment
ich777 Posted August 6 Author Share Posted August 6 18 hours ago, pauldavidtaylor said: I can't seem to get it to work, following the instructions on your Git repo. What do you mean exactly or better speaking what is not working? The Plugin is only meant to be able to control the fans and read sensor data from QNAP units because they have non standard chips for I/O It seems from your Diagram this is just a JBOD which should work right OOB on Unraid without you needing the plugin. Is the add on card recognized and is the driver for the add on card loaded? Are you sure the cable from your NAS to the JBOD is in a working condition and is not longer than the spec says? Some JBODs/add on cards are really weird and require a reboot after putting in a new disk. Do you maybe have Diagnostics with the add on card installed and the JBOD connected? EDIT: After further investigation it seems that is really just a simple JBOD with a pretty default add on card to be able to connect the JBOD to your NAS so it seems the plugin isn't needed. 1 Quote Link to comment
ssjucrono Posted August 14 Share Posted August 14 (edited) @ich777 I have been trying for sometime now to get my Coral Dual TPU m.2 to work properly with magic-blue-smoke pcie adapter The Coral TPU works fine no problem with a generic PCIE to m.2 adapter. That only allows me to use one TPU. I am trying for the second time to get both TPUs working using Maic-blue-smoke adapter. Currently I have it in my server and it can see both TPUs fine and if I don't run any inference on it it is fine. Once I start using Frigate or CodeProject AI my whole server crashes and I have to hard/unclean shutdown. I have been trying to track this down for a long time. any help would be appreciated. Here is some diagnostics, let me know what else I can provide. I do have pcie_aspm=off set I am wondering if it's a permissions issue on the unraid host? Thank you for any help you can provide ``` root@RAID:~# ls /dev/apex* /dev/apex_0 /dev/apex_1 root@RAID:~# ls /dev/apex* /dev/apex_0 /dev/apex_1 root@RAID:~# lspci -nn | grep 089a 83:00.0 System peripheral [0880]: Global Unichip Corp. Coral Edge TPU [1ac1:089a] 84:00.0 System peripheral [0880]: Global Unichip Corp. Coral Edge TPU [1ac1:089a] root@RAID:~# lspci -nn | grep 089a 83:00.0 System peripheral [0880]: Global Unichip Corp. Coral Edge TPU [1ac1:089a] 84:00.0 System peripheral [0880]: Global Unichip Corp. Coral Edge TPU [1ac1:089a] root@RAID:~# lsmod | grep apex apex 16384 0 gasket 102400 1 apex root@RAID:~# dmesg | grep apex* [ 642.227673] apex 0000:83:00.0: enabling device (0100 -> 0102) [ 642.230442] apex 0000:84:00.0: enabling device (0100 -> 0102) [ 647.318016] apex 0000:84:00.0: Apex performance not throttled due to temperature [ 647.318030] apex 0000:83:00.0: Apex performance not throttled due to temperature ``` UNRAID SYSLOG ``` Aug 12 14:30:20 RAID kernel: x86/PAT: frigate.detecto:45576 map pfn RAM range req uncached-minus for [mem 0x263b910000-0x263b913fff], got write-back Aug 12 15:58:28 RAID kernel: apex 0000:83:00.0: Apex performance not throttled due to temperature Aug 12 15:58:28 RAID kernel: apex 0000:84:00.0: Apex performance not throttled due to temperature Aug 12 15:58:33 RAID kernel: apex 0000:84:00.0: Apex performance not throttled due to temperature Aug 12 15:58:33 RAID kernel: apex 0000:83:00.0: Apex performance not throttled due to temperature Aug 14 13:07:59 RAID kernel: x86/PAT: python3:54426 map pfn RAM range req uncached-minus for [mem 0x248987c000-0x248987ffff], got write-back Aug 14 13:07:59 RAID kernel: x86/PAT: python3:54426 map pfn RAM range req uncached-minus for [mem 0x245e308000-0x245e30bfff], got write-back ``` Coral Temps Don't appear to go over 60 C 024-08-07 13:51:46 Coral Temp: 49.05C 2024-08-07 13:52:01 Coral Temp: 47.30C 2024-08-07 13:52:16 Coral Temp: 47.05C 2024-08-07 13:52:31 Coral Temp: 46.55C 2024-08-07 13:52:46 Coral Temp: 46.55C 2024-08-07 13:53:01 Coral Temp: 46.55C 2024-08-07 13:53:16 Coral Temp: 46.30C 2024-08-07 13:53:31 Coral Temp: 46.55C 2024-08-07 13:53:46 Coral Temp: 48.05C 2024-08-07 13:54:01 Coral Temp: -89.70C This is when my server crashes 024-08-12 15:57:13 Coral Temp1: 44.80C 2024-08-12 15:57:28 Coral Temp2: 47.30C 2024-08-12 15:57:43 Coral Temp1: 44.80C 2024-08-12 15:57:58 Coral Temp2: 47.05C 2024-08-12 15:58:13 Coral Temp1: 44.55C 2024-08-12 15:58:28 Coral Temp2: -89.70C server crash 2024-08-12 16:10:25 Coral Temp1: 43.55C force power off and power on 2024-08-12 16:10:40 Coral Temp2: 44.55C 2024-08-12 16:10:55 Coral Temp1: 44.05C 2024-08-12 16:11:10 Coral Temp2: 48.55C 2024-08-12 16:11:25 Coral Temp1: 45.80C 2024-08-12 16:11:40 Coral Temp2: 47.05C 2024-08-12 16:11:55 Coral Temp1: 45.30C 2024-08-12 16:12:10 Coral Temp2: 46.05C 2024-08-12 16:12:25 Coral Temp1: 44.80C 2024-08-12 16:12:40 Coral Temp2: 45.80C 2024-08-12 17:32:42 Coral Temp2: 55.80C 2024-08-12 17:32:57 Coral Temp1: 55.30C 2024-08-12 17:33:12 Coral Temp2: 55.30C 2024-08-12 17:33:27 Coral Temp1: 54.80C 2024-08-12 17:33:42 Coral Temp2: 54.80C 2024-08-12 17:33:57 Coral Temp1: 54.55C 2024-08-12 17:34:12 Coral Temp2: 55.30C 2024-08-12 17:34:27 Coral Temp1: 54.80C 2024-08-12 17:34:42 Coral Temp2: 55.05C 2024-08-12 17:34:57 Coral Temp1: 55.80C 2024-08-12 17:35:12 Coral Temp2: 56.30C 2024-08-12 17:35:27 Coral Temp1: 57.05C 2024-08-12 17:35:42 Coral Temp2: 57.05C 2024-08-12 17:35:57 Coral Temp1: -89.70C 2024-08-12 17:58:57 Coral Temp1: C 2024-08-12 17:59:12 Coral Temp2: C 2024-08-12 17:59:27 Coral Temp1: C raid-diagnostics-20240814-1447.zip Edited August 14 by ssjucrono added more coral temps and diag zip Quote Link to comment
ich777 Posted August 14 Author Share Posted August 14 22 minutes ago, ssjucrono said: magic-blue-smoke pcie adapter I have this adapter and it works as intended: 24 minutes ago, ssjucrono said: Once I start using Frigate or CodeProject AI my whole server crashes and I have to hard/unclean shutdown. I've heard multiple reports about Dual EDGE TPUs being defective and behaving similar to your experience... I think someone already reported something really similar to your temp readings in the Frigate thread. 26 minutes ago, ssjucrono said: I am wondering if it's a permissions issue on the unraid host? Definitely not, this seems like a hardware issue to me. Quote Link to comment
ssjucrono Posted August 14 Share Posted August 14 @ich777 okay thank you! The thing that bugs me is it works totally fine with the generic adapter where I only have access to one of the TPUs. I guess I'll ask for a refund on the adapter board. And go bac to the single tpu. Thank you again for all your work in the community it is greatly appreciated Quote Link to comment
ssjucrono Posted August 14 Share Posted August 14 Also wondering if it's overheating and just not reporting it? I was going to buy a heatsink and thermal pad for it but didn't want to if it's not the issue. Quote Link to comment
ich777 Posted August 15 Author Share Posted August 15 6 hours ago, ssjucrono said: Also wondering if it's overheating and just not reporting it? I can‘t quiet remember where I saw this behavior (Frigate thread or on GitHub) but I think it was the Frigate thread here on the forums and what it boiled down was that he replaced his TPU and I never heard again from this issue until now. The dual EDGE TPU usually works also fine, maybe it‘s overheationg but I really can‘t tell for sure since it must happen really quick or the power delivery system is overload. Please note that back in the days when the Coral TPU was relatively new the documentation said that you have to mount a cooler since it is otherwise a fire hazard, IIRC the power delivery system gets very hot (but that note seems to be removed from the documentation). It‘s just my suspicion that the TPU is defective and it would not be the first TPU that I see that is defective. 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.