Lombard failure to boot

I have a G3 Lombard 400 with a Daystar G4 433 processor installed. (I still have the good G3 processor.) I was running OS 10.2.8 and all was well except that I could no longer download some of the web sites I need, presumably because my Safari needed updating. I had 512 of RAM. I loaded Xpostfacto and started to install OS 10.4 (hitting all the default buttons) and the installation ran to 23% completed whereupon the system froze. I left it running for over 2 hours, thinking there might be some installation slowdown. On restart I got a kernal panic. I reset the PRAM (little button on back) and tried a restart. No good - still a kernal panic. Since then, I have removed the lower RAM and on restart, I get the blue screen with the Apple, but that is all, no little spinning pinwheel, nothing else no matter how long I wait. I tried booting from various discs (OS 10.4, OS 10.2, from OS 9.) It won't read the disc, just gives the blue Apple screen with the apple and no spinning wheel. I disconnected the hard drive and tried to start from the disc and I only get the little folder with the question mark flashing. I swapped out the dvd drive and got the same result. I tried disconnecting the battery, the PRAM battery, the keyboard (used a USB board from my Cube) and swapping various RAM cards. I even tried the original G3 processor. Nothing works. It won't start from the dvd drive and it won't start from the hard drive past the blue screen and apple without the spinning wheel.
Any suggestions out there about what might be going on?
Any suggestions about other things to try?
Note: it was running fine prior to trying to install OS 10.4 with Xpostfacto, other than that I couldn't use a couple of the websites I need using Safari with OS 10.2, though I could get them using Firefox.

mmgar,
Sorry nothing has worked. Unfortunately the Lombard does not support Startup Manager as does the Pismo and all later Macs.
http://support.apple.com/kb/HT1310?viewlocale=en_US
Have you tried booting with all peripherals disconnected?
You may in fact have a hardware problem since both the HD and optical drive will not work. Both of these use the same IDE controller on the logic board. If just the HD or HD ribbon cable was the problem, the optical drive would still boot when the HD was removed. The only way I can see for testing if the IDE controller has failed is to mount a known-good HD with a bootable OS in the Lombard and see if it will boot. There is a fairly simple way to accomplish this:
-Mount your Lombard's HD in a 2.5" FireWire HD enclosure, connect it to another Mac running 10.2.x or 10.3.x or 10.4.x and clone the host's OS to the external FireWire HD. After the FW HD mounts on the host's desktop, you may first wish to drag-copy your User's folder from the Lombard's HD to the host computer before erasing the Lombard's HD. Using the freeware Carbon Copy Cloner or the shareware SuperDuper! (I prefer SD and you can use its basic features without contributing), install one of these clone utilities on the host computer and follow the instructions...very simple.
-After cloning the OS, restart to the FW HD to make sure it works. If successful, install the HD back in the Lombard and test.
-You can clone to a 2.5" USB HD enclosure but you cannot boot the USB drive to check the installation; only Leopard/10.5 supports USB booting.
-You can also install OSX on the FW or USB HD enclosure by booting to the OSX CD or DVD as long as it is supported on the host computer.
-You can natively run Tiger/10.4 on the Lombard without XPostFacto if you install Tiger in the above manner. XPostFacto is only needed on the Lombard to boot the Tiger DVD; the installer script on the Tiger DVD looks for supported computers and the Lombard is not one, so the DVD will not boot. However, limiting Tiger support to only computers with built-in FireWire was an arbitrary cutoff point; the Lombard is fully supported with Tiger (no XPostFacto) as many Lombard owners will attest to.

Similar Messages

Mac Pro Display flicker & failure to boot

Hello people who are smarter than me.
I have a 2008 Mac Pro 3.2/ 8CX 8800GT with the original Geforce video card installed. When I turn the machine on I get a grey screen with a black bar at the top, with no evidence of an actual boot (such as a darker grey apple in the middle of the screen.
After a minute or so, the screen retains the form of the black and white horizontal bar at the top but adds a rapidly cycling/strobing organge red and yellow flicker reminiscent of the old Monty Python crazy title screens.... It looks like this if you blink fast enough... or take a still photo.
I live in Haiti, where a fair amount of dust is constantly invading my tower, so I've had dust related issues before with memory... THis time, I don't think it's that. I've cleaned out the tower with pressurized air, reseated the memory and reseated the video card as well, to no advantage. The problem first came when the computer was working fine and while my daughter was opening a page on Firefox the screen just started jittering with this little color show. At the time, though, you could still see the desktop behind all the flickering. Now the computer doesn't seem to even boot. If I have to fly to the states to fix this, I'd love to not have to haul the whole machine, so if we can get this down to a couple likely parts that I could travel with, test and replace, that would be great. This is a hardware issue, right? Would video card failure make sense of this AND the failure to boot? AND if I do replace it, is the ATI Radeon HD 5770 Graphics Upgrade Kit still the ticket? If you help me, you'll be helping a lot of Haitians too, as I use this computer for humanitarian work with the Apparent Project. Help me Obi Geeks, you're my only hope!

Okay, so after doing all of the above, the computer still takes between 40 seconds and 1 minute or so to boot up, and the VersionCue messages still appear. However I discovered that the "kdcmond cannot retrieve..." messages disappeared after I disabled my ethernet connections. So at least I know that that had nothing to do with the extended boot-up time.
I have heard that the more RAM you have, the longer it takes to boot due to the RAM count. Since I have 10 GB, maybe this is why?
I've included the most recent Console messages below:
22/4/08 9:56:16 AM com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
22/4/08 9:56:16 AM com.apple.launchd[1] (com.adobe.versioncueCS3) Unknown key: ServiceDescription
22/4/08 9:56:16 AM com.apple.launchd[1] (org.cups.cups-lpd) Unknown key: SHAuthorizationRight
22/4/08 9:56:16 AM com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
22/4/08 9:56:16 AM com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
22/4/08 9:56:39 AM com.apple.SystemStarter[28] Starting Aladdin USB daemon
22/4/08 9:56:39 AM org.ntp.ntpd[25] Error : nodename nor servname provided, or not known
22/4/08 9:56:39 AM com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[74]) Exited: Terminated
22/4/08 9:56:39 AM com.apple.launchctl.Aqua[90] launchctl: Please convert the following to launchd: /etc/machinit_peruser.d/com.adobe.versioncueCS3.monitor.plist
22/4/08 9:56:42 AM com.apple.launchd[82] (0x1011e0.VersionCueCS3monitor) Failed to check-in!

