Firewire External HD with Clone won't boot

I just installed an OWC Mercury Elite-AL Pro 250GB external Firewire 400 HD to supplement storage on my eMac. I used the supplied Prosoft DataBackup 3 software (supplied with the OWC drive) to Clone my internal drive to the external drive, following instructions to make the Clone bootable.
The software indicated a successful backup, and Disk Utility shows the volume as "Bootable".
But, when I choose the external drive as the boot drive in the Startup prefs, it gets to the Apple Gray screen, and the little clock/fan thingy just spins and spins (I've waited as long as 10 minutes).
If I use the Option key on startup, the Startup Manager shows both drives as available (with the little "X" on the corner of both the internal and external drives), but choosing the external drive at this point doesn't work either.
Any suggestions as to what I may have done wrong, or what else I should try.
Thanks
PowerMac G4 Dual 1.25 & G4 17 Powerbook Mac OS X (10.4.9) 1.0 eMac, D-Link DSL Router & Switch, D-Link USB Hub

Download either Carbon Copy Cloner or SuperDuper. Both are good cloning programs and are both free to try (CCC all the time, SD is shareware). SD is a bit easier to get going and use, but CCC works fine and I use it because it is donationware. SD locks you out of certain functions in the free version.
Anyway... Try cloning your drive with one of those and see if you can then boot off it. If you can, then the software that came with the drive is either crud, or you just happened to get a bad clone that time. If the drive still doesn't boot, then that particular model may not fully be bootable compatible (it happens sometimes).
Patrick

Similar Messages

External hard drive(s) won't boot

Okay, I am at my wits end here. I hope someone may be able to help.
An earlier discussion on this board concluded that the hard drive on my PPC iMac (flower pot) is a goner, so I purchased an OWC Mercury elite AL-Pro 250 GB external drive. I partitioned the drive and set it to the Apple Partition Map as per the instructions, then installed the Leopard OS from the black retail disk to the external drive. After several failed attempts, the OS successfully installed on the drive. The drive showed up on my desktop and when I clicked on the drive it had folders for applications, system etc that make me think it was installed.
BUT when I tried to boot from the external drive, I just got a gray screen. I tried the startup manager and the external drive didn't even show up. I wiped the drive and started over with the same results. So I hooked the drive up to my iBook G4 that runs on PPC, erased the drive, reinstalled the OS and selected the external drive as the startup disk and got the gray screen. So I repeated again and got the same results again. When I tried startup manager on my laptop, I only saw the Mac HD and the drive didn't show up as a possible startup disk, even though it is hooked up and available on my desktop.
So I called OWC tech support. We agreed that the OS was installing but the external drive wasn't booting. The tech guy concluded the drive must be faulty and sent me a replacement.
I eagerly formatted the SECOND hard drive and installed the OS from the install disk on my iMac. First install attempt failed and said the drive must be damaged. I run the repair disk utility and it found a few issues but said they were repaired. So I tried again and the install failed with the same message. So I moved everything over to my laptop and over the course of an hour or so got the OS installed. I then selected the drive as the startup disk (in system preferences), restarted and . . . gray screen. Startup manager shows. . . . no external drive. The drive is available on my desktop but just won't boot.
What am I doing wrong???? I am so frustrated and confused. Please, any help or thoughts?
PS -- interestingly, in the process of installing on the first drive, the internal hard drive on my iMac reappeared from wherever it had vanished to and I erased and partitioned it for the heck of it and the #!&*&% kernel panics that started this whole mess reappeared. Now every single time I start the computer booting from the prodigal internal hard drive I get a kernel panic about 5 seconds after the space scene appears. Agghhh.

BUT when I tried to boot from the external drive, I just got a gray screen. I tried the startup manager and the external drive didn't even show up.
You need to use a firewire connection on all PPCs.
This may be the problem.
My OWC Mercury drive is a little finicky about booting. It needs to be powered down before it will boot. The sequence that works for me.
1) You need to power off everything.
2) poweron external drive.
3) Wait til external drive stablizes ( 10 seconds??? )
4) Holding down the option key then power on iMac. This brings up the startup manager. Click on your external hd. Click on right arrow key.
( once you get it to work, powering off the external drive is probably enough. ) The drive only seems to be bootable right after a poweron. Once you get it to work, you can put all on a power strip. Configure Mac OS X to boot from external drive. Flip powerstrip switch & I thnk all is well.
Robert

