MacPro dual Xenon 2.66ghz boot issues

I'm the new owner of a used Mac Pro. it's a dual 2.66ghz Xenon and it seems to have a booting issue. I'm an Network Admin in the PC world and I have some Mac knowledge.
I have disc's for Lepard & Snow Lepard and possibly Tiger. I cannot boot to any of these disc's or enter the diagnostic tests. To make it clear I can hold option and select the disc, however, the CD drive will spin for a few minutes then bring me to a black screen with a cursor that I can move but nothing else.
I have tried to reset the PRAM manually also with no difference.
The really interesting part is that I put a SATA hard drive loaded with Windows XP from work in the computer and it booted right to XP- the proper drivers aren't there but it got me to the login screen in 16 color mode.
I put my MB's drive in it with SL loaded just for fun and got stuck at a beach ball if I recall correctly.
Today I just read about resetting the SMC and pulling the battery to reset the "real time clock". I'll try those later too, but do you guys have any sugestions?

hassiman wrote:
Lately my MacPro has been having an off and on problem when booting.
Sometimes when the peer button is pushed I will get the GONG sound and the white screen comes up but no gray Apple symbol or rotating circle below it. It just sits there with a blank white screen.
When I push the power button again the process starts again and the machine boots with no
problem. Is this symptomatic of a dying HD or some
other component?
This is set as the primary boot drive and is running Leopard. I have a mother OS HD running SL that I am gradually switching to.
Any ideas?
to
If this behaviour is consistent I would say it is probably not the HD. Failing HDs tend to behave inconsistently.
AHT is worth doing, but if first thing I would try is resetting the SMU and PRAM .

Similar Messages

IMac 27" 3.2GHz iCore 3 V/S MacPro Dual Core 2.66GHz

Hello there,
I need some advise, my friends selling 2 Mac, they both 14 months old and they are both same prices and my questions is: which one should you buy from him and the reason "why" you go with that machine, thank you very much for all inputs.
1. iMac 27" with 3.2GHz Intel Core i3, 4GB of memory, 1TB hard drive, 8x double-layer SuperDrive, ATI Radeon HD 5670 with 512MB, mouse and keyboard of course, no additional software installed.
2. MacPro Dual Core Intel Xeon Two 2.66GHz "Woodcrest" processors, 8GB memory, ATI Radeon X1900 XT graphics with 512MB memory, 2TB hard drive, 16x double-layer SuperDrive, mouse and keyboard of course, no additional software installed but no monitor.
Thank you very much.

What do you want to do with this Mac?
High-end graphics editing or Video editing, or something more mundane?
According to this site, the 2.66 Quad core was discontinued Jan 2008. That ain't no 14-month old system.
http://www.everymac.com/systems/apple/mac_pro/stats/mac-pro-quad-2.66-specs.html
Message was edited by: Grant Bennet-Alder

Want to Upgrade my MacPro (Dual Core) 2.66 Ghz to a SSD

Hi,
I would like to upgrade my current MacPro (Dual Core) 2.66Ghz computer that has a 250GB HD to a possible 256 SSD or bigger. Are they compatible? I dont know if this matters or not but I also have 10gb of RAMM.

Once you install the SSD do the following. First, prepare the new SSD:
Drive Preparation
1. Open Disk Utility in your Utilities folder.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed.
Next, clone your existing drive to the SSD (assuming the SSD is 256 GBs this will work.)
Clone using Restore Option of Disk Utility
Open Disk Utility from the Utilities folder.
Select the destination volume from the left side list.
Click on the Restore tab in the DU main window.
Check the box labeled Erase destination.
Select the destination volume from the left side list and drag it to the Destination entry field.
Select the source volume from the left side list and drag it to the Source entry field.
Double-check you got it right, then click on the Restore button.
Destination means the SSD. Source means the startup drive.
Now, restart the computer and after the chime press and hold down the OPTION key until the boot manager appears. Select the SSD's disk icon then click on the arrow button below the icon. This will boot the computer from the SSD if all is well.
If it boots successfully then open Startup Disk preferences, select the SSD, then click on the Restart button which will restart from the SSD.

Mac Pro Boot Issue

