atu

Hi, thanks a lot for your work on this plugin! Is there any chance you could add the metrics for the disks temperature please?

I still haven't been able to make that part work, anybody to assist?

Hi, I have an onboard RJ45 + a quad port Intel I350-T4. The onboard port (eth0) is set on 192.168.10.12 and is connected to my default vlan. I'm trying to setup a custom Docker network so that all my containers are running inside a different vlan. I've configured the port (eth2) for the containers to use 192.168.41.2 as you can see here. If I set a container to use the network "Custom : br2 -- Docker", the container gets a unique IP in the 192.168.41.X range which is the expected behavior. What I want is to get all my containers running behind the IP I've configured for this interface (192.168.41.2) so for that I created a custom docker network using the following command: docker network create -o com.docker.network.bridge.name=br2 apps Now when I set a container to use the newly created "apps" network, it gets an "internal" ip in the 172.X.X.X range (which is what I want) but this range gets behind the 192.168.10.12 IP instead of 192.168.41.2. Any idea what I'm doing wrong here? Thank you in advance for helping me sort that issue out!

All cables are seating correctly. I'm using an HBA with a SATA octopus cable. I do need to use a power splitter because I have a BeQuiet 300W TFX PSU with only 3 SATA connectors. But I do think the disk is faulty cause I swapped it with the one that has no issues (swapped physical place, sata and power cable) and it's failing again while the other is syncing without issues. To be 100% sure I would need to test with another drive to see if my setup can handle 6 spinning drives at once but I don't have any left so I'll just end up using a single parity drive. To be noted that these drives are 10 years old and have been used 24/7 in my previous NAS, it's not impossible this drive is actually faulty

The first of the two 3TB drive is correctly working and synced as a parity drive. I just switched both drives and I'll start the parity sync again, I'll let you know how things went tomorrow (it takes 7 hours to sync/rebuild the parity). If that drive still has issues, I will probably just use a single parity drive which is fine for my use case, it's just that I had those 2 disks laying around so I thought I could better use them as 2 parity drives but it's not critical. Thank you both for your help.

I tried that already, I changed the SATA cable, changed the SATA port on which it is connected, entirely disconnected and reconnected it.

Hi, I just recently started the setup of my home server with unraid and I'm very new to all of this, coming from Synology. When I first set up my unraid instance, I used 4x brand new 2TB drives (1 parity and 3 usable drives), once the migration done from my old Synology, I then moved 2 of my already used 3TB drives into my unraid machine. My goal is to use the 2 old 3TB drives as parity drives and 4 new 2TB drives as usable space, so to do that here is what I did: I connected the 2 old 3TB drives Assigned 1 of these to the parity (so I have the 2TB parity in place + one of the 3TB) Started the array to perform a parity-sync Stopped the array Unassigned the 2TB parity drive Assigned the 2TB parity drive to a normal array drive I can use Start the array to clear the 2TB drive and add it to the usable space Stopped the array Assigned the 2nd 3TB drive to the parity Started the array to perform a parity-sync This last step never succeeded, I did it 3 times and I get the same error all the time where it says "Parity disk in error state (disk dsbl)" and shows 1024 errors. Am I doing that wrong or is my disk faulty? You can find the diagnostic zip in attachment. Thank you very much in advance for helping me! adhara-diagnostics-20230730-2042.zip