cfm21

Unfortunately, even with the Marvell controller removed, my parity drive is still throwing read errors and then being disabled. I have attached the new diagnostics. mccoyserver-diagnostics-20240609-1008.zip

I have connected my M.2 drive to a PCI adapter, allowing me to use the full 6 SATA ports on my motherboard for the remaining drive and removed the SATA PCI card. I'll order an HBA so I can move the M.2 cache drive back to the normal slot and report back if it's solved for sure. Parity is rebuilding now

Okay, good to have a place to start. I'll replace it and test. Wonder why it started with the GPU addition, think it was something something PCI?

Yes, it ran for months without issue prior to the GPU. I have removed the GPU to lower the power draw

Hi everyone, I'm pulling my hair out over this one and would love for some help. My server has been stable for months with no issues, so I decided to add an old GPU I had laying around to help with media transcoding. To do so, I moved a couple SATA connectors to other ports. A couple days later, my parity drive started going offline with read errors and then subsequently disabled by Unraid. Strange, I thought, so I rebooted. After the reboot, disk 3 appeared missing, even though no physical reconfiguration was done (I was away for work). After a couple reboots, it reappeared. I booted the server, let the parity rebuild, but after a couple hours everything happened again. I resigned myself to leave it offline for a few days until I got home and could remove the GPU since that was the only thing that changed, and return the SATA connectors back to their original ports. That worked great, for about a week. Then this morning, I awoke to all the same errors, with millions of parity read errors and a few hundred read errors on disks 1-4. I'm at a loss as to what would cause this to happen. My specs are below. Rosewill Rack Mount Chassis MSI B450-A PRO MAX AMD Ryzen 7 3700X PCI SATA Expansion Card (4 ports) 2x 8TB Seagate 1x 4TB Seagate 1x 4TB WD 2x 3TB WD 2 drives are plugged into motorboard SATA, and 4 are plugged into the PCI expansion card. My diagnostics are attached. mccoyserver-diagnostics-20240608-1135.zip

Hi all, I'll try to explain the issue in as much detail as possible. I just completed my move to a new house with a new ISP. I brought my unRAID server and updated the network configuration settings in unRAID accordingly by stopping the Docker service, changing it, and restarting the service. However, all my docker containers really want to use the old IP address for the server on the old subnet (e.g. old IP: 192.168.86.42 new IP: 192.168.1.100). Most of my containers are running on a custom docker network named 'proxy'. Any tips?

If I remember correctly, somewhere inside the server settings, you can change the port associated with the unRAID web panel and forward that port with your router. I’m not where I can check at the moment, but I know I connect to my web panel with a port that isn’t 443

Are you using the My Servers plugin?

This would not work, I’m not anywhere close to the server.

Bump, I still need a solution

Bump, still looking for an answer here.

As a heads up, when I installed the container with the supplied template, it would not launch until I updated the Java version to 16. I was getting an error in the web GUI until I made that change. Not sure if you want to change the default value.

Did you add the drive via a motherboard SATA port? Do you have NVMe or PCI expansion drives present?

Glad I could help! I'm certainly no wizard, just someone who is used to a lot of janky fixes 😉