Hi All,

 

I have a 14TB disk as parity disk, and I started my first checking one day ago. But, I lost the connection to my server (even ping returns timeout) immediately after the checking started, is it normal for not able to access server while first time doing the checking?

And any estimation for how long will it take? My data pool size is 20T and 7T of it is having data, using an old CPU E3-1230v3.

It has been 24 hours after checking began, is it hung or still running?

 

Thanks for any help.

Running a parity check does not normally make the server inaccessible.   Sounds as if something caused the server to crash.

 

One possible culprit could be inadequate power as a parity check is likely to put maximum load on that so that is definitely worth checking out.

 

you could try enabling the syslog server to see if you can get more information.

Thanks for reply, I will enable the syslog, and try again .

Yesterday, after manually reboot the server, everything comes back, and it said checking has done with no errors.

I enabled the syslog, and then, I enabled parity. (It was disabled since I installed it.)

System sent an msg which it is about to do parity sync, and then I lost all connection again.

 

Today, I have let it run for another 24 hours, I manually rebooted the server again, but, no matter how many times, I am still not able to connect to it.

 

My guessing is, as I have rebooted the server with unplug the power, and parity is enabled, every time after reboot, system triggered the auto checking.

And for my machine, parity checking will always hang there. 

 

Checked syslog, seems I didn't set it correctly, it only contain the info from last reboot, I have only attached the diagnostics file of my server.

Will try enable the parity again.

 

 

diagnostics-20211203-1628.zip

Syslog attached, it starts from I enabled the Parity disk, and end just before I lost the server connection.

Before it went down, can see CPU usage are extremely high, about 80% to 100%.

 

Can someone help to take a look?

syslog.html

A screenshot before it went down, 77540 days for parity-sync/rebuild, that's 212+ years..... 

There are ATA errors in multiple devices, could be a controller issue, use all the onboard SATA ports and then try again ideally with a different controller for the remaining two devices.

I have replaced my SATA control card, it was some ASM1061 chip, I changed it to a LSI 9207-8i card.

Now, the parity sync is running ok, and for a 14T disk, it will take about 30 hours per estimation.

Thanks for the support.