Unraid 7.2.5

Micro-Star International Co., Ltd X370 GAMING PRO CARBON (MS-7A32) , Version 1.0

AMD Ryzen 9 5900X 12-Core @ 3700 MHz

Memory: 64 GiB DDR4

Nvidia 960FTW

I recently swapped out my single 20tb recertified Exos HDD for a pair of 22TB Exos drives to begin expanding my system. I mainly use my server for an Emby server installation and basic file storage and then Audiobookshelf as my book/comic/audiobook server. I'm an Unraid neophyte so I tried to look at the diagnostic log (attached) and also my Fix Commons Problems readout. The Fix Common Problems plugin listed a "Machine Check Events detected on your server" and then allows me to acknowledge the error (Your server has detected hardware errors. The output of mcelog has been loggeg. Post your diagnostics and ask for assistance on the Unraid forums).

Early this morning at approximately 3:48 my Parity Rebuild stopped and then restarted upon the error and has been going again without incident and has found 0 errors. Should I acknowledge the error and allow it to move on? Or is this something unsafe and if so, what should my next move be? The rebuild is at 72% with 6hr 48min remaining (estimated).

Any help is greatly appreciated as I generally lurk the forums before trying to bug anybody about stuff. If I spaced on leaving any pertinent information, please let me know.

Thanks, everyone!

kelex-diagnostics-20260506-0731.zip

The hardware error was corrected, but it's not a good sign, especially if it keeps happening. The parity check pause was unrelated to that; it was the tuning plugin.

53 minutes ago, KaptainKrypton said:

Early this morning at approximately 3:48 my Parity Rebuild stopped and then restarted upon the error and has been going again without incident and has found 0 errors. Should I acknowledge the error and allow it to move on? Or is this something unsafe and if so, what should my next move be? The rebuild is at 72% with 6hr 48min remaining (estimated).

It did not restart (from the beginning). At about 3:00 it was paused by the parity check tuning plugin because an appdata backup started running (and you have the tuning plugin configured to pause checks while backup is running) and then resumed from where it was when the backup finished at 3’;48.

28 minutes ago, JorgeB said:

The hardware error was corrected, but it's not a good sign, especially if it keeps happening. The parity check pause was unrelated to that; it was the tuning plugin.

Now I suppose I should find out what the hardware issue is. Is there any way to know if that's a mobo, PSU, memory or drive problem? Many thanks.

5 minutes ago, itimpi said:

It did not restart (from the beginning). At about 3:00 it was paused by the parity check tuning plugin because an appdata backup started running (and you have the tuning plugin configured to pause checks while backup is running) and then resumed from where it was when the backup finished at 3’;48.

Ah, alright. I assumed since it said it had started again that it had actually stopped. Good to know.

56 minutes ago, KaptainKrypton said:

Ah, alright. I assumed since it said it had started again that it had actually stopped. Good to know.

You can configure the plugin to give you notifications when the plug-in does a pause/resume, and the reason why.