Hi @ll,

I today upgraded my CPU again and I want to know what's going on with my server.

1. Time I had trouble was after trying to remove an directory (non critical just a temporary one)

   The UI stopped responding and nothing reacted. UI seemed to time out and manually pressing the power button didn't shut down the server. I had to reset the server.

2. Now after the reset the server started a parity check and immediately started a parity check and found errors... of course it did...
   in the beginning of the check I stopped all docker containers.
   After 3 hours my UI suddenly has an timeout.

I am again unable to access the UI, but ssh was still working. I tried to start a diagnostics, but the CLI stopped responding. After 10 minutes of waiting I opened another session to check if something has been generated, but nothing ...

But now while I write here ssh also begins to timeout.

Should I would a couple of hours until the server maybe finishes its parity check, or is my server doomed?

I have a jetkvm plugged into the server, but I noticed that the CLI always stops working ~5 minutes after start unless I log in instantly. Is that a bug or a feature? (Have experienced this for years and also before 7.0)

Edited January 10Jan 10 by W0nderW0lf

I don't think the parity check is important right now. You can do it again after things are working.

Have you done memtest?

See if you can get diagnostics immediately after rebooting, and setup syslog server.

Seems like my ram is A**...

You should not attempt to run any computer unless memory is working perfectly. Everything goes through RAM. The OS and other executable code, your DATA. EVERYTHING. The CPU can't do anything with anything until it is loaded into RAM.

Yep, I know. Luckily I had another pair of working RAM in an older server and now it's working and tests passed.