http://norman.walsh.name/2007/12/15/moreLossage 10 139 2007-12-15T16:24:18-05:00 $Date$ Norman Walsh 2007 Norman Walsh The evidence, the likely culprit, and the annoying tale of repair. Another kernel panic. Several too many now. A little digging revealed evidence, in the form of a panic.log: Sat Dec 15 13:09:52 2007 panic(cpu 0 caller 0x002EDAE4): btree_journal_modify_block_end: about to write corrupt node! Backtrace, Format - Frame : Return Address (4 potential args on stack) 0x485739b8 : 0x128d0d (0x3cc65c 0x485739dc 0x131f95 0x0) 0x485739f8 : 0x2edae4 (0x3e7218 0x6aafe70 0x1 0x2) … and some suspicious lines in the system.log: Dec 1 15:56:12 traytable kernel[0]: disk0s2: 0xe0030005 (UNDEFINED). Dec 1 15:56:12 traytable kernel[0]: disk0s2: 0xe0030005 (UNDEFINED). Dec 1 15:56:12 traytable kernel[0]: disk0s2: 0xe0030005 (UNDEFINED). Dec 1 15:56:12 traytable kernel[0]: disk0s2: 0xe0030005 (UNDEFINED). … December first is a while back, so the gun isn't so much smoking as in plain sight. Anyway, that data plus some web searching are enough to convince me that the disk is bad. AppleCare is going to fix it and there's now an Apple store just a couple of towns over, so that's good. Not so good is the fact that they don't have a replacement drive in stock and they won't order one before the “geniuses” actually looks at my laptop. That means it'll be a two-trip affair to get it fixed, but c'est la vie. Hopefully it'll make my Mac, you know, stable again. Like my Linux box used to be.