G4 boot from external OS9, but now won't boot back to 10.4?

Sorry if this may be a little confusing..
Basically I have an old sawtooth/AGP single processor unit from a friend who moved to New Zealand to work on a movie/graphics project.
He upgraded it to a newtech 1.6 processor.
The problem is I booted into 9.2 via external firewire as I still have some specialty cards/apps that are not supported in 10. The mouse will not "click" for selection purposes, it only moves the cursor which does not allow me to go into the control panels and select the "startup disk" utility and go back to 10.4 or anything else for that matter.
I unplugged the external firewire while shut down and restarted assuming it would pick one of the two internal drives with OSX.
It did not! It gets to the grey OSX "apple logo" screen and then powers off.
When I plug the external back in, it will start all the way to desktop9, but the same problem persists in that neither the new wireless mouse nor the old G3 puck will click.
I do not have an apple keyboard that works, so the "new" wireless one will not work for keyboard startup commands, so I cannot just press "x" or "c" and boot to another source that way. I do have a G3 usb mouse I dug out of the closet (I just recently recycled my old Apple II+ from said same closet) but as I said it does not "click".
I tried the programmer's button while in OS9 to try to command boot to the OSx drives. The dialog box showed up, but it won't take the commands; ie: nothing happened.
Next I tried plugging the firewire (while shut down) into an external with OSX. Nothing!
I plugged it back into the 9 drive and get to the desktop with the same useless mouse problem.
I am considering pulling the internal battery in hopes it will kill the boot memory and perhaps default back to the OSX disks again.
Any thoughts and ideas are much appreciated!
Many Thanks!
El Jefe de Biosmell!

Hi, biosmell -
I am considering pulling the internal battery in hopes it will kill the boot memory and perhaps default back to the OSX disks again.
That should work to reset PRAM, which contains the boot volume selection. Be sure to also pull the power cord, and to wait long enough; about a half hour should be fine.
After replacing the battery and reconnecting the power cord, wait another couple of minutes and then boot it - by default it should boot to the first OS it finds on a local (i.e., internal) hard drive.

Firewire card installation failed, now won't boot into os x

G4 gigabit dual 450 was working fine except firewire port wasn't so I installed a firewire port card. On reboot i got/get a nice startup tone but the screen stops on the grey on grey apple image... with the grey bar circle spinning, and won't move into os x. I tried the button switch (PMU? counted to 12) by the internal battery, but no change. HELP, please...
(I took the firewire card out)

Hi
Dale Wiesshaar,
I installed YellowDog Linux last week. I deleted the installation, personal reasons, and tried to install this week.
Guess what happened? All three firewire ports are not working.
When trying to install YDL, the installation tries to load the ohci1394 driver and abends, dumps, throws and exception, whatever.
In addition, none of the 4 daisy chained firewire drives appear on the desktop. None of the additional 3 daisy chained firewire drives appear on the desktop. The firewire camera does not appear on the desktop.
So I broke the chain into a 15 feet chains, and distributed the chains over 2 external firewire ports. Four devices are on one chain, and two devices are on the other chain. The other firewire device was moved to the 12 port usb hub (this device switches b/w usb/firewire). The camera is off the chain entirely.
The following are the installed extensions on my mac:
IOFireWireAVC.kext
IOFireWireFamily.kext
IOFireWireIP.kext
IOFireWireSBP2.kext
IOFireWireSerialBusProtocolTransport.kext
This is the fix I performed: http://www.index-site.com/firewirebug2.html#RESETPMU
pull the plug on all devices and power mac; waited an entire day to replug
reset-all = in open firmware
reset parameter ram
broke up the chain of firewire devices to 15 feet each, on each port
blew any dust particles from the firewire ports
lastly, reset PMU
the battery is problably less than 2 years old (my mac is 10 to 12 years old; it is my personal computer)
None of the above fixes restored my firewire ports. Therefore, I purchased a firewire card. All firewire devices appear within the finder.app.
I am not able to install YDL. YDL allows me to perform a multiple boot:
Linux
MacOSX
MacOS
OpenFirmWare
CD
NetWork
(for security reasons i do not perform all of these boots)
When YDL attempts to load the ohci1394 driver, it fails. I removed the new firewire card, now I am back to circle one.
I will now try the following solutions:
combo update
repair permissions
If this does not work, I will reseat my fireWire card and not install YDL.
Thank you in advance for your assistance, and helpful post on the fireWire conumdrum.

