UNOPARATOR

Members
  • Content Count

    57
  • Joined

  • Last visited

Everything posted by UNOPARATOR

  1. Your template has only a portion of keys comparing to mine. (also have Host Port 1 & 2 above these, couldn't fit in a single screenshot) Maybe you should remove (but keep the appdata) this docker image and reinstall it, just a thought. Also like @binhex mentioned the important part of a variable is the "Key" name, you can set "Name" the same thing if you like, it is only for labeling (left part of the screenshot).
  2. I'm running paper-mc 1.16 with java 16 (not this docker but with binhex-minecraftserver, I want to switch to this but need time), so all you have to do is use a newer/latest paper-1.16.5-xxx.jar file.
  3. I would love to have an amule docker by you. By the way, after a long period of hiatus, there is new version out 2.3.3.
  4. You might try `smb://192.168.1.10/ShareName` or like you mentioned try to add the necessary share in your Node-RED template.
  5. The latest update (v1.2.7) went fine and I didn't have to do anything by hand. Cheers!
  6. AFAIK, that *2TB* limit would only affect the boot drive. When using unRAID, you will be booting from a small USB stick and whether you use BIOS or UEFI will be irrelevant. In order to format a drive larger than 2TB to full capacity, you would need it to GPT since MBR support is up to 2TB.
  7. This was the case till my ASRock Rack C2750D4I died 2-3 months ago. Last month I built a Ryzen 7 5800X with a B550 MB, and put 128 GiB DDR4 non-ECC (4x 32 GiB sticks) in it.
  8. I already did change the iconUrl on my side, but with each NodeRed update, it was overwritten hence my cry for help Glad to hear that I won't be needing to do this manually from now on. 👍
  9. @spants, have you missed my message? I know this is a cosmetic issue but it is a nice *nice to have* feature.
  10. If this is your only use case, then wouldn't it be easier and cost free to make your machine dual boot? I love unRAID but just saying. 😉
  11. I've been using double commander (not docker versions) for a few months. Since it is not v1.0.0 yet, I assumed all versions were labeled as beta. Sorry, my bad.😞
  12. The version of double commander is pretty old, any plans to update it to the latest version (0.9.9 beta)? Or you are waiting for the v1.0.0 which is supposedly coming out in a few days postponed 3 months? Roadmap - Double Commander Bug Tracker (sourceforge.io)
  13. Merry Christmas and a healthy new year Ed. Cheers mate!!! And thanks for the excellent video as usual, couldn't do without you.
  14. Since you don't have any parity drive(s) set in your array, there won't be any way to recover the data of the missing disk. Also keep in mind that SSD's need TRIM support to have a longer life, but that won't be available if the SSD is in an array.
  15. Sadly nothing new is detected. root@UNONAS:~# sensors k10temp-pci-00c3 Adapter: PCI adapter CPU Temp: +47.4°C Tdie: +47.4°C By the way, sorry that I hijacked your thread.
  16. According to List of AMD Ryzen processors wiki post, your CPU does not include a GPU which essentially means you cannot use your MB's graphics ports (neither HDMI nor DP), so like @jonathanm said, you would need a discrete GPU and connect your monitor there. After making necessary adjustments to your BIOS, you might remove the graphics card to have a headless unRAID system.
  17. Alright just did #2. It is exactly the same as before. k10temp is auto loaded. If I run "sensors" command it shows: root@UNONAS:~# sensors k10temp-pci-00c3 Adapter: PCI adapter Tctl: +66.6°C Tdie: +66.6°C "sensor-detect" shows the same output: #----cut here---- # Chip drivers modprobe nct6775 /usr/bin/sensors -s #----cut here---- If I run the above lines, and then run "sensors" command, the same output is shown (only k10-temp, no values from nct6775). root@UNONAS:~# modprobe nct6775 root@UNONAS:~# /usr/bin/sensors -s root@UNONAS:~# sensors k10temp-pci
  18. Ok, I will try that and report back. Should I be using your package and modprobe nct6687 then use sensors command to see what can be read? Or use sensors-detect and use the output commands for modprobe then use sensors command to see what can be read?
  19. root@UNONAS:~# lsmod Module Size Used by veth 24576 0 xt_nat 16384 34 xt_CHECKSUM 16384 1 macvlan 24576 0 ipt_REJECT 16384 2 ip6table_mangle 16384 1 ip6table_nat 16384 1 iptable_mangle 16384 1 ip6table_filter 16384 1 ip6_tables 28672 3 ip6table_filter,ip6table_nat,ip6table_mangle vhost_net 24576 0 tun 45056 4 vhost_net vhost 28672 1 vhost_net vhost_iotlb 16384 1 vhost tap
  20. I already did in my post from this page: If you want all the output above these lines, please say so.
  21. Yes, that was the output that you've asked of me. For future reference should I have uploaded it as a file or use "Code" instead of "Quote"?
  22. Well I can see the link even after refreshing the page, but here you go. Maybe second times the charm: https://wiki.unraid.net/Setting_up_CPU_and_board_temperature_sensing
  23. Also is this (Setting up CPU and board temperature sensing) still relevant or would help with my issue?
  24. Apparently, my CPU temps come from k10temp (after upgrading to RC2 yesterday, haven't tried ich777's workaround before that since I missed it): Also running sensors-detect in unRAID terminal (with default answers to confirmations) outputs this (if it is of any use): Now follows a summary of the probes I have just done. Just press ENTER to continue: Driver `k10temp' (autoloaded): * Chip `AMD Family 17h thermal sensors' (confidence: 9) Driver `nct6775': * ISA bus, address 0x290 Chip `Nuvoton NCT6798D Super IO Sensors' (confidence: 9) Do you want to generate /etc/syscon