G4 450 Sawtooth - Won't Boot to FW Target Disk Mode

Running 10.5.8
Upgraded NewerTech 2G Processor
ATI 9800 Pro Video Card
Original WD 20G Drive with 10.5.8 (Back Up Boot Disk)
New Seagate 500G SATA - Primary Boot drive
FirmTech SATA Controller Card
New Seagate 1.5T - Misc Storage
Disk Utility and Disk Warrior both report no problems on either boot drive.
The machine will boot in any form I choose.
Any available boot drive / disk using Start Up > Option key
To the Install DVD using Start Up > C key
Using single user mode - Start Up > Comm and S key
Using USB Thumb Drive (Has 10.5.8 and Disk Warrior)
The machine will not boot to Target Disk Mode using the T key. Before getting beyond the Black screen the computer shuts down.
I've tried:
alternately using each boot drive while the other is disconnected
removing RAM
removing the SATA controller card
checked all connections
Zapped Pram and reset PMU (had to reset Mac OSX Firmware for the NewerTech Processor after pram set)
The only other thing I can find is a reference to Firmware Password Protection, but from what I read the computer should show start up problems beyond just TDM. Additionally, I am not familiar with FPP. All I know is it would be set (reset) from the Install Disk.
Any thoughs please?

Make sure there is a hard drive available as Master on the ATA 0 bus.
FireWire Target Disk Mode: Target Computer Shuts Down at Startup
How to use and troubleshoot FireWire target disk mode

