Slither13 Posted April 30, 2020 Share Posted April 30, 2020 This notice popped up a few days ago. I have attached the diagnostics and screenshot of the parity check history. tower-diagnostics-20200422-0909.zip Quote Link to comment
trurl Posted April 30, 2020 Share Posted April 30, 2020 Can you explain the parity errors you got on previous checks? Since there weren't many perhaps they were from unclean shutdowns. Have you always shutdown cleanly from the webUI? And why are you checking weekly? Most people only check monthly. Parity is maintained realtime and a parity check isn't required to have valid parity. But clean shutdowns are. As for the MCEs, have you done memtest? 1 Quote Link to comment
Slither13 Posted April 30, 2020 Author Share Posted April 30, 2020 I just let the server run, although we had a couple power outages this week. So I'm guessing it could be that. I followed a YouTube video to originally set up unRAID, so I've changed it over to a monthly parity check. I'll run memtest tonight and come back with the results. Quote Link to comment
trurl Posted April 30, 2020 Share Posted April 30, 2020 8 minutes ago, Slither13 said: had a couple power outages this week. Get an UPS 1 Quote Link to comment
Slither13 Posted May 3, 2020 Author Share Posted May 3, 2020 (edited) I unplugged all the ram and reset it. I'm not getting the error anymore. I also set parity to once a month. I gave it a run, no errors. Thanks for the help. Edited May 3, 2020 by Slither13 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.