UNOPARATOR

Members
  • Content Count

    54
  • Joined

  • Last visited

Community Reputation

4 Neutral

About UNOPARATOR

  • Rank
    Newbie

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. You might try `smb://192.168.1.10/ShareName` or like you mentioned try to add the necessary share in your Node-RED template.
  2. The latest update (v1.2.7) went fine and I didn't have to do anything by hand. Cheers!
  3. 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.
  4. 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.
  5. 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. 👍
  6. @spants, have you missed my message? I know this is a cosmetic issue but it is a nice *nice to have* feature.
  7. 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. 😉
  8. 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.😞
  9. 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)
  10. Merry Christmas and a healthy new year Ed. Cheers mate!!! And thanks for the excellent video as usual, couldn't do without you.
  11. 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.
  12. 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.
  13. 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.
  14. 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
  15. 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?