More lossage

Volume 10, Issue 139; 15 Dec 2007; last modified 08 Oct 2010

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.

Comments

What do you mean, c'est la vie? C'est la vie en pomme, you mean.

—Posted by John Cowan on 16 Dec 2007 @ 12:00 UTC #

you know, stable again. "Like my Linux box used to be." What's the message there Norm?

—Posted by Dave Pawson on 16 Dec 2007 @ 08:34 UTC #

I think the message is mostly that I'm feeling cranky. Having a laptop crash randomly on a weekly or semi-weekly basis is seriously irritating. Losing a day recovering email caused by such a crash is seriously irritating.

Of course, to the extent that the underlying cause is a hardware problem, it's not really OS X's fault.

—Posted by Norman Walsh on 16 Dec 2007 @ 09:28 UTC #

I don't feel like renaming this weblog "Norm's gripes about broken hardware" so I won't post a new essay. But for those following along, the Mac needed more than a new disk. Maybe lots more. It'll be off at repair for a week. (Except this is the holiday season, so who knows how long a week will actually be.)

I spent all of yesterday afternoon configuring my desktop box to be a usable workstation again. Thank goodness that Linux can read HFS disks and SuperDuper! doesn't store backups in any kind of weird encrypted or compressed format.

This morning, my almost brand new LCD monitor died. That means I'm working on a partially configured machine with a small, hard-to-read monitor. Bah, humbug!

—Posted by Norman Walsh on 18 Dec 2007 @ 01:55 UTC #

My MBP purchased in August 2007 Tiger (Santa Rosa) and upgraded in november into leopard began showing a very serious slowdowns (JANUARY 2008), some applications have lost their icons and did not want to start. The log files informed on malformated files and the error code disk0s2: 0xe0030005 (UNDEFINED). appeared several times. Apple Care had to replace the hard disk (160GB 7200trs)

—Posted by Joel AZEMAR on 12 Jan 2008 @ 10:24 UTC #

Local Apple Care insisted my problem wasn't hardware. I've only had one crash since I rebuilt. Maybe they were right. I'm thinking I might take the leap to Leopard soonish.

—Posted by Norman Walsh on 12 Jan 2008 @ 01:48 UTC #