Failure to boot after restarting, no distinct pattern.

My Mac Pro has an issue where every third or fourth restart the mac will fail to boot, needing me to hold the power button until it turns off.
I get the grey apple and the spinning progress wheel for 30 seconds, then the screen stays grey and the apple is replaced by what looks like a circle with a diagonal bar through it. I believe this means something along the lines of 'No Bootable Directory Found'.
Before the 10.5.2 update this happened almost every restart. I'm using a Samsung Spinpoint 750gig drive as my boot drive, and the stock 500gig drive as a media disk.
I have tried several solutions. Repair permissions, Disk Utility from CD and run verify and repair disk, AHT extensive, TechTool Deluxe with surface scan, Format and Reinstall (twice), Memtest, NVRam.
Could the Samsung drive be bad even though I can't get any software to find a fault?

Here is a console log of the most recent failure to boot. The events here are a restart, a failure to boot, a forced off and a power on. Hopefully this helps.
27/02/2008 02:31:00 com.apple.launchd[68] (0x10a650.Locum[2615]) Exited: Terminated
27/02/2008 02:31:57 com.apple.launchd[68] ([0x0-0xa00a].com.apple.dock[94]) Stray process with PGID equal to this dead job: PID 2586 PPID 1 DashboardClient
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] *Wakein::CancelEvents: requested event type: wakepoweron
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] *Wakein::CancelEvents: requested app name: com.elgato.eyetv
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] *Wakein::CancelEvents: canceling wakepoweron - com.elgato.eyetv - 02/27/08 21:35:00
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] *Wakein: 0 entries in power event schedule table
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] *Wakein::ScheduleEvent: requested event type: wakepoweron
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] *Wakein::ScheduleEvent: requested app name: com.elgato.eyetv
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] *Wakein::ScheduleEvent: requested date: 02/27/08 21:35:00
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] *Wakein: 1 entries in power event schedule table
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] * date: 02/27/08 21:35:00
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] * appName: com.elgato.eyetv
27/02/2008 02:31:57 [0x0-0x13013].com.elgato.eyetvhelper[106] * eventType: wakepoweron
27/02/2008 02:32:07 com.apple.loginwindow[23] Shutdown NOW!
27/02/2008 02:32:07 com.apple.loginwindow[23] System shutdown time has arrived
27/02/2008 02:32:07 com.apple.SystemStarter[16] Starting Aladdin USB daemon
27/02/2008 02:32:08 com.apple.SystemStarter[16] process already running on this system - daemon terminated!
27/02/2008 02:34:04 com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
27/02/2008 02:34:04 com.apple.launchd[1] (com.adobe.versioncueCS3) Unknown key: ServiceDescription
27/02/2008 02:34:04 com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
27/02/2008 02:34:04 com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
27/02/2008 02:34:22 com.wacom.wacomtablet[79] TabletDriver[79]: ISO keyboard: OSI
27/02/2008 02:34:23 com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[80]) Exited: Terminated
27/02/2008 02:34:23 com.apple.launchd[1] ([0x0-0x7007].com.wacom.TabletDriver[87]) Exited: Terminated
27/02/2008 02:34:23 com.apple.launchd[1] (com.wacom.wacomtablet[79]) Exited with exit code: 255
27/02/2008 02:34:23 com.apple.launchctl.Aqua[88] launchctl: Please convert the following to launchd: /etc/machinit_peruser.d/com.adobe.versioncueCS3.monitor.plist
27/02/2008 02:34:23 com.apple.launchd[69] (0x1010d0.VersionCueCS3monitor) Failed to check-in!
27/02/2008 02:34:24 com.wacom.wacomtablet[89] TabletDriver[89]: ISO keyboard: OSI
27/02/2008 02:34:31 [0x0-0x13013].com.elgato.eyetvhelper[115] EyeTV Helper version 3.0 build 267
27/02/2008 02:34:33 com.apple.SystemStarter[16] Starting Aladdin USB daemon
27/02/2008 02:38:48 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein::CancelEvents: requested event type: wakepoweron
27/02/2008 02:38:48 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein::CancelEvents: requested app name: com.elgato.eyetv
27/02/2008 02:38:48 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein::CancelEvents: canceling wakepoweron - com.elgato.eyetv - 02/27/08 21:35:00
27/02/2008 02:38:49 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein: 0 entries in power event schedule table
27/02/2008 02:38:51 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein::CancelEvents: requested event type: wakepoweron
27/02/2008 02:38:51 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein::CancelEvents: requested app name: com.elgato.eyetv
27/02/2008 02:38:51 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein: 0 entries in power event schedule table
27/02/2008 02:38:51 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein::ScheduleEvent: requested event type: wakepoweron
27/02/2008 02:38:51 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein::ScheduleEvent: requested app name: com.elgato.eyetv
27/02/2008 02:38:51 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein::ScheduleEvent: requested date: 02/27/08 21:35:00
27/02/2008 02:38:51 [0x0-0x1b01b].com.elgato.eyetv[158] *Wakein: 1 entries in power event schedule table
27/02/2008 02:38:51 [0x0-0x1b01b].com.elgato.eyetv[158] * date: 02/27/08 21:35:00
27/02/2008 02:38:51 [0x0-0x1b01b].com.elgato.eyetv[158] * appName: com.elgato.eyetv
27/02/2008 02:38:51 [0x0-0x1b01b].com.elgato.eyetv[158] * eventType: wakepoweron
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::CancelEvents: requested event type: wakepoweron
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::CancelEvents: requested app name: com.elgato.eyetv
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::CancelEvents: canceling wakepoweron - com.elgato.eyetv - 02/27/08 21:35:00
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein: 0 entries in power event schedule table
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::ScheduleEvent: requested event type: wakepoweron
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::ScheduleEvent: requested app name: com.elgato.eyetv
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::ScheduleEvent: requested date: 02/27/08 21:35:00
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein: 1 entries in power event schedule table
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] * date: 02/27/08 21:35:00
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] * appName: com.elgato.eyetv
27/02/2008 02:39:38 [0x0-0x13013].com.elgato.eyetvhelper[115] * eventType: wakepoweron
27/02/2008 02:39:48 com.apple.loginwindow[23] Shutdown NOW!
27/02/2008 02:39:48 com.apple.loginwindow[23] System shutdown time has arrived
27/02/2008 02:39:48 com.apple.SystemStarter[16] Starting Aladdin USB daemon
27/02/2008 02:39:48 com.apple.SystemStarter[16] process already running on this system - daemon terminated!
27/02/2008 02:40:11 com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
27/02/2008 02:40:11 com.apple.launchd[1] (com.adobe.versioncueCS3) Unknown key: ServiceDescription
27/02/2008 02:40:11 com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
27/02/2008 02:40:11 com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
27/02/2008 02:40:30 com.wacom.wacomtablet[79] TabletDriver[79]: ISO keyboard: OSI
27/02/2008 02:40:30 com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[80]) Exited: Terminated
27/02/2008 02:40:30 com.apple.launchd[1] ([0x0-0x7007].com.wacom.TabletDriver[87]) Exited: Terminated
27/02/2008 02:40:30 com.apple.launchd[1] (com.wacom.wacomtablet[79]) Exited with exit code: 255
27/02/2008 02:40:30 com.apple.launchctl.Aqua[88] launchctl: Please convert the following to launchd: /etc/machinit_peruser.d/com.adobe.versioncueCS3.monitor.plist
27/02/2008 02:40:30 Dock[97] _DESCRegisterDockExtraClient failed 268435459
27/02/2008 02:40:31 com.apple.launchd[69] (0x1010d0.VersionCueCS3monitor) Failed to check-in!
27/02/2008 02:40:31 com.wacom.wacomtablet[89] TabletDriver[89]: ISO keyboard: OSI
27/02/2008 02:40:37 [0x0-0x13013].com.elgato.eyetvhelper[115] EyeTV Helper version 3.0 build 267
27/02/2008 02:40:40 com.apple.SystemStarter[16] Starting Aladdin USB daemon
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::CancelEvents: requested event type: wakepoweron
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::CancelEvents: requested app name: com.elgato.eyetv
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::CancelEvents: canceling wakepoweron - com.elgato.eyetv - 02/27/08 21:35:00
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein: 0 entries in power event schedule table
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::ScheduleEvent: requested event type: wakepoweron
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::ScheduleEvent: requested app name: com.elgato.eyetv
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein::ScheduleEvent: requested date: 02/27/08 21:35:00
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] *Wakein: 1 entries in power event schedule table
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] * date: 02/27/08 21:35:00
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] * appName: com.elgato.eyetv
27/02/2008 02:40:45 [0x0-0x13013].com.elgato.eyetvhelper[115] * eventType: wakepoweron
27/02/2008 02:40:45 com.apple.loginwindow[23] Shutdown NOW!
27/02/2008 02:40:45 com.apple.loginwindow[23] System shutdown time has arrived
27/02/2008 02:40:45 com.apple.SystemStarter[16] Starting Aladdin USB daemon
27/02/2008 02:40:45 com.apple.SystemStarter[16] process already running on this system - daemon terminated!
27/02/2008 04:06:51 com.apple.launchctl.System[2] launchctl: Please convert the following to launchd: /etc/mach_init.d/dashboardadvisoryd.plist
27/02/2008 04:06:51 com.apple.launchd[1] (com.adobe.versioncueCS3) Unknown key: ServiceDescription
27/02/2008 04:06:51 com.apple.launchd[1] (org.cups.cupsd) Unknown key: SHAuthorizationRight
27/02/2008 04:06:51 com.apple.launchd[1] (org.ntp.ntpd) Unknown key: SHAuthorizationRight
27/02/2008 04:07:07 com.wacom.wacomtablet[79] TabletDriver[79]: ISO keyboard: OSI
27/02/2008 04:07:07 com.apple.launchd[1] (com.apple.UserEventAgent-LoginWindow[80]) Exited: Terminated
27/02/2008 04:07:07 com.apple.launchd[1] ([0x0-0x7007].com.wacom.TabletDriver[87]) Exited: Terminated
27/02/2008 04:07:07 com.apple.launchd[1] (com.wacom.wacomtablet[79]) Exited with exit code: 255
27/02/2008 04:07:07 com.apple.launchctl.Aqua[88] launchctl: Please convert the following to launchd: /etc/machinit_peruser.d/com.adobe.versioncueCS3.monitor.plist
27/02/2008 04:07:07 Dock[96] _DESCRegisterDockExtraClient failed 268435459
27/02/2008 04:07:08 com.wacom.wacomtablet[89] TabletDriver[89]: ISO keyboard: OSI
27/02/2008 04:07:08 com.apple.launchd[73] (0x1010d0.VersionCueCS3monitor) Failed to check-in!
27/02/2008 04:07:15 [0x0-0x13013].com.elgato.eyetvhelper[115] EyeTV Helper version 3.0 build 267
27/02/2008 04:07:18 com.apple.SystemStarter[16] Starting Aladdin USB daemon

