February 27, 20251 yr This morning I logged in and found that the system was running a correcting parity check and had corrected 1888 sync errors. This was not a scheduled parity check. I performed a clean shut down the other day to remove a few cache drives I had replaced. Turned the system on and didn't notice it started a correcting check. I ran a non correcting check a few weeks ago and found zero errors. My question is how screwed am I if these sync errors were not actual errors. Can I be sure that there is no corruption caused or is it far too late? Is it really this easy to cause corruption if you don't catch the system starting a correcting check? tower-syslog-20250227-1527.zip
February 27, 20251 yr Feb 25 15:51:16 Tower emhttpd: unclean shutdown detected A few sync errors are normal after an unclean shutdown.
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.