MP 7,1 Mac Pro 2019 Kernel Panic on boot Macos Monterey 12.7.6

[GreppMichaels]

Hello Everybody,

Have been having this infrequent issue only at boot and pretty randomly. I did a lot of research prior to posting and couldn't find anyone with this exact issue. All I know is this is likely related to the onboard SSD or controller, and that typically symptoms arise with a Bootcamp partition which I had and then deleted however the symptoms remain. Here are the first few lines of the panic:

panic(cpu 0 caller 0xfffffff00c21b774): ANS2 Recoverable Panic - assert failed: [11184]:HIX 207 timed out for segIdx 0x314d in 8.1 seconds, comp FIFO count 0, bus=15, nandOp=11 - Timer(12)

assert failed: [11184]:HIX 207 timed out for segIdx 0x314d in 8.1 seconds, comp FIFO count 0, bus=15, nandOp=11

RTKit: RTKit-2419.140.12.release - Client: t8012.release-AppleStorageProcessorANS2-1306~24224~1306~24224

!UUID: 5d2b0cdb-b1ff-3166-979f-68ad5ebbefa6

Time: 0x000000000c7cffb7



Faulting task 12 Call Stack: 0x0000000000015724 0x00000000000150a0 0x0000000000014eac 0x00000000000173f0 0x000000000001c904 0x000000000001c77c 0x00000000000b50a8 0x000000000005569c 0x000000000003cc3c



Is my SSD toast? I never have crashes or issues when in the OS, this is only on boot. I did find some fixable errors at a point on my drive, but this didn't seem to fix it. I'm going to do a fresh install of Monterey and see if it keeps happening.

Any advice is appreciated!


-Michael

 

[GreppMichaels]

I should add, I wiped the drive, ran first aid multiple times and didn't see any issues. Currently reinstalling Macos Monterey, hoping this fixes things.

Also, when it does this, the computer basically half boots. It will light up, pause, turn off light, longer pause, and then boot again. But it always makes it to Macos when it does, and there is no logic to this.

 

[tsialex]

Did you tried Apple Configurator DFU restore? Seems the only way to force a onboard SSD low-level clean-up.

 

[GreppMichaels]

Did you tried Apple Configurator DFU restore? Seems the only way to force a onboard SSD low-level clean-up.

First just want to say you are THE MAN as usual. And yes this actually was my first move however I can't get it installed on my Macbook with Monterey, says I need OS 14 or later, and even Apples instructions on getting past this issue don't seem to work.

To add insult to injury I'm getting errors updating from Monterey to Seqouia so I'm trying Sonoma as we speak. I will be running the configurator then however can you give some insight into what this issue is? Is it is something that hopefully I can fix or are the codes more likely a permanent hardware issue?

 

[tsialex]

Sometimes unfortunately is NAND sector exhaustion, but other times the SSD just need some logical shake-up for running good again.

You should try it, solve the issues with the MacBook, install Apple Configurator and then do a DFU restore.

Btw, never do a restore while Apple is releasing new software, the load on the content servers can make Apple Configurator to have time-outs and weird issues, lots of posts on this.

Also, after doing the restore, try installing and running macOS for some time over a NVMe blade. This will give you clues related to the NAND banks/ onboard controller.

 

[GreppMichaels]

Sometimes unfortunately is NAND sector exhaustion, but other times the SSD just need some logical shake-up for running good again.

You should try it, solve the issues with the MacBook, install Apple Configurator and then do a DFU restore.

Btw, never do a restore while Apple is releasing new software, the load on the content servers can make Apple Configurator to have time-outs and weird issues, lots of posts on this.

Also, after doing the restore, try installing and running macOS for some time over a NVMe blade. This will give you clues related to the NAND banks/ onboard controller.

It's an 8TB drive in my Mac Pro so I'd like to think those would last the longest but who knows!

I don't have another drive to boot from right now, but I can look into that eventually.

When you mention issues with a restore, is there something going on right now that may be problematic? Or are you just speaking in general.

 

[tsialex]

It's an 8TB drive in my Mac Pro so I'd like to think those would last the longest but who knows!

Ouch! This is really unfortunate.

I don't have another drive to boot from right now, but I can look into that eventually.

You should do it, get a cheap M.2 adapter and a cheap NVMe blade and see if the crashes stop.

When you mention issues with a restore, is there something going on right now that may be problematic? Or are you just speaking in general.

See this thread, there are other threads all over the forum:

https://forums.macrumors.com/threads/install-macos-on-new-ssd-kit.2429259/post-33211664

 

[Regulus67]

... I can't get it installed on my Macbook with Monterey, says I need OS 14 or later, and even Apples instructions on getting past this issue don't seem to work. ...

You couldn't install Apple Configurator on Monterey? I use that on my iMac Pro with Monterey 12.7.2.
As I documented in the thread tsialex was kind enough to reference.

I did however not use the DFU mode, when downgrading the new iMac Pro to Monterey. Only re-formatted the SSD with Disk Utility.

I am not able to decipher panic logs, so have no comment on that part.
I would also believe that the 8TB SSD kit is long-lasting.
And if there are no issues except for on boot, I would assume other than hardware failure.

If you use DFU-mode restore, it will also wipe the security startup admin. So installing from a bootable usb will not work. At least that has been my experience

 

[benmuetsch]

Sorry to jump in with a general question, but is it also possible to do a fresh, clean reinstall of macOS using DFU restore mode? I think I saw dosdude doing this, but it was on an Apple Silicon machine, if I recall correctly.

 

[Regulus67]

... but is it also possible to do a fresh, clean reinstall of macOS using DFU restore mode?...

Yes it is. That will wipe the SSD completely, with no trace of the old install.
I am not sure if you will be able to download an older macOS from Apple. You can try to use different options with the new install.

If it doesn't work, the latest macOS should download and install without any issue.
Perhaps that is what you want anyway.

 

[benmuetsch]

I really meant a fresh installation of a specific macOS, like Monterey, completely without Internet Recovery, which can sometimes be a bit unreliable. When you update the firmware of the SSD kit using DFU - as you experienced - you can’t initially boot from USB because of the security settings which cannot be changed without any local macOS install.

 

[Regulus67]

I really meant a fresh installation of a specific macOS, like Monterey, completely without Internet Recovery, which can sometimes be a bit unreliable. When you update the firmware of the SSD kit using DFU - as you experienced - you can’t initially boot from USB because of the security settings which cannot be changed without any local macOS install.

You should not use DFU mode then.
Use a bootable USB with Monterey, and use Disk Utility to format the SSD kit. Then install macOS Monterey.


When my attempt failed with a brand new SSD kit, it had to connect to the Apple server for the firmware. At least that was what the boot process told me. But it never did.
The problem was not repeated with the Sonoma install, it installed without any issue. I realised later that I could install Monterey again. When I followed that procedure with an iMac Pro

 

[mattspace]

You couldn't install Apple Configurator on Monterey? I use that on my iMac Pro with Monterey 12.7.2.
As I documented in the thread tsialex was kind enough to reference.

Apple doesn't offer configurator for any OS version prior to macOS 14 now. If you already have it on Monterey, you're good, but you can't get it afresh.

 

[Regulus67]

Apple doesn't offer configurator for any OS version prior to macOS 14 now.

The situation is far worse than I would have imagined, then.

That Apple stops selling the previous hardware models is one thing. But to cut off access to software just because one doesn't happen to be on the latest OS version is beyond the pale.
As macOS is updated with a new version every single year, and encourages everyone to do the upgrade.

Shouldn't the Apple Configurator be based on hardware support? And offer to download an older version based on the macOS version?
I just checked my version. I got mine June last year, Apple Configurator 2.16 with macOS Monterey installed.
The new version is Apple Configurator 2.17

That said. I hope GreppMichaels is able to fix the kernel panic on boot

 

[tsialex]

Apple doesn't offer configurator for any OS version prior to macOS 14 now. If you already have it on Monterey, you're good, but you can't get it afresh.

Nope, just got it with a clean install of Monterey:

Maybe you are saying that you can't get if you never "purchased with the MAS" before, then you can get it for first time with Sonoma/Sequoia, go back to Monterey and download it.

 

[mattspace]

Shouldn't the Apple Configurator be based on hardware support? And offer to download an older version based on the macOS version?

I'm on Ventura, I can't get a version of Configurator for any OS earlier than Sonoma.

I'd be curious what happens on a machine that tops out at Ventura or Monterey.

 

[mattspace]

Nope, just got it with a clean install of Monterey:

View attachment 2438540

Maybe you are saying that you can't get if you never "purchased with the MAS" before, then you can get it for first time with Sonoma/Sequoia, go back to Monterey and download it.

Possibly that's the subtlety, maybe if you have a machine that tops out on an older OS version you can still buy it and get the older version.

But they sure won't "sell" it to you if you're on an older OS version with hardware capable of running something newer.

 

[tsialex]

Just downloaded a previously purchased Apple Configurator 2 with a Mojave VM, no problem:

Same MAS rules as any other Apple software sold there, this VM can run Sequoia btw.

 

[mattspace]

Just downloaded Apple Configurator 2 with a Mojave, no problem:

I'm trying to buy it for the first time on a High Sierra machine, and I get the same "macOS version 14 or later is required" refusal.

So that's the thing, if you want to get configurator now, and you haven't "bought" it previously, Apple won't sell it to you unless you're on Sonoma or later.

