MP 7,1 Latest Security Update bricked Mac Pro

[Ryan P]

Freaking out at the moment. After installing the security update for Catlina and rebooting I get a white circle with an X in it.... was a very weird update process... with a screen telling me that my disk needed to be updated after the reboot.

No non Apple products installed... trying the Internet recovery now..

Proceed with caution.

 

[Ryan P]

It's letting me restore from Time Machine... started at 14 hours remaining...but down to 3 hours now.. I need it back by 4am. Joyful.

 

[LeonPro]

Interesting.

I updated mine. I have connected peripherals both internal as well as external via a Thunderbolt dock. I did not disconnect anything. Update went smooth with no hiccups.

 

[OkiRun]

The latest update for Catalina ~
It shut down after download, started back up again and finished install, then shut down again.
Editor had to restart computer ~ which happened with no problems after that.

 

[LeonPro]

Whoops. I can't read. I thought this post was referring to the latest Big Sur update which I did for the Mac Pro.

Curious what's making you guys stick with Catalina until now? What software is holding you back?

 

[LeonPro]

Also off topic, @OkiRun, I noticed your signature says the Brio magnetic 4K sux. I'm using the original Logtiech 4K Brio and don't like it as well because it goes in and out of focus at times. I was going to switch to the Apple version, but is that the same issue you have?

 

[OkiRun]

Also off topic, @OkiRun, I noticed your signature says the Brio magnetic 4K sux. I'm using the original Logtiech 4K Brio and don't like it as well because it goes in and out of focus at times. I was going to switch to the Apple version, but is that the same issue you have?

It looks a little grainey and pixelates during motion. Editor has tried different ports on 7,1. Nothing makes image look good.
Everyone on zoom meeting comments negative at us image. Claim us to be cheap. Sad camera.

 

[OkiRun]

Whoops. I can't read. I thought this post was referring to the latest Big Sur update which I did for the Mac Pro.

Curious what's making you guys stick with Catalina until now? What software is holding you back?

The 7,1 has many Pixel Film Studio apps loaded and make for fast editing of small projects. Not compatible with Big Sur so not updating.

 

[Macschrauber]

Op does use the wrong terms.

this is not bricking.

bricking is unusable, dead machine what needs to be replaced or physically repaired.

 

[dominicperry]

Freaking out at the moment. After installing the security update for Catlina and rebooting I get a white circle with an X in it.... was a very weird update process... with a screen telling me that my disk needed to be updated after the reboot.

No non Apple products installed... trying the Internet recovery now..

Proceed with caution.

Good luck with the recovery. Not sure what your full spec is but mine is below....

Worked fine here on a plain 7.1 Mac Pro, 16 core, 48GB RAM, 1TB SSD, running Catalina 10.15.7
System Report now reads:

System Version: macOS 10.15.7 (19H1030)
Kernel Version: Darwin 19.6.0

I don't have SIP enabled and I'm not using FileVault.

 

[JesterJJZ]

I always stay a solid year behind on OS updates, sometimes every other release. That's about how long it takes for a new OS to become stable and supported by everything I need. No need to try to stay bleeding edge and be a beta tester.

 

[th0masp]

I always stay a solid year behind on OS updates, sometimes every other release. That's about how long it takes for a new OS to become stable and supported by everything I need. No need to try to stay bleeding edge and be a beta tester.

Well you might be in this case - if your machine was locked at a minimum version of Catalina.

Anyway these updates are kinda scary and they don't clearly communicate what's going on. Computer rebooting a couple times, seemingly turning itself off now and then and just sitting there for a while - not cool. I do recall I had that case as well where I let it sit for an hour or so to be safe before manually turning it on again - aaaaand update ... continues.

 

[dominicperry]

I always stay a solid year behind on OS updates, sometimes every other release. That's about how long it takes for a new OS to become stable and supported by everything I need. No need to try to stay bleeding edge and be a beta tester.

This has nothing to do with 'bleeding edge' or staying behind on version updates.
Before you start this upgrade your machine is on 10.15.7. When you finish it's on 10.15.7. It's a security update and it isn't intended to provide any additional functionality. It's the essence of a patch.
The problem is most likely to be with the installer rather than the OS itself.

 

