Unable to Install OS 10.2 (Jaguar) or OS 10.3 (Panther) on PowerBook G4

Question

Level 1

8 points

Unable to Install OS 10.2 (Jaguar) or OS 10.3 (Panther) on PowerBook G4

I was having issues with my PowerBook G4 Titanium (667 MHz) running OS 10.3 (Panther), see http://discussions.apple.com/message.jspa?messageID=5846471#5846471, so I zeroed and erased the harddrive before installing the original operating system, OS 10.1 (Puma). Using the Software Update feature, I updated to OS 10.1.5, verified/repaired permissions and the harddrive, and then updated firmware before proceeding to install OS 10.2 (Jaguar) using a full retail upgrade disk. The installation produced a kernel panic in the final stages, so I repeated the process from the beginning (zeroed and erased the harddrive, etc.). The second go-around, the installation hung up in the final stages (with 8 minutes to go, which went on for a good hour), until I received an Unexpected Error. (Exit Code 0). I restarted the computer while holding down the Option key to select the original OS 10.1 startup disk, and now my laptop starts up with the smiling mac icon and a crude black-and-white spinning sun. I used the Disk Utility feature to verify/repair permissions and the harddrive, but ejecting the Installation CD and attempting to start up still displays the smiling mac and crude sun.

I suspect the harddrive itself may be defective (at least that's what started this whole chain of events), but the Disk Utility verifies the harddrive. If it's not the harddrive (how else can I tell?), is there something else that may be impeding installation of OS 10.2?

My OS 10.3 is an upgrade CD, not a full retail installation DVD, so I am reluctant to try and jump from the original OS (10.1) to 10.3 without first installing 10.2. Or, is that possible?

Would I be able to install OS 10.2 using the full retail CD, or do I have to install the original, base OS (10.1) first?

I appreciate any advice the forum is willing to offer.

MacBook ProPowerBook G4 Titanium (667 MHz), Mac OS X (10.1.x)

Posted on Jun 25, 2008 11:38 AM

Reply

Answer 1

Kappy

Level 10

362,007 points

Jun 25, 2008 12:50 PM in response to gaznmick

You can indeed install Jaguar directly if you have the full retail installer package. No need to install an earlier version and upgrade. In fact I would not recommend trying to upgrade 10.1.x. Best to perform and Erase and Install of Jaguar. I would suggest using Disk Utility first to re-partition and reformat the hard drive before installing Jaguar. The procedure is:

Extended Hard Drive Preparation

1. Boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.

2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window. SMART status may not be reported in the Jaguar version of DU.

3. Set the number of partitions from the dropdown menu (use 1 partition unless you wish to make more.) Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the volume(s) mount on the Desktop.

4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.

5. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window. Now a caveat here is that I do not remember if you can actually zero out the hard drive with the Jaguar version of Disk Utility. If not simply ignore Steps 4-6.

6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.

After formatting quit DU and return to the installer. Complete the OS X installation.

Reply

Answer 2

gaznmick Author

Level 1

8 points

Jun 25, 2008 3:44 PM in response to Kappy

Thank you or the prompt reply, Kappy. Before I perform yet another Erase and Install, I thought I would respond with more details and ask a few follow-up questions.

My previous attempts to verify/repair the disk and disk permissions was on the volume and not the actual hard drive. The only error found on the volume was an "Invalid leaf record count" which was easily repaired (presumably) using the Jaguar OS X Installer Disc Disk Utility program.

Since the Jaguar OS X Installer Disc Disk Utility program does not display the SMART status, I tried using the Panther OS X Installer Disc, where I went ahead and verified/repaired both the hard drive and volume disks and permissions. I couldn't find a SMART status displayed anywhere; however, the same "Invalid leaf record count" error turned up on both the hard drive and the volume disks. It could not be repaired on either. Is that indicative of a hard drive failure? Do you think it is still okay to attempt an Erase and Install of OS 10.2?

I have never partitioned the hard drive before. Is that necessary / helpful?

Reply

Answer 3

Kappy

Level 10

362,007 points

Jun 25, 2008 3:51 PM in response to gaznmick

Disk Utility cannot repair an invalid leaf record error. You would need Disk Warrior to repair it. Without Disk Warrior you should instead reformat the drive. Do not attempt to install OS X until the drive has been correctly repaired or reformatted.

I believe that the Jaguar version of DU does not have the Zero Data options. However, the Panther version does. I would recommend using the Zero Data option (one pass only) because if there are any bad blocks on the disk this will identify and spare them out.

Repartitioning may not be necessary but given the circumstances I would do it anyway. It's easy to do. Just follow the instructions I provided.

Reply

Answer 4

gaznmick Author

Level 1

8 points

Jun 25, 2008 4:11 PM in response to Kappy

All roads seem to lead back to Disk Warrior...

I will attempt another Erase and Install using the Panther OS X Installation Disc, zeroing and (this time) partitioning the drive.

After I sent my last message, I connected my PowerBook G4 via Firewire and Target Disk Mode to my new MacBook Pro to see if I could read the SMART status using Disk Utility 11.1. It reads "Not Supported".

The PowerBook G4 disk mounted and I was able to view all of the files created as part of the (unfinished) installation process. Just for kicks, I verified and then repaired the hard drive, and the volume disk was verified error free. Nonetheless, when I started the PowerBook G4 I received yet another kernel panic.

I will let you know the results of the Erase / Partition / Install. Thanks again!

Reply

Answer 5

Kappy

Level 10

362,007 points

Jun 25, 2008 4:25 PM in response to gaznmick

SMART status information is not communicated over a Firewire interface. If the drive supports SMART you will only see its status directly from Disk Utility running from the computer itself. Either you must boot from the installer disc and run DU or boot from the computer and run DU.

Reply

Answer 6

gaznmick Author

Level 1

8 points

Jun 25, 2008 10:12 PM in response to Kappy

Thanks to your advice, I successfully erased, partitioned, and then installed OS 10.2. After installation, I verified and repaired permissions before running the Software Update, which included a number of programs. The Software Update resulted in a kernel panic. After verifying and repairing permissions yet again, I installed the various software updates individually, leaving the Mac OS X Update Combined (10.2.8) for last. All installed without a hitch. During the combo update, however, I received another kernel panic.

Do you recommend continuing the verify/repair/update process? Should I also verify/repair the disk using the Installation Disc Disk Utility? My goal is to ultimately upgrade from OS 10.2(.8?) to OS 10.3 using my upgrade CD.

Reply

Answer 7

Kappy

Level 10

362,007 points

Jun 26, 2008 12:36 AM in response to gaznmick

Kernel panics can be caused by any number of things. Most commonly it's bad RAM. Do you have at least 256 MBs of RAM installed? It would be useful to look at the panic.log using the Console application in the Utilities folder. The log may provide clues to the cause as might other console.log entries.

I would not proceed any further without first trying to ascertain the cause of the kernel panics.

Reply

Answer 8

gaznmick Author

Level 1

8 points

Jun 26, 2008 7:48 PM in response to Kappy

I have 1024 MB of RAM in the form of two (2) 512 MB chips which I installed shortly after purchasing my PowerBook G4 new some years ago (2002?).

In the event you can decipher the following, which I suspect you can, I am attaching both the finder.crash.log and pbs.crash.log, which I opened from the Console, as well as the Kernel Panic Log, which I opened in Apple System Profiler.

********

Date/Time: 2008-06-25 21:15:45 -0700
OS Version: 10.2 (Build 6C115)
Host: Gary-Huntzingers-Computer.local.

Command: Finder
PID: 384

Exception: EXC BADACCESS (0x0001)
Code[0]: 0x0000000aCode[1]: 0x01917000

Thread 0 Crashed:
#0 0x90519bf8 in _ZN17CIconStorageEntry17SetCompressedDataEmlPhl
#1 0x9051b6cc in _ZN22CIconStorageLocalEntry7SetDataElPcl
#2 0x90516b64 in _ZN17CIconStorageEntry16SetIconFamilyPtrEPK18IconFamilyResourcem
#3 0x9051fc30 in _ZN20CFileBasedIconLoaderC4EP17CIconStorageEntryPK5FSRefsmsPs
#4 0x905192e0 in _ISGetStorageByIconFile
#5 0x9300c8e8 in Z20GetStorageFromLSInfoPK5FSRefmmPK10_CFStringh
#6 0x9300681c in _Z16ISBuildBaseImagePK5FSRefPK12HFSUniStr255PmP13FSCatalogInfoP19CustomBadgeRes ource
#7 0x93008ed4 in GetImageForFSItem
#8 0x93007360 in GetIconRefFromFileInfo
#9 0x9073ab48 in _ZNK9TMetaData11ReadIconRefERP13OpaqueIconRefb
#10 0x90740be8 in _ZNK11THFSPlusRef11ReadIconRefERP13OpaqueIconRefb
#11 0x9073fcb0 in _ZNK13THFSPlusStore11ReadIconRefERP13OpaqueIconRef
#12 0x90737cc8 in _ZNK13THFSPlusStore10GetIconRefER18TPropertyReference
#13 0x90731d68 in _ZNK13THFSPlusStore11GetPropertyEmR18TPropertyReference
#14 0x90733578 in _ZNK5TNode11GetPropertyEmR18TPropertyReferenceRy
#15 0x90731f6c in _Z15GetNodePropertyPK13OpaqueNodeRefmPyR18TPropertyReference
#16 0x907359dc in GetNodePropertyAsIconRef
#17 0x000113fc in 0x113fc
#18 0x00004b54 in 0x4b54
#19 0x00007040 in 0x7040
#20 0x000128d8 in 0x128d8
#21 0x0000c4fc in 0xc4fc
#22 0x00022870 in 0x22870
#23 0x95020d6c in _ZN5LView4DrawEP15OpaqueRgnHandle
#24 0x95020d9c in _ZN5LView4DrawEP15OpaqueRgnHandle
#25 0x95020d9c in _ZN5LView4DrawEP15OpaqueRgnHandle
#26 0x95020d9c in _ZN5LView4DrawEP15OpaqueRgnHandle
#27 0x95020d9c in _ZN5LView4DrawEP15OpaqueRgnHandle
#28 0x95023f30 in _ZN7LWindow10UpdatePortEv
#29 0x000231e4 in 0x231e4
#30 0x000110dc in 0x110dc
#31 0x92ba25b4 in DispatchEventToHandlers
#32 0x92ba291c in SendEventToEventTargetInternal
#33 0x92ba5d28 in SendEventToEventTargetWithOptions
#34 0x92be6f10 in _Z17HandleWindowEventP14OpaqueEventRefm
#35 0x92bb209c in _Z29ToolboxEventDispatcherHandlerP25OpaqueEventHandlerCallRefP14OpaqueEventRefP v
#36 0x92ba266c in DispatchEventToHandlers
#37 0x92ba291c in SendEventToEventTargetInternal
#38 0x92bb4c88 in SendEventToEventTarget
#39 0x92bb6a4c in _Z22ToolboxEventDispatcherP14OpaqueEventRef
#40 0x92bc7f20 in CallEventDispatchHook
#41 0x92bb3484 in TryEventDispatcher
#42 0x92ba3ecc in GetOrPeekEvent
#43 0x92ba3b78 in GetNextEventMatchingMask
#44 0x92ba799c in WNEInternal
#45 0x92bad858 in WaitNextEvent
#46 0x00004340 in 0x4340
#47 0x00008c14 in 0x8c14
#48 0x00027cd8 in 0x27cd8
#49 0x00026d5c in 0x26d5c
#50 0x00026bdc in 0x26bdc

Thread 1:
#0 0x90042d68 in semaphore timedwait_signaltrap
#1 0x9003ef94 in pthread_condwait
#2 0x902300ec in MPWaitOnQueue
#3 0x90737084 in _ZN13TNodeSyncTask12SyncTaskProcEPv
#4 0x9025e538 in PrivateMPEntryPoint
#5 0x90021428 in pthreadbody

PPC Thread State:
srr0: 0x90519bf8 srr1: 0x0200f030 vrsave: 0x00000000
xer: 0x00000000 lr: 0x90519bd0 ctr: 0x00000000 mq: 0x00000000
r0: 0x000026b2 r1: 0xbfffd360 r2: 0x00000000 r3: 0x04e6eaee
r4: 0x00000012 r5: 0x00000000 r6: 0x00000003 r7: 0x01917d8d
r8: 0x000000ff r9: 0x00000017 r10: 0x04e7eaf1 r11: 0x04e75085
r12: 0x90580f40 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000002 r21: 0x00000000 r22: 0xa2ffc74c r23: 0x0000008e
r24: 0xbfffd760 r25: 0x00003ce5 r26: 0x00000000 r27: 0x00010000
r28: 0x00000012 r29: 0xbfffd7a0 r30: 0x01917000 r31: 0x90519b5c

********

Date/Time: 2008-06-25 21:15:39 -0700
OS Version: 10.2 (Build 6C115)
Host: Gary-Huntzingers-Computer.local.

Command: pbs
PID: 377

Exception: EXC BADACCESS (0x0001)
Codes: KERN INVALIDADDRESS (0x0001) at 0x00075e98

Thread 0:
#0 0x90074328 in mach msgtrap
#1 0x90006670 in mach_msg
#2 0x901490b0 in __CFRunLoopRun
#3 0x90181578 in CFRunLoopRunSpecific
#4 0x907f5a0c in -[NSRunLoop runMode:beforeDate:]
#5 0x90809244 in -[NSRunLoop run]
#6 0x00002dc8 in main
#7 0x00002a74 in _start
#8 0x000028f4 in start

Thread 1 Crashed:
#0 0x900052c8 in szone_malloc
#1 0x90005144 in malloc zonemalloc
#2 0x900112c4 in strdup
#3 0x90264618 in ZN10VolFSMount5initEv
#4 0x9025b898 in _ZN7FSMount4initEv
#5 0x9022da98 in Z11INITVOLUMEP10VolumeInfo
#6 0x90268c38 in _Z19MountInitialVolumesv
#7 0x90268b44 in Z16INITFileManagerv
#8 0x90236ea8 in _Z21GetVolFSVCBByVolumeIDm
#9 0x902324d0 in Z17PathGetObjectInfoPKcmPP10VolumeInfoPmS4_PcS4Ph
#10 0x90234b48 in _Z24FSPathMakeRefWithOptionsPKhmP5FSRefPh
#11 0x9014ac44 in _CFGetFSRefFromURL
#12 0x9014ab4c in CFURLGetFSRef
#13 0x9016d68c in _CFBundleCopyInfoDictionaryInResourceForkWithAllocator
#14 0x90177790 in CFBundleCopyInfoDictionaryForURL
#15 0x00005bb4 in processFile
#16 0x00006084 in processDirectory
#17 0x00006504 in processDirectories
#18 0x000068a8 in processRequestData
#19 0x00006fbc in make_services
#20 0x00008860 in _NSUpdateDynamicServices
#21 0x907fd32c in __NSFireDelayedPerform
#22 0x90163884 in __CFRunLoopDoTimer
#23 0x901493e8 in __CFRunLoopRun
#24 0x90181578 in CFRunLoopRunSpecific
#25 0x907f5a0c in -[NSRunLoop runMode:beforeDate:]
#26 0x90809244 in -[NSRunLoop run]
#27 0x00008538 in -[ServicesServer runServicesServer:]
#28 0x9081cd38 in forkThreadForFunction
#29 0x90021428 in pthreadbody

PPC Thread State:
srr0: 0x900052c8 srr1: 0x0200f030 vrsave: 0x00000000
xer: 0x20000000 lr: 0x9000528c ctr: 0x9005e930 mq: 0x00000000
r0: 0x00000000 r1: 0xf002c520 r2: 0x00000000 r3: 0x00000001
r4: 0x00000001 r5: 0x00000000 r6: 0x80808080 r7: 0x00000000
r8: 0x00000000 r9: 0xa0001054 r10: 0x00000000 r11: 0x00075e90
r12: 0x9005e930 r13: 0x00000000 r14: 0x00062110 r15: 0x00000001
r16: 0xf002dfa8 r17: 0xf002dfa4 r18: 0xf002dfa0 r19: 0xf002dfac
r20: 0xf002dc90 r21: 0x00000000 r22: 0xf002dca0 r23: 0x00000000
r24: 0x0005125c r25: 0xf002c560 r26: 0xa00051ac r27: 0x00000001
r28: 0x00051010 r29: 0x00051060 r30: 0x00061100 r31: 0x900051ac

Unresolved kernel trap(cpu 0): 0x600 - Alignment DAR=0x03ffcd8d PC=0x0008d544
Latest crash info for cpu 0:
Exception state (sv=0x28200C80)
PC=0x0008D544; MSR=0x00009030; DAR=0x03FFCD8D; DSISR=0x000000A0; LR=0x00022184; R1=0x18943710; XCP=0x00000018 (0x600 - Alignment)
Backtrace:
0x00022268 0x00023B4C 0x0003913C 0x001D11D0 0x001DB11C 0x00027450 0x00092B14 0x0002903C
0x0008FE90 0x0008FC4C 0x000926B8
Proceeding back via exception chain:
Exception state (sv=0x28200C80)
previously dumped as "Latest" state. skipping...
Exception state (sv=0x296D6280)
PC=0x9005E930; MSR=0x0000D030; DAR=0x0006CE49; DSISR=0x000000A0; LR=0x901812D8; R1=0xF00379A0; XCP=0x00000018 (0x600 - Alignment)

Interestingly enough, I hadn't suspected the RAM. I always thought it was the hard drive going out on me (which it may still be).

I ran an Extended Test using my Apple Hardware Test CD and it revealed the following error code: mem_2/4

I verified that the RAM shows up in my System Profile in Apple System Profiler. Is it possible one or both of the RAM chips is going bad? Is it possible that the built-in RAM is going bad?

Do you recommend I remove one or both of the RAM chips and then run the hardware test again? Are there memory tests other than the Apple Hardware Test CD that may be able to better pinpoint the problem?

Thanks again for your help.

Reply

Answer 9

Kappy

Level 10

362,007 points

Jun 26, 2008 8:49 PM in response to gaznmick

I don't really know what the log entries mean, but the panic.log is incomplete so I can't make head or tails of it.

The hardware test error is definitely a memory error, so I suspect you have one or two bad DIMMs. Remove one. Restart and operate for a while. If the panic recurs then remove the installed DIMM and replace it with the other one and retry. This will identify whether one or both DIMMs are bad. Be sure to operate long enough and under usual conditions to allow a panic to occur.

Reply

Answer 10

gaznmick Author

Level 1

8 points

Jun 27, 2008 4:39 PM in response to Kappy

I removed the top DIMM and ran a hardware test, which revealed the same mem_2/4 error. Then, I removed the bottom DIMM, returned the top DIMM, and ran another hardware test. No errors were detected. Running on only 512 MB in the top slot, I managed to update to OS 10.2.8, and then run all of the other software updates without experiencing any kernel panics. The Verify Disk feature also shows the disk as "OK."

It would appear that either the bottom DIMM or the slot itself is defective. I've read in the forum that this is a known issue for various PowerBook G4 models, just not mine.

It doesn't appear that the top and bottom DIMM switches are interchangeable, otherwise I'd swap them out to see if it is indeed the DIMM or the slot. I should still have the original 128 MB chip that shipped with the computer and that fits into the bottom slot, so I may insert that and see if the kernel panics return. I believe that you can only insert up to a 512 MB DIMM into each slot, correct? Is there any other way to determine if the DIMM itself is defective? I should try and locate the purchase paperwork because I believe they have lifetime warranties...

Anyway, I will attempt to upgrade to OS 10.3 next and will post the results. Thanks, again, for your advice.

<Edited by Moderator>

Reply