Took me 4 years to realize I was reading event logs wrong

I used to just scan for red X's and critical errors. Last week a server at work kept crashing and I couldn't find anything obvious. A sysadmin buddy told me to look at the warnings and informational events before the crash too. Found a pattern of disk warnings that led to a failing drive. Has anyone else missed something obvious because you only looked at errors?

2 comments

2 Comments

price.jake1mo ago

Oh man, I was exactly the same way. Used to think anything that wasn't a red error was just noise. Took a similar situation with a client's machine to finally get it through my head.

the_skyler1mo ago

Three times I had to rebuild Windows on my buddy's gaming rig before I got that the issue was a bad SATA cable all along, not any of the obvious errors... @price.jake I feel you on that client machine thing, sometimes it takes a real headache to really change how you look at things. It's funny how you can stare at the same kind of problem for years and then one weird case just flips a switch in your head. I still catch myself ignoring the little warnings sometimes though, old habits die hard.