Posted: Sat Feb 10, 2007 12:04 pm Post subject: iMac 233 will not shut down after 10.4 install.
Hi,
Here are the steps taken, so far:
1. Partitioned new 200GB HD in an iMac 233 into 'OSX', 'OS9' and 'Install'.
(Only 128GB are available, as expected.)
2. Installed OS 9.2.2 onto the 'OS9' partition from OS 9 Install CD.
3. Installed XPostFacto onto same partition.
4. Attached an external USB DVD ROM (the iMac only has a CD drive).
5. Copied all files from the 10.4 DVD (full version) to 'Install' partition.
6. Rebooted into OS 9. Launched XPostFacto.
7. Selected OS 10.4 on 'Install' partition from within XPostFacto to boot from.
8. Rebooted and installed OS 10.4 seemingly flawlessly onto 'OSX' partition.
9. Rebooted into OS 10.4 from 'OSX' partition. Booted seemingly flawlessly.
10. Apps all seem to work great with the single exception of Software Update. (I will be posting a separate topic for this, next.)
11. Attempted to shut down the computer. Result...
All of the OS's desktop iconography disappears as if the machine is going to shutdown, but the desktop background image remains on screen and the mouse icon remains visible. The mouse icon responds to mouse movement, but nothing else can be done. Even after a long wait, the machine never actually shuts down.
Eventually, I pulled the plug, and rebooted off of an OS 9 Install CD. Ran OS 9's Disk Utility, because I couldn't think of anything else to do, and got reports of major errors on the 'OSX' partition. Assuming that the drive might have been corrupted by my forced shutdown, I reformat the entire drive and repeat the entire install process from the beginning. Same EXACT results.
What can I provide by way of further information or log reporting that would help to resolve this issue? Thank you for any and all help!
Posted: Wed Feb 14, 2007 2:14 pm Post subject: Further Info
To be specific, the errors generated by OS 9's Disk Utility are as follows:
Problem: Invalid LEOF, 9078, 6653
Wrapper System File needs to be replaced, 0, 0
Of course, I have no idea whether OS 9's Disk Utility is even propperly capable of evaluating the health of an OS X Journaled partition, so I'm not even sure if this has any relevance. Any support would be very much appreciated, as I have to return this computer to its rightful owner in a working state soon!
I've never worked on an iMac myself, but as you're in a hurry, here's my try to help.
I can't tell you why that wrapper file got damaged (twice). But - if you can get your hands on a DiskWarrior CD, you might have a chance to repair the wrapper. While it depends on how much damage had been done, DW can often successfully do wrapper repairs.
Once the wrapper is repaired, the OS on that partition has a good chance to work ok.
A Mac OS Extended (HFS Plus) disk has a Mac OS Standard (HFS) wrapper. When you make an HFS Plus disk the startup disk, the abbreviated System file in its wrapper is accessed as part of the startup process. Startup code in the wrapper System file is used to access the "real" System file in the System Folder of the embedded HFS Plus partition. Note that every wrapper contains a System file regardless of whether the disk is used as a startup disk.
A bug in one version of the wrapper System file startup code can prevent the real System file from being found when the disk directory or the real System file is fragmented into more than 8 extents. The result is an inability to start up from the disk.
The wrapper System file bug only affects startup disks that are initialized when running under Mac OS 9.0 through 9.0.4. It doesn't matter whether you initialize the disk with the Mac OS installer, the Finder, Drive Setup, Disk First Aid or any other utility. All that matters is that you're running some version of Mac OS 9.0. That's because when you initialize a disk, the wrapper System file is created with startup code that is copied from the current System file. Only the Mac OS 9.0.x System file contains the errant wrapper System file startup code.
Few startup disks have sufficient fragmentation to be affected by the startup bug. Regardless, the new Disk First Aid 8.6 will report that any wrapper System file created under Mac OS 9.0.x needs to be replaced. It
doesn't matter whether there is enough fragmentation to cause a start up problem or if the disk is even a startup disk. In fact, you can initialize an HFS Plus disk under Mac OS 9.0.x and then immediately run Disk First Aid 8.6 and you'll see that it reports that the wrapper System file needs to be replaced. It also reports that the disk needs to be repaired. This should not be interpreted as damage to the directory or to the wrapper System file..
Because only disks that were initialized while started under Mac OS 9.0.x have the bug, Disk First Aid 8.6 corrects the startup problem by replacing the wrapper System file startup code with the startup code that was in Mac OS 8.6 (the similarity in the Disk First Aid and Mac OS version numbers is purely coincidental).
When Disk First Aid is done, it's as if the disk was initialized while started under Mac OS 8.6. If the disk is a startup disk, the real System file is not modified by Disk First Aid. Note that having a disk with a wrapper System file containing Mac OS 8.6 startup code does not create any compatibility problems with any version of Mac OS 9.
My instinct tells me that the primary problem lies with the shutdown process, but let's stay with the drive itself for a few more seconds. First, can you say, for a fact, that OS X can be installed on a partition created using OS 9 tools? Is the format of an Apple extended, journaled, partition unchanged? Or does OS X reformat the partition as it begins to install itself?
According to the documentation above, it should be coming as no surprise that I am receiving the wrapper error. But, when I try to repair using OS 9's Disk Utility, it can't successfully complete the repair, as the documentation recommends.
Also, I am using a 200GB drive. Only 128GB are recognized. When I place the drive limiter pin onto the drive, the drive then only appears to have a much smaller size; I forget the exact number, but it was something like 80GB, if I recall, from my first experiments. I am presently running the drive without the limiter to get the 128GB. Is there anything about the large drive size that may be contributing to this problem?
Finally, getting back to my first concern, should any of this be affecting the computer's ability to shut down? I can understand that these drive errors would certainly affect startup.
Thank you again for your assistance, and to any others who contribute. Meanwhile, I will continue a search for a copy of DiskWarrior.
I didn't know about the wrapper probs in early OS9 versions, I went straight to 9.1 (from 8.6) and then further to 9.2.2 on all my Macs. Must be ages ago, now...
Quote:
...can you say, for a fact, that OS X can be installed on a partition created using OS 9 tools? Is the format of an Apple extended, journaled, partition unchanged? Or does OS X reformat the partition as it begins to install itself?
Using "Drive Setup" that came with OS9.1 (or later) is perfectly ok, Ryan recommends it. In fact, all drives in my (OS9 capable) Macs were set up that way. Worked fine on 10.2 .. 10.4 so far.
Btw., the "journaled" attribute does not have to be set up during the volume's initialisation. It can, in fact, be switched on/off at any time later on.
As for the reformat on OSX installation: the installer does not do it by default. When you select the drive to install to, you can tell the installer to reformat that volume first, that's what the "Options" button is for. But if you are doing an install on an unsupported Mac via XPF, you MUST NOT do this, anyway. All the "special preparation" done by XPF would get wiped, too.
Quote:
...Also, I am using a 200GB drive.
.... I am presently running the drive without the limiter to get the 128GB. Is there anything about the large drive size that may be contributing to this problem?
That should be ok, too. Can't think of any reason why this could cause problems, and I do know people with older iMacs who have a perfecly working system with a big replacement drive of which only 128MB are "seen" and used.
Quote:
Finally, getting back to my first concern, should any of this be affecting the computer's ability to shut down?....
I can only guess here. When the OS is shutting down, a lot of writing to disk is going on, especially work on various log files. Maybe it's just only then, that some routine stumbles across the (for whatever reason) damaged wrapper.
One last thing. From your first post:
"8. Rebooted and installed OS 10.4 seemingly flawlessly onto 'OSX' partition.
9. Rebooted into OS 10.4 from 'OSX' partition. Booted seemingly flawlessly."
Right before #9 I'd force the reboot to go to OS9 by pressing the Option key. Start XPF, chose your OSX partition to boot there and tell XPF to re-install "Everything" (from the menu) before clicking the reboot button.
Hi. Thank you again for following this thread, and providing assistance. I have blanked the drive, repartitioned, and reinstalled. This time, I checked the OS_X partition with Disk Utility BEFORE installing OS X. There was my old friend - the wrapper error. I was able to repair it with no problems on the otherwise empty partition with no problems.
I installed OS X. Immediately repaired permissions:
Code:
Repairing permissions for “OS_X”
Determining correct file permissions.
Permissions differ on ./System/Library/Filesystems/cddafs.fs/Contents/Resources/cddafs.util, should be -r-xr-xr-x , they are ----------
Owner and group corrected on ./System/Library/Filesystems/cddafs.fs/Contents/Resources/cddafs.util
Permissions corrected on ./System/Library/Filesystems/cddafs.fs/Contents/Resources/cddafs.util
Permissions differ on ./bin/[, should be -r-xr-xr-x , they are ----------
Owner and group corrected on ./bin/[
Permissions corrected on ./bin/[
Permissions differ on ./bin/csh, should be -r-xr-xr-x , they are ----------
Owner and group corrected on ./bin/csh
Permissions corrected on ./bin/csh
Permissions differ on ./bin/link, should be -r-xr-xr-x , they are ----------
Owner and group corrected on ./bin/link
Permissions corrected on ./bin/link
Permissions differ on ./bin/ln, should be -r-xr-xr-x , they are ----------
Owner and group corrected on ./bin/ln
Permissions corrected on ./bin/ln
Permissions differ on ./bin/pax, should be -r-xr-xr-x , they are ----------
Owner and group corrected on ./bin/pax
Permissions corrected on ./bin/pax
Permissions differ on ./bin/rm, should be -r-xr-xr-x , they are ----------
Owner and group corrected on ./bin/rm
Permissions corrected on ./bin/rm
Permissions differ on ./bin/tcsh, should be -r-xr-xr-x , they are ----------
Owner and group corrected on ./bin/tcsh
Permissions corrected on ./bin/tcsh
Permissions differ on ./bin/test, should be -r-xr-xr-x , they are ----------
Owner and group corrected on ./bin/test
Permissions corrected on ./bin/test
Permissions differ on ./bin/unlink, should be -r-xr-xr-x , they are ----------
Owner and group corrected on ./bin/unlink
Permissions corrected on ./bin/unlink
Permissions differ on ./bin/zsh, should be -rwxr-xr-x , they are ----------
Owner and group corrected on ./bin/zsh
Permissions corrected on ./bin/zsh
Permissions differ on ./bin/zsh-4.2.3, should be -rwxr-xr-x , they are ----------
Owner and group corrected on ./bin/zsh-4.2.3
Permissions corrected on ./bin/zsh-4.2.3
Permissions differ on ./sbin/dump, should be -r-xr-xr-x , they are ----------
Owner and group corrected on ./sbin/dump
Permissions corrected on ./sbin/dump
Permissions differ on ./sbin/halt, should be -r-xr-xr-x , they are ----------
Owner and group corrected on ./sbin/halt
Permissions corrected on ./sbin/halt
Permissions differ on ./sbin/mount_cddafs, should be -r-xr-xr-x , they are ----------
Owner and group corrected on ./sbin/mount_cddafs
Permissions corrected on ./sbin/mount_cddafs
Permissions differ on ./sbin/rdump, should be -r-xr-xr-x , they are ----------
Owner and group corrected on ./sbin/rdump
Permissions corrected on ./sbin/rdump
Permissions differ on ./sbin/reboot, should be -r-xr-xr-x , they are ----------
Owner and group corrected on ./sbin/reboot
Permissions corrected on ./sbin/reboot
Group differs on ./sbin/restore, should be 4, group is 0
Permissions differ on ./sbin/restore, should be -r-sr-sr-x , they are ----------
Owner and group corrected on ./sbin/restore
Permissions corrected on ./sbin/restore
Group differs on ./sbin/rrestore, should be 4, group is 0
Permissions differ on ./sbin/rrestore, should be -r-sr-sr-x , they are ----------
Owner and group corrected on ./sbin/rrestore
Permissions corrected on ./sbin/rrestore
Permissions differ on ./usr/bin/arch, should be -r-xr-xr-x , they are ----------
Owner and group corrected on ./usr/bin/arch
Permissions corrected on ./usr/bin/arch
Permissions differ on ./usr/bin/cpio, should be -r-xr-xr-x , they are ----------
Owner and group corrected on ./usr/bin/cpio
Permissions corrected on ./usr/bin/cpio
Permissions differ on ./usr/bin/gnutar, should be -rwxr-xr-x , they are ----------
Owner and group corrected on ./usr/bin/gnutar
Permissions corrected on ./usr/bin/gnutar
Permissions differ on ./usr/bin/machine, should be -r-xr-xr-x , they are ----------
Owner and group corrected on ./usr/bin/machine
Permissions corrected on ./usr/bin/machine
Permissions differ on ./usr/bin/tar, should be -rwxr-xr-x , they are ----------
Owner and group corrected on ./usr/bin/tar
Permissions corrected on ./usr/bin/tar
The privileges have been verified or repaired on the selected volume
Permissions repair complete
This time, I was able to get it to be a bit more responsive, and was able to collect some logging before it crapped out on me. Again, my problem has been that the system seems to hang on a shutdown request. Pertinent log records:
Code:
Mar 4 11:10:38 imac SystemStarter[440]: The following StartupItems failed to properly start:
Mar 4 11:10:38 imac SystemStarter[440]: /System/Library/StartupItems/AuthServer
Mar 4 11:10:38 imac SystemStarter[440]: - execution of Startup script failed
Mar 4 11:10:38 imac shutdown: shutdown: can't exec /sbin/reboot: Exec format error.
Then, it hangs on my next reboot. I pull the plug, and it boots on the second try. Boot log:
Code:
Mar 4 07:40:08 localhost kernel[0]: standard timeslicing quantum is 10000 us
Mar 4 07:40:07 localhost DirectoryService[56]: Launched version 1.8 (v346)
Mar 4 07:40:08 localhost kernel[0]: vm_page_bootstrap: 18489 free pages
Mar 4 07:40:08 localhost kernel[0]: mig_table_max_displ = 70
Mar 4 07:40:08 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Mar 4 07:40:09 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Mar 4 07:40:09 localhost kernel[0]: using 256 buffer headers and 256 cluster IO buffer headers
Mar 4 07:40:09 localhost kernel[0]: USBF: 31.728 AppleUSBOHCI[0x1871000]::start OHCI controller will be unloaded across sleep
Mar 4 07:40:08 localhost lookupd[66]: lookupd (version 365) starting - Sun Mar 4 07:40:08 2007
Mar 4 07:40:09 localhost kernel[0]: Extension "com.apple.driver.HeathrowATA" has no kernel dependency.
Mar 4 07:40:09 localhost kernel[0]: Security auditing service present
Mar 4 07:40:09 localhost kernel[0]: BSM auditing present
Mar 4 07:40:09 localhost kernel[0]: disabled
Mar 4 07:40:09 localhost kernel[0]: rooting via boot-uuid from /chosen: 097B48D0-1AF7-3940-AF3B-9D5210B1553E
Mar 4 07:40:09 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Mar 4 07:40:09 localhost kernel[0]: ADB present:0
Mar 4 07:40:09 localhost kernel[0]: Extension "com.apple.iokit.IOUSBMassStorageClass" has no kernel dependency.
Mar 4 07:40:09 localhost kernel[0]: in6_ifattach: lo0 failed to attach a linklocal address.
Mar 4 07:40:09 localhost kernel[0]: Got boot device = IOService:/GossamerPE/pci@80000000/AppleGracklePCI/mac-io@10/Heathrow/ide@20000/HeathrowATA/ATADeviceNub@0/IOATABlockStorageDriver/IOATABlockStorageDevice/IOBlockStorageDriver/Maxtor 6L200P0 Media/IOApplePartitionScheme/untitled 2@8
Mar 4 07:40:09 localhost kernel[0]: BSD root: disk0s8, major 14, minor 8
Mar 4 07:40:09 localhost kernel[0]: HFS: created HFBT on OS_X
Mar 4 07:40:09 localhost kernel[0]: BootCache: cache init failed
Mar 4 07:40:09 localhost kernel[0]: Jettisoning kernel linker.
Mar 4 07:40:09 localhost kernel[0]: Resetting IOCatalogue.
Mar 4 07:40:09 localhost kernel[0]: Matching service count = 0
Mar 4 07:40:09 localhost kernel[0]: Matching service count = 1
Mar 4 07:40:09 localhost kernel[0]: Matching service count = 1
Mar 4 07:40:09 localhost kernel[0]: Matching service count = 1
Mar 4 07:40:09 localhost kernel[0]: Matching service count = 1
Mar 4 07:40:09 localhost kernel[0]: ROM ndrv for ATY,RagePro_C is too old (0xb34623ea)
Mar 4 07:40:11 localhost kernel[0]: BMacEnet: Ethernet address 00:05:02:1f:8e:89
Mar 4 07:40:11 localhost diskarbitrationd[51]: disk0s7 hfs 49252677-8305-3DFD-9D58-BAA04B0FE887 OS_9 /Volumes/OS_9
Mar 4 07:40:11 localhost diskarbitrationd[51]: disk0s8 hfs 097B48D0-1AF7-3940-AF3B-9D5210B1553E OS_X /
Mar 4 07:40:11 localhost diskarbitrationd[51]: disk0s9 hfs DD0AE9CC-6986-3E42-BC14-5ED72CDC99AA Mac OS X Install DVD /Volumes/Mac OS X Install DVD
Mar 4 07:40:11 localhost launchd: Server 2727 in bootstrap 1103 uid 0: "/usr/sbin/lookupd"[66]: exited abnormally: Hangup
Mar 4 07:40:12 localhost kernel[0]: AppleCuda_AutoRestartOnPowerLossSetting - entered
Mar 4 07:40:13 localhost lookupd[87]: lookupd (version 365) starting - Sun Mar 4 07:40:13 2007
Mar 4 07:40:13 localhost /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
Mar 4 07:40:15 localhost kernel[0]: BMacEnet::monitorLinkStatus: Link up at 100 Mbps - Full Duplex
Mar 4 07:40:15 localhost mDNSResponder: Couldn't read user-specified Computer Name; using default “Macintosh-0005021F8E89” instead
Mar 4 07:40:15 localhost mDNSResponder: Couldn't read user-specified local hostname; using default “Macintosh-0005021F8E89.local” instead
Mar 4 07:40:17 localhost kernel[0]: ATY,RagePro_C: vram [81800000:00800000]
Mar 4 07:40:18 localhost mDNSResponder: Couldn't read user-specified Computer Name; using default “Macintosh-0005021F8E89” instead
Mar 4 07:40:18 localhost mDNSResponder: Couldn't read user-specified local hostname; using default “Macintosh-0005021F8E89.local” instead
Mar 4 07:40:18 localhost mDNSResponder: Adding browse domain local.
Mar 4 07:40:19 localhost launchd: Server 3e17 in bootstrap 1103 uid 0: "/usr/sbin/lookupd"[87]: exited abnormally: Hangup
Mar 4 07:40:19 localhost configd[49]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-network
Mar 4 07:40:19 localhost configd[49]: posting notification com.apple.system.config.network_change
Mar 4 07:40:19 localhost lookupd[92]: lookupd (version 365) starting - Sun Mar 4 07:40:19 2007
Mar 4 07:40:21 localhost mDNSResponder: Couldn't read user-specified Computer Name; using default “Macintosh-0005021F8E89” instead
Mar 4 07:40:21 localhost mDNSResponder: Couldn't read user-specified local hostname; using default “Macintosh-0005021F8E89.local” instead
Mar 4 07:40:22 localhost configd[49]: target=enable-network: disabled
Mar 4 07:40:24 localhost KernelEventAgent[57]: tid 00000000 received unknown event (256)
Mar 4 07:40:25 localhost KernelEventAgent[57]: tid 00000000 received unknown event (256)
Mar 4 07:40:25 localhost KernelEventAgent[57]: tid 00000000 received unknown event (256)
Mar 4 07:40:41 localhost kernel[0]: AppleCuda_AutoRestartOnPowerLossSetting - entered
Mar 4 07:42:08 localhost /System/Library/CoreServices/Setup Assistant.app/Contents/MacOS/Setup Assistant: _MDSuspendIndexing() 1
Mar 4 07:42:10 localhost /System/Library/CoreServices/Setup Assistant.app/Contents/MacOS/Setup Assistant: starting movie now
Mar 4 07:42:41 localhost /System/Library/CoreServices/Setup Assistant.app/Contents/MacOS/Setup Assistant: movie done now (hide)
Mar 4 07:45:14 localhost kernel[0]: AppleSCCSerial: gTimerCanceled set to Zero
Mar 4 07:45:24 localhost ntpdate[256]: no servers can be used, exiting
Mar 4 07:47:23 imac configd[49]: setting hostname to "imac.local"
Mar 4 10:51:42 imac /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/Support/LAServer.app/Contents/MacOS/LAServer: kCGErrorInvalidConnection : CGSGetNextEventRecord: Invalid connection
Mar 4 10:51:43 imac /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
Mar 4 10:51:47 imac loginwindow[342]: Login Window Started Security Agent
There seem to be a number of issues including broken kernel dependencies, issues with the lookupd daemon, BootCache cache init failing, RagePro_C being too old, and problems with mDNSResponder, just to list a few. A forced restart gets a bit better of a result:
Code:
Mar 4 12:15:36 localhost kernel[0]: standard timeslicing quantum is 10000 us
Mar 4 12:15:36 localhost lookupd[61]: lookupd (version 365) starting - Sun Mar 4 12:15:36 2007
Mar 4 12:15:36 localhost kernel[0]: vm_page_bootstrap: 21353 free pages
Mar 4 12:15:36 localhost mDNSResponder-107 (Mar 20 2005 20: 31:47)[64]: starting
Mar 4 12:15:36 localhost kernel[0]: mig_table_max_displ = 70
Mar 4 12:15:36 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Mar 4 12:15:36 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Mar 4 12:15:36 localhost kernel[0]: using 256 buffer headers and 256 cluster IO buffer headers
Mar 4 12:15:36 localhost kernel[0]: USBF: 19.403 AppleUSBOHCI[0xd54000]::start OHCI controller will be unloaded across sleep
Mar 4 12:15:36 localhost kernel[0]: Extension "com.apple.driver.HeathrowATA" has no kernel dependency.
Mar 4 12:15:36 localhost kernel[0]: Security auditing service present
Mar 4 12:15:36 localhost kernel[0]: BSM auditing present
Mar 4 12:15:36 localhost kernel[0]: disabled
Mar 4 12:15:36 localhost kernel[0]: rooting via boot-uuid from /chosen: 097B48D0-1AF7-3940-AF3B-9D5210B1553E
Mar 4 12:15:36 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Mar 4 12:15:36 localhost kernel[0]: ADB present:0
Mar 4 12:15:36 localhost kernel[0]: Extension "com.apple.iokit.IOUSBMassStorageClass" has no kernel dependency.
Mar 4 12:15:36 localhost kernel[0]: Got boot device = IOService:/GossamerPE/pci@80000000/AppleGracklePCI/mac-io@10/Heathrow/ide@20000/HeathrowATA/ATADeviceNub@0/IOATABlockStorageDriver/IOATABlockStorageDevice/IOBlockStorageDriver/Maxtor 6L200P0 Media/IOApplePartitionScheme/untitled 2@8
Mar 4 12:15:36 localhost kernel[0]: BSD root: disk0s8, major 14, minor 8
Mar 4 12:15:36 localhost kernel[0]: jnl: journal start/end pointers reset! (jnl 0xf5fe60; s 0xd5f200 e 0x494800)
Mar 4 12:15:36 localhost kernel[0]: BootCache: cache init failed
Mar 4 12:15:36 localhost kernel[0]: Jettisoning kernel linker.
Mar 4 12:15:36 localhost kernel[0]: Resetting IOCatalogue.
Mar 4 12:15:36 localhost kernel[0]: Matching service count = 0
Mar 4 12:15:36 localhost kernel[0]: Matching service count = 1
Mar 4 12:15:36 localhost kernel[0]: Matching service count = 1
Mar 4 12:15:36 localhost kernel[0]: Matching service count = 1
Mar 4 12:15:36 localhost kernel[0]: Matching service count = 1
Mar 4 12:15:36 localhost kernel[0]: ROM ndrv for ATY,RagePro_C is too old (0xb34623ea)
Mar 4 12:15:36 localhost kernel[0]: ATY,RagePro_C: match category IOFramebuffer exists
Mar 4 12:15:36 localhost kernel[0]: IPv6 packet filtering initialized, default to accept, logging disabled
Mar 4 12:15:36 localhost DirectoryService[62]: Launched version 1.8 (v346)
Mar 4 12:15:40 localhost kernel[0]: BMacEnet: Ethernet address 00:05:02:1f:8e:89
Mar 4 12:15:40 localhost launchd: Server 3143 in bootstrap 1103 uid 0: "/usr/sbin/lookupd"[61]: exited abnormally: Hangup
Mar 4 12:15:40 localhost diskarbitrationd[56]: disk0s7 hfs 49252677-8305-3DFD-9D58-BAA04B0FE887 OS_9 /Volumes/OS_9
Mar 4 12:15:40 localhost diskarbitrationd[56]: disk0s8 hfs 097B48D0-1AF7-3940-AF3B-9D5210B1553E OS_X /
Mar 4 12:15:40 localhost lookupd[91]: lookupd (version 365) starting - Sun Mar 4 12:15:40 2007
Mar 4 12:15:40 localhost diskarbitrationd[56]: disk0s9 hfs DD0AE9CC-6986-3E42-BC14-5ED72CDC99AA Mac OS X Install DVD /Volumes/Mac OS X Install DVD
Mar 4 12:15:41 localhost kernel[0]: AppleCuda_AutoRestartOnPowerLossSetting - entered
Mar 4 12:15:43 localhost kernel[0]: ATY,RagePro_C: vram [81800000:00800000]
Mar 4 12:15:43 localhost kernel[0]: BMacEnet::monitorLinkStatus: Link up at 100 Mbps - Full Duplex
Mar 4 12:15:43 imac configd[54]: setting hostname to "imac.local"
Mar 4 12:15:47 imac mDNSResponder: Adding browse domain local.
Mar 4 12:15:48 imac launchd: Server 3153 in bootstrap 1103 uid 0: "/usr/sbin/lookupd"[91]: exited abnormally: Hangup
Mar 4 12:15:48 imac configd[54]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-network
Mar 4 12:15:48 imac configd[54]: posting notification com.apple.system.config.network_change
Mar 4 12:15:48 imac lookupd[97]: lookupd (version 365) starting - Sun Mar 4 12:15:48 2007
Mar 4 12:15:49 imac ntpdate[109]: no servers can be used, exiting
Mar 4 12:15:53 imac configd[54]: target=enable-network: disabled
Mar 4 12:15:54 imac /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
Mar 4 12:16:40 imac kernel[0]: AppleCuda_AutoRestartOnPowerLossSetting - entered
Mar 4 12:16:41 imac loginwindow[140]: Login Window Started Security Agent
Still not great. I then make an attempt to use software update. No go. Error returned is:
Code:
Software Update could not expand the package correctly.
I am familiar with this error, and try some workarounds. No luck. The related system log references for my first attempt are:
Mar 4 12:24:31 imac crashdump[275]: Software Update crashed
Mar 4 12:24:38 imac crashdump[275]: crash report written to: /Users/imac/Library/Logs/CrashReporter/Software Update.crash.log
I download the combo update, security updates, etc. manually, and run them. All is going when, but at some point I have to reboot...and it won't. I manage to get the following related log lines:
Code:
Mar 4 12:41:09 imac kernel[0]: Creating HFS+ Attribute B-tree File (153 nodes) on OS_X
Mar 4 13:00:09 imac shutdown: reboot by imac:
Mar 4 13:00:12 imac SystemStarter[563]: authentication service (576) did not complete successfully
I reboot into OS 9. Disk utility tells me I've got bad B-tree records. Repair seems to go well, but I can tell it's not really being repaired. Computer will no longer start! Arrggggghhhhh!
This all brings me to an observation and another question. When loading the OS X DVD in the OS 9 environment, directories and files longer than 32 characters are renamed with something like #1234 in the name. I get the concept behind this, but could this be causing problems any of these problems?
I've now got about 80 hours on this 'test'. I am not happy, and learning more about nvram, etc. than I really ever wanted to. I've got BIND configurations and a whole bunch of Fedora installations to be focusing on right now! Any help would be MUCH appreciated!
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum