Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

jk2addict (4946)

jk2addict
  (email not shown publicly)
http://today.icantfocus.com/blog/
AOL IM: chrislaco (Add Buddy, Send Message)
Yahoo! ID: chrislaco@sbcglobal.net (Add User, Send Message)
Jabber: laco@scribblewerks.com

Journal of jk2addict (4946)

Thursday April 05, 2007
07:56 AM

Ghost in the Machine

[ #32914 ]
I have a conspiracy theory: IBM puts time bombs in their RAID hardware. Sounds silly right? Here me out. For the second time in 6 months, I've seen this pattern with older ServeRAID cards/drives/enclosure.
  1. MSSQL Database file currupts itself. CHECKDB fixes it. Machine is fine for a few days. No hardware errors about drives.
  2. MSSQL Database file corrupts itself again. Reboot machine. Chkdsk /XRF finds no file system or sector errors. CHECKDB fixes the issues. Upgrade RAID firmware/drivers.
  3. MSSQL Database file corrupts itself again. Reboot machine. Chkdsk /XRF finds no file system or sector errors. CHECKDB fixes the issues. Install new RAID controller.
  4. MSSQL Database file corrupts itself again. Reboot machine. Chkdsk /XRF finds no file system or sector errors. CHECKDB fixes the issues. Move everything to new machine. Problems cease.

Again, I've seen this pattern TWICE. Both times, no SQL/Windows updates or patches were applied nor were any drivers/firmwares updated before the problems started for at least 6 months. Dear St. Murphy: Die.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.