System file tampered with - Mac won't boot up. HELP!

Hi i have somehow managed to delete part of my system file and now when i try to start the computer it is fixed on the start up screen but the login box does not appear just a blue screen.
Is there anything i can do to overcome this problem? For example some way to reset my mac?
Any replies would be greatly appreciated

If you've deleted system files then you will need to reinstall OS X. If you are using Snow Leopard then the reinstall will not erase the drive. If you are using Leopard then you will need to do an Archive and Install to avoid erasing the drive:
How to Perform an Archive and Install
An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
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, Leopard or Snow Leopard.) 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 click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro 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.

External Hard Drive, System won't boot

I recently purchased a Western Digital 750 gb hard drive. I reformatted it to Mac Journaled and it is connected through firewire 400. It works great and all, but I've noticed that it has significantly slowed my system startup time when I press the power button (recently, it won't start at all). After I unplug the firewire cord and press the power button, it starts normally. I'd rather not have to unplug my hard drive every time I turn my computer off.
Please Help.

ok... i don't recall reading what kind of enclosure it wasin???
I don't think you are going to get away from the problem of unplugging and plugging back in... I have to do the same thing with TWO of my drives - one is firewire and one is USB2.0...
no one has been able to provide a solution for me and I know for a fact my drives are fine and the cables are new (and i have tried using others). i switch between my mac and pc's with the drive all the time and there has never been an issue with the drive... just the same problem you are seeing, have to unplug and plug back in.
ciao

Early 2008 with 8800 won't boot

When the machine is post chime.... I get horizontal blue lines that look like tire treads up and down the screen which makes me think video card. In verbose mode it stops in the same spot each time... the drive is reading I can hear it and then it just stops loading. I did FSCK -FY in single user mode and it modified things, ran it until it again until I got the disk was "okay" message. I get the blue lines regardless of the boot device, and no drive will boot all the way in. The funny thing is, this happened yesterday and after doing the FSCK -FY in single user mode everything booted fine, but after sleeping the machine last night it woke up not working, just blue lines on the screen. Things I've done:
Flashed the PRAM many times.
Unplugged everything and let it sit for 15+ seconds, then plugged in display and keyb to clear the SMB
Removed RAM and tried various combinations. No LED indicators to indicate RAM issues
Reseated all drives and the video card, as well as RAM obviously see above
I pulled the trigger on a new video card which will arive whenever it gets here in case it is the card. Got the ATI 5770 which supposedly works on the Early 2008 model. I had been planning on doing this for awhile as playing RIFT has had the video card fan revving constantly so it's been pushed hard, plus I do a lot of video editing. If anyone has any other ideas please let me know. The last shutdown condition = 3 whatever that means. Any other ideas would be apprecated. I'll post back otherwise when i get the new card and report.
Eric

Oh and I had forgot to mention, I'd tried more than one display, and both DVI ports on the 8800 with the same result, so the cause of the lines is not external.

G3 B&W with Tiger won't boot

hi
i got a used Power Mac g3 (350mhz, 512mb, 6gb, CD,)with Tiger installed, but during the boot process, it stops at the "Starting Mac OS X" It still shows the progress bar and it is still moving, but i think it must have errors and cannot progress. I am a noobie to Macs, but i have been arround Windows PCs and Linux for a long time....By the way i got Ubuntu PPC to boot nicely on it, so i think the problem must be software. I will gladly buy OS X Tiger, if that will fix the problem (reinstalling) But i want to make sure it is software before i buy any software.....thanks,
bones

upgrade the hard drive to a 60gb or 80gb, this should be no problem, right??
It is very important to determine whether you have a Rev 1 or Rev 2. The rev 1 "HeartBreaker" Blue & White generally does not respond well to a new hard drive that is any faster than the stock model. Rather than generating error messages, it gets so flaky and unreliable as to be unuseable.
This article show the "stacking bracket". If you have that, you almost certainly have a rev 2 [the reverse is NOT true.]
58193 -- Power Macintosh G3 (Blue and White): Additional Hard Drive Installation Options
This article discusses the definitive test for whether your is a Rev 2, reading the part number off the IDE/ATA chip, [646U2-402 for Rev 2}:
New Features of the latest [Rev 2] B&W G3