"Error 300: Failure to boot" When trying to boot up imac

This is the error I get when I try to boot up my imac, it will not boot up, just leaves me with this Error 300: Failure to boot. I don't know what to do as I'm not all that mac - knowlegeable. Please help me if you can.

Message from daughter in Italy:
Here's what happened. When I typed in the first line, the output was a TON of lines somewhat like this:
-rw-rw-r-- 1 0 80 12292 (a date, a time) (Firefox, Users, etc.)
drw------- 7 0 99 238 (a date, a time) (Volumes, afs, bin,etc.)
d-wx-wx-wt 2 0 80 68 (a date, a time) (var -> /private/var, etc)
drwxr-xr-x 1 0 80 649 (a date, a time) (Desktop Folder, private)
There were lots of lines that started with drwxr. Also, where I typed parentheses above, there weren't any parentheses (that's just to show where the date and time would be). And on the very last item, those things listed in parentheses (which were not on the code) include some samplings of what was listed there (but not necessarily corresponding to the previous code in the line that I typed -- I just wrote down some of the words I saw throughout). There was only one word at the end of each line (or sometimes something like the very two last lines, which were var -> /private/var and one other somewhat like it with the var.delete code.
When I typed in the second line of code suggested, there was nothing, just a new prompt (that same weird prompt with the pound sign).
When I typed in the third line of code suggested, the output was the following:
ls: /private/etc/: No such file or directory
Also, when I typed in the very first line of code, there was no weird prompt thing...just a blank line with the cursor blinking. The prompt thing always appears after you type in something and hit return.
Hope that all makes sense (at least to the Apple geniuses out there). Thank you!!

Lombard won't boot off System disc

Hi,
I have a problem that I wonder if any of you mac experts can help me with.
My problem is the computer will not boot from a system disc (any system disc) from the CD drive.
I have a Lombard Powerbook that has been running OS 8.6 (I know, I am way behind !) 192 mg RAM (64 in the lower, 128 in the upper from OWC), 4 Gb Hard drive.
The computer runs great in 8.6 - seldom crashes - however, all I have been mainly using it for is word processing.
When I try to load from any OS system disc (not the original Lombard disc, but any OS disc - 8.5, 9.2, Panther) holding down the C key, the CD drive runs for approximately 20 seconds, then stops, and on the screen I get a picture of a blank folder with a question mark - the Lombard is not reading the CD drive for some reason and won't boot from it. After a short wait OS 8.6 loads from the Hard drive.
I bought the computer on e-bay 4 years ago, and this has always been a problem - I just have been to busy in the past to deal with it.
Is there a simple command other than holding down the C key when restarting that will safely (remember I am a novice) allow me to bypass the hard drive and boot from the CD drive ?
I have done the following, which have all been unsuccessful at resolving this problem, and am out of ideas.
I have taken out all virus software from the system folder, cancelled all non-OS extensions and made sure the password extension is turned off.
I have zapped the PRAM.
I have taken out the (upper) RAM chip to be sure that it wasn't the problem - no difference.
Chosen the CD drive in the Startup Control Panel.
Checked to see if the system and finder are locked - they're not.
The CD drive may be the problem, but it runs software CDs fine, and it is the correct drive for the Lombard.
Any suggestions ? I would appreciate any ideas that people have.
Thanks.
Steve
Powerbook Lombard Mac OS 8.6 or Earlier

Steve,
You have performed a lot of troubleshooting which is helpful. There are several causes for a no-boot to CD...
1. Corrupted PRAM: You have addressed that.
2. Peripheral/external device preventing boot: Disconnect ALL peripherals.
3. Damaged or incorrect CD: The Lombard will not boot any CD earlier than OS 8.6, so the original Powerbook G3 Series Bronze Keyboard CD (has OS 8.6) or a retail MacOS 8.6 CD or newer will boot the Lombard. If you have a machine-specific OS 8.6 > 9.2.1 CD that has a computer name on it like iMac, iBook, Power Mac, etc, it will not boot your Lombard (there are a few exceptions.
Assuming you have no other problems, the Panther/10.3.x CD should boot unless you tried with only 64MB in the lower slot...then it may not boot...a Jaguar CD will, but not sure about Panther.
4. Bad drive: I don't know if an optical drive that performs normally when running an OS from the HD can also have the problem of not booting a CD. If you can find another Lombard or Pismo, swap drives and test.
5. The options for booting to a CD on the Lombard are the 'c' key, selecting the volume in the Startup Disk control panel, or the 'delete-option-command-shift' keys on restart...this forces a bypass of the HD.
6. It doesn't matter what is on the HD when trying to boot a CD; it can have a working OS or it can be empty.
Try this: If you have a supported CD, put the CD in the drive and shut down (not restart). Now press the power button and hold down the four keys for a PRAM reset...command-option-R-P...wait for two startup chimes, release the keys and immediately press the 'c' key.

Intermittent failure to boot, flashing question mark or white screen

So, I've had two MacBooks with similar problems (I am a Mac consultant). The first one would intermittently boot to a white screen, often enough to be annoying. This current one is occasionally booting to a flashing question mark. My first thought is, of course, the hard drive, but in both cases the hard drive tests fine using SMART Utility, which is usually great at giving advance warning when a drive starts experiencing hardware errors.
On the first MacBook, the one with the white-screen boots, I tried reinstalling the system with no effect; replacing the drive eventually made the problem go away. The current MacBook, with the question-mark boots, has already had its drive replaced once, when the stock drive failed.
I will reseat the drive, which is all Apple could suggest. I just wonder if anybody else had experienced something like this and can offer any information about what might be going on.

Thanks for the reply. Aside from finding that holding the mouse button down at boot might cause a flashing question mark, I already knew all that. I will ask the owner if she is leaning on the trackpad button when she starts up her computer in the morning.
I've already reset the power manager and the PRAM; we'll see if that makes any difference. The puzzling thing here is that the problem is intermittent.
I also need to ask her if, when the computer does boot to the question mark, there has been a chime first. Somehow I think there has to be, for the system to have gotten as far as looking for a boot drive. I couldn't find anything useful in the logs; not surprising, since if it can't find a drive to boot to, it won't have anything to write a log to.
Again, the mystery is why the failure to boot is intermittent. If it happened every time, I'd know what to do!
Thanks
cavenewt

IMac Drive Failures and Boot Camp - large install experience and question

We have a large 24" iMac install, purchased in August of '08, 49 machines spread across 6 offices. All run Windows Vista in Boot Camp as their primary (and mostly sole) operating mode - I will be happy to explain why after we get this cleared up, but that is not the point of this question.
We have had 11 hard drive failures, a rate of over 22% in one year. No machine has failed twice. The equipment was purchased in different groups so a bad lot is unlikely. I am aware that there is an HD failure issue with the iMac's but this seems to be extreme. Personally I've been building apples and pc's since my first apple kit, have a mac plus in a box somewhere, and am fond of these machines (as is the staff) but I've never seen a failure rate like this.
It has been suggested that it is the use of Boot Camp that is causing these failures. While I have seen viruses over the years that can lead to hardware failure I've never seen validated (or even simply non-malignant) software have the same effect.
Any thoughts on this? Could BC be the cause? Is this failure rate unusual? Have folks heard of similar cases? Thanks.

no one has any thoughts on this?

Hard Drive failure - various boot modes won't work, HELP!

Hello all,
First of all, sorry for the essay, but I didn't want to miss out on possible crucial details that could help!
A couple of weeks ago, my beloved 27" iMac had a hard drive failure. It won't boot, but instead goes to the grey 'no entry' sign when booting up. I tried holding Cmd + V on boot and this message repeated itself whilst failing to boot:
"rooting via boot-uuid from chosen/: D94DA2D5-DB38-3517-B05D-70A97AC6EE5B
Waiting on <dict ID="0"><key><IOProviderClass</key><string ID="1"> IOResorces</string><key>IOResourceMach</key><string ID= "2">boot-uuid-media</string></dict>
Got boot device = IOService:/AppleACPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleIntel5Serie sAHCI/PRT0@0/IOAHCIDiskDriver/IOAHCBlockStorageDevice/IOBLockStorageDriver/Hitac hi HDS722020ALA330 Media/IOGUIDPartitionScheme
BSD root: disk0s2, major 14, minor 2
jnl: unknown-dev: open: phys_blksz 4096 does not match journal header size 512, and journal is not empty!
hfs: late jnl init: failed to open/create the journal (retval 0)
cannot mount root, errno = 19"
I'm not sure how much of that is useful, but I thought I'd copy it all down anyway.
I googled error number = 19 and found articles on an invalid b-tree node and corrupt journals, leaving me to believe that because I recently deleted a Windows Vista partition and reformed the overall HD into a 2TB OSX volume, some windows data may have been left over and corrupted the journal?
So it fails to boot normaly, using Cmd V, and using the OSX install disk, as well as failing to boot from the DiskWarrior 4 DVD I purchased from my local Apple Reseller because I'd heard that it's very good at helping with issues such as what I think my HD is having. I tried Disk Utility whilst booting from the install disk, and tried to repair the drive, and each time I tried it said that invalid content was present in the journal but the disk repair had been successful.
Am I right in thinking that my data is on the drive, it's just that OSX won't register the drive's existence because of a corrupted journal? (the little I know of hard drives is shining brightly through at this point, I'm sure!)
I also tried to boot using target mode by connecting my iMac to a MacBook Pro also running Snow Leopard, but, whilst the iMac clearly went into target mode (bouncing firewire icon on screen), my HD never appeared on the desktop of the MacBook Pro, nor in Disk Utility.
Whilst I have AppleCare, I haven't tried taking it to a mac store yet because of two reasons; 1. The last time I did this I had HD failure on my old 2008 MBP and, whilst I told them to keep the data on it, the first thing they did was reformat the disk. Needless to say, it worked, but I lost all my valuable Data! The second reason is that it's bloody heavy, and I don't own a car!
Before people go on about the way I should have backed up my data, I did, and that's gone as well! D:
System Specs:
First generation of 27" iMacs
2.8Ghz Intel i7 quad core
2TB HD
ATi Radeon HD 4850 512mb VRAM
8GB DDR3 RAM
OS version: not the very latest snow leopard but the one before.
Thanks in advance, and once again sorry for the essay!
Westy

I'm not sure about the DW disk. Check that out at Alsoft's website. Apple doesn't provide data recovery services.
Apple has records of your iTunes purchases. However, the licensing for music only permits you to download it once. I'm surprised that you don't have backups.
If you get an external enclosure in which to put the drive then you might try accessing it from the MBP as an external drive. If you have an external drive you could try using recovery software:
General File Recovery
If you stop using the drive it's possible to recover deleted files that have not been overwritten by using recovery software such as Data Rescue II, File Salvage or TechTool Pro. Each of the preceding come on bootable CDs to enable usage without risk of writing more data to the hard drive. Two free alternatives are Disk Drill and TestDisk. Look for them and demos at MacUpdate or CNET Downloads.
The longer the hard drive remains in use and data are written to it, the greater the risk your deleted files will be overwritten.
Also visit The XLab FAQs and read the FAQ on Data Recovery.
Beyond this you would need to send the drive off to a data recovery service which will be extremely expensive.

Lombard won't boot to Hard Drive

I erased and installed 10.3, once that is done it restarts and works great. Then after I turn it off, or restart again, or unplug AC adapter from the wall it will not boot to hard drives, boots to the circle slash. I booted to install cd and ran disk utilities then when I restart nothing. The only time I can get the powerbook to work is right after I install 10.3. The date/time is always remembered, but I do have a dead battery - won't hold charge at all. Thinking about buying battery, just really thought I should be able to run the laptop on ac adapter. Any thoughts are greatly appreciated.

TJ,
Welcome to the Discussions.
See if the suggestions in this article, especially the resetting of the PRAM and power manager help:
http://docs.info.apple.com/article.html?artnum=106805
One issue the Lombard suffers more than other black G3s is a failed backside L2 cache. Once you are up and running again, go to the System Profiler > Hardware and see if it reports either 512K or 1MB of L2 cache or is missing. If this is the case, resetting the power manager, at least when running 9.x, will allow a successful start, but of course the problem is still present.
If you have a bootable OS 8.6 > 9.2.2 CD, and from a cold start, not restart, boot to the CD and see if you get a warning dialogue that there is a problem with RAM or cache memory.
Message was edited by: jpl

IPhone 5 failure to boot or restore

Hey Guys!
I am posting on behalf of my mate as this is his phone. Unfortunatly his iPhone 5 (purchased under contract from Vodafone Australia) has stopped working in a way that I have never seen. Upon booting with the Apple logo appearing, white text appears in the top left of the screen.
This is the following text:
[NAND] _FindflashMediaAndKeepout:601 physical nand block offset1
[NAND] start:356 this 0x89ba1400 PROVIDER=0x89b380 flashmedia=0x89b3b380
[NAND] WMR_Start:149 Apple PPN NAND Drive, Read/Write
[NAND] WMR_Start:174 FIL_Init [OK]
[NAND] s_cxt_boot:80 sftl: error, unclean shutdown; adopted 92 spans
[NAND] WMR_Open:420 FTL_Open [OK]
[NAND] _publishServices:642 FTL capabilities: 0x00000001
[NAND] _ppnvfGetStruct:3469 Checking borrowed blocks - count: 23 max_count: 23
[NAND] _fetchBorrowedList:881 number of borrowed blocks 16
I am unable to restore it as this keeps appearing on the screen as it restarts the device upon completetion of the extraction. I have tried restore mode and DFU mode with the same issue. Any help would be gladly accepted!
Thanks, Goddo

Hi goddo2305,
Welcome to Apple Support Communities.
It's more of a hardware problem but also software problem.
It appears that the main logic board's failure,throws those errors.
So you have to go to Technician any where in your country and ask him about the things i will set them below :
1- tell him to change your parts one by one and step by step to see if your phone will boot up again and work .
2- change first thing home button completely and try open your phone again . see if it work without nand screen or not . if its ok and your phone work will so the problem was a HomeButton if its not try third step
3- change power cable to original one and after that open up your phone to see if it work or not. if your phone work so its power Cable problem if its not so try fourth step
4- change volume buttons Cables and after that power up your phone . if your phone work well so its volume cables problem . if its not try fifth step
5- try to walk on every cable and buttons in your phone change them and open the phone to see if well work or not.
Thanks!

Problems with 1st Boot (media test failure, disk boot failure)

I have the K7N2G motherboard.
I hooked up everything in my system and on my first boot I get this error:
PXE-E61: Media Test Failure, check cable
PXE-M0F: Exiting NVIDIA Boot Agent
DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER
So, I figure I'll start from scratch and just start with the floppy drive, cpu, and ram hooked up and I get the same error. Here are my specs:
MSI K7N2G
Athlon 2400
Kingston PC3500 RAM
Volcano 7 Fan/Heatsink
Seagate Barracuda V SATA 80 GB
Verbatim CDRW 52/24/52
Any help or suggestions would be greatly appreciated.

This happens if:
- The hard drive is not installed
- An Operating System is not installed
- The BIOS cant detect the hard drive, maybe:
= The wrong jumpers are set on the hard-drive
= The cable is not polarised and pin 1 is on the wrong pin
- The hard-drive has not been set-up in the BIOS
Try something like the above

Application Launch Failures & wont boot into OSX!!

My Powerbook was getting "Application Launch Failures" for a while within OSX, now it wont even boot. I get the question mark folder flash, then it goes away, and I get the grey screen with the Apple logo and spinning progress indicator...then it just stays there. I tried taking it into Safe Mode, but no luck. Does it sound like I need to reinstall OSX, or is the HD hosed?

It means required system files are corrupted. You may not need to reformat the hard drive and reinstall OS X by doing an Archive and Install:
How to Perform an Archive and Install
1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
Repairing the Hard Drive and Permissions
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 Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
If DU reports errors it cannot fix, then you will need Disk Warrior (4.0 for Tiger) and/or TechTool Pro (4.5.2 for Tiger) to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.

Failure to boot due to Biohd-4,-8 errors

My PC was built with Windows Vista OS. I installed W7 upgrade and I had no end of problems. Most important is boot failure. I ran the HP doctor diagnostics and was told the the PC ship, ram and Hard drive were OK, but the diognostics pointed out two errors. the first error was Biohd-8 and the second is Biohd-4. I am assuming that this means there is some problem in the Bios. The system will not boot all the way using the W7 repair disc or the old W Vista recovery discs. Help !!!

Lou, welcome to the forum.
The error codes (BioHD-4 & 8) are generated by S.M.A.R.T. (Self-Monitoring, Analysis and Reporting Technology). It is used to alert you to problems with your hard drive/s. It appears that you have a failed hard drive. The only way to solve the problem is by replacing the drive.
Please click "Accept as Solution" if your problem is solved.
Signature:
HP TouchPad - 1.2 GHz; 1 GB memory; 32 GB storage; WebOS/CyanogenMod 11(Kit Kat)
HP 10 Plus; Android-Kit Kat; 1.0 GHz Allwinner A31 ARM Cortex A7 Quad Core Processor ; 2GB RAM Memory Long: 2 GB DDR3L SDRAM (1600MHz); 16GB disable eMMC 16GB v4.51
HP Omen; i7-4710QH; 8 GB memory; 256 GB San Disk SSD; Win 8.1
HP Photosmart 7520 AIO
++++++++++++++++++
**Click the Thumbs Up+ to say 'Thanks' and the 'Accept as Solution' if I have solved your problem.**
Intelligence is God given; Wisdom is the sum of our mistakes!
I am not an HP employee.

No longer able to boot - failure with /boot

I recently, due to a hard drive change, rebuilt my desktop. Every now and again, since then, it hasn't booted. I just logged into root and rebooted; figuring I'd sort it out at some point.
Only, now it won't boot at all. When I go through journalctl -xb I get the following errors (the ellipsis, in case it isn't clear, indicate an number of lines with no error in between the error messages):
Job dev-sda2.device/start timed out.
Timed out waiting for device dev-sda2.device.
Dependency failed for /boot.
Dependency failed for Local File Systems.
Triggering OnFailure= dependencies of local-fs.target.
Dependency failed for File System Check on /dev/sda2
and also, much later in the logs:
Failed at step EXEC spawning /bin/plymouth: No such file or directory
My initial assumption would have been that the relevant drive is failing, but I only recently ran a check on the drives (a few days ago and since the rebuild) and all was fine and dandy - but I had already been seeing these errors on a periodic basis. Only now, as I said, they happen at every boot and I never get as far as login.
Thanks in advance for any help.