Mac Pro - "Quad", 2 X 2.66Ghz; 5GB RAM; OS X 10.5.6
Mac Pro will not boot. It powers up to the grey Apple logo screen. The progress circle spins for about 3 seconds, then powers itself off.
This past week I came back from two weeks off. The first morning back I noticed my Mac was sluggish at times and freezing for a few seconds here and there. When Time Machine backups would kick in, the whole system would be unresponsive for minutes at a time. After turning off all other equipment in my office, I could detect a tell-tale "click click, spin" type noise coming from one of my two internal drives (one for OS and a second for backups).
I tracked the noise to the boot drive and guessing it was about to go out, I ordered a replacement Samsung Spinpoint 750GB. Good thing, because the next day when I came in to work my machine was having worse problems. IF it would boot, it would hang after a few minutes of use. If it would not boot, it would power up to the grey Apple logo, the progress circle would spin a few seconds, the power itself off.
I waited another day and the new drive arrived. I pulled the old OS drive, installed the new one, then dumped our standardized clone image on the drive (using CCC). After the clone was complete, I booted up on the drive, tested it out for a couple of hours and verified that it was working as expected. Next I copied data over to my drive from my backup drive. Everything looked fine.
Three days later, I come in to find my Mac will no longer boot. Grey Apple logo, spinning, etc.. I power off and boot from my external diagnostic drive (OS X 10.5.5). It will not boot. I remove both internal drives and try another boot from the external diagnostic drive. It boots up fine. Shutdown. Remove the backup drive (drive bay 2) and try to reboot from the diag drive once again. It will not boot. Remove the OS drive (drive bay 1) and it boots to the diagnostic drive fine (note: no internal drives are installed at this point). Shutdown. Install the OS drive into drive bay 2 and it then boots to the diagnostic drive just fine.
So now I have booted to my external diag drive and can see that the OS drive is showing on the Desktop; however a pop-up error stating there is a problem has appeared. I try to verify the OS drive using Disk Utility and it stops about 2 seconds into the process with a "Filesystem verify or repair failed" error. The OS drive will then not mount.
I restart booting back to the external diag drive. The OS drive shows up on the Desktop with the same pop-up error message as before.
I run Tech Tool Pro from the diag drive and it comes back with a File Structure error of "Type List Offset Is Invalid" and "No method for Tech Tool Pro to repair a corrupt file". I have a surface scan and drive hardware test running now, but on a 750GB it will be a WHILE.
So here is my predicament... I can understand my original OS drive having problems. It was at least 3 yrs old and has been run quite hard. But what are the odds that I would replace it with a brand new drive running a verified to be good cloned disk image AND have almost the exact same boot issues on the new drive that I had on the old one?
I have taken my original OS drive and hooked it up to external cases and sata-to-usb adapters to make sure that it was actually dead and it is. It will not spin up properly and makes lots of clicking noises. However, having a similar boot issue with a brand new drive has me worried something may be wrong with the Mac Pro hardware also. The new OS drive ran fine for a few days and only had these problems today.
Any guesses?

Here is my own "cookie cutter" template to this type of problem.
Insure your UPS is working properly and that you have 1300VA to start with.
Run Apple Hardware Test of course.
CCC has been updated so make sure latest (it auto checks probably already).
Do you have Windows? run diagnostics from there, much better.
I settled on WD drives and use WD Diagnostic and has saved a drive.
Avoid Barracudas, seems even their 1TB is also suffering early failures (the 1.5TB was suffering from firmware problem).
Check for reviews and drive upgrade DB on AccelerateYourMac.
http://www.xlr8yourmac.com/
I know the F1 got a lot of early praise but they aren't compatible with Apple Pro RAID card and may have other issues.
If you want a fast low-cost drive, WD Cavair 640GB $69.
http://www.barefeats.com/harper14.html
Hitachi E7K1000: http://techreport.com/articles.x/16130/10
http://www.tomshardware.com/reviews/hdd-terabyte-1tb,2077-8.html
I have seen more than a couple of similar stories from people going away for 1-2 weeks and coming home to system that won't work properly. Hopefully people shutdown and unplug, or shutdown and have UPS, but it is strange to say the least.
Resetting SMC is a good idea but best done with 2008 model by leaving it unplugged for a full night 8-12 hrs. and not just 5 minutes. contrary to Apple tech article. For yours, there is a small physical button accessed by pulling drive tray #4 (easier to see if it is on its side and you have flashlight!)
http://support.apple.com/kb/HT1806
http://www.apple.com/support/macpro/

Boot issues

