February 26, 20251 yr Author I am having a very good laugh now. Trurl, I think you might too - this actually fixed it & see your post at the bottom. I'm back in plex and ready to rock on.
February 26, 20251 yr Author 6 minutes ago, JorgeB said: So it's all resolved? Yessir, I am 99% good and the only thing remaining is to regain some confidence in the new hardware, or finish backing it out. But I'm going to let the server sit for a few days and monitor things to make sure it's behaving as normal. I have the server configured to begin a parity check on 3/1, and am hoping I can use that to see if there are any issues with the new memory. If there are parity errors detected, I would then try to revert to the old cpu/ram/mobo and check parity again to see if those errors are valid. Because I don't know for sure that the memory integrity is 100% stable, I do NOT want 'write corrections to parity' enabled for the first run. I have disabled this under Settings -> Scheduler, but the setting remains enabled under the 'Main' tab. I can uncheck it, but it becomes checked again if I refresh the page. 1. Is the setting on the 'Main' page only for parity checks that are manually started after disabling it, which is why it appears to reset? 2. I assume then that the setting under 'Scheduler' is the only one that will be used for the scheduled parity run?
February 26, 20251 yr Author 20 minutes ago, trurl said: 1 & 2 yes & yes Great, thanks for the confirmation! With that, I should be all set. I will keep an eye on the machine and hopefully the parity check completes without issue.
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.