*edit* which gets back to my previous point - IF you need to do a DFU restore, you can't repurpose an old laptop to do it, if you haven't "bought" configurator at some time in the past.

 

[tsialex]

I'm trying to buy it for the first time on a High Sierra machine, and I get the same "macOS version 14 or later is required" refusal.

So that's the thing, if you want to get configurator now, and you haven't "bought" it previously, Apple won't sell it to you unless you're on Sonoma or later.

Yes, as any other Apple software sold by the MAS. FCPX people knows this rule very well.

 

[mattspace]

Yes, as any other Apple software sold by the MAS. FCPX people knows this rule very well.

I am wondering though, what happens if you buy it on sonoma, will the older version become available for older OSes, or does the purchase receipt limit you to newer versions only.

 

[tsialex]

I am wondering though, what happens if you buy it on sonoma, will the older version become available for older OSes, or does the purchase receipt limit you to newer versions only.

AFAIK, even with FCPX you can buy and first download with the current macOS and then later download with past macOS versions.

 

[mattspace]

AFAIK, even with FCPX you can buy and first download with the current macOS and then later download with past macOS versions.

Well, when I get back from weekend I'll spin up a Sonoma VM and see if I can get Apple to sell me a free app *shakes head*.

 

[GreppMichaels]

Ouch! This is really unfortunate.



You should do it, get a cheap M.2 adapter and a cheap NVMe blade and see if the crashes stop.



See this thread, there are other threads all over the forum:

https://forums.macrumors.com/threads/install-macos-on-new-ssd-kit.2429259/post-33211664

Appreciate the insight.

No issue reinstalling Monterey or the firmware after getting it into DFU mode. My main issue was the one a few other people posted about how you cannot install the configurator anymore on older machines if you didn't once have it before.

Mac Pro seemed stable and great for the last 24 hours as I did about 20+ shutdowns mixed with 5 or 10 restarts throughout the day after config yesterday, however after a 4th or 5th test boot today I got the same error again:

panic(cpu 0 caller 0xfffffff019e677b0): ANS2 Recoverable Panic - assert failed: [11184]:HIX 1 timed out for segIdx 0x2f00 in 8.1 seconds, comp FIFO count 0, bus=15, nandOp=11 - Timer(12)
assert failed: [11184]:HIX 1 timed out for segIdx 0x2f00 in 8.1 seconds, comp FIFO count 0, bus=15, nandOp=11
RTKit: RTKit-2758.1.1.release - Client: t8012.release-AppleStorageProcessorANS2-1307~17857~1307~17857
!UUID: 4f8a10a1-9aef-34a8-90b7-79ad0f4428a9
ASLR slide: 0x0000000000000000
Time: 0x000000000c7ea05f

Does anyone know explicity what this means? All I know is the ANS2 refers to the onboard drives. Otherwise I have no idea.

 

[GreppMichaels]

AFAIK, even with FCPX you can buy and first download with the current macOS and then later download with past macOS versions.

UPDATE 10/22/24: finally got the same ANS2 Kernel Panic on first boot this AM and dropped it off an hour ago at Apple for a free diagnostic.

Here is where things currently stand, I think I resolved the issue but am documenting it in depth below for anyone in the future who encounters something similar:

After reformatting and then going into DFU and re-flashing firmware and doing a reinstall, I upgraded back to Monterey and did Migration assistant from my time machine backup. Seemed I was in the clear as I had no Kernel panics for maybe 24 hours after booting the machine around 30 times.

The next day after around 24 hours it Kernel panicked again and restarted (like it would do) on a cold boot in the late AM. I did some more research, removed all accessories/TB dock and kept running it to isolate the issue further.

Still more panics.

Called a local Apple repair shop I've gone to in the past and they suggested I try a clean boot without Migration assistant. I'd already been leaning towards this solution because it was the last thing I hadn't done, but hearing them suggest it after I described all my other issues made me more confident about testing it out.

It's now been roughly 72 hours and I have not had a Kernel Panic. I'm on a fresh install of Monterey, literally nothing installed on it and have been booting, rebooting, and restarting 10 or so times a day. As the issue only happens on reboot.

As much as it seems this is a hardware issue I really think something deep down in my backup or OG install of Monterey is causing the problem. Especially because this computer was migrated from a different specc'd 7,1 that I sold, to afford to upgrade to this one. And that 7,1 was originally migrated from a 2019 MBP.

So there is a lot of room for a weird corruption or config along the way. I even ran Apple hardware diagnostics and have been checking the console to confirm things are ok now.

I will update this post if the issue continues but I think it was a software problem all along. Am wondering what I should do about my original system config. I have a similar install on my 2019 MBP and I may do a migration from there, I'm just worried I'll corrupt the drive again though.

But thank god My system/drive/logic board appears to not be failing.. (for now lol)