Similar Messages

  • Old MBP won't boot, not even Target disk mode

    Hi all,
    My 2009 MacBook Pro was being used by a student to prepare some material for me while I worked on my new(ish) Retina MBP. The system was sluggish, despite numerous attempts to use disk repair on it, throw out unused programs, etc. It finally got so slow (we were scanning large files, and even the attempt to open Finder on a directory with the large files would cause it to freeze) that we re-installed the operating system. That didn't help, so we reformatted the disk (losing a lot of work) and started again. Things were working just fine (although it was getting slower again) and then out of the blue it would not boot.
    We tried everything: Safe boot, single user, resetting *RAM, the whole kit and kaboodle.
    We then set it us as a Target disk - and were happy to see some files. But happiness was only short lived. Two files could be copied before the disk refused to continue, noting errors. We turned it off and back on in Target mode - the firewire symbol appears, but it is not seen in the Finder. The disk utility can see it, but as soon as we try to verify or repair it, it disappears.
    I've tried connecting it to a Windows machine - it dings, but does not appear. I've tried booting with the Install CD (won't move), I've tried booting with Linux (I get an error). Every now and then after a looooong time, it gets mounted as a Target disk. I've managed to scrape 3 (three) files from the disk, it is soon unresponsive, and then it won't mount again. Every now and they I can use the disk utility to access the disk, verify says I need to repair it, repair says I need to re-format the disk. I've done that a few weeks ago.
    Any ideas for something else I can try? Thanks!

    You have a hardware problem. Probably the drive has failed. But if the system does not turn on at all, no sounds of any kind, then the problem is more serious. Like the logic board has failed.
    Connecting a mac hard drive to a windows system wouldn't work unless you have a program that will allow windows to read mac formatted drives. Windows can't do that itself. You need something like macdrive (I think it is called) or some other program that can read mac formatted drive on a windows pc.
    But from reading your whole post the drive has completely failed. If the system still starts up, you hear the startup chime, all you have to do is replace the failed hard drive and reinstall the os and program to get the system working again.

  • Boot up from target disk mode doesn't work. (Why?)

    I have a 2010 Macbook Pro, and a 2013 iMac. I connected the Macbook pro with the firewire cable to the iMac, and enabled target disk mode on the laptop. (It is successful because I see the hard drive appear on the iMac desktop.
    I restart the iMac and hold 'option' to show the hard drive list, and sure enough the Mac Book Pro hard drive appears. I select it, and this lovely icon greets me.
    From this point, I have no idea what to do.
    Would you happen to know why it doesn't work and/or how to fix it?

    I am able to do that... this is not the problem.
    I have seen people boot up from the hard drive using target disk mode. When I try to do it, it doesn't work. Does this feature still exist?

  • G4 PM will not boot after using Target Disk mode connected Intel iMac.

    Hi,
    We have some new Intel iMacs and have transferred some information from our previous G4 PM (one MDD and one Quicksilver) to the new iMacs. For some reason the G4's will now not boot up and kernal panic on the gray Apple boot screen. This has happened to all the G4's we have in our office. They are running OSX 10.2.8 and the iMacs are running OSX 10.4.4. We can still mount the drives from the G4's using FireWire Target Disk mode.
    I have tried zapping the PRAM etc but they still wont boot. I have also tried running the OSX 10.2 Installer disks to try and reinstall OSX on the G4's but the installer cannot see the drives?
    Anyone have any idea what is wrong. Never had this problem before using the FireWire transfer.
    Thanks,
    Nick.

    I had an experience with a mini mac after booting in target disk mode while connected to a blue and White G3 via Firewire. After attempting a restart, all I got was a blinking ? which usually means the startup disk or system folder can not be found.
    I fixed this problem by booting using the originall install CD and then using the startup disk menu to reselect the original system disk/system folder as the startup disk. On reboot. all was good. Only took a couple of minutes.....

  • G4 450 sawtooth won't boot OS 9 anymore??

    OK it seems nobody is interested in OS 9 any more which is a shame because the plugins and hardware that still run on it are bring used every day by studios all over the place. The thing that is weird is I was able to boot on both 9 and X for years until suddenly my machine hates 9 and still likes X. It won't boot on a 9 CD only on a X CD. The preferences pane shows all OS 9 and OS X discs available put will only boot up onto X and once when I put in an OS 9.2.2 content disk it did boot but went running back to X for some reason and refused to boot in OS 9. This is a G4 450 sawtooth which was originally built and made to run OS 9 so it makes no sense that it refuses now to boot into OS 9. Can somebody please help me to get this machine to boot into OS 9?!
    I would gladly erase the X disc and format it with the original restore discs that I have with OS 9 and then upgrade with the discs I have to get back to OS 9.2.2 but I'm afraid that if I do that my machine won't boot at all because it hates 9 now and loves X. I just bought a new pram battery so I hope that helps but I doubt it.  Also just to be clear I have OS 9 classic installed on this machine and it starts up and runs fine in OS X but certain programs won't launch such as ...............PROTOOLS!!!! AAGH which goes right up to the point of loading plugins and then says "unable to create a DAE Deck". I know there has to be a simple answer for this is any body out there?
    I'm running OS 9.2.2 (not) and OS X tiger (unfortunately) on a G4 450 with a protools expansion chassis hooked up and digidesign quiet drive (which isn't very quiet) everything appears to show up fine on and work on the desk top and digi init and Quicktime all show up when launching OS 9 classic after booting from OS X. This machine was built to run OS 9 ......OS 9 not OS X but now it has decided never to boot in OS 9 again! Can somebody please tell me why?

    The Sawtooth G4 will only run Mac OS 9 discs that look like:
    http://www.wap.org/journal/macos9/OS-9c.jpg
    with either 9.0, 9.0.2, 9.0.4, 9.1, 9.2.1 in fine print on the left.
    No system specific Mac OS 9 disc will work, nor update, nor dropin.
    Booting off Mac OS 9 on the hard drive if you erased and installed Mac OS X requires installing Mac OS 9 drivers first:
    Mac OS X: About the "Install Mac OS 9 Drivers" Option in Disk Utility
    Make sure you are indeed talking the Sawtooth (AGP PowerMac), and not the earlier revision known as Yikes (PCI PowerMac):
    Power Mac G4: How to Differentiate Between Models
    The Sawtooth is the first one to support the startup manager for booting:
    Use the Option key, when possible instead of 'C' key to boot discs
    And that's handy because it works on multiple partitions, showing you the last operating system that Startup Disk Control Panel or System preference selected to boot. 
    Classic mode, sadly does not support Mac OS 9 extensions very well.   You have to boot directly into Mac OS 9 for specific extensions, which may answer a Protools in Classic mode issue.

  • Boot OS9 in Target Disk Mode on iMac G5

    Hi! Wonder if any of you good people can help. I have an application which will only run on a native OS9 platform, but I would like to be able to boot OS9 off an external Firewire drive for ease of use from an iMac G5.
    How can this be acheived? I have a dual boot eMac. Is it possible to use carbon copy cloner to copy this drive and install it on the external firewire HDD?
    I would very much appreciate any help anyone can offer.
    Many thanks,
    Andrew

    Hi, Andrew -
    I'm looking for ways to future proof my equipment so if the eMac dies, I atleast have an alternative.
    As far as I know none of the current lineup of new Macs is OS 9 bootable, and this won't change in future releases.
    I'd suggest doing two things -
    Check on eBay or other sources, like on-line dealers of used Macs, for an OS 9-bootable machine of adequate speed - a G4 Quicksilver or early MDD model, for example, or another early eMac. Get it, refurbish it if necessary, and keep it safe as a backup. If it's going to sit for a while, get a spare internal battery for it.
    Investigate alternative software, something that will do the job and that will also run in OSX. For the long term this would be a better solution.

  • Pismo with Tiger won't go into target disk mode

    I recently upgraded my Pismo to Tiger and can't seem to boot into firewire target disk mode. The computer restarts and gives me a terminal screen that reads: "can't OPEN DISK" and then goes on to say "Welcome to Open Firmware. To continue booting, type "mac-boot"..."
    I tried zapping the pram, but that did nothing. Does anybody have any suggestions?

    MacUser,
    When booted in 10.4.8, select Target Disk Mode in the System Preferences > Startup Disk and see what happens.
    If no success, try resetting Open Firmware (from Apple docs):
    Boot into Open Firmware by holding down the 'Command-Option-O-F' keys from a cold start while the chime is being played. You will see a command-line screen...enter these commands:
    1. At the Open Firmware prompt, type: reset-nvram
    2. Press Return.
    3. At the Open Firmware prompt, type: reset-all
    4. Press Return.
    Example:
    0 > reset-nvram
    Press Return
    0 > reset-all
    Press Return
    The reset-all command should cause the computer to restart. If this occurs, you have successfully reset the Open Firmware settings.

  • Won't go into Target Disk Mode

    Help,
    I have an iMac that is several years old, OS X v. 10.3.9, has never had any trouble. I recently bought a new MacBook Pro and have been trying to move files over from the iMac, but I cannot get the iMac to boot up in Target Disk Mode.
    I reboot, hold the "T" key, etc., and the FireWire symbol comes up, but then it just slowly bounces around the screen while the machine whirs away, and I don't get any further.
    Open Firmware Password is not activated; I've run software updates.
    Any suggestions would be greatly appreciated.
    Thanks

    Hi,
    A while back I tried what you have and also, the Panther OS G4 would not show up on the Tiger OS G4, although the Panther OS was in Target Disk Mode with the floating icon.
    The connection was per instructions, both on line and step-by-step per the Tiger OS, but no disk showed up even after a few hours of wait.
    What I found is that my Panther OS G4 Firewire socket was 'mushy' (it moved fairly easy from slight finger pressure on the plug-in end... it was not 'firm' like my USB socket was. So I tried a Firewire external drive I have, that did work before, and it too, did not show-up (although it did start it by being plugged in). Everything I tried with that Firewire socket on the Panther Computer was not there... although these did work on the Tiger Computer.
    Since the Firewire is soldered onto the motherboard I have come to the conclusion that one or more of the connections are disconnected... perhaps not the power one, as the external items react to the plug-in, but there is no 'communication' after the fact.
    Perhaps this is what has happened on the iMac end for you. And yes, I have used that Firewire plug many many times and not always with TLC in the past, as it is a laptop.
    Now I use a Firewire 400 to Firewire 800 (either direction works, depending on what plug works on which item) for what I have and do... as to repair it would be more then a new computer and the Panther computer is an '05 model (but still used daily for what it does).
    Maybe you can check how 'solid' your iMac feels when it is plugged in with the Firewire, compare it to other connections... do it gently though, but if it is loose you will know by the 'mushy give' it has.

  • G5 won't boot but will go to target disk mode

    Hi,
    Well it started like this: suddenly a dark grey veil lowered across the screen with a notice in several languages saying "you must restart your mac" (or something to that effect). I panicked and pressed the power button, the mac shut down.
    I started it again but it only got as far as the grey Apple screen and then sat there for a while until the fans started ramping up in the famous jet engine style. I shut it down again.
    I have tried starting it:
    In single user mode = no joy, same as above
    In safe mode = some text on a black background, keyboard not functional, fans start going crazy again.
    In target disk mode = everything exactly as one might expect, all files accessable, fans ticking over normally.
    I have attached an ibook to it, booted the G5 in Target disk mode and run disk utility, repair, but it reported the disk "could not be unmounted". There was a lot of clicking from the G5 though so I assume something happened. I then ran "verify" and it reported that everything was fine.
    The G5 still won't start, exhibiting the same symtoms as before.
    Anyone got any ideas?
    Cheers,
    Cliff

    Hi Cliff, and a warm welcome to the forums!
    See if any of this gives us more clues....
    How to reset the SMU on a Power Mac G5 (Late 2004) or Power Mac G5 (Late 2005) ...
    http://support.apple.com/kb/HT1436
    Earlier G3, G4, G5 models...
    http://support.apple.com/kb/HT1939
    PM G5 won't start...
    http://support.apple.com/kb/HT2173

  • Powerbook won't boot past apple screen, disk utility can't repair

    Last night I applied the most recent software updates, I don't remember exactly what they were but there was a Java update, a security update, a quicktime update and an itunes update. after the required restart, my powerbook g4 won't boot past the apple icon screen.
    I can't boot it into safe mode or single user mode.
    I can start it up in target disk mode and transfer a handful of files/directories at a time before it hangs.
    When I try to run the repair in Disk Utility against the target disk, it gets about halfway before the following:
    Verify and Repair disk “Macintosh HD”
    Checking HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    Invalid sibling link
    Volume check failed.
    Error: The underlying task reported failure on exit
    1 HFS volume checked
    1 volume could not be repaired because of an error
    the disk doesn't make any grinding or anything, just a few clicks when it tries to boot but nothing bad sounding.
    Is my computer hosed? Is it worth bringing it to the genius bar?

    Hi, Pat. How much time did you give DW to complete its work? Locating the data it needs to rebuild your directory can take a while — that's the step at which DW far outperforms other utilities. It digs deeper and tries harder than anything else, and that can take a long time. The longest successful DW "fix" I've seen reported here in the seven and a half years I've been participating in Apple Discussions was *14 days* of continuous work to find the necessary data and reconstruct a hard drive directory from it. That was after all other disk utilities had been tried and had failed; it was the user's last hope to save data that hadn't been backed up anywhere. If you haven't allowed DW at least a few hours to accomplish its task, give it another chance. And don't try to use the computer for anything at all while DW is working.

  • Macbook won't boot or start, constant disk drive noise

    I purchased a Macbook Pro and been using it constantly for over 2 years now but never seen a problem like this.
    I partitioned my HD to run Windows a while back but recently decided to remove it. I partitioned the HD back into its original state. While verifying the drive in Disk Utility, the drive said it had an error, don't remember what, but was able to repair it using the installation cd.
    Soon after i thought everything was normal but my computer started to slow down and freeze, I had to manually turn off my Mac by holding now the power button. This went on for a bit and soon afterwards the computer wont start at all. I also heard a beeping noise when i turned on my mac but that was only once.
    I dont hear a boot chime and the screen doesnt turn on. All i hear is the disk drive making its noise that it usually makes when you turn on the Mac but in this case it just keep making the noise.
    Has anyone encountered a problem like this before? Any help would be great. My data has been backed up but i would rather that i didnt has to reset my Mac. I'm guess is that the HD might be failing, if thats the case then i got no choice.

    Have you tried starting from the installation dvd? If it won't start from this it's likely to be a hardware problem.
    You could also try starting in target disk mode by holding the t key until you see the screen with the target on. Even if you don't see the screen light up still try the following. If you have access to a second Mac and a firewire cable try connecting the 2 with the cable after the attempted target mode startup and see whether the hd shows on the second machine. If it does then you probably have a failure of the graphics processor. I was able to do this earlier this year when my screen didn't light up.
    My next Q: Do you have the Applecare extended warranty? If you do then take it to your nearest authorised service centre for diagnosis.
    Neville
    Message was edited by: Neville Mayfield

  • Mac Mini won't Boot after Target Disk Mode

    We just bought a new iMac and used target disk mode via firewire from our older Mac Mini running OSX 10.4 to transfer data.  Now when we go to restart the mini, the grey screen appears with apple logo and it seems to try to boot up but after a long time alway just ends up with a blue screen.  I don't  think I "ejected" the mini properly from the imac after the target disk mode transfer.  Could the mini be stuck in target disk mode?  I've tried to restart in different modes eg. safe mode, pram by holding down keys on start up but doesnt make a difference at all almost as if the keyboard isn't registering (and its a wired keyboard).  Any ideas???
    Thanks

    Try starting up from the Recovery Partition holding the Option (Alt) key and see if you can Repair your Macintosh HD, as per > OS X: About OS X Recovery

  • Mini won't boot - tried many methods, disk visible in Target Disk Mode

    I have a PPC Mac Mini running Leopard. It stopped booting last week. It goes to the point where the Apple appears and then stops. No moving ring at the bottom of the screen.
    I've done the following w/ no luck to get it booting.
    1) Put it in Target Disk mode and run Disk Utility. Repaired permissions and did a Repair Disk. No issues found.
    2) Put it in Target Disk mode and ran Tech Tool Pro. Checked volume/file structures and sectors. Nothing found.
    3) Reset PRAM.
    In Target Disk Mode, I can see the files. But I want to get it running one last time to archive some program configuration files. I know I can erase and restore from a TM backup but I'm using that as a last resort. Other than trying Spinrite, any other ideas?

    You must be very keen on those config files. You are going thru a lot of work to get them. But if you must ...
    If you have an extra firwire external drive free, that you can partition with APM (Apple Partition Map) and format, then you could use your original install disc or Leopard install disc to install a bootable version of OSX on that external.
    Boot from the external, and then download the latest combo update for Leopard and install it on the internal drive. Hopefully that will fix the the internal enough to make it bootable.
    Another approach is to pay $100 for DiskWarrior. Most of the time it can fix a problem like yours ... but no guarantees. It is a worthwhile program to own anyway, however.

  • Won't boot, recognise superdrive or startup in target disk mode

    I've been trying to help a friend with his iMac G4 that crashed. Of course he hasn't backed up his hard drive in years. I've searched the forums and have tried several methods to get his machine running or at least recover his data but with no luck.
    Here's what happens:
    When I turn on his computer I can hear repeated clicking which eventually stops. The screen comes up grey and eventually a flashing icon appears, alternating between a folder with a Finder icon and a folder with a question mark.
    Here's what I've tried:
    I've tried booting in target disk mode but that doesn't work.
    I've tried booting holding down the mouse button but the superdrive tray doesn't open.
    I've booted into Open Firmware and typed "eject cd". The system pauses for a long time then gives me the message "can't OPEN the EJECT device".
    I've manually opened the superdrive tray, loaded a disc, then booted while holding down the "c" key. I can hear the drive spin, but the computer doesn't boot from the disk. I've tried loading a Tiger DVD, a DiskWarrior CD and an OS 9 CD.
    I've tried removing the Airport card and additional RAM.
    I've tried resetting the PRAM.
    I've tried resetting the PMU.
    I've booted into Open Firmware and typed "reset-nvram" then "reset-all".
    Nothing has worked. The computer always returns to the flashing Finder/question mark folder.
    I'd really appreciate any suggestions on where to go from here.
    Thanks!

    When you can't boot from any method it usually signals that one of 2 things (maybe both) have failed:
    Motherboard
    Hard drive - Some hard drive failures lock up the ATA controller so badly that the Mac can't boot from any device.

  • PowerBook G4 17" Boots into Open Firmware; Won't boot from HD or Disk

    This PBG417 (1GHz/512MB/60GB) has an complex recent history directly related to this problem. It was thought to have a dead logic board, and was given to me for a very insignificant amount of money. I discovered today (at an Authorized Apple Repair center) it merely had a ribbon cable disconnected from the logic board which kept it from powering on, which, when rge cable was reconnected it did on the spot, fully booting (imagine my satisfaction). However, upon getting home, it booted into Open Firmware instead, and offedrs a choice of typing mac-boot or shut-down. Mac-boot takes it to the grey screen where the question mark/Finder guy blink and nothing happens. I put a grey PowerBook G4 17" system disk in, but not the one that shipped with it, hoping it would do. When I try to boot from disk, it goes to Open Firmware, I enter mac-boot, it goes to happy Finder with no question folder, but stays there with the optical drive occasionally making movememts and sounds. If you enter any command besides shut down or mac-boot, iot says unknown word; the command prompt itself is 0> .
    I'm not sure the hard drive is seated correctly. When I got the computer, the drive was removed; I put it in an enclosure and installed Tiger on it and put it back in, but apart from connecting the ribbon cable, it just sat in its bay not fixed down. However, it booted correctly the first time it was successfully started.
    Finally, the previous owner removed all 23 bottom case screws when he took out the drive and lost them; the Apple repair tech mustered up about 9 and put them in the crucial locations but it's still not screwed down everywhere, although the one time it booted correctly, it had no screws in it.
    It seems the computer doesn't read the hard drive or the disk, but the hard drive mau be installed wrong and the disk, while for a 17" was not the one that shipped with this PowerBook 17". The computer is missing many case screws, bnutg booted properly only when there were none it place. I also tried resetting the PMU but am not sure I did reset it because the Apple article isn't clear about which models have which processes. I tied Target Disk Mode but it woujldn't mount/boot.
    How can I get the disk out and how to make it boot to the desktop?

    You can try to reset NVRAM here is KBase from apple site:
    http://docs.info.apple.com/article.html?artnum=42642
    and after that reset PRAM in your unit, here is the kbase:
    http://docs.info.apple.com/article.html?artnum=2238
    If needed you can also tried to reset PMU, here is the kbase:
    http://docs.info.apple.com/article.html?artnum=14449
    Make sure you choose the correct step for your unit.
    If after all the steps your unit still booting up to open firmware then there is possibility that you have corrupt NVRAM which could not be fixed by doing reset except replacing logic board.
    Good luck. Hope this help
    Flippo

Maybe you are looking for