Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Hammertime 01

macrumors newbie
Original poster
Jul 25, 2024
7
0
My Mac Pro hits the logo, loads about halfway and then loops or goes black. I have exhausted the google searches.
Before the logo I get the three options - boot my drive ( goes to logo and then loops) - recovery ( goes blank after trying to reload or do something) - nvram reset ( I think it resets then goes back to the three choices again

The last thing on all the apple support options to solve it says to take it into the shop, I live in the mountains.
 
My Mac Pro hits the logo, loads about halfway and then loops or goes black. I have exhausted the google searches.
Before the logo I get the three options - boot my drive ( goes to logo and then loops) - recovery ( goes blank after trying to reload or do something) - nvram reset ( I think it resets then goes back to the three choices again

The last thing on all the apple support options to solve it says to take it into the shop, I live in the mountains.
It would help to understand more about your computer/software environment.

Can you let us know what cMP you have - a true 2010/2012 5,1 or a 4,1 patched to 5,1? What OS, if you are using an unsupported OS what means of using OpenCore are you using? What video card? Did you change anything that might have contributed to the boot issue (hardware, software)?
 
Ok this is the best to my knowlegde.. I think it was updated to big sur and it was running ok for awhile. not sure about the rest sorry, how can I find this info for you now?
 
Remove all your bootable disks, install a spare disk and do a Mojave clean install. Without a supported macOS release as a rescue disk you can't get anywhere when you have issues with unsupported macOS releases.
 
Hi, Thanks in advance for any help. I have a mac pro 5,1 mid 2010, with 12-Core 3.46GHz Xeon 64 GO 1333 DDR3, NVDIA NVS 510. I was running Big Sur before it wouldn't boot up.
On loading I get the Disk, Recovery and Reset NVRAM options on the screen. The Disk just goes into a loop or just crashes to a black screen, Recovery makes a few different noises and then goes back and this is the same with the reset NVRAM. I've tried command+R etc and safe mode, different key boards (Bluetooth and USB), changed the the xeon's to new ones.
My guess was/is that it was the update firmware and I might of tried to update to a later one. so in goes the bootable USB with High Sierra, yay it's working and it's loading..... well after a few attempts with it loading then crashing to the black screen, I am able to get it to load the bar all the way but that's it, a full bar and after a day still the same, the full bar showing on the screen...... I have a new graphics card coming from macvidcards europe, but I'm not sure if thats the problem and I've just wasted money.
I have a macbook pro and want to know is it possible to hook in up and use disk utilities to look at the mac pro 5,1???? or any other options I could use???
all hot keys I could find don't work ie: command+R - command+alt+P+R - command+alt+R - command+S - command+D

Any ideas/help is much appreciated
Thanks
 
1st: there is no firmware updates for MacPro5,1 AFTER Mojave, once you have 144.0.0.0.0 installed, you are done.

2nd: Only High Sierra and Mojave full installers can update MacPro5,1 BootROM. The former up to MP51.0089.B00 and the latter from MP51.0089.B00 to 144.0.0.0.0.

3rd: Target Disk Mode will require a FW800 cable and is not the best way to test a disk. Anyway, you can try it.

4th: Internet Recovery is not available with a MacPro5,1, so, is useless to try anything related with a blank disk, you need to create a createinstallmedia USB installer.
Hey Thanks Tsialex, I have got the createinstallmedia USB installer and as I said, it loads but it stops at best at a full bar. your 2nd option is what I think went wrong but I'm stuck on how to fix the issue.
 
1st: Why open a new thread exactly about the same issue of your previous thread?!?


2nd: there is no firmware updates for MacPro5,1 AFTER Mojave, once you have 144.0.0.0.0 installed, you are done.

3rd: Only High Sierra and Mojave full installers can update MacPro5,1 BootROM. The former up to MP51.0089.B00 and the latter from MP51.0089.B00 to 144.0.0.0.0. Catalina and newer does not have firmware updates for a MacPro5,1.


4th: Target Disk Mode will require a FW800 cable and is not the best way to test a disk. Anyway, you can try it.

5th: Internet Recovery is not available with a MacPro5,1, so, is useless to try anything related with a blank/defective disk, you need to create a createinstallmedia USB installer.

Run AHT/ASD and see if you have a harware defect somewhere.

AHT/ASD:
You need an Apple OEM GPU (HD 2600XT, 8800GT, Quadro FX 5600, GT120, HD 4870/5770/5870) to run AHT/ASD. AHT/ASD can be used with PC flashed GPUs, but will fail mid test with a sensor error when the GPU sensors are tested. Non flashed PC GPUs won't work at all. You need to boot completely vanilla, no OC, to use AHT/ASD.​
You can get AHT links and instructions on how to install it on this GitHub article.​
AHT, you need 022-4831-A.dmg:​
The ASD version that you need is 3S149. The AHT instructions are valid for creating an ASD USB key and Apple provides an installation PDF with it.​
ASD, you need 3S149:​
For people that have an early-2009 cross-flashed with MP5,1 firmware, you will need to run the MacPro5,1 versions of AHT (022-4831-A) and ASD (3S149).
 
1st: Why open a new thread exactly about the same issue of your previous thread?!?


2nd: there is no firmware updates for MacPro5,1 AFTER Mojave, once you have 144.0.0.0.0 installed, you are done.

3rd: Only High Sierra and Mojave full installers can update MacPro5,1 BootROM. The former up to MP51.0089.B00 and the latter from MP51.0089.B00 to 144.0.0.0.0. Catalina and newer does not have firmware updates for a MacPro5,1.


4th: Target Disk Mode will require a FW800 cable and is not the best way to test a disk. Anyway, you can try it.

5th: Internet Recovery is not available with a MacPro5,1, so, is useless to try anything related with a blank/defective disk, you need to create a createinstallmedia USB installer.

Run AHT/ASD and see if you have a harware defect somewhere.

AHT/ASD:
You need an Apple OEM GPU (HD 2600XT, 8800GT, Quadro FX 5600, GT120, HD 4870/5770/5870) to run AHT/ASD. AHT/ASD can be used with PC flashed GPUs, but will fail mid test with a sensor error when the GPU sensors are tested. Non flashed PC GPUs won't work at all. You need to boot completely vanilla, no OC, to use AHT/ASD.​
You can get AHT links and instructions on how to install it on this GitHub article.​
AHT, you need 022-4831-A.dmg:​
The ASD version that you need is 3S149. The AHT instructions are valid for creating an ASD USB key and Apple provides an installation PDF with it.​
ASD, you need 3S149:​
For people that have an early-2009 cross-flashed with MP5,1 firmware, you will need to run the MacPro5,1 versions of AHT (022-4831-A) and ASD (3S149).
Okay i'll see how I go with this ASD thanks
 
Okay i'll see how I go with this ASD thanks
Hi tsialex, thanks for all the info. I have over looked something which could help on the opening screen, the recovery reads "recovery 11.7.6 (dmg)" which is big sur i think, and as you stated is not supported on this mac pro 5,1 with the card I have.
I'm now thinking of connecting a sata ssd to my macbook and installing high seirra on it, install it and see if that runs? or is this a waste of time and you have a better idea?
 
Should work unless is a MacBook with NVIDIA chipset. Worth a try.
Hi Tsialex, just thought I give you an update. I installed the new sapphire rx 580 from Macvid Europe ( https://www.macvidcards.eu/products/amd-radeon-rx-580-8-gb-gddr5 ) comes with boot screen etc and this solved the issue. conculion is that even though it ran for awhile the NVDIA NVS 510 was stopping everything from loading due to macOS Big sur. Thanks for you help and the work you do here
 
Hi,

i have the same issue. I have a patched 4.1 (with new FW Build to 5.1 from Macschrauber) and 2x6 Core CPU inside.

Yesterday I turned on my Mac Pro for the first time in the last 6 Months. Everything okay. Then i updated OCLP to 1.5. Also everything okay. The MacOS Version was 14.4 so i decided to make the Update to 14.6.1.

After that, i have the infinite Loop with this Errormessage:
IMG_3017.jpg


So i deleted my SSD with Sonoma (i have also a Mojave SSD inside) and made an install with an Sonoma Install Stick with 14.4.1 (generated with OCLP 1.5). Everything fine. But when i migrate my Data from TimeMachine (via Synology) and after the first reboot ... the same Error.

I don't know exactly was this AHCI failure means but now i will install a clean copy and get my data manually back from my backup. I migrate the whole User but i don't understand, why this causes in a crash.

Perhaps, anyone has an idea? I also tried safe boot but this also crashes.

Here ist the line:
[AHCI][PRT][001F0200] AbortCommands: :5382:port 0 - called, deviceWithError 0, errCode = 0xe0030005
 
Last edited:
Here ist the line:
[AHCI][PRT][001F0200] AbortCommands: :5382:port 0 - called, deviceWithError 0, errCode = 0xe0030005

Disk/storage related message, all AHCI errors are storage related. The most probable is that your main disk is problematic/dying.

I'd at least take a look with DriveDX for any SMART errors, also try with another disk.
 
  • Like
Reactions: SirVikon
@tsialex many thanks. I will Test this. I have ordered a crucial BX500 to Test it. i dont want to Sprint too much Money fit my Mac Pro.

My SSD is a Evo 860. i will Test the Drive.

Okay, here is the DriveDX Report: I think the drive is okay. I Will test the drive in another Slot. Perhaps there is a problem.

Any other ideas?
 

Attachments

  • DriveDxReport_Samsung SSD 860 EVO 500GB_2024-08-27_20-52-20-819.txt
    9.8 KB · Views: 26
Last edited:
@tsialex many thanks. I will Test this. I have ordered a crucial BX500 to Test it. i dont want to Sprint too much Money fit my Mac Pro.

BX500 is not a MacPro compatible SSD and fails within days/weeks of being installed, personally had two failing within the first month. Crucial BX500 is the equivalent of Samsung 870 QVO.

No SATA SSD currently being sold by Crucial is fully compatible with a Mac Pro, not even the MX500 (today's generation of MX500 just have the same name as to the beloved by some old MX500 from 2016~2019, nothing similar internally).

Crucial does not test SSDs with Macs.

My SSD is a Evo 860. i will Test the Drive.

Okay, here is the DriveDX Report: I think the drive is okay. I Will test the drive in another Slot. Perhaps there is a problem.

Any other ideas?

Check any other disk installed, remove anything that you don't need, add one at a time.

I'd install Mojave to the Samsung SSD and use for some days to be sure that the problem is not somewhere else and is being shown wrongly as an AHCI problem.

Run AHT/ASD, see my earlier post on this thread. Also check the RTC battery voltage.
 
  • Like
Reactions: SirVikon
I ran the AHT with no errors. For the ASD i am too stupid. I cant make a bootable ASD ... tried but failed.

I ordered a new Battery (BR 2032) and will change it tomorrow.

Mojave on the SSD (Samsung Evo 860) works fine for now. But when i want to upgrade, every attempt ends in infinite loops.

The messages with AHCI also appear, when i start recovery in OC. In the past i did my OC config at my own (with the tutorial here) and now i trust to OCLP, which worked fine for me the last two years.
 
The messages with AHCI also appear, when i start recovery in OC. In the past i did my OC config at my own (with the tutorial here) and now i trust to OCLP, which worked fine for me the last two years.

Diagnose with Mojave, Sonoma will get you nowhere trying to diagnose this issue since, the missing AVX2 instructions can make macOS to have very weird behavior with crashes happening in weird and unexpected places.

Btw, frequent crashes can brick your Mac Pro since the crashes are written to the NVRAM volume inside the BootROM.
 
  • Like
Reactions: SirVikon
Hi, now i have Monterey back at my cMP and in this moment i play back my TM-Backup Data.

Looks like there is an App on my Mac that causes the problems with AVX2 ... perhaps i will stay at monterey. And in the next two years i will buy an used Mac Studio :)

Thank you for your Support. An i have a backup of my Firmware (including EnableGOP) :) When my Data is back i will check with Macschraubers tool and restore the Clean Dump :)
 
Last edited:
Hi, now i have Monterey back at my cMP and in this moment i play back my TM-Backup Data.

Looks like there is an App on my Mac that causes the problems with AVX2 ... perhaps i will stay at monterey. And in the next two years i will buy an used Mac Studio :)

Thank you for your Support.

You still need to address the mess that the crashes caused inside the BootROM, if you have clean dump to flash, flash it. If not, then you gonna need the BootROM reconstruction service.
 
  • Like
Reactions: SirVikon
Yeah. My Test to bring back the Data from TM was a mistake. After that, Monterey doesnt start anymore.

I thought there wäre only Userdata but it fails tonstart up then.

So i will delete everything and begin with a clean install of Monterey. After that i will install every App for it’s own.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.