I ran the extended smartmontools test on the disk today and it returned with no errors. However, the error log for the disk did contain the following:
Complete error log:
SMART Error Log Version: 1
Warning: ATA error count 21 inconsistent with error log pointer 5
ATA Error Count: 21 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 21 occurred at disk power-on lifetime: 10341 hours (430 days + 21 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 08 00 00 00 e0 08 01:12:12.224 READ DMA
27 00 00 00 00 00 e0 08 01:12:12.224 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 0a 01:12:12.224 IDENTIFY DEVICE
ef 03 45 00 00 00 a0 0a 01:12:12.224 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 08 01:12:12.224 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 20 occurred at disk power-on lifetime: 10341 hours (430 days + 21 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 08 00 00 00 e0 08 01:11:26.048 READ DMA
27 00 00 00 00 00 e0 08 01:11:26.048 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 0a 01:11:26.048 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 0a 01:11:26.048 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 08 01:11:26.048 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 19 occurred at disk power-on lifetime: 10341 hours (430 days + 21 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
c8 00 08 00 00 00 e0 08 01:10:16.816 READ DMA
27 00 00 00 00 00 e0 08 01:08:51.584 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 a0 0a 01:08:51.584 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 0a 01:08:51.584 SET FEATURES [Set transfer mode]
27 00 00 00 00 00 e0 08 01:08:51.568 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 18 occurred at disk power-on lifetime: 10340 hours (430 days + 20 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
25 00 01 00 00 00 e0 08 00:04:28.384 READ DMA EXT
c6 00 10 00 00 00 e0 08 00:04:28.384 SET MULTIPLE MODE
91 00 3f 00 00 00 a0 08 00:04:28.384 INITIALIZE DEVICE PARAMETERS [OBS-6]
10 00 00 00 00 00 a0 08 00:04:28.352 RECALIBRATE [OBS-4]
25 00 01 00 00 00 e0 04 00:04:28.352 READ DMA EXT
Error 17 occurred at disk power-on lifetime: 10340 hours (430 days + 20 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
84 51 00 00 00 00 e0 Error: ICRC, ABRT at LBA = 0x00000000 = 0
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
25 00 01 00 00 00 e0 08 00:04:28.288 READ DMA EXT
c6 00 10 00 00 00 e0 08 00:04:28.288 SET MULTIPLE MODE
91 00 3f 00 00 00 a0 08 00:04:28.288 INITIALIZE DEVICE PARAMETERS [OBS-6]
10 00 00 00 00 00 a0 08 00:04:28.272 RECALIBRATE [OBS-4]
25 00 01 00 00 00 e0 04 00:04:28.272 READ DMA EXT
Does this mean my disk is dying? That would be very annoying after just rebuilding from another failed disk!

Failure to boot after new hard drive install

trying to resurrect old graphite 466mh firewire clamshell.
It was running tiger fine, had a problem charging it so sat in basement for a year. Turns out it was powercord,replaced, and now working again. Decided to replace the 10G hard drive, using the fixit site manual. Installed a Toshiba 80G drive, am now unable to boot from tiger cd's (not dvd) while holding down c-key. Any suggestions? By the way, have access to other firewire iBook running tiger but don't know how to boot from that. Any help much appreciated!

The reason for not being able to start
via 'C' on you new drive may be because it is
assigned (jumpered) incorrectly as the 'Slave' rather
than the 'Master'.
Of course! it seems so obvious now
you've said it.
Actually it's almost
certainly best that this gets done sooner rather than
later or it is complicate any future trouble
shooting
kind regards
mrtotes
OK gentlemen (thanks for responding). So I hook up the 2 iBooks, put the tiger cd in my wife's iBook and start them up. On the screen of the ibook I'm trying to resurrect my wife's desktop appears. I go into disk utility, it scans the systems and the only icons that appear are my wife's hard drive and the new (untitled) hard drive. No sign of the tiger installation cd. I can restore my wife's hard disk onto the untitled drive and end up with a working system. I know little about slaves and masters (I don't get out much)- how do I assign the new drive?
thanks again,
marc

Lombard failure to boot

Similar Messages

Maybe you are looking for