Abhijeet Gupta

Sorry if I miss out on anything—English isn’t my first language. The parity issue was resolved by replacing the drive. Now, the main issue is that the server randomly goes offline, and I have to restart it manually to bring it back online. The last time I booted, I saw a notification from the plugin called "Fix Common Problems" saying there was a hardware issue. However, after a reboot, that error disappeared. Despite this, the server still keeps going offline at random times.

syslogThe common fix problems plugin was saying that there are some errors in the hardware.

I got the 6TB drive replaced and it is working fine now. The issue now is that the serv er is getting disconnected automatically. syslog

It tried it again with the 6TB drive as parity - it didn't work. syslog

The parity sync completed successfully when I used a different drive as parity. Initially, I was using a 6TB Seagate drive for parity along with two 4TB WD drives for data, but the parity sync kept failing. After posting about the issue, I decided to remove the 6TB drive and use one of the 4TB drives as parity instead. This time, the sync completed without any errors.

So I removed my parity and instead selected my other data drive as parity and this time the parity sync was completed without any issue. Here is the syslog: syslog

Here are the diagnostics- cosmos-diagnostics-20250306-1345.zip

The parity process runs for hours and almost completes, but then the server suddenly becomes unreachable. When I restart and log back in, it shows that the parity was canceled just 11 seconds after starting, which doesn’t make sense given how long it actually runs. I’ve already run a RAM check, and everything seems fine. There is a UDMA CRC error on the parity drive, but it’s not increasing.