Wednesday at 02:40 PM3 days I’ve done 2 consecutive parity checks and both reported 4 errors, even though the errors were reported to have been corrected after the first parity check. Could someone look at my attached diagnostics and tell me what issues you see with my server tower-diagnostics-20261111-0821.zip
Wednesday at 02:51 PM3 days Two correcting checks that each find the same 4 means the correction did not stick, so something is still handing back different data. I would not start a third correcting check yet. In that diagnostics zip, open the syslog and look for the disk that logged read errors or UNC during the check. That is the one to reseat or replace. A correcting check rewrites parity to match whatever was read, so the same four spots can show up again if the disk is still flaky.
Wednesday at 04:37 PM3 days Are you sure the 1st check was also correct? The diags only show one, so run another one without rebooting, and if there are still errors, post new diags.
Friday at 03:17 AM1 day Author So, I did a memetest86 and found out that one of my ram sticks were bad. I removed the faulty stick, but now my MongoDB docker container keeps stopping, Jellyfin’s web ui won’t open, and in Plex I have a ton of 4k that won’t play. I t just says playback error. Is it possible that operating my server while the ram was bad corrupted something? What step can I take to fix/troubleshoot this issue?
Friday at 07:43 AM1 day 4 hours ago, weezysteel said:Is it possible that operating my server while the ram was bad corrupted something?Possibly and likely, please post the current diagnostics.
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.