June 18, 20233 yr I find this confusing. Sadly, I don't believe I captured the syslog before shutting the server down. One of my disks scared me with a red X. I ordered new drives, pre-cleared them and started the server up, replacing the one drive. Rebuild went fine. (Which means the controller doesn't have an issue as it's on the same port). Then I took the "red x" drive and put it in my 2nd server. So far, no SMART Errors presented so I ran a quick self test and it says there are no errors. Now I'm running the extended test. My second server isn't vital; what would you do prior to deploying it again - if at all?
June 18, 20233 yr The Red X means that a write to the drive failed. By and large actual drive errors are exceedingly rare. Far more likely that the drive disconnected momentarily due to poor cabling (reseat the cables) which caused the issue, In other words, the system acted as it should have in the circumstances.
June 19, 20233 yr Author That seems to be what I'm observing. I forgot to mention that the error happened as my monthly parity check began, resulting on 2048 error before it aborted and got the red X label.
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.