MBV201

Q: Mac Pro 2,1 unexpectedly shuts down and restarts

Mac Pro 2,1 shuts down without warning and restarts, the normal Apple "chime" plays and the Mac starts back up.

One problem that exists is a bad DIMM Riser -- the "B" DIMM Riser doesn't recognize RAM, could this be the root of the shutdown?

 

MacPro 2,1

Quad-Core Intel Xeon 3GHz

8GB RAM

OSX 10.6.8

 

Thanks for any direction.

Posted on Jul 10, 2016 8:22 PM

Close

Q: Mac Pro 2,1 unexpectedly shuts down and restarts

  • All replies
  • Helpful answers

  • by lllaass,Helpful

    lllaass lllaass Jul 12, 2016 6:52 PM in response to MBV201
    Level 10 (189,522 points)
    Desktops
    Jul 12, 2016 6:52 PM in response to MBV201

    • Note the time of the next unintended reboot. After rebooting open the Console app in Finder>Applications>Utilities and look for log entries at the time of the reboot. Post suspicious ones here.

    Look before the log entry that starts with BOOT_TIME since that is the first line of a bootup

  • by MBV201,

    MBV201 MBV201 Jul 11, 2016 5:55 PM in response to lllaass
    Level 1 (4 points)
    Desktops
    Jul 11, 2016 5:55 PM in response to lllaass

    Thanks for your interest in helping, below is the log for immediately before the reboot that happened just a few moments ago.

     

    7/11/16 8:42:00 PMkernelGot boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleAHCI/PRT2 @2/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDri ver/ST31000528AS Media/IOGUIDPartitionScheme/Untitled@2
    7/11/16 8:42:00 PMkernelBSD root: disk1s2, major 14, minor 5
    7/11/16 8:42:00 PMkerneljnl: unknown-dev: replay_journal: from: 52615680 to: 54434816 (joffset 0x1d1c000)
    7/11/16 8:42:00 PMkernelFireWire (OHCI) TI ID 8025 built-in now active, GUID 001b63fffe8310cc; max speed s800.
    7/11/16 8:42:00 PMkerneljnl: unknown-dev: journal replay done.
    7/11/16 8:42:00 PMkernel[Bluetooth::CSRHIDTransition] switchToHCIMode (legacy)
    7/11/16 8:42:00 PMkernel[Bluetooth::CSRHIDTransition] transition complete.
    7/11/16 8:42:00 PMkernelCSRUSBBluetoothHCIController::setupHardware super returned 0
    7/11/16 8:42:00 PMkernelhfs: Removed 4 orphaned / unlinked files and 0 directories
    7/11/16 8:41:56 PMcom.apple.launchd[1]*** launchd[1] has started up. ***
    7/11/16 8:41:59 PMcom.apple.launchd[1](com.apple.usbmuxd) Unknown key: POSIXSpawnType
    7/11/16 8:42:00 PMDirectoryService[15]Improper shutdown detected
    7/11/16 8:42:01 PMkernelAppleIntel8254XEthernet: Ethernet address 00:19:e3:f9:77:6a
    7/11/16 8:42:01 PMkernelAppleIntel8254XEthernet: Ethernet address 00:19:e3:f9:77:6b
    7/11/16 8:42:01 PMkernelAirPort_Brcm43224: Ethernet address 00:1b:63:ef:0c:3a
    7/11/16 8:42:01 PMkernelIO80211Controller::dataLinkLayerAttachComplete():  adding AppleEFINVRAM notification
    7/11/16 8:42:01 PMkernelsystemShutdown false
    7/11/16 8:42:06 PMbootlog[43]BOOT_TIME: 1468284115 0
  • by lllaass,Helpful

    lllaass lllaass Jul 12, 2016 6:52 PM in response to MBV201
    Level 10 (189,522 points)
    Desktops
    Jul 12, 2016 6:52 PM in response to MBV201

    If you have a FireWire device connected, disconnect it.

    Try booting form Snow Leopard install disk and repairing the startup disk

  • by MBV201,

    MBV201 MBV201 Jul 12, 2016 6:52 PM in response to lllaass
    Level 1 (4 points)
    Desktops
    Jul 12, 2016 6:52 PM in response to lllaass

    Thanks so much for your help and assistance to this point. There is/was no FireWire device connected. Utilized the Max Osx Snow Leopard startup disk to start utilities and disk repair... but still had the same shutdown problem and the log looked identical to the previous versions.  Is this a dead end?

     

    Supplemental points:

    1) Do not have the original install disk for the Mac Pro 2,1... the disk being used is the Snow Leopard update.

    2) The port directly below the FireWire port is lit up with a red light, "optical audio" and the "out" port.

    2A) Considering it might be a FireWire port issue, inserted a FireWire cable connected to an external drive and the Mac shutdown almost immediately.

     

    Thanks again, your insight has been very valuable.

  • by lllaass,

    lllaass lllaass Jul 13, 2016 1:04 AM in response to MBV201
    Level 10 (189,522 points)
    Desktops
    Jul 13, 2016 1:04 AM in response to MBV201

    I would try a fresh install of Snow Leopard on another disk to rule out a software problem.

     

    You can also try to run Apple hardware Test

    Using Apple Hardware Test - Apple Support

    Since you do not have the original disks with AHT, you can get it here

    https://github.com/upekkha/AppleHardwareTest

    https://gist.github.com/drewreece/2e5eed7dbfbd5dd7e929

    AHT is specific to each model Mac so make sure you get the one for your model Mac

  • by MBV201,

    MBV201 MBV201 Jul 14, 2016 8:27 PM in response to lllaass
    Level 1 (4 points)
    Desktops
    Jul 14, 2016 8:27 PM in response to lllaass

    Didn't realize that AHT was available for download. Thanks for that!

     

    Performed AHT, received a "No trouble found" report. However, while performing the extended testing, the Mac crashed again.

     

    Now, there's a new console message different than the previous previous to the boot_time message. Attached below. Thanks so much for your guidance thus far! I'm thinking I need to re-install and see if the problem continues.

     

    7/14/16 9:26:07 PMbootlog[43]BOOT_TIME: 1468545954 0
    7/14/16 9:26:19 PMloginwindow[31]USER_PROCESS: 31 console
    7/14/16 9:26:19 PMcom.apple.launchd.peruser.501[107](com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    7/14/16 9:26:59 PMbootlog[43]BOOT_TIME: 1468546008 0
    7/14/16 9:27:16 PMloginwindow[31]USER_PROCESS: 31 console
    7/14/16 9:27:16 PMcom.apple.launchd.peruser.501[108](com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    7/14/16 9:27:24 PMcom.apple.launchd.peruser.501[108](com.apple.mrt.uiagent[142]) Exited with exit code: 255
    7/14/16 9:27:24 PMcom.apple.launchd.peruser.501[108](com.apple.Kerberos.renew.plist[143]) Exited with exit code: 1
    7/14/16 9:28:41 PMlogin[164]USER_PROCESS: 164 ttys000
    7/14/16 9:28:44 PMlogin[164]DEAD_PROCESS: 164 ttys000
    7/14/16 9:44:07 PMbootlog[43]BOOT_TIME: 1468547038 0
    7/14/16 9:44:23 PMloginwindow[31]USER_PROCESS: 31 console
    7/14/16 9:44:24 PMcom.apple.launchd.peruser.501[108](com.apple.ReportCrash) Falling back to default Mach exception handler. Could not find: com.apple.ReportCrash.Self
    7/14/16 9:44:31 PMcom.apple.launchd.peruser.501[108](com.apple.mrt.uiagent[141]) Exited with exit code: 255
    7/14/16 9:44:31 PMcom.apple.launchd.peruser.501[108](com.apple.Kerberos.renew.plist[142]) Exited with exit code: 1
  • by lllaass,

    lllaass lllaass Jul 15, 2016 12:52 AM in response to MBV201
    Level 10 (189,522 points)
    Desktops
    Jul 15, 2016 12:52 AM in response to MBV201

    Because of the shutdown with extended test and

    2A) Considering it might be a FireWire port issue, inserted a FireWire cable connected to an external drive and the Mac shutdown almost immediately

    I suspect a hardware problem.

     

    - If you have the original graphics card it could be that. AHT is not good at detecting graphics card problems.

    - It could be memory since the memory in the 200602008 Mac Pros run hot and tend to fail with time. I would take out some memory and run AHT extended and see what happens. Repeat the swapout as necessary.