Just because I’m paranoid doesn’t mean they’re not out to get me!

Rebooted at 4:33 pm. We’ll see what the logs have to say.

I finally got the MS page about the errors. They both say “bad cable”, so I’ll start with that. Am I right in thinking there’s a single controller for both drives? I’m getting errors about the D drive, I think (assuming that’s what \Harddisk0\D means).

The errors go back to last july, but I think the logs truncate then. The errors probably go beyond that as well.

But if the errors go back to last July, that’s a different story. Is the server running RAID with parity? Perhaps there’s a problem with one of the disks in the array, but the controller is smart enough to keep things running, logging the errors in the meantime. Scandisk should be able to notice that one…

/half blind, grasping at straws

I looked at the error logs and there are controller parity errors going back as far as the log exists (last July). They seem to be increasing in number, though. That doesn’t make me feel too comfortable. I’m not quite sure what to do. Scandisk is still running. I’m really hoping there’s a bad sector on the disk, possibly the Nero location, but that doesn’t really explain why there are so many errors. I use Nero almost never. And I have doubts as to whether a bad disk sector would show up as a controller parity error.

There are also a lot of warnings saying something about an error on paging. I’m a bit confused about what that means as well. To me “paging” means system paging, but AFAICT, it’s complaining about the D drive. The paging files are on the C drive, I don’t think thereare any on the D drive. Unless “paging” here just means block transfer or something.

At least I have everything backed up now.

P.S. Holiday for you maybe. At least my commute was less crowded this morning.