When I boot my computer (MacBook Pro, 15", Early 2010, 4GB RAM, 320GB HD, 2.4GHz Intel Core i5), it does nothing for quite awhile, and eventually gives me the folder with the question mark on it, signifying it can't find a startup volume. I think I know why, but this has not helped me fix the problem.
I used Disk Utility to partition the internal hard drive so I could install Linux (Ubuntu 10.10) and dual-boot. I used Linux to reformat the partition and used one of the 134MB spaces between partitions (the one at the end of the drive) as Swap space for Linux. I installed Ubuntu, and it worked fine. I could use the built in boot manager (holing down the option key at startup) to boot into either operating system.
That was last night. This afternoon, I booted up the computer, and it gave me the flashing question mark folder and wouldn't boot. I connected it to my iMac (20", Early 2009, 2GB RAM, 320GB HD, 2.66 GHz Intel Core 2 Duo) via a FireWire 800 cable and started the laptop up in Target Disk Mode. I started my iMac up holding down the option key to get it to look for the (possibly) bootable hard drive of the laptop. It did not find it, but displayed only the boot volumes normally available to it (Mac OS X 10.6.7, Windows 7 Ultimate, Mac OS X 10.5.8). I then shut down the laptop and proceeded to start it back up. Miraculously, it booted of its own accord into Mac OS X (10.6.7). I later booted the machine into Linux and began dinking around with some settings to get the illuminated keyboard to work. I did not entirely succeed, but the laptop was still working fine. I shut the clamshell to put it to sleep (while in Linux), and about an hour later, upon opening the clamshell, all I got was a black screen and the mouse pointer (as if it was stuck trying to get me to enter a password to unlock the screen). On rare occasions, this happens to me under Mac OS X as well, and I have usually been able to resolve it by shutting and opening the clamshell. After waiting a few minutes, I tried this, and when it failed, I decided to force shut down the machine, as I have had to do sometimes when this has happened under Mac OS X. Upon restarting the computer, I got the flashing question mark once again. I tried holding down the option key on startup, but only got a mouse pointer against a blank grey screen (like the boot loader screen, but without any icons). I tried zapping the PRAM, starting up in Safe Mode, starting in Verbose mode, holding down the x key, then Command-Option-O-F (then realized that wouldn't work since Apple doesn't use Open Firmware anymore), and also tried Command-Option-V-R, but that also appeared to do nothing. I just got the question mark folder each time (except for resetting the PRAM: that worked, but then I got the question mark folder).
I repeated the same steps as before (Target Disk Mode, etc) to see if they would miraculously fix the problem a second time (I still don't know how they did the first time), but to no avail. I fully booted my iMac with the laptop connected as a FireWire disk to attempt to use Disk Utility on it. Disk Utility did not recognize the drive. I checked System Profiler. It recognized that there was a Target Disk device attached to my iMac, but it did not list any hard drives under it. I proceeded to boot my laptop from its install DVD, which worked. However, Disk Utility on the pseudo-OS that is on the install DVD failed to recognize the internal hard drive. I checked under the Serial-ATA section of System Profiler. It showed two connections, one for the DVD drive, and I presume the other for the hard drive, but the hard drive one showed nothing connected to it. It simply listed a few specs on the SATA port.
I decided to boot my laptop from my iMac's internal drive. I reversed the roles of the machines, my iMac now being in Target Disk Mode, and the laptop trying to boot from its hard drive. I held down the option key at startup so I could choose what to boot from. I choose Mac OS X 10.6.7, and the machine started to boot. Just before it should have gotten to the brief blue screen before the login screen, it had a kernel panic, and the grey came down the screen and told me to restart the computer. I did, tried again, got the same kernel panic, so I decided to try Windows 7. When I selected Windows from the boot manager, it seemed to try to start up in Mac OS X (10.6.7, because 10.5.8 wasn't connected), but never got past the grey Apple icon. After a while, it started occasionally flashing a circle with a line through it, and sometimes the question mark folder, but always switched back to the Apple icon quickly. After at least 10 minutes, I decided to shut down the computer. I then tried booting Mac OS X 10.6.7 in Safe Mode. After showing the progress bar (it only got about half completed before it vanished, but it took a long time to get halfway) for awhile, it eventually successfully booted to the login screen. I signed in, and opened Disk Utility. Nothing. I checked System Profiler and got the same result I had from the install DVD. I shut down the computer, and tried to boot it normally one last time. Nothing.
Does anyone have a clue what's going on? I can understand why the computer would be having boot issues, with my shaky installation of Linux, and all, but I can't understand why nothing will recognize that the computer's internal hard drive exists.
I do have AppleCare for the laptop, unless I've voided the warranty by installing Linux. Should I send the computer in? (I'm over 250 miles from the nearest Apple Store). Is there anything I could do by opening up the computer (I know that would void the warranty if I haven't already). I do have a backup of most of the data, but the backup excludes some video files because of their size. Luckily, I do still have them on MiniDV tape if I have to reimport them.
I feel like I've tried everything, but I wouldn't be surprised if I've missed something obvious…
Thanks in advance for any ideas, suggestions or answers!

Update 2: That successful boot seems to have been one of about four flukes. For some strange reason, my computer will successfully boot into Mac OS X and Ubuntu, but only on rare occasions. There seems to be no pattern, but every once in a while, the computer will decide to recognize it has a hard drive.
Any thoughts?

G4 Quicksilver Dual 1Gig chimes and boots normally, sometimes nothing??

Some what of a quirky problem and I don't know what else to check. I'm suspecting the processor, but once booted the system works great, so maybe it's not the processor. Here what happens.
If I try to start the computer from a cold system that's been shutdown for a while, I will never even get a chime or a system boot. Understand, the power supply appears to be working normally, as the fans spin and the drives fireup. However, either the motherboard or processor won't post. Now, if I sit there and work with it, repeatedly forcing a restart by holding down the start button, allow it to shut down, then doing a restart, eventually it does chime and then starts normally. However, I may have to repeat this 5 or 6 times (or more) before I get a chime and a boot up. Again, once it's booted everything works normally. I'm tending towards the processor being the problem, as I've exchanged the processor with a 933MHz, and it boots every time. I've also removed the processor and re-installed it (this is the Dual 1 GIG processor) into a different Quicksilver. The results are exactly the same. Sometimes it will boot normally and sometimes nothing.
As I said, once I get the computer started, everything works great. Oh, and if I leave the computer running, no problems with operating at all. It's just the start up where this issue arises. Both of the motherboards I tested the processor on are the 1342-B models, and known to be operational.
More info: The hard drive being used is an older model 20 GB, Western Digital - IDE drive, but it passes all the disk utility checks once it formated. Also, I have 1.25 GB of SDRAM installed and it all checks out as good.
Any suggestions of what else could be causing this? Are there any firmware updates for these model (2002) Quicksilvers that I need to install? Any help or ideas of what to check would be greatly appreciated.
Thanks!
Rudy

Thanks for the replies. Here are some answers to the advice you have offered.
Grant - Thanks for your help. I will try to burn the disk image of the AHT program, and see what it shows. However, I doubt if it will show any abnormalities, though, as the diagnostics section, under the "About This Mac" > "More Info" section shows that it passes the diagnostics once it boots.
Lou - Thanks for your reply also! I suppose it's possible there could be a stress crack somewhere on the PCB for the processor. However, I would tend to rule out the motherboard having one that could cause this, as it (the Processor/Boot issue) does exactly the same on two separate motherboards. That tends to tell me it's probably some sort of a processor issue (though it works just fine once booted). It's got me stumped.
Limmos - Thanks to you also! The batteries on both motherboards are relatively new (only a couple of months old). Also, I'm familiar with re-setting the PRAM, and the PMU reset button. There s an issue that I'll bring up here regarding the PMU button. If I try to start the computer and it fails to boot as my question states, then I can try 10 times or more and the results are the same. Meaning it doesn't boot. However, if I shut down, open the case and press the PMU button (5 secs or more), then within a couple of times doing that I can get a good boot. So clearing the PMU cache does seem to help.
Oh, and another thing I've noticed is I can "RESTART" without any hang up, or failure to boot. By that I mean if the system is running and I reboot the system, there is no problem restarting. It restarts normally. I've done these restarts as many as 6 times in a row just to see if it would fail to boot. Booted every time.

MSI P55 GD65 Booting issue [SOLVED]

Hello everyone!
I finished a new build two days ago:
Intel i5-750, 2.66GHz
MSI P55-GD65, rev. 1.0, BIOS 1.3, Lotes socket
A-DATA 2x2GB DDR3 1600Mhz CL8 Vitesta Extreme Edition
GIGABYTE ATi R5850 1GB
KINGSTON V-series SSD 64GB SATA
SAMSUNG SpinPoint F3 500GB SATA 7200rpm
Artic Cooling Fusion 550, 550W, dc outputs are mentioned below
and some minor components (optical drives, wifi card etc.)
I started the computer and everything seemed fine. I managed to enter the bios. I was checking H/W monitor and several other options, I didn't change anything. Suddenly (after circa 5mins) the computer shut down and started to turning on and off repeatedly. I stopped the loop by turning off the power supply. I started it again, however it got stuck in the loop imediately. After a while I managed to access the bios again, meanwhile I was trying to find some answers on internet.
I decided to remove all memory sticks (as a lot of topics here in forum which are describing the very same problem sign RAM problem) and started computer. I expected beeps and LED-show. However, the computer didn't start at all! Even fans were not spinning, just nothing (although PSU was giving tension). I put RAM back and computer started. It was like black magic. I tried again, remove RAM - no start, put RAM back - no start too. Mobo went definitely dead. So I RMAed it.
I've obtained a new one, which was:
MSI P55-GD65, rev. 1.0, BIOS 1.2, Foxconn socket
I put all the stuff together and started computer. Everything went fine, I managed to enter the bios. Nevertheless, I decided to check RAMs for sure; I changed booting devices, restarted and booted system rescue cd with some utils. I started memcheck basic test. The basic test was fine with no errors, then I started filling with random pattern test. It ran for almost 24h. I wanted to try another exercise test and... computer shut down and the loop was there once AGAIN!
I don't think the mobo is the issue here anymore. I bet on two things: PSU or RAM (I'm not going to think about CPU!)
I don't recall exact dc ouputs but: AC Fusion has 2 12V rails with 17A each. Mobo needs 18A, but as I understand it, I have to check 2 rails combined against the requirement - 34A > 18A, it's okay, isn't it? I've choosen this one as I wanted silent PSU (it performed really good in tests, f.e.: http://www.anandtech.com/casecoolingpsus/showdoc.aspx?i=3516). I don't have any other similar PSU to swap (neither my friends).
My suspicion is the problem is RAM incompatibility. My RAMs (AD31600E002GU2K) have 1.65-1.8V working voltage. Maybe the mobo sets auto settings badly (I'm not present at my computer now, I left for the weekend); they are not in QVL too (http://eu.msi.com/uploads/test_report/TR10_1846.pdf). The problem is I was not able to get into bios before I left. As I read on the internet, P55 is pretty touchy when it comes to RAM. I'm thinking about swapping them for Kingston 2x2GB 1333MHz DDR3 CL7 (http://www.valueram.com/datasheets/KHX1333C7D3K2_4GX.pdf; which are not in QVL either, but KHX1333C8D3K2_4GX are; only latency difference).
Any advices on the whole problem?
P.S.: I've tried CMOS clear on the former one too, no change. As I mention I went through the most of the gd65 booting issues posts here on MSI forum and several others.

Do you think Corsair VX550 550W could do the job? It has a single rail with 41A on 12V. ATi certified Straightpower BQT E6-550W for 5850, which has 4 rails per 18A, but overall 41A too (http://www.be-quiet.net/be-quiet.net/data/media/_stories/216/sp_e6_550_EN.pdf).

The Mac HD has booting issues - how do I make a clone that is free of these?

I spilled water on my MacBook Air (10.6.8) and now it has booting issues.
When I shut it down, the power button doesn't work to boot it. But when I close the lid, it powers up. However even when I shut it down AND close the lid, it keeps booting up and staying on.
So I have to send it for repairs.
I cloned the Mac HD using Carbon Copy Cloner and put the clone using Migration Assistant onto the new machine (MacBook Pro - 10.7.2). Now the MacBook Pro won't boot at all. Before this, it was working fine.
So I want to know how to make a clone of the Mac HD of the MacBook Air that won't have booting issues when I migrate the clone to another machine.
I have to make a clone of the MacBook Air before I send it off for repairs as the last back up is quite old and out of date.
Also the fact that the Mac HD of the MBA has booting issues affects the ability to access the Boot Camp (Windows 7 partition) as now I can't even boot the new machine. (But I am asking about Boot Camp in another section.)
It seems like a catch-22 situation. I can't fix the booting problem until I send it off to the repair center to get the computer fixed. And yet the booting problem is preventing me from making a usable clone of the Mac HD.
I think the booting problem is a software problem because the MacBook Pro was working perfectly before I migrated the Mac HD of the MBA onto it, The MBP is only two days old. I migrated another Mac HD backup (one I made before the booting issues came up) onto the MBP on the first day I bought it and the MBP worked fine.
Do you think I will just have to clone things separately manually? I mean should I format an external hard drive, plug it in the USB port, and transfer the files I need to save? What files/folders should I save? Can I move folders or do I have to move files? I have many files in Desktop, Downloads, Documents. I also want to save my applications. I want to save the BookMarks of Opera, Firefox.
Will this take a long time? I have used about 200 GB of the MBA's hard drive.
Any advice? Thanks.
I don't use Time Machine and am not confident about using it. Will it be substantially different to CCC in the way it clones files? Will a Time Machine clone after migration contaminate the second computer with booting issues?
I am not so worried about the booting issues on the second computer. I know it's from the faulty clone and nothing to do with the machine itself. I can take it to Apple Genius Bar and they will probably be able to reinstall a new operating system on the machine and I can start from scratch, I think. I am more worried about how to save and restore my data from the old machine. Thanks for any advice.

applecore_eater wrote:
I cloned the Mac HD using Carbon Copy Cloner and put the clone using Migration Assistant onto the new machine (MacBook Pro - 10.7.2). Now the MacBook Pro won't boot at all. Before this, it was working fine.
Ok, you used Migraine Assistant to try to transfer the account from the clone drive to the MBP and it didn't work, that's ok, it can be fixed by command r booting into Lion Recovery and simply erasing and reinstalling Lion from Apple's servers. (AppleID)
I suggest you transfer the account data manually because the clone is a copy of a failing drive/corruption, use the same name in System Preferences >Accounts, drag and drop files transfer and hold option key, click on Purchases in crapStore to redownload to the new machine, install other programs from fresh sources. Cleaner machine that way. So that shoudl fix the MBP.
in the future, try to avoid Apple's "answers" like Migraine Assistant as much as possible, it's really not reliable in any sense in actuality.
So I want to know how to make a clone of the Mac HD of the MacBook Air that won't have booting issues when I migrate the clone to another machine.
You can't boot a clone of OS X from another type Mac on another type Mac, only the same exact machine model.
In your case the Migraine Assistant didn't work, so you'll have to manually install.
Also the fact that the Mac HD of the MBA has booting issues affects the ability to access the Boot Camp (Windows 7 partition) as now I can't even boot the new machine. (But I am asking about Boot Camp in another section.)
Well it's possible that Windows or something messed up the GUID partition map of the Mac, why it has booting issues. Likely why Migraine Assistant didn't work.
You'll have to set up BootCamp again on the new MBP machine, talk to Microsoft about validation on the new machine and return your Windows files, programs from fresh sources.
Likely you got malware and it was trying to write to the boot sector of the Mac, mistaking the MBR portion of the GPT for a full Windows one. This also happens when Mac users try to install Linux on their Mac's.
Unless you need full hardware performance, you really should look at virtualization software like VMFusion, Parallels Desktop or even VirtuaBox (might be outdated) and run Windows in a window on OS X instead. Much easier to recover from malware that way.
It seems like a catch-22 situation. I can't fix the booting problem until I send it off to the repair center to get the computer fixed. And yet the booting problem is preventing me from making a usable clone of the Mac HD.
Well if you make a clone, it's going to be junk any.
What you need to do is fix the new MBP machine first then use Firewire Target Disk Mode (firewire 800/400 cable and adpater if needed) and grab a copy of your files off the sick Mac or off the sick clone.
The drive is likely fine, it's just not booting and that could mean some sort of malware/drive/data corruption.
You'll have to install third party software on the new fixed MacBook Pro to read the NTFS drive format of the Windows 7 bootcamp parittion when the sick MacAir is in Firewire Target Disk Mode.
http://www.paragon-software.com/home/ntfs-mac/
https://support.apple.com/kb/HT1661

Booting issue on a new installation on Acer Aspire 4752 laptop.

Hi All,
     I have done a new installation of OS on a Acer laptop stated above. However, due to some reason, during the booting up process, it will always stuck at screen right before it enter into the logon screen. I will have to press
Enter in order to move it, as if there is a "press Enter to continue...".
     After this "enter" key, everything else works normally. However, this is pretty annoying and I could not sent this laptop back to my enduser because of this trivial issue.
     Some other information as below:
This is a new OS and no other apps is installed. Though now it is patched (with Microsoft patches). But it happens since the first boot after install.
In according to Device Manager, all drivers are in place. No exclamation mark and error.
Event Viewer shows no error for the boot up.
Safemode (command prompt) shows that it is stuck at loading "classpnp.sys".
     My questions:
It will be good if there is already a resolution. :)
How to diagnose, or identify which apps actually waiting for that "enter" to move on?
     Thanks!
wsn

Hi,
For the boot issue, first I suggest you use startup repair if you have an installation disk, check if it can detect and fix some certain problems.
Or run sfc/scannow in command prompt in recovery console, check if it can make any difference.
If doesn’t work, then try “Enable boot logging”, then check the log called ntbtlog.txt, usually located in system drive\Windows.
Advanced startup options (including safe mode)
http://windows.microsoft.com/en-in/windows/advanced-startup-options-including-safe-mode#1TC=windows-7
You can also share a screen image with us about the “stuck” screen.
Regards
Yolanda
TechNet Community Support

Windows 8 Laptop Boot Issue (and other related problems)

My Toshiba Satellite S855D-S5148 laptop was bought about a month ago, but it's been giving me issues for the last week.
The most significant one was a boot issue, where out of nowhere, the PC would not start, and after a hard restart, I received an error message saying Windows was not able to start. So I called tech support and they guided me through a PC refresh. That seemed to have solved the issue until twenty minutes later, when my system froze and I could not move the cursor let alone use any applications. So I did a hard restart again, and tried to do another PC refresh until the laptop 'clicked' and shut off. I restarted again, and my system seemed to be working normally until two days later (I did not shut it off or restarted it during this period, only kept it in hibernate when not in use).
Upon trying to use my laptop, it said Windows was reconfiguring. Afterwards, I received an error message saying that Windows had to restart due to 'this problem,' though the problem was not specified. The error message included a list of file addresses that presumably contained a description of the problem, but I can't access the files because they don't show up when I search their addresses. They are .dmp and .xml files, respectively.
Is anyone familiar with this problem? I wish I could return the laptop but it's a couple of weeks shy of the return period (Staples has a measely 14-day return period, but I didn't think I'd have to use it). I don't want to go through the hassle of shipping it off to Toshiba for repairs. Would reformatting the laptop solve the problem? I wish I could attach the .dmp and .xml files to this post but I can't locate them. I'd try using the recovery disks, but they were recently destroyed in a flood.
Any comments, advice, and/or suggestions are very much welcome!

Happy to learn the hardware is fixed.
I was told they could not do so without the product key. ... Any ideas as to how I can get my product key?
Everybody should know by now that there is no product key for preinstalled Windows. The OEM has it locked into the motherboard.
As I've said over and over, recovery media will restore the hard disk to its original out-of-the-box contents. Windows will be activated.
Windows is not installed during this process. Everything on the hard drive is restored. It's an important distinction.
-Jerry

Safe boot issues tried everything

Howdy From NZ
I have a MBP with a bad case of safe Boot Issues
Things I have tried:
Disk Repair
Checked S.M.A.R.T status of HDD under linux and run a full surface scan to check HDD is fine
Replaced SATA Cable
Reloaded OSX (upto yosimite)
tried another hdd just in case
replaced top panel (thought maybe it was holding down the shift button)
and a few others I cannot remember at the moment
i'm Thinkin' it's motherboard related but would like a second opinion from the forum guru's
Also I've taken it to the closest apple authorised repair store, and they said it was the HDD, but clearly it isnt as I have replaced it with a brand new one and the sata cable
interestingly enough, If i 6 second death it, upon reboot it works fine, but if i restart normally it hits this problem, I'm thinking maybe its doing some sort of start up check thats causing it?, it seems to work fine if you boot with verbose mode every time without fail, so is verbose mode disabling something upon startup?
I run a repair store here, but im not apple authorized, but as stated before, have gotten further than the people that are.... any help will be greatly appreciated

Good Timing,
I was heading to Christchurch (the only town in the south island with an "apple genius store")
they told me it was the HDD again, even after telling them I have put a new HDD in and also changed the Sata cable!!!
Clearly this isn't going anywhere fast, and although I appreciate the help you have given me, I'm going to nut this one out by myself.
***update***
I borrowed a mates mac that was the exact same model and swapped the Motherboards over, worked straight from the get-go
Thank for the help, it was appreciated in making me think I'm not crazy.
Scott

Macpro dual core xeon. Why can I not download Lion even with snow leopard 10.6.8 already as sysyem?

macpro dual core xeon January 2008 Why can I not download Lion even with snow leopard 10.6.8 already as sysyem?

If you need to purchase Lion call 1-800-692-7753 or 1-800-676-2775. Ask for a Sales Representative. They will check your Apple ID, and email you a code and instructions. The cost is $29.99 (as it was before) plus tax. It's a download.

Satellite L50D - Boot issues after Hard Drive replacement

I have just upgraded my hard drive from the pathetic 5400 crod they supply to an SSHD@7200rpm but now have a major issue.
I initially imaged the os from the old hard drive back to the new drive and have had chronic boot issues (1 in 3-4 boot attempts succeed else it fails at any point (often at the Toshiba startup screen)).
I've reinstalled from a plain clean Win 8.1 ENT disc (trying to avoid the bloatware) and this has the exact same issue and was what I used to format the laptop fine with previously and worked previously.
I've tried reformatting and reinstalling (deleting ALL partitions each attempt) in CSM, UEFI non secure and UEFI secure. CSM is a straight never works no go and both UEFI methods have the exact same outcome.
I've tried with the original restore discs and it seems to work (haven't had time to fully test) but I don't want the bloatware and this should not matter since if I were a customer who forgot to make the restore discs (happens too often) and just had to have a failed or killed hard drive replaced the laptop would now be a door stop.
This seems as bad as Apple for locking people in :/.
So I'd appreciate ideas from people please, I'm not sure if there is a prep program that is supposed to be run over a new drive like PS3's etc (I doubt it) but this is driving me up the wall and will be the last time I consider Toshiba as anything other than a joke if there is no fix.
I've had to replace hard drives a few times in my previous Toshiba laptops and had none of this crod, it has something to do with the UEFI which seems more of a nuisance than assistance at the moment.
TIA.

Hi
In my opinion you should check firstly if this booting issue is related to the new installed HDD or new installed system.
You said that the notebook fails to boot often at the Toshiba splash screen.
The splash screen appears while POST (power on self test) procedure. During this test, the hardware will be checked.
Im wondering if the hybrid SSD/HDD isnt recognized by BIOS during this particular step.
From my point of few this might be the reason why the system cannot be booted up.
Another important note:
The Win 8.1 requires enable secure boot as well as the UEFI boot mode.
Therefore you should enable both options in BIOS.
Last but not least check if you are using latest BIOS version as well as latest firmware for hybrid SSD/HDD

Anyone see an ios 7.1.2 boot issue AFTER updating?

From everything I read, I wonder if iOS 7.1.2 has a general boot issue. I have 4 devices, one of which locked on update. When i reset it and checked the crash log, my reset counter was zero and it said there was a boot failure. There was no indication of any application crash for the time in question.
I never reboot any of my devices, so I don't know, but it crossed my mind that perhaps the lockups on boot or booting into recovery mode has nothing to do with the update process, but is related to rebooting 7.1.2 in general. In other words, just because the devices are working fine now, is there still a chance that any of them can lockup or go into recovery mode the next time they are reset?

There appears to be a plethora of similar reports out there (I've been looking around). So we wait for Apple to provide a fix for this problem.
What I am most unhappy about is the inability to downgrade to, at least, the last known working firmware; in this case, 7.1.1. In situations like this, newly introduced problems become a corporate liability, more so on the part of end users that experience limited use of these expensive devices due to these newly-introduced problems. Then, there is the added liability of support calls, feedback/bug reports, etc.
I do not see any logic in the decision to disable downgrading firmware -- in this case, it's seems more paranoia (ie: jailbreak prevention) than a solid engineering decision, in my opnion.

Problem solving expertise appreciated. What does a MacPro do in its initial booting phase?

My MacPro 3.1 (2008) with 20 Gb Ram does no longer want to boot. I checked the harddrive (startup disc), it is OK (my MacBook) boots from it. I checked the ram, it appears to be OK. When I push the power button the fan begins to work, red lights appear shortly on the RAM circuit boards and they go out again but then nothing happens. Monitor does not wake up, there is no start up chime, machine appear unresposive to any keyboard commands.
Anyone can tell what may be wrong, what the cause is why the MacPro does no longer want to boot and what could possibly be done about it?
So some Problem solving expertise and advice is higlhly appreciated. I really like to know what exactly does a MacPro do in its initial booting phase? Information that could bring life b to my well respected grand-old lady.

Conventional wisdom is that you get nowhere until you get the chime.
For that reason, the approved method is to remove everything that could possible be dragging down power and test the absolute minimum configuration, hoping to get the chime. Once it chimes, you slowly build it back up. adding one part at a time until you find something faulty or it "comes clean".
Disconnect AC power and remove:
graphics card
All other PCIe cards
All Hard drives
All Optical drives
All RAM -- then check for the power light blinking
next step is to restore one pair of DIMMs and try for the chime.
Then more DIMMs
Then graphics card, etc.

MacPro dual Xenon 2.66ghz boot issues

Similar Messages

Maybe you are looking for