Leaderboard

Popular Content

Showing content with the highest reputation on 12/13/23 in all areas

  1. As long you don't connect any drives, you won't see the but which is caused by the old firmware. As long powertop is showing the other states, it should be able to display their usage. If it does not support anything above C3 it won't show them at all. Usually a CPU has one or more PCI bridge devices to provide the lanes for all the PCI devices. You could output a tree to understand it better: https://superuser.com/questions/1768544/how-can-i-understand-the-device-topology Yes and no. If low packages states would be reached, the CPU should throttle to 800 Mhz. But the high frequency is not the reason for the hight pgk c states. Usually the reason are the other devices or the BIOS itself. Please test with the least amount of connected devices as possible. So remove the ASM1166 and maybe play around with the Ethernet/USB ports. For example I tried on a different board to install Ubuntu and removed USB and Ethernet and finally it I found out that it only reached C8 when I disconnected the Ethernet port.
    2 points
  2. We will incorporate these changes for upcoming Unraid version 6.12.7 (and 6.13 of course). I have done a similar fix for VMs, which may experience the same thing. It would be nice if more users can confirm this fix works for them. Thanks everyone for participating and bringing in some useful information and help to uncover this situation. Though it is still a mystery to me why some people have slow write access to their flash device, something to keep an eye on.
    2 points
  3. @CiscoCoreX Can you go to Tools -> PHP Settings Error reporting level = All Categories Then open the View Log Revisit the pages which end up blank and observe the PHP log for any errors. Please post these errors. Thx Fixed my typos, please use the updated files. @KluthR The fix is not really the answer to the root cause, which I don't know but it prevents unnecessary writing to the flash device.
    2 points
  4. I personally consider UNRAID a system that always preferred the ease of use over security concerns and I just learned to treat it accordingly. Meaning that I only allow LAN access, share nothing to the internet, install no plugins that I don't trust and use restrictive Docker settings (e.g. for volume mounts, no privileged containers). I love UNRAID for its ease of use as a dataserver and wouldn't want to have it any other way, so requiring 2FA would mostly be an annoyance for me personally. Because as long as everything continues to run as root (which I like, as it makes administration much easier) the only thing that 2FA would accomplish - I think - is leading people into a false sense of security and making stupid decisions in the process... exposing unsecured services to the internet among the various possibilities. I continue to read posts where people ask for LTS versions (which keep getting "security updates"), calling for 2FA or other more advanced security mechanisms. It seriously makes me wonder what their expectations towards UNRAID are and if I'm the only one who doesn't have any such expectations. Because, myself, I want a rock stable dataserver for my LAN (or at most accessible over VPN) which works and requires minimum effort on my part - best case it runs without problems and I don't need to login for anything ever. I have UNRAID servers which still are on 6.8.3. with hundreds of days of uptime, zero issues and I've never been hacked or had any significant efforts from external parties to breach into my servers. I keep my network as secure as possible and apply a principle of no trust towards letting people on my network, which I think is the most important factor for me. I think many people try to make base UNRAID into some kind of "jack of all trades" that can do everything from hosting gameservers to crypto mining while 100% secure with all ports exposed to the internet but also having premium ZFS support and whatnot. For me that makes no sense and I compare it to preferring to eat at a restaurant which does fewer dishes excellently rather than one that offers 500 dishes which are all mediocre at best. There's various software for various use-cases, for me base UNRAID will always be an easy to use dataserver OS - for the rest I have VMs and other software. I'm not saying my personal view is the right one, just wanted to offer another perspective here. 🙂
    2 points
  5. I originally was looking for a low power, lower cost Xeon build but was, after a lot of research, a PIA finding all I wanted in my build with that, so I decided to bite the bullet and spend a couple hundred more and just go for a build that will hopefully last me another 10 years as my previous system did. So here it is: (FPB) = from previous build unRAID v6.12.4 (upgraded from 6.10.3) Case: Fractal Design Define R5 (FPB) PSU: SeaSonic SSR-450RM (FPB), may upgrade at some point MB: SuperMicro X13SAE-F CPU: i5-13500 RAM: 32GB Micron DDR5 ECC DRIVES: (FPB) WD Gold- Parity 1x 2TB, Cache 1x 1TB • DATA- Seagate Barracuda 7200 rpm 2x 1TB + 4x 2TB • 1TB Unassigned SATA CONTROLLER: Adaptec 1430SA (FPB) CPU Cooler: Noctua NH-D9L Cooler Power Consumption: All 9 Drives spun down = 36w (same as previous build) All 9 Drives spun up but idle = 63w (9w lower than previous) I Haven't checked it under typical full load yet. Update: Running ChannelsDVR in a Docker and Recording 4 HD TV Show Streams to unRAID and Streaming 1 HD Show to an Apple TV from unRAID and also Transcoding 1 HD stream to an iPAD power consumption is 99w. Without the Transcode stream consumption bounces between 63w and 72w I suspect the bouncing maybe do to saving the recording streams to the Cache HDD. IGPU & CPU Fan: To get the igpu to work for transcoding I had to change the Primary Video in BIOS to IGFX I also had to install IPMI Tools to control the CPU Fan so SuperMicro's Fan Sensors wouldn't complain about the fan speed being too low. I set the Min fan speed to 31.2% in the IPMI Tools plugin so it would run at 560 RPM and SM's IPMI Fan control at Standard (before setting it in IPMI Tools), the IPMI Tools plugin seems to change it back to Full Speed so that's where I left it. I did set the Max speed in the IPMI Tools plugin to 100% If the Fan is set to Full Speed in SM's IPMI without the IPMI Tools plugin the power consumption at idle with drives spun down jumps to 56w. The setting I have doesn't seem to affect power consumption. Previous Build for ref. MEDIA: V 6.10.3 plus • Fractal Design Define R5 • SeaSonic SSR-450RM • SanDisk Ultra FIT 16GB • SuperMicro X9SCM-F-O • i3 3240 • 4GB Kingston Value RAM • DRIVES- WD Gold- Parity 1x 2TB, Cache 1x 1TB • DATA- Seagate Barracuda 7200 rpm 2x 1TB + 4x 2TB • 1TB Unassigned • Adaptec 1430SA SATA Controller • Stock Cooler I hope this info is helpful to someone in the future since it seems hard to find in one place.
    1 point
  6. See here: https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces
    1 point
  7. You don't need to forward ports for local connection, but you do need to forward them if you expect the game to know your server exists. If you don't want to forward, you should be able to go into Steam > View > Game Servers, then add your local IP and the correct port. I don't know that game specifically, but if the container has a Steam UDP or similar port (not a game port) that is the one you should use in the Steam. Edit: Yes. You should be able to add your server in steam using {local_ip}:27015 since that is the assigned query port for steam.
    1 point
  8. Indeed. Ignored that. I still remember that @CiscoCoreX mentioned clearly a normal operation after downgrading. To clarify all currently affected users should make tests (which is not doable on prod). I still making some tests with @CiscoCoreX in background. Maybe we just observe the behavior for now. But it seemed weird that users explicitly reported this after .4. As I understood, the exec‘s were executed several times below .4 as well, right? 🤔
    1 point
  9. Have you installed the Dynamix File Manager plugin?
    1 point
  10. Yes, and you can then rename the new pool to the old name in case any paths were using the old one.
    1 point
  11. Super, danke, genau so hat es ohne Probleme funktioniert.
    1 point
  12. Any snapshots? Vdisks can also report wrong used size, but you can be pretty confident that the GUI is showing the correct used space, if you can't find what it is you can move some stuff to the array or elsewhere until you find it.
    1 point
  13. It can be, since other users have that issue.
    1 point
  14. For anyone else reading this thread, New Config isn't the normal way to add a disk to the array. @cruzerkk New Config isn't normally needed to add a disk. I suspect you already had a missing disk and Unraid wouldn't let you add a disk when another disk was already missing. Perhaps you previously assigned a disk to the array and removed it without setting a new array configuration (New Config). If you remove a disk without New Config then the missing disk would mean you had no parity protection.
    1 point
  15. Your power top screen looks really good! CPU cores are even reaching C10, which is quite a feat. pc3 = is the package c state includibg all controller. (Memory, SATA, network. Etc..) cc3 = is the core c state of the CPU. The core c state should be more important than the package c state, since the cores can use quite a bit of power. The package power will not fluctuate a lot and is more difficult to get lower, because of all the different controllers involved. Laptop power should be more efficient than a full ATX PSU. I am really interested in the power values you will measure.
    1 point
  16. Hi @bonienl Good news, It's working. All the pages are fast like normal. Would be nice to see other with similar problem, test your files also. Desktop 13-12-2023 17-56-03.zip
    1 point
  17. Da über USB keine verlässlig und somot stabile Verbindung besteht, wird Unraid sobald es dazu kommt deine Festplatten "deaktivieren" und somit hast du ein Problem im Array, also mit deinem Speicher. Wenn du ohne den Schutz der Parity leben kannst. Kannst du die USB Platten per Unassigned Disk Plugin benutzen. Da ist das mit der verlässlichen Verbindung kein Problem, da dort eben keine Parität nebenbei aufgebaut werden soll.
    1 point
  18. @Daniel22 Jetzt verstehe ich. Der Mover lässt sich nicht systemweit abschalten. Du musst in den jeweiligen Shares einstellen, das der Mover nicht aktiv wird. Sprich keinen Secondary Storage nutzen.
    1 point
  19. I managed to do the upgrade and get gui back after dynamix reset in 6.12.0, but no succes in getting the docker templates. I've copied the templates-user back into the dockerMan folder but its not used. Edit: nevermind, it was because containername was changed, other do work Thanks!
    1 point
  20. Run the diskspeed docker controller test to check for any bottlenecks.
    1 point
  21. Always stick with a lower version if you dont know why to upgrade. New features are only beneficial if you actually need to use them. The v7 recommended is working well.
    1 point
  22. Es ist einfach viel auf einmal, sagen wir es mal so. Die Eingangsfrage habe ich jetzt auch lösen können. Man muss vorher das Array stoppen, dann werden einem die fehlenden Docker Einstellungen angezeigt. Auch das gibt es so übrigens nicht, dort lässt sich nur das logging deaktivieren.
    1 point
  23. Any time there are writes going on to 2 or more disks turbo write won't work and write speed will be much slower because parity is being updated at the same time for all disks, you can only test turbo write if writing to a single disk.
    1 point
  24. Hey, I use IP Tables at the VPS to route incoming traffic into my Lan network. In my Lan I have the NginxProxyManager where I forward the Ports to the specific container. At the moment there is a bug, so that doesn't work. I try to fix it in January. You can look at the linked GitHub repo there are two sections how to forward with IP Tables (ip.sh)
    1 point
  25. Okay, ich habe mir gestern alle Teile bestellt, das heißt: ASUS ROG STRIX Z490-I GAMING (gebraucht, Kleinanzeigen) Jonsbo N2 Mini-ITX Gehäuse picoPSU-160-XT DC/DC (160 Watt) + AC/DC 192W Adapter SATA auf 2x MOLEX Adapter (von picoPSU zu Gehäuse SATA Platte) Noctua NH-L9i CPU Kühler Noctua NF-A12x15 PWM Lüfter (original Gehäuse Lüfter soll wohl relativ laut sein) 1x Crucial RAM 32GB DDR4 RAM Sobald alles da ist werde ich es zusammenbauen und mich dann nochmal melden. Bis dahin kann ich schonmal bisschen schauen wie powertop funktioniert. Danke bisher @mgutt @MPC561 ! LG
    1 point
  26. @CiscoCoreX I made some typos, sorry for that. Here are the updated files dashboard-test.zip
    1 point
  27. I've been putting off the switch to the new Docker, but was wondering: is it worth moving to v8 before I make the switch, or after? Or is it still too early to trust Ubiquiti with a new major version, and I should just stick with v7 for a while longer, anyway? Thanks for your insight!
    1 point
  28. @faxxe71 @pappaq ITE IT87 Driver oder Nuvoton NCT6687 Driver könntet ihr mal probieren. Sind Treiberpakete im App. Erst das eine dann deinstallieren, dann das 2. testen.
    1 point
  29. Vielen Dank für die Unterstützung! go file habe ich ebenfalls angepasst.
    1 point
  30. as its installing fresh on very boot, yes, goto /config/plugins/... and remove the gvt-g plugin ... but actually you may should post a screen where its stuck as its not common ... to prevent a boot.
    1 point
  31. What I do is have the .plg create a default config file: <FILE Name="/boot/config/plugins/&name;/&name;.cfg"> <INLINE> <![CDATA[ [general] refresh_interval="30" lazy_load="0" destructive_mode="0" exclusion="" directory_listing="" snap_max_days_alert="30" snap_pattern="Y-m-d-His" snap_prefix="" ]]> </INLINE> </FILE> The brackets around "general" may be an issue.
    1 point
  32. Mein "Testbericht zum Z790" ist hier: https://forums.unraid.net/topic/149033-atx-messungen-gigabyte-z790-d-ddr4/ das Neue Board ist das hier: https://www.gigabyte.com/Motherboard/B760M-GAMING-X-DDR4-rev-10#kf <-- das hat auch MGUTT schon getestet.. ist jetzt schon das 4te und hoffentlich letzte Mainboard *daumedrück*
    1 point
  33. kopierst Du den Ordner wieder zurück (ohne die VM vorher zu starten) (natürlich an die Stelle, wo nun die VMs erzeugt wurden) Völlig simpel Danach VM starten und alles sollte gut sein
    1 point
  34. Vermutlich hat es schon vorher auch funktioniert, vermutlich war eine kleinigkeit falsch eingestellt. Ja, es funktioniert. Vermutlich war es nicht das skript aber sonst schmeiß einfach das in dein go file ganz am Schluss rein (/boot/config/go) : nvidia-persistenced Kannst auch mit einem User Script machen, nach dem initialen boot, einmal genügt wenn Unraid hochgefahren wird.
    1 point
  35. Mit etwas Handarbeit wohl schon. Erstmal musst Du die VM stoppen und den Mover zuende laufen lassen. Dann sollte auf der Zielplatte eine "heile" virtuelle Disk existieren, die Du irgendwohin wegkopieren kannst. Bei der Neuinstallation ist die VM zwar weg, aber Du kannst einfach eine neue erzeugen (möglichst mit den alten Einstellungen für Netzwerk usw.) und der die alte Platte (die Du natürlich dann vorher an "die richtige Stelle" kopiert hast) als Systemplatte unterjubeln. Deine HA Einstellungen sollten alle vorhanden sein.
    1 point
  36. Uiiihjuijui... so ziemlich alles 😁 * die NVMe hat im Array nix zu suchen, die ist ja wohl die schnellste aller Platten, also ein würdiger "Cache" * die Samsung SSD (jetzt Cache) gehört da aber auch nicht hin, im Array wird kein "Trim" ausgeführt, mit der Zeit wird sie also grottenlahm werden. SSDs gehören in separate "Pools" * die 4Tb Datenklo sind da richtig plaziert. * die system shares "system", "appdata" usw. gehören nicht ins Array. So viel Lebenszeit wirst Du nicht über haben. Idealerweise sind sie auf der NVme, alternativ geht auch die "Pool SSD" AUF KEINEN FALL DÜRFEN SIE VERSCHOBEN WERDEN!!! (was dann passiert, lernst Du ja jetzt gerade durch Schmerzen). Ich geh mal davon aus, dass da noch keine wichtigen Daten drauf sind, deshalb würde ich sagen, am Besten löscht Du die gesamte Konfiguration und fängst nochmal von vorne an: * 4TB ins Array * NVMe SSD als "Cache" * SATA SSD als Pool * SystemShares entweder nur auf "primary Cache" lassen, oder "primary SSD" einstellen (und die automatisch erzeugten Ordner vom Cache von Hand auf die SSD verschieben). Natürlich hat dieses Setup weder viel Speicher, noch irgendeine Art von Datensicherheit. Aber, das ist Dir ja wohl bewußt, oder? Ach ja, noch eine Ergänzung zu "Mover steht": Klar steht er, er will eine VM verschieben, muß aber warten, bis sie "frei" wird. Das passiert aber niemals, solange die VM läuft. Also wartet er, und wartet, und wartet... Und wenn Du nicht gestorben bis, wartet er weiter 🙂
    1 point
  37. Das aktuelle System reicht. Selbst der Prozessor sollte locker reichen. Docker Container sind meist nicht so anspruchsvoll. Wie gesagt ich hatte das auf einem J4105 ATOM board was Du auch an Dockern planst und das lief gut. Solange du keine VMs nutzt brauchst Du nichtmal 16GB RAM. Würde ich auf jeden Fall erstmal testen. Aufrüsten kannst Du immer noch. Unraid heißt Unraid weil es eben nicht mit RAID arbeitet. Was ist ein Raid? Raid5, z.B. 4 Festplatten gleicher Kapazität bei denen eine ausfallen kann und man kann die ersetzen und die Daten wiederherstellen. Aber das macht Unraid (also "Kein"Raid) eben anders. Du hast dann 3 Datenplatten und eine Paritätsplatte. Auf den Datenplatten liegen ganz normal Daten (kann man in einen anderen Rechner stecken und einfach lesen wenn nötig) und bei schreiben der Daten wird eine Paritätsinformation auf der Paritätsplatte abgelegt, mit der man dann ggf. auch eine Platte wiederherstellen kann. Diese Datenplatten + Parität ist dann das Array. Hab ich nie gemacht aber geht wohl beim Cache/Pool (ohne Raid HW, sprich Softraid,, wobei Raid 1 ja eh nur Spiegelung ist). Ich hab mir das gespart, ich kopiere via einen Backupprogramm alle wichtigen Docherdaten täglich noch aufs Array. Deswegen verliere ich da max. einen tag Daten. Dafür spar ich Strom. Wie das unter deinen Windows Server war ist irrelevant, ich meine unter Unraid. Da kann man einstellen das die Platten auch x Minuten in den Spindown gehen wenn keine Daten in dem Zeitraum geschrieben oder gelesen wurden. Dadurch sinkt der Stromverbrauch der Platte von ca. 10W auf 1W. Und das die Platten nicht dauernd hochfahren müssen kann man auf zwei Arten realisieren. Zum einen den Cache nutzen. Der ist NVME/SSD und geht nach paar ms schon in den sleep und wacht auch so schnell wieder auf. Die zweite Möglichkeit ist Daten die man sehr wenig braucht auf einer Platte (oder mehreren) zu speichern und die Daten die man öfter braucht auf eine andere Platte zu legen. Zum Beispiel. Du hast Videos und Musik. Nehmen wir an Videos und Musik sind so gross das sie jeweils auf eine Platte passen würden. Musik hörst Du jeden Tag. Videos schaue Du nur am Wochenende. Dann machst alle Videos auf eine Platte und die gesamte Musik auf eine andere statt alles zu mischen. Dann schläft die Videoplatte faktisch die ganze Woche bis aufs Wochende und die Musikplatte halt immer wenn Du Musik hörst. Btw. ich hab meine Musik sogar auf dem Cache weil ich die täglich höre.
    1 point
  38. The same page that has the USB Creator tool for download also has the links to download the zip files for the latest Unraid releases that can be used with the manual install method.
    1 point
  39. For what is this mainboard? And the price... what the hell... € 564.- 🤪 And there is no 10GB-Lan on it... well... Way too expensive in my opinion but ok...
    1 point
  40. It is magic. 🎅🎄🎄🎄
    1 point
  41. 你这个135在怎么用,屏蔽核显做什么呀? 你要直通的话 试试这个. 安装一下777大神的插件. 插件没上ca,自己装一下.应该看的懂吧.试试这个. 我13700,intel gpu top工作正常. 容器jellyfin和直通给虚拟机都工作正常. https://raw.githubusercontent.com/ich777/unraid-i915-sriov/master/i915-sriov.plg
    1 point
  42. da es vermehrt zu Fragen wie, was, wo in diesem thread kommt, hier nochmals der Hinweis mit der Bitte die Fragen einfach im normal Part zu tätigen, Danke.
    1 point
  43. I have now adapted the plugin so that users are able to install it on Unraid 6.12.4 without any workarounds and to make sure that packages for upcoming Unraid versions are available. The new plugin also is a bit more verbose, made a few changes under the hood which makes installation a bit more easy and reliable -> this means you don't need to have a Userscript anymore that runs on startup. The plugin is now also part of the Plugin-Update-Helper, this will basically ensure when you update Unraid to a newer version that it will download the new plugin package version even before you reboot to the new Unraid version (keep an eye on your Unraid Notifications since the Plugin-Update-Helper will inform you there when the download is finished or failed). You can install the new plugin with this link (currently it's not on the CA App): https://raw.githubusercontent.com/ich777/unraid-i915-sriov/master/i915-sriov.plg Thanks to @domrockt for helping me test the plugin if everything is working properly since I have no compatible hardware on hand! (This plugin requires Unraid 6.12.4+)
    1 point
  44. The issue was the Docker Folders plugin. After uninstalling the plugin all buttons under Docker and VM worked properly.
    1 point
  45. Maybe it's just my impression but you seem to be unfamiliar with certain ways of collecting copyrighted material. Yes, many people around here are using the *arr app dockers. Just a word of caution. Depending on the country of your residence this practice can be deemed illegal. You'd have to make sure to learn all about this method and potential consequences, before blindly jumping on the bandwagon.
    1 point
  46. I finally found a solution to this. I disabled SMB and the re-enabled it again. First stop the array (From MAIN hit Stop) In Settings | SMB in SMB Settings set SMB Enabled to "No" In Settings | SMB in SMB Settings set SMB Enabled back to "Yes (Active Directory)" Then enter the AD username and password to and Hit Join as usual and now it Joins the AD domain. Finally restart the array. I checked all configuration files before and after doing this, there's no significant different other than what you would expect now UNRAID is domain joined so I can only assume this is some error in a cached value in UNRAID or SMB that resetting SMB cleared out.
    1 point
  47. I'd run find /mnt/user -name @eaDir -exec rm '{}' \; but because it's potentially dangerous I'd run find /mnt/user -name @eaDir -exec ls '{}' \; first to find and list them.
    1 point