UNOPARATOR

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. 😉

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.😞

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)

Merry Christmas and a healthy new year Ed. Cheers mate!!! And thanks for the excellent video as usual, couldn't do without you.

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.

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.

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.

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-00c3 Adapter: PCI adapter Tctl: +33.1°C Tdie: +33.1°C I guess I'm out of luck for the time being. Any other ideas?

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?

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 24576 1 vhost_net xt_MASQUERADE 16384 15 iptable_filter 16384 1 iptable_nat 16384 7 nf_nat 36864 4 ip6table_nat,xt_nat,iptable_nat,xt_MASQUERADE ip_tables 28672 3 iptable_filter,iptable_nat,iptable_mangle xfs 671744 8 md_mod 45056 7 nct6775 53248 0 hwmon_vid 16384 1 nct6775 bonding 114688 0 edac_mce_amd 32768 0 btusb 45056 0 kvm_amd 90112 10 btrtl 16384 1 btusb btbcm 16384 1 btusb btintel 24576 1 btusb kvm 421888 1 kvm_amd bluetooth 380928 5 btrtl,btintel,btbcm,btusb crct10dif_pclmul 16384 1 crc32_pclmul 16384 0 crc32c_intel 24576 2 ghash_clmulni_intel 16384 0 aesni_intel 364544 0 mvsas 53248 8 wmi_bmof 16384 0 crypto_simd 16384 1 aesni_intel cryptd 16384 2 crypto_simd,ghash_clmulni_intel ecdh_generic 16384 1 bluetooth libsas 69632 1 mvsas i2c_piix4 24576 0 i2c_core 45056 1 i2c_piix4 wmi 24576 1 wmi_bmof k10temp 16384 0 scsi_transport_sas 32768 2 mvsas,libsas glue_helper 16384 1 aesni_intel igc 86016 0 ecc 24576 1 ecdh_generic ahci 40960 1 ccp 69632 1 kvm_amd libahci 28672 1 ahci rapl 16384 0 acpi_cpufreq 16384 0 button 16384 0

This outputs nothing, but doesn't give an error either.

I already did in my post from this page: If you want all the output above these lines, please say so.

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"?

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

Also is this (Setting up CPU and board temperature sensing) still relevant or would help with my issue?

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/sysconfig/lm_sensors? (yes/NO): To load everything that is needed, add this to one of the system initialization scripts (e.g. /etc/rc.d/rc.local): #----cut here---- # Chip drivers modprobe nct6775 /usr/bin/sensors -s #----cut here---- You really should try these commands right now to make sure everything is working properly. Monitoring programs won't work until the needed modules are loaded. Unloading i2c-dev... OK

Supposedly by, the github repo owner tested this with a B550 MB. Since I'm not a linux expert, I don't know why the procedure gave an error.

Thank you for this information but I couldn't find that plugin when I searched in CA. Any ideas?

I have an ASUS ROG STRIX B550-F GAMING (WI-FI) with an AMD Ryzen 7 5800X CPU.

First of all, as I mentioned in my previous post, I did change the url to your RC2 .txz link, ran all lines one by one in unRAID Terminal, but the last line gave an error. Should I change anything in System Temps before trying? Secondly, RC2 only shows the CPU temp but no MB temp or fans. Did your workaround offer those values? I know you don't own such hardware but who would know what your package does other than yourself, right? (maybe @Bolagnaise does, since your RC1 package worked for him.)

If you want a specific GPU not to be used by unRAID OS itself so that you could passthrough it to a VM, you would need to go to MAIN tab and lick on your Flash drive: From there you would need to change Syslinux Configuration: The red box is used for a completely headless unRAID, so you might omit that. The values in the yellow box can be gathered from TOOLS --> System Devices menu: You might need to fiddle with SETTINGS --> VM Manager (in Advanced mode) --> PCIe ACS override: for a working IOMMU Group configuration. Note: I have a single GPU in my system, I'm running unRAID as headless and I'm reserving that GPU to be used in a VM. But as @jonathanm mentioned, if you would like to use a dedicated GPU just for unRAID, you must set it up as your primary GPU from your motherboard's BIOS (if that option is there). P.S: There might other workarounds, but this is all I can provide.

v6.9-rc2 can show the CPU temp without anything special, @ich777 what does your .txz package solve for RC2? I tried the above script - changing the url for RC2 - but modprobe line gives an error:

The parity drive must be equal or greater in capacity than the largest drive in the array. The drives in the array could be of different sizes, as long as my previous statement is true. unRAID is not RAID, but you can think of like RAID such as: no parity drive ~= JBOD 1 parity drive ~= RAID5 2 parity drives ~= RAID6 But you cannot connect any drive from a RAID array (not sure about JBOD since I've never used it) to another machine and access the data. However in unRAID, if your array is formatted as XFS you can just disconnect any drive other than parity and connect to another machine and access your data. Which means even if more drives than your parity fails, you would only loose the data on the failed drives. !!! Remember RAID or unRAID is not a backup solution. !!!

I would like to learn about this too. Thanks for bringing it up.