GilaMonster (5/7/2014)
Corruption is 99.99% IO subsystem problem. Not necessarily the disks, could be anything anywhere in the IO stack.Since you mentioned an uncontrolled shutdown, I'd check and make sure all write caches are battery-backed (with working batteries) or disabled.
Without seeing the full results of a CheckDB (not one run with repair), it's very, very hard to say more. There's not enough information.
I agree. But given the extent of the problem (pun intended 😛 ) I doubt it is from the shutdown itself, or even multiple unexpected shutdowns. This seems systemic, and that goes to entire-IO-stack firmware and drivers (and maybe other stuff you may have on your system like antivirus, disk defraggers, file-filter-driver thingies. It could also be a bad chip somewhere leading to corruptions too, but that is WAY less likely than firmware/drivers.
It is a virtual certainty that you will continue to get these errors until you patch everything. And honestly I would IMMEDIATELY take this system offline and never use it for any work I cared about again until I had beat the sh!t out of it to validate that my patching everything in sight prevented any errors from occurring. And maybe not even then.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service