Created zone with defaults won't boot completely (Solaris 10, Update 1)

If I create a zone with defaults, i.e. allowing the zone to inherit the typical package dirs, the resulting zone does not boot completely. When I attach to the zone via zlogin, the zone looks to be in an administrative state. It never boots to a point where one would typically enter in the initial configuration info, e.g. timezone and root password.
However if I create the zone after first removing the inherited dirs, the zone boots to a state where it subsequently can be confiured and fully booted.
Looks as if the SMF facilities are not fully initialized when the zone is configured to inherit its packages. This could be a red herring as I'm a newbie who's moved over from Linux and starting to understand SMF specifically and Solaris in general.
I did not have this problem with Solaris 10. I've just installed Solaris 10 Update 1; the problem seems specific to that installation. I reinstalled and the problem persists.

I snipped the output because there were some errors, which on retrospect seems to have been a silly decision. I repeated the process and captured the missing output:
# zoneadm -z foo install
Preparing to install zone <foo>.
Creating list of files to copy from the global zone.
Copying <5913> files to the zone.
Initializing zone product registry.
Determining zone package initialization order.
Preparing to initialize <942> packages on the zone.
Initialized <942> packages on zone.
Zone <foo> is initialized.
Installation of <1> packages was skipped.
Installation of these packages generated warnings: <SUNWxwfnt
SUNWxwplt SUNWxwcft SUNWjxmft SUNWxwpls SUNWpmowu
SUNWxilrl SUNWolrte SUNWi13rf SUNWi15rf SUNWi2rf SUNWi5rf
SUNWi7rf SUNWi9rf SUNWtxfnt SUNWdoc SUNWi1of SUNWi4rf
SUNWi8rf SUNW1251f SUNWarrf SUNWxwoft SUNWxwxst
SUNWkoi8f SUNWasu SUNWxrpcrt SUNWasac SUNWasdb
SUNWasut>
The file </zone/foo/root/var/sadm/system/logs/install_log> contains a log of the zone installation.The packages are related to App development and X11. I don't see any that might be related to SMF.
The logfile is too large to post at over 37K lines. However there seemed to be a pattern to the package failures. Hopefully these greps highlight the important messages:
# grep "partially failed" /zone/foo/root/var/sadm/system/logs/install_log
Installation of <SUNWxwfnt> on zone <foo> partially failed.
Installation of <SUNWxwplt> on zone <foo> partially failed.
Installation of <SUNWxwcft> on zone <foo> partially failed.
Installation of <SUNWjxmft> on zone <foo> partially failed.
Installation of <SUNWxwpls> on zone <foo> partially failed.
Installation of <SUNWpmowu> on zone <foo> partially failed.
Installation of <SUNWxilrl> on zone <foo> partially failed.
Installation of <SUNWolrte> on zone <foo> partially failed.
Installation of <SUNWi13rf> on zone <foo> partially failed.
Installation of <SUNWi15rf> on zone <foo> partially failed.
Installation of <SUNWi2rf> on zone <foo> partially failed.
Installation of <SUNWi5rf> on zone <foo> partially failed.
Installation of <SUNWi7rf> on zone <foo> partially failed.
Installation of <SUNWi9rf> on zone <foo> partially failed.
Installation of <SUNWtxfnt> on zone <foo> partially failed.
Installation of <SUNWdoc> on zone <foo> partially failed.
Installation of <SUNWi1of> on zone <foo> partially failed.
Installation of <SUNWi4rf> on zone <foo> partially failed.
Installation of <SUNWi8rf> on zone <foo> partially failed.
Installation of <SUNW1251f> on zone <foo> partially failed.
Installation of <SUNWarrf> on zone <foo> partially failed.
Installation of <SUNWxwoft> on zone <foo> partially failed.
Installation of <SUNWxwxst> on zone <foo> partially failed.
Installation of <SUNWkoi8f> on zone <foo> partially failed.
Installation of <SUNWasu> on zone <foo> partially failed.
Installation of <SUNWxrpcrt> on zone <foo> partially failed.
Installation of <SUNWasac> on zone <foo> partially failed.
Installation of <SUNWasdb> on zone <foo> partially failed.
Installation of <SUNWasut> on zone <foo> partially failed.and# grep "not installed" /zone/foo/root/var/sadm/system/logs/install_log
*** package <SPROmrdwf> was not installed:
*** package <SPROdwrfb> was not installed:
*** package <SPROlang> was not installed:
*** package <SPROlangx> was not installed:
*** package <SPROdwrfx> was not installed:
*** package <SPROsbld> was not installed:
*** package <SPROsbldx> was not installed:
*** package <SPROrdbkb> was not installed:
*** package <SPROrdbkx> was not installed:
*** package <SPROcc> was not installed:
*** package <SPROutool> was not installed:
*** package <SPROmrcc> was not installed:
*** package <SPROmrcom> was not installed:
*** package <SPROmr3m> was not installed:
*** package <SPROmrtcv> was not installed:
*** package <SPROm9xs> was not installed:
*** package <SPROsunms> was not installed:
*** package <SPROsmsx> was not installed:
*** package <SPROsmpx> was not installed:
*** package <SPROmrsbe> was not installed:
*** package <SPROsbe> was not installed:
*** package <SPROpnsn> was not installed:
*** package <SPROfd> was not installed:
*** package <SPROupdck> was not installed:
*** package <SPROcpl> was not installed:
*** package <SPROcplx> was not installed:
*** package <SPROcmpl> was not installed:
*** package <SPROtlbn7> was not installed:
*** package <SPROtll7> was not installed:
*** package <SPROtl7x> was not installed:
*** package <SPROtll7x> was not installed:
*** package <SPROscl> was not installed:
*** package <SPROsclx> was not installed:
*** package <SPROmrstd> was not installed:
*** package <SPROmrcpl> was not installed:
*** package <SPROstl4h> was not installed:
*** package <SPROstl4a> was not installed:
*** package <SPROstl4o> was not installed:
*** package <SPROstl4x> was not installed:
*** package <SPROstl4y> was not installed:
*** package <SPROftool> was not installed:
*** package <SPROl90> was not installed:
*** package <SPROl90x> was not installed:
*** package <SPROl90s> was not installed:
*** package <SPROl90sx> was not installed:
*** package <SPROf90> was not installed:
*** package <SPROmrftn> was not installed:
*** package <SPROgc> was not installed:
*** package <SPROlgc> was not installed:
*** package <SPROgcx> was not installed:
*** package <SPROlgcx> was not installed:
*** package <SPROdbx> was not installed:
*** package <SPROdbxx> was not installed:
*** package <SPROjdbx> was not installed:
*** package <SPROjdbxx> was not installed:
*** package <SPROmrdbx> was not installed:
*** package <SPROdemo> was not installed:
*** package <SPROdmake> was not installed:
*** package <SPROmrdmk> was not installed:
*** package <SPROtdemo> was not installed:
*** package <SPROmride> was not installed:
*** package <SPROdbxui> was not installed:
*** package <SPROsvc> was not installed:
*** package <SPROxdplg> was not installed:
*** package <SPROidext> was not installed:
*** package <SPROjnsnb> was not installed:
*** package <SPROjnsrt> was not installed:
*** package <SPROjnsup> was not installed:
*** package <SPROctags> was not installed:
*** package <SUNWnbide> was not installed:
*** package <SUNWnbcpp> was not installed:
*** package <SUJAnbcpp> was not installed:
*** package <SUZHnbcpp> was not installed:
*** package <SUNWexted> was not installed:
*** package <SUJAexted> was not installed:
*** package <SUZHexted> was not installed:
*** package <SPROnbreg> was not installed:
*** package <SPROfdxd> was not installed:
*** package <SPROmrxd> was not installed:
*** package <SPROgvim> was not installed:
*** package <SPROxmbin> was not installed:
*** package <SPROxmshr> was not installed:
*** package <SPROxmsrc> was not installed:
*** package <SPROmrxm> was not installed:
*** package <SPROprfan> was not installed:
*** package <SPROmrpan> was not installed:
*** package <SPROprfax> was not installed:
*** package <SPROprflb> was not installed:
*** package <SPROprflx> was not installed:
*** package <SPROprfgn> was not installed:
*** package <SPROmrpgn> was not installed:
*** package <SPROhtbas> was not installed:
*** package <SPROhttl7> was not installed:
*** package <SPROhtstd> was not installed:
*** package <SPROhtxd> was not installed:
*** package <SPROdwrfs> was not installed:
*** package <SPROrdbks> was not installed:
*** package <SPROctsrc> was not installed:
*** package <SPROplg> was not installed:
*** package <SPROpl> was not installed:
*** package <SPROplx> was not installed:
*** package <SPROpls> was not installed:
*** package <SPROplsx> was not installed:
*** package <SPROmrpl> was not installed:These messages seem to be inline with the general output captured from the zone install itself.
> What does "svcadm list -vc" give you when you started the zone ?
I took that as a typo, instead using "zoneadm?"
# zoneadm list -vc
ID NAME             STATUS         PATH
   0 global           running        /
   7 foo              running        /zone/fooThe zone is not on its own slice, however "/zone" is mounted as a loopback from /export/zone. I don't think that's a problem since the zone install seems to work if I don't inherit packages. Unless perhaps its a nesting level of lofs's.
