psyc

Yep, the latest v4.0.16.2944 is working.

Mine was hanging as well, downgrading to binhex/arch-sonarr:4.0.15.2941-1-03 worked for me. I'll check back in a few days for a fix.

Well, that was really odd. I attempted everything again today and just tried moving the NVMe to a different slot, and everything worked fine. I am going to guess that is the answer since nothing else makes sense. Thanks!

As I said in my post, I checked and replaced all the cables. They clearly work fine, since when I unplug one of the new devices the old device comes back from missing, and vice versa.

I am having some difficulties with my new drive installation. I am hoping someone can help. My current setup is 6 HDDs (1 14TB parity, 5 array), 1 SSD, and 1 NVMe for cache. I have just tried adding a 14TB HDD and a 2TB NVMe...when I did that, I lost two of the array drives and thought I knocked a wire loose, but after replacing the cables and checking wires, that was not the case. I unplugged the new HDD, and one of the lost drives came back. I then took out the NVMe, and the other lost drive came back. Typing this out, I am starting to think it is a power issue, but my 750W PSU should be able to handle this, right?

Device shows up in the system but is not available as a network interface. I have seen the patch from the Chinese section but this also does not work: r8152 4-2:1.0 eth0: failed tx_urb -22 xhci_hcd WARN waiting for error on ep to be cleared mediatower-diagnostics-20221203-1826.zip

This appeared to work after installing the patch but now it crashes with: r8152 4-2:1.0 eth0: failed tx_urb -22 xhci_hcd WARN waiting for error on ep to be cleared I have rtl8156b, can anyone help?

Oof. That was pretty stupid of me. Thanks.

Kinda at a loss with this issue. I recently installed 2 new drives and had a cable seating problem causing one of the drives to get corrupted, after fixing the cable and rebuild this new issue popped up. So far I've tried rebooting, setting the IP to static (which allowed me to access the docker apps by ip again), and updating to the latest UnRAID, I've also tried accessing it from different devices and browsers. It's clearly not a routing issue so I can only assume some issue with unRAID. ping mediatower Pinging MediaTower.local [192.168.1.139] with 32 bytes of data: Reply from 192.168.1.139: bytes=32 time<1ms TTL=64 Reply from 192.168.1.139: bytes=32 time<1ms TTL=64 Reply from 192.168.1.139: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.1.139: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms ping 192.168.1.139 Pinging 192.168.1.139 with 32 bytes of data: Reply from 192.168.1.139: bytes=32 time<1ms TTL=64 Reply from 192.168.1.139: bytes=32 time<1ms TTL=64 Reply from 192.168.1.139: bytes=32 time<1ms TTL=64 Reply from 192.168.1.139: bytes=32 time<1ms TTL=64 Ping statistics for 192.168.1.139: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms mediatower-diagnostics-20220629-0846.zip