[JesterJJZ]

This has nothing to do with 'bleeding edge' or staying behind on version updates.
Before you start this upgrade your machine is on 10.15.7. When you finish it's on 10.15.7. It's a security update and it isn't intended to provide any additional functionality. It's the essence of a patch.
The problem is most likely to be with the installer rather than the OS itself.

It was in reply to a comment saying "why not just upgrade to big sur...etc".

 

[theirongiant]

Did anyone here with problems have FileVault enabled?

That seems to be the common thread with these systems that just applied the Catalina Security Update 2021-002. The new build number is 19H1030. We had more than 10 iMac Pro's in our environment affected by this and we called Apple.

Currently they have reproduced the issue and are waiting on a fix from engineering.

One good workaround is to go to Recovery Mode and decrypt the disk from there. A decrypted disk, even with the security update installed, will always boot. As soon as you re-enable filevault, it goes south. There's no risk to data.

Another workaround is to upgrade the iMac Pro straight to Big Sur, instead of applying the security update. We don't like it, but it works. I'm still pretty confident Apple will fix this before macOS 12 drops.

 

[OkiRun]

Did anyone here with problems have FileVault enabled?

That seems to be the common thread with these systems that just applied the Catalina Security Update 2021-002. The new build number is 19H1030. We had more than 10 iMac Pro's in our environment affected by this and we called Apple.

Currently they have reproduced the issue and are waiting on a fix from engineering.

One good workaround is to go to Recovery Mode and decrypt the disk from there. A decrypted disk, even with the security update installed, will always boot. As soon as you re-enable filevault, it goes south. There's no risk to data.

Another workaround is to upgrade the iMac Pro straight to Big Sur, instead of applying the security update. We don't like it, but it works. I'm still pretty confident Apple will fix this before macOS 12 drops.

You posted to the Mac Pro forum.

 

[theirongiant]

You posted to the Mac Pro forum.

 

[patrick.a]

Did anyone here with problems have FileVault enabled?

That seems to be the common thread with these systems that just applied the Catalina Security Update 2021-002. The new build number is 19H1030. We had more than 10 iMac Pro's in our environment affected by this and we called Apple.

Currently they have reproduced the issue and are waiting on a fix from engineering.

One good workaround is to go to Recovery Mode and decrypt the disk from there. A decrypted disk, even with the security update installed, will always boot. As soon as you re-enable filevault, it goes south. There's no risk to data.

Another workaround is to upgrade the iMac Pro straight to Big Sur, instead of applying the security update. We don't like it, but it works. I'm still pretty confident Apple will fix this before macOS 12 drops.

So is this the same problem we've discussed over here? https://forums.macrumors.com/threads/prohibitory-sign-on-mac-pro-7-1-after-security-update.2295893/

 

[Ryan P]

So is this the same problem we've discussed over here? https://forums.macrumors.com/threads/prohibitory-sign-on-mac-pro-7-1-after-security-update.2295893/

Ya I just posted there, saying that FileVault disable fixes...as does going to Big Sur....but I had other issues with Big Sur, so back to Catalina with FileVault disabled. I don't really like it, but no choice at the moment.

 

[Schismz]

Well you might be in this case - if your machine was locked at a minimum version of Catalina.

Anyway these updates are kinda scary and they don't clearly communicate what's going on. Computer rebooting a couple times, seemingly turning itself off now and then and just sitting there for a while - not cool. I do recall I had that case as well where I let it sit for an hour or so to be safe before manually turning it on again - aaaaand update ... continues.

Ya, Cheesegrater 2019 debuted on Catalina, so it was Catalina or Catalina ;-)

The updates have become both gigantic for every .point "security" release and do those very long multiple reboots wherein I assume it's updating firmware.

I have 99 things plugged into a variety of ports, bunch of cards, drives, etc, and I haven't ever disconnected anything during upgrades, and thus far it's all Just Worked with Big Sur. Go figure.