FWIW,
# mount |grep zone
/zone on /export/zone read/write/setuid/devices/dev=1540000 on Fri Feb 24 16:10:55 2006
/zone/foo/root/dev on /zone/foo/dev read/write/setuid/devices/zonedevfs/dev=4640007 on Tue Feb 28 13:13:03 2006
/zone/foo/root/lib on /lib read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/platform on /platform read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/sbin on /sbin read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/usr on /usr read only/setuid/nodevices/nosub/dev=dc0440 on Tue Feb 28 13:13:03 2006
/zone/foo/root/proc on proc read/write/setuid/nodevices/zone=foo/dev=4400007 on Tue Feb 28 13:13:06 2006
/zone/foo/root/system/contract on ctfs read/write/setuid/nodevices/zone=foo/dev=43c0008 on Tue Feb 28 13:13:06 2006
/zone/foo/root/etc/svc/volatile on swap read/write/setuid/nodevices/xattr/zone=foo/dev=448000e on Tue Feb 28 13:13:06 2006
/zone/foo/root/etc/mnttab on mnttab read/write/setuid/nodevices/zone=foo/dev=4440008 on Tue Feb 28 13:13:06 2006

Windows 200 PC with SP4 won't boot after install of iPod software from CD.

I installed the iPod software from the CD of my new iPod mini. It requested that I reboot the PC, which I did but it never rebooted. It hung and would not even boot in safe mode. After many attempts I booted to the boot console and when throught the install repair process. The PC will still not boot.
Is there any way to bring up the PC without having to rebuild it?
Has anyone found a way to get the PC back to it's original state, without a disk re-format?
Does Apple have a solution?
Any comments from Apple Support or their QA team would be of interest

