JPG2016
Level 1 (0 points)

Q: Mac Pro really not booting - IS THERE A FIX?!

I have a Mac Pro (Early 2008) running Mavericks that refuses to boot and I seriously need some assistance. It froze a couple of times with a 8bit-style colour palette, shortly before a text warning in a grey box, and needed forced restart. Today it will not boot. It hangs on the grey screen with Apple logo, the spinning wheel spins for around 20 seconds and freezes and goes no further no matter what I have done.

I have tried the following:


• Safe mode: the progress bar goes half way and hangs.

• Resetting PRAM - no change in behaviour

• Booting from a recovery drive – I can see the drives as options but again it hangs on trying to boot to them.

• Booting from a CD - as above, or holding C on boot, again hangs

• Cmd-Opt-R with a wired connection does nothing

• Terminal disk verification (/sbin/fsck -fy) says everything is ok, 'reboot' continues the issue
• Tried removing and rearranging RAM.


Via Firewire Target Disk Mode (connected to a MacBook) I have copied off the important files, I have also used Carbon Copy Cloner to make a clone and a HD recovery partition. I again cannot boot the Mac Pro from these (t's just a static pin wheel).

 

A few other things - one boot-up brought up a large black and white checkerboard (see images below) and in general there are often green lines down the screen (not when it's grey though!)

 

Importantly, Using Target Disk Mode I have booted the Mac Pro hard drive onto the MacBook, which appears to be running ok (so I'm assuming the Mac Pro HDD is ok?) - I've repaired and verified the Mac Pro HDD through Disk Utilities.

 

I also copied the Error Report when booting the Mac Pro HDD with the MacBook (see this log below)...

 

So, what are the next steps to get the Mac Pro booting and working again on it's own? Can I diagnose anything via Target Disk Mode on the MacBook? PLEASE HELP!

 

Thanks!

 

---- ERROR LOG ------

Anonymous UUID:       5882DF34-239D-E9F7-A107-C166A3F45878

 

 

Tue Feb 16 15:50:51 2016

panic(cpu 3 caller 0x28d4b9): "pmap_flush_tlbs() timeout: " "cpu(s) failing to respond to interrupts, pmap=0x84b6e0 cpus_to_respond=0x40"@/SourceCache/xnu/xnu-1504.3.12/osfmk/i386/pmap.c:3548

Backtrace (CPU 3), Frame : Return Address (4 potential args on stack)

0x88d63a78 : 0x21b449 (0x5ce420 0x88d63aac 0x2238a5 0x0)

0x88d63ac8 : 0x28d4b9 (0x58c4e8 0x84b6e0 0x40 0x0)

0x88d63b38 : 0x292985 (0x84b6e0 0x88d63c24 0x88d63b68 0x51dac3)

0x88d63c68 : 0x2936d6 (0x84b6e0 0x790d6000 0x0 0xfebc86b0)

0x88d63cd8 : 0x270bef (0x84b6e0 0x790d6000 0x0 0x790d7000)

0x88d63d28 : 0x253eff (0x1200f8dc 0x790d6000 0x0 0x790d7000)

0x88d63d88 : 0x254c00 (0x49ffe70 0x0 0x7fe9e4f8 0x11ddeb88)

0x88d63df8 : 0x257cd6 (0x49ffe70 0x1142d074 0x27000 0x1)

0x88d63f38 : 0x2a839c (0x11ddeb88 0x27000 0x1 0x5)

0x88d63fc8 : 0x29e80a (0x11de3ca4 0x0 0x10 0x11de4c64)

 

 

BSD process name corresponding to current thread: mDNSResponder

 

 

Mac OS version:

10D575

 

 

Kernel version:

Darwin Kernel Version 10.3.0: Fri Feb 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386

System model name: MacPro3,1 (Mac-F42C88C8)

 

 

System uptime in nanoseconds: 85973407493

unloaded kexts:

(none)

loaded kexts:

com.apple.driver.AppleHWSensor 1.9.3d0 - last loaded 84043891732

com.apple.driver.AppleTyMCEDriver 1.0.1d8

com.apple.driver.InternalModemSupport 2.6.2

com.apple.driver.AudioAUUC 1.4

com.apple.driver.AppleIntelYonahProfile 14

com.apple.driver.AppleUpstreamUserClient 3.3.2

com.apple.driver.AppleIntelPenrynProfile 17

com.apple.Dont_Steal_Mac_OS_X 7.0.0

com.apple.GeForce 6.1.0

com.apple.driver.AppleIntelNehalemProfile 11

com.apple.driver.AudioIPCDriver 1.1.2

com.apple.driver.AppleHDA 1.8.4fc3

com.apple.driver.AppleIntelMeromProfile 19

com.apple.driver.AppleMCEDriver 1.1.9

com.apple.driver.ACPI_SMC_PlatformPlugin 4.1.1d0

com.apple.driver.AppleLPC 1.4.11

com.apple.driver.DiskImages.SparseDiskImage 283

com.apple.driver.DiskImages.ReadWriteDiskImage 283

com.apple.driver.DiskImages.UDIFDiskImage 283

com.apple.driver.DiskImages.RAMBackingStore 283

com.apple.driver.DiskImages.HTTPBackingStore 283

com.apple.driver.DiskImages.FileBackingStore 283

com.apple.driver.CSRHIDTransitionDriver 2.3.1f4

com.apple.iokit.SCSITaskUserClient 2.6.2

com.apple.BootCache 31

com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1

com.apple.driver.AppleIntel8254XEthernet 2.1.1b7

com.apple.driver.AppleUSBHub 3.9.6

com.apple.driver.AppleFWOHCI 4.5.7

com.apple.iokit.IOAHCIBlockStorage 1.6.1

com.apple.driver.AppleUSBEHCI 3.9.6

com.apple.driver.AppleAHCIPort 2.1.1

com.apple.driver.AppleIntelPIIXATA 2.5.1

com.apple.driver.AppleEFINVRAM 1.3.0

com.apple.driver.AppleUSBUHCI 3.9.6

com.apple.driver.AppleACPIButtons 1.3.2

com.apple.driver.AppleRTC 1.3.1

com.apple.driver.AppleHPET 1.5

com.apple.driver.AppleSMBIOS 1.5

com.apple.driver.AppleACPIEC 1.3.2

com.apple.driver.AppleAPIC 1.4

com.apple.driver.AppleIntelCPUPowerManagementClient 104.3.0

com.apple.security.sandbox 0

com.apple.security.quarantine 0

com.apple.nke.applicationfirewall 2.1.11

com.apple.driver.AppleIntelCPUPowerManagement 104.3.0

com.apple.driver.AppleHDAPlatformDriver 1.8.4fc3

com.apple.driver.AppleProfileReadCounterAction 17

com.apple.driver.AppleProfileTimestampAction 10

com.apple.driver.AppleProfileThreadInfoAction 14

com.apple.driver.AppleProfileRegisterStateAction 10

com.apple.driver.AppleProfileKEventAction 10

com.apple.driver.AppleProfileCallstackAction 20

com.apple.iokit.IOSurface 74.0

com.apple.iokit.IOBluetoothSerialManager 2.3.1f4

com.apple.iokit.IOSerialFamily 10.0.3

com.apple.driver.AppleHDAHardwareConfigDriver 1.8.4fc3

com.apple.driver.DspFuncLib 1.8.4fc3

com.apple.iokit.IOAudioFamily 1.7.6fc2

com.apple.kext.OSvKernDSPLib 1.3

com.apple.nvidia.nv50hal 6.1.0

com.apple.NVDAResman 6.1.0

com.apple.iokit.IONDRVSupport 2.1

com.apple.iokit.IOFireWireIP 2.0.3

com.apple.iokit.AppleProfileFamily 41

com.apple.driver.AppleHDAController 1.8.4fc3

com.apple.iokit.IOGraphicsFamily 2.1

com.apple.iokit.IOHDAFamily 1.8.4fc3

com.apple.driver.AppleSMC 3.0.1d2

com.apple.driver.IOPlatformPluginFamily 4.1.1d0

com.apple.driver.DiskImages.KernelBacked 283

com.apple.driver.CSRUSBBluetoothHCIController 2.3.1f4

com.apple.driver.AppleUSBBluetoothHCIController 2.3.1f4

com.apple.iokit.IOBluetoothFamily 2.3.1f4

com.apple.driver.AppleUSBHIDKeyboard 1.2.0a3

com.apple.iokit.IOUSBHIDDriver 3.9.6

com.apple.driver.AppleHIDKeyboard 1.2.0a3

com.apple.driver.AppleUSBMergeNub 3.9.6

com.apple.driver.AppleUSBComposite 3.9.0

com.apple.iokit.IOSCSIMultimediaCommandsDevice 2.6.2

com.apple.iokit.IOBDStorageFamily 1.6

com.apple.iokit.IODVDStorageFamily 1.6

com.apple.iokit.IOCDStorageFamily 1.6

com.apple.driver.XsanFilter 402.1

com.apple.iokit.IOATAPIProtocolTransport 2.5.1

com.apple.iokit.IOSCSIArchitectureModelFamily 2.6.2

com.apple.driver.AppleFileSystemDriver 2.0

com.apple.iokit.IONetworkingFamily 1.9

com.apple.iokit.IOUSBUserClient 3.9.6

com.apple.iokit.IOFireWireFamily 4.2.6

com.apple.iokit.IOAHCIFamily 2.0.3

com.apple.iokit.IOATAFamily 2.5.1

com.apple.iokit.IOUSBFamily 3.9.6

com.apple.driver.AppleEFIRuntime 1.3.0

com.apple.iokit.IOHIDFamily 1.6.2

com.apple.iokit.IOSMBusFamily 1.1

com.apple.security.TMSafetyNet 6

com.apple.kext.AppleMatch 1.0.0d1

com.apple.driver.DiskImages 283

com.apple.iokit.IOStorageFamily 1.6

com.apple.driver.AppleACPIPlatform 1.3.2

com.apple.iokit.IOPCIFamily 2.6

com.apple.iokit.IOACPIFamily 1.3.0

Unable to gather system configuration information.Model: MacBookPro5,2, BootROM MBP52.008E.B05, 2 processors, Intel Core 2 Duo, 2.66 GHz, 4 GB, SMC 1.42f4

Graphics: NVIDIA GeForce 9400M, NVIDIA GeForce 9400M, PCI, 256 MB

Graphics: NVIDIA GeForce 9600M GT, NVIDIA GeForce 9600M GT, PCIe, 512 MB

Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353637334548312D4346382020

Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1067 MHz, 0x80CE, 0x4D34373142353637334548312D4346382020

AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.106.98.100.22)

Bluetooth: Version 4.2.6f1 14216, 3 services, 23 devices, 1 incoming serial ports

Serial ATA Device: FUJITSU MHZ2320BH FFS G1, 320.07 GB

Serial ATA Device: MATSHITADVD-R   UJ-868

USB Device: Built-in iSight

USB Device: Microsoft Basic Optical Mouse

USB Device: BRCM2046 Hub

USB Device: Bluetooth USB Host Controller

USB Device: Apple Internal Keyboard / Trackpad

USB Device: IR Receiver

FireWire Device: unknown_device, Unknown

FireWire Device: fw_target_disk_mode, AAPL, Up to 800 Mb/sec

Thunderbolt Bus:

 

 

 

 

 

12722497_10153238778541786_1471948650_o.jpg

12751892_10153238778556786_1892703239_o.jpg

12754950_10153238778481786_1247066581_o.jpg

12736764_10153238778391786_525865463_o.jpg

Mac Pro, OS X Mavericks (10.9.5), Will not boot

Posted on Feb 16, 2016 10:06 AM

Close
JPG2016

Q: Mac Pro really not booting - IS THERE A FIX?!

  • All replies
  • Helpful answers

Page 1 of 3 last Next

  • by lllaass,

    lllaass lllaass Feb 16, 2016 10:15 AM in response to JPG2016
    Level 10 (188,828 points)
    Desktops
    Feb 16, 2016 10:15 AM in response to JPG2016

    Try with one video card removed. The try with the other installed and the first one removed.

     

    The panic report only shows two 2 GB stick of memory installed?

    How much memory is installed?

    Could be bad RAM. The FB-DIMMs in the 2006-2008 Mac Pros run hot and frequently fail after some time.

  • by Grant Bennet-Alder,

    Grant Bennet-Alder Grant Bennet-Alder Feb 16, 2016 10:30 AM in response to JPG2016
    Level 9 (60,931 points)
    Desktops
    Feb 16, 2016 10:30 AM in response to JPG2016

    Your screen anomalies could indicate a dying graphics card. This colors EVERY experiment you do. It is difficult to tell the difference between "hung" and "graphics stopped updating".

     

    Be sure you do the same experiments with your external display disconnected, and using ONLY the built-in display -- the results may be completely different.

     

    The kernel panic with 'processor not updating' COULD be used by a graphics processor that has stopped working.

     

    When you copy files off a sick system, they are immediately suspect, and if you find the copied files do not work, no on should be surprised.

     

    It is encouraging that fsck completes successfully at least in one scenario. Your Disk Directory may be OK, and your disk does not seem to have "dropped out". Whether it contains a valid copy of Mac OS X is not certain.

     

    It is distressing you cannot use these modes that use only "simple graphics" that do not require the driver be loaded:

    Option-boot (aka Startup Manager)

    Recovery Mode

    Boot from CD

     

    ...but again, the "iffy" condition of your graphics card may be coloring these experiments.

     

    Unable to gather system configuration information.Model: MacBookPro5,2,

     

    In a MacBook Pro, you do not have the option of replacing the graphics cards, as it they are not in a slot -- they are soldered to the board. Your MacBook Pro may need a replacement motherboard, and it is not clear if Apple still stocks these parts.

     

    Third-party MacBook repairers certainly do.

  • by Drew Reece,

    Drew Reece Drew Reece Feb 16, 2016 10:34 AM in response to JPG2016
    Level 5 (7,537 points)
    Notebooks
    Feb 16, 2016 10:34 AM in response to JPG2016

    @ lllaass & Grant Bennet-Alder, the Macbook was booting from the MacPro boot disk in target disk mode - hence the weird specs & output.

     

     

    JPG2016,

    Does verbose mode give any info …

    https://support.apple.com/en-us/HT201573

     

    Disconnect ALL non-Apple peripherals & ethernet etc, ideally use just a keyboard & mouse/ trackpad to retest. I would also try the other monitor since on it's own you seem to have 2 Apple ones

     

    Do you have the original grey disc with Apple hardware test? There are instructions printed on one of them to use AHT.

    Using Apple Hardware Test - Apple Support

     

    Run that in 'extended mode' & 'normal mode' to see if anything shows an error. You can also enable 'loop mode' via cmd+L - it will repeat the test over & over, sometimes it need to sit for a few hours! Grab any error strings that appear & post them here, they are undocumented, but sometimes users here understand them.

     

    That error log is from the Macbook running from the Mac Pro boot disk?

    Installations on a Mac Pro may not be compatible with MacBookPro's - the hardware differences mean that certain drivers are not installed etc. Please try to use a similar Mac model only. I know that is difficult - but you may introduce unexpected issues by switching OS's across different hardware models.

    Try another safe boot to allow the OS to flush the kernel caches, so the old MBP caches are removed from the Mac Pro HD (give it time too, safe mode can be slow to boot).

     

    Can you detail what (if any) third party addons are on the Mac Pro? It may be wise to remove some & retest depending on why AHT shows.

  • by JPG2016,

    JPG2016 JPG2016 Feb 16, 2016 10:48 AM in response to lllaass
    Level 1 (0 points)
    Feb 16, 2016 10:48 AM in response to lllaass

    Hmmm... There were 16 GBs but I did a lot of experimentation removing ram before I figured out booting the HDD with the MacBook and found the Error report - the time says the afternoon so it's likely from that time.

     

    Do you know the correct RAM slot set up for a minimum RAM boot - so either top/bottom card and which DIMM slots /how many slots required?

     

    This image only show x4 of the x8 sticks I current am using.

     

    Thanks for your help
    12736817_10153238778631786_783442301_o.jpg

  • by JPG2016,

    JPG2016 JPG2016 Feb 16, 2016 10:54 AM in response to Grant Bennet-Alder
    Level 1 (0 points)
    Feb 16, 2016 10:54 AM in response to Grant Bennet-Alder

    Hi I think you've mistaken the sick machine. My Mac Pro, is suffering --- I have been able to boot the Mac Pro's HDD on to a MacBook via Target Disk mode so forgive me, but there is no 'built in display?' - all I have is the tower unit.

     

    The GeForce card appears to be removable also so there may be hope there.

     

    Thanks for your suggestions

  • by lllaass,

    lllaass lllaass Feb 16, 2016 10:56 AM in response to JPG2016
    Level 10 (188,828 points)
    Desktops
    Feb 16, 2016 10:56 AM in response to JPG2016

    See:

    http://support.apple.com/en-us/HT4433

  • by Grant Bennet-Alder,

    Grant Bennet-Alder Grant Bennet-Alder Feb 16, 2016 11:01 AM in response to Drew Reece
    Level 9 (60,931 points)
    Desktops
    Feb 16, 2016 11:01 AM in response to Drew Reece

    Thanks for that clarification, Drew Reece.

     

    So some of my comments above may not apply. But this one still stands, and as you make your experiments more and more complex, you gain less and less information that is not colored by the increasing complexity as well.

    Your screen anomalies could indicate a dying graphics card. This colors EVERY experiment you do. It is difficult to tell the difference between "hung" and "graphics stopped updating".

     

     

    2GB is enough to boot any version of Mac OS X, especially the "incorruptible" version from a "Full Retail", full color, silkscreened, DVD for any appropriate Mac.

  • by Drew Reece,

    Drew Reece Drew Reece Feb 16, 2016 11:03 AM in response to JPG2016
    Level 5 (7,537 points)
    Notebooks
    Feb 16, 2016 11:03 AM in response to JPG2016

    You were not using the MacPro's RAM  – you were booting using the MacPro's HD only. The 2GB figure is the RAM in the MacBookPro. It is not relevant to your Mac Pro issue at all.

     

    Target disk mode (TDM) turns the computer into a 'massive HD', the RAM, GPU & other resources are not used on any other computer if you choose to boot from the disk in TDM.

     

     

    The inside of the door Mac Pro's should also illustrate the order to add RAM too.

  • by JPG2016,

    JPG2016 JPG2016 Feb 16, 2016 11:04 AM in response to Drew Reece
    Level 1 (0 points)
    Feb 16, 2016 11:04 AM in response to Drew Reece

    Hi Drew,

     

    I tried without anything connected - same issue. I also tried with only one monitor... Oddly enough halfway through my multiple boots and tests the Mac switched the primary monitor it was booting to (from the left back port to the right) - which confusingly is the opposite when on the desk.

     

    I'm not certain I have the correct disk to be honest because it was inherited form a closing business and we have lots of random disks. Just to be clear it was working fine for the last 8 years or so. I have Mac Pro grey disk OS version 10.5.1. I inserted disk 2 and held D - once again it hung on the spinning wheel. So I can't get to AHT.

     

    The Error log is from the MacBook booting from the Mac Pro's HDD, yes.

     

    Safe mode was hanging for 30 mins before I gave up...

     

    No physical/hardware 3rd party add-ons I don't think apart from upgraded RAM which was working fine (8GB up to 12GB).

     

    I'll try verbose shortly!

     

    Thank you!

  • by Drew Reece,

    Drew Reece Drew Reece Feb 16, 2016 11:15 AM in response to JPG2016
    Level 5 (7,537 points)
    Notebooks
    Feb 16, 2016 11:15 AM in response to JPG2016

    http://MacTracker.ca says the early 2008 shipped with …

    Original OSMac OS X 10.5.1 (9B2117)

     

     

    Hardware Test

    		AHT 3A130

     

     

    It may be the correct disk set. I think AHT may be on disk 1? The tiny text normally states the process to boot AHT on the correct disk, only one disk has AHT.

  • by JPG2016,

    JPG2016 JPG2016 Feb 16, 2016 11:16 AM in response to JPG2016
    Level 1 (0 points)
    Feb 16, 2016 11:16 AM in response to JPG2016

    Latest development - two new lines!

     

    AND LOTS OF CLICKING!
    12751712_10153238878561786_114583081_o.jpg

  • by Grant Bennet-Alder,

    Grant Bennet-Alder Grant Bennet-Alder Feb 16, 2016 11:36 AM in response to JPG2016
    Level 9 (60,931 points)
    Desktops
    Feb 16, 2016 11:36 AM in response to JPG2016

    These graphics anomalies indicate your graphics card cannot handle the simplest things you are asking it to do.

     

    A chime, followed by Disk Activity, indicates your Mac has was found to be working, has enough RAM to start up, and is attempting to do so. The dark Apple at center screen is not present in the Mac's ROM, and will only be seen after being loaded in the first "blob" of software off the Boot drive.

     

    The progress bar shown (but not in the right place on the screen) is likely an indicator that your boot drive could not be "Mounted" (using the File system) so it may still have some directory problems. Not in the right place on screen is an indicator of GROSS problems with your graphics card.

     

    Clicking is often caused by many, many re-tries in reading information off the drive. Every read is processed by error correction logic, and if good data cannot be recovered, the data are re-tried. After about 100 of these, many disks will do a re-calibrate (which sends the read/write head back to track 000 where there is a switch that affirms the head is indeed at track 000). Recalibrate is what causes the click. then the data are retried another 100 times. then another click. This may continue for up to 1000 total re-tries before throwing an I/O error.

     

    Although it is not conclusive at this point, I see a new Boot Drive in your future.

  • by JPG2016,

    JPG2016 JPG2016 Feb 16, 2016 11:42 AM in response to JPG2016
    Level 1 (0 points)
    Feb 16, 2016 11:42 AM in response to JPG2016

    I think this is the HDD - although there was a CD in the drive this doesn't sound like anything I've heard before! Bad to worse! Thank you for the assistance so far!

    http://www.filedropper.com/video-14556506061

  • by Drew Reece,

    Drew Reece Drew Reece Feb 16, 2016 11:48 AM in response to JPG2016
    Level 5 (7,537 points)
    Notebooks
    Feb 16, 2016 11:48 AM in response to JPG2016

    Yup sounds like a dying HD.

    It looks like an original Maxtor? It must be getting old now!

    You may feel the clunky disk if you have multiple installed, it should be evident which one is flipping the heads back & forth from the vibrations.

     

    Remove all disks & try booting the install disk, see if that operates. If it works refit them one by one & retest.

Page 1 of 3 last Next