weird problem

[ercw]

Mac G5 ppc OSX10.4.11

Starting up from any boot disk will give me a kernel panic forcing me to hard restart.

Background:

After many freezes I ran disk utility and I get:

Checking Catalog file.
Invalid index key
The volume Macintosh HD needs to be repaired.

Error: The underlying task reported failure on exit


1 HFS volume checked
Volume needs repair

So I use my wife's Imac startup disk to boot it in order to repair but I get the dreadfull death screen (I know how to press the C)
I'm thinking maybe it's because her disk if for her Intel proc so I go and buy a copy of disk warrior 4, and same problem.

 

[fernandovalente]

If the Mac OS X running on your wife's Mac came with the computer, you obviously won't be able to boot it on a G5. I'm not sure if you can boot your G5 onto an Intel Mac hard drive, the system won't probably start up. If the computer can't start from the specified disk, it will try another boot volume.

You should press C if you want your computer to start up from the CD/DVD drive, not from another hard drive.

Kernel panic may be caused by many things, including hardware issues.

You may repair your volume using Disk Utility from the Mac OS X install DVD. This is the best option for you.

Hope it helps.

 

[ercw]

Thanks, did just that using DiskWarrior but again, gave me a kernel panic using the standard procedure of starting from the DVD

 

[fernandovalente]

You probably got hardware problems. OK, It may be hard to do, but try running Apple Hardware Test. If it crashes, try a few more times. This can be many things, including RAM memory problems.

 

[ercw]

I should mention that this message has been appearing in the console lately:

Mac OS X Version 10.4.11 (Build 8S165)
2009-12-04 21:42:40 -0800
Dec 4 21:42:41 erics-Computer mDNSResponder: Adding browse domain local.
2009-12-04 21:42:42.042 SystemUIServer[134] lang is:en
Debugger() was called!
Debugger() was called!
Debugger() was called!
Debugger() was called!
Debugger() was called!
Debugger() was called!
Debugger() was called!