Last know good does not work. I don't receive any error messages. I did the repair but PC still will not boot. The starting windows bar goes about three quarter of the way to the right and then it just stops. It does this regardless fo which boot mode I choose (ie. safe mode).
I do not have the iPod plugged in during this process.
Is there anything else I can do or that we can try from the console command mode?

MacBook pro with retina won't boot. Dark blue screen on start up. Any thoughts.

my MacBook pro will not boot up. I have no idea what happened to it. It is only a few months old. I have tried safe mode but that doesn't seem to work either.

FIxed

Boot from Firewire External, OS 9.2, Lombard 400 with OrangeLink card?

I have a Lombard 400, running 9.2.1 with an OrangeLink Card. I have a Firewire external drive with a bootable 10.3.9 drive cloned to it. I have sucessfully booted from this drive to clone the drive to another powerbook I have, so I know it is bootable. The firewire drive shows up on the desktop of the Lombard and I can choose it as the startup disk in the control panel. However, when I restart the computer, it boots back into OS 9. What step am I missing here? I read documentation that the Firewire card is okay for booting.

Amy,
Unfortunately you cannot boot through a FireWire PC card; it does not have the onboard firmware necessary to initialize at startup as does built-in FireWire. In addition, it does require supporting software and this does not load until the OS loads. The only bootable external drive would be a pure SCSI HD or an ATA/IDE HD in a case that uses a SCSI interface.
There is one possible alternative which I have never tried, but the application XPostFacto, used to install OSX on unsupported machines, can be used as a "helper" to boot an external FW drive through a PC card. How well this works I just don't know...
http://eshop.macsales.com/OSXCenter/XPostFacto/

IMac won't boot with external drives attached

I am using iMac 27" Late 2013 model upgraded to mavericks 10.9.4. Two external drives are always attached with it, one is segate 3.5" 2TB USB 3.0 drive and another one is 2.5" usb 2.0 drive.
when i start my imac with external drives attached it won't boot up. Stuck at plain white screen after a startup chime, not even any apple logo or any progress circle appears. And i have to detach all of my drives to make it boot.
This problem arises after upgrading to mavericks. Already tried resetting PRAM, SMC and checked Startup disk and verify disk with disk utility.

Raja,
Do a SMC reset perhaps even a couple of times and see if that helps. Also in System Preferences + Startup Disk make sure the internal HD is selected.
SMC RESET
Shut down the computer.
Unplug the computer's power cord and all peripherals.
Press and hold the power button for 5 seconds.
Release the power button.
Attach the computers power cable.
Press the power button to turn on the computer.
PRAM RESET
Shut down the computer.
Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
Turn on the computer.
Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
Hold the keys down until the computer restarts and you hear the startup sound for the second time.
Release the keys.
Roger

Help!! My Mac won't boot up!!

Hi,
I have a Dual 2.5 ghz G5 w/5 gb of RAM. I just purchased the Adobe CS3 Master collection and I was about to install it on my computer when noticed that it said the OS had to be 10.4.9. I was running 10.4.8. So I went to the downloads section of the apple website, downloaded the 10.4.9 combo update for PPC, and did the installation. Only when the installation finished, it said that the software didn't install, adn there was an error. I tried to open the .dmg again but it said that it couldn't open it because of a "broken pipe." So I trashed that .dmg and downloaded it again. This time, the .dmg wouldn't open at all and gave the same "broken pipe" message. So I tried to restart the computer...and now it won't boot up at all!!!
THe white screen shows up with the swirling little circle, but when it gets to the blue screen with the shiny apple and the status bar it just freezes! The status bar isn't even blue! It's just empty!!
I don't know what to do. When I had that error in the initial installation, did it erase my OS? I have a PowerBook running 10.4.8 too. Is there any way I can use my PowerBook to fix the G5? Help! Tech support is after hours already! I need this computer for big time production work!

Hi. If you cannot boot from the system DVD and repair the G5 boot drive (...?)
http://docs.info.apple.com/article.html?path=DiskUtility/10.5/en/duh1018.html
You may be able to use firewire TDM
http://docs.info.apple.com/article.html?artnum=58583
to access the G5 boot drive as the Target from the laptop and run Disk Utility(the one on the laptop) > Repair Disk on it.
Or you could connect the firewire external drive with the CCC clone on it to the G5, and try holding down the Option (alt) key on Startup - which should offer you the choice of booting from the external firewire drive - if it is bootable. Good Luck.

Mac won't boot after installing Kaspersky antivirus demo

when i turn on, the macbook pro has apple logo with spining grey thing but then it goes to just apple logo like normal and then it just stays like that instead of going into desktop?

I'm not sure that anything but a clone or Time Machine backup will work with Setup Assistant or Migration Assistant. Boot from the Recovery partition and use the Restore tab in Disk Utility. Drag your startup drive from the left pane (the indented icon that has your internal drive name) to the Source window. Drag the destination drive (the indented icon) to the Destination window. If you are copying to a drive with one partition this process will erase the destination drive. If you are copying to a partition on a drive with multiple partitions it will erase the partition you choose as the destination.
After the copying process is complete you can try booting from the cloned drive. Restart and press the option key after the startup chime. Keep the option key pressed until you see the Apple logo and spinning gear. Select the clone and click on Return to select it. If it boots run the Kaspersky uninstaller. Then download a copy of Carbon Copy Cloner (donationware) or SuperDuper! (free and paid versions). Use CCC or SuperDuper to copy the fixed clone back to your hard drive.
If the clone won't boot, and it probably won't, you will need to boot from the Recovery partition and choose to reinstall Lion. I haven't had to reinstall Lion or install it to an erased drive so if someone who has done so doesn't reply to this thread post a new question asking how to do it. It is my understanding that one is able to reinstall Lion over the existing installation or choose to erase the drive using Setup assistant to bring over your data from a clone. If you have to erase and install you will want to boot from the the Lion installation and clean off all the Kapersky stuff by searching for it (include invisible files in your search). Then you can use Migration assistant to bring your data back from your clone.
There is also a possibility that you can remove the Kapersky stuff by booting in single user mode. One you have your data copied to a bootable clone you could post a question about how to go about finding and removing the files in single user mode.

Firewire External HD with Clone won't boot

Similar Messages

Maybe you are looking for