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

Startup Chime Changes After 2020-007 Security Update...

Hombre53

Hombre53

macrumors regular
Original poster
Feb 27, 2018
246
263
After some initial trepidation, I applied the 2020-007 Mojave Security Update to my late 2013 27" iMac. All seemed to go well, at least until the Mac rebooted and then gurgled a low demonic sounding "chime" in place of the "normal" chime I have become used to, at least since 2006 when I gave up on PC's and Microsoft and moved to the Apple platform. What was Apple thinking? The new chime is a "gurgling" low sounding noise like someone clearing their throat. Seriously Apple, this is how you spend your time "improving" your product?? I used Onyx to silence the new Apple "chime". I will miss the old chime like I miss Snow Leopard (10.6.8). Those were the days...
 
Last edited:
  • Like
Reactions: Agneev
No change to the chime sound on my mac pro 5,1 running Mojave,
and yes I have the 2020-007 update applied.
Screen Shot 2020-12-16 at 10.37.01 PM.png
 
I have backups, so I rebooted using the option key to boot off a CCC clone and restore to a backup, back to 2020-006. Well, all of my external drive backups disappeared. Only options I have are booting from the main SSD or a Mojave boot SD disk. Two CCC clone drives and two Time Machine backup drives are invisible. I booted from the SD drive and restored back to 2020-006 from a Time Machine backup. No problem, Time machine could see my backup drives as well as the CCC clone drives. Everything appears back to normal except the startup tone is unchanged and when rebooting with the option key, none of my boot devices appear. Just the main SSD and the SD Mojave boot disk. I went back into Onyx and reset everything back to defaults thinking I could have accidentally changed something, but that didn't work either. Tried NVRam reset and SMC resets, no change. Kinda frustrating as this system was operating perfectly before the 2020-007 install. Looks like my CCC clone backups are useless to me now since I can't boot from them on startup. Time Machine is working ok. Any suggestions would be greatly appreciated, thanks.
 
jbarley said:
Any chance this is a format issue?
HFS vs APFS
Just a thought.
Click to expand...
I don't think so. TM backups are HPFS and Carbon Copy Clone backups are APFS. I reformatted one of the CCC backups to APFS and rsestored, but my Mac still refuses to see anything on "Option" boot other than the main SSD drive (Samsung 860 EVO 500gb) and the SD Mojave boot disk. Looks like all USB-3 ports are not being recognized pre-boot, like they were shut off. After the system boots up, everything is normal. For now, I'll use the TM backups and put CCC on the shelf until this gets resolved. Bummer, I liked CCC. Great program.
 
Hombre53 said:
After some initial trepidation, I applied the 2020-007 Mojave Security Update to my late 2013 27" iMac. All seemed to go well, at least until the Mac rebooted and then gurgled a low demonic sounding "chime" in place of the "normal" chime I have become used to, at least since 2006 when I gave up on PC's and Microsoft and moved to the Apple platform. What was Apple thinking? The new chime is a "gurgling" low sounding noise like someone clearing their throat. Seriously Apple, this is how you spend your time "improving" your product?? I used Onyx to silence the new Apple "chime". I will miss the old chime like I miss Snow Leopard (10.6.8). Those were the days...
Click to expand...

I have exactly the same problem after applying the 2020-007 Mojave Security Update to the same model of iMac (llate 2013 27" iMac)! There is one more strange problem: For the first few minutes, the finder shows much less free space
(in my case, just about 40 GB free, instead of 215 GB). I wonder what more problems will shop up :)
 
For those of you that are having these same issues (late 2013 iMac 27") after installing the 2020-007 security update, I have an interim "fix". If I do a force power off and reboot with the option key pressed, all of my external devices are recognized and back to normal. Forcing power off is depressing the power button down and holding it down, basically forcing the Mac to power off without an orderly shutdown. an extreme measure to say the least, but it works. I make sure all apps are closed and the computer is "idle", at least to the best of my ability. I won't be doing this very often unless I have a need to boot from an external drive, etc. Another step backwards thanks to Apple and their crack macOS software division which has become a joke. Steve Jobs must be spinning in his grave, RIP.
 
For myself, restart after update I was greeted with the new distorted lower pitched chime followed by a black screen. Left the system for 5 minutes to return to ramped up fans and a burning hot system.

I was afraid this was yet another Mac to die on me this year, but clearing the SMC had it starting up as normal again. I've been predominately a Mac user since ~2001 and will say with confidence that the last 2 years have been by far the most problematic.

This new startup chime is only on my Macbook Pro, nothing changed on my Mac Pro - though it now has a different issue possibly unrelated to the update. Of the now four startup chimes I've enountered, this is my least favourite.
 
Hombre53 said:
...the Mac rebooted and then gurgled a low demonic sounding "chime" in place of the "normal" chime I have become used to, ...new chime is a "gurgling" low sounding noise like someone clearing their throat....
Click to expand...

Late joining, but yes, I got this dreadful lo-fi chime after installing an update last night and my boot up icons changed to Big Sur ones despite not installing the Beta. What is going on...
 
space_bo said:
Late joining, but yes, I got this dreadful lo-fi chime after installing an update last night and my boot up icons changed to Big Sur ones despite not installing the Beta. What is going on...
Click to expand...
The latest security updates for Mojave and Catalina updated the firmware on all Macs to be the same versions as in Big Sur, and that's where the startup chime and boot picker icons come from.
 
  • Like
Reactions: space_bo
chrfr said:
This is because there's no firmware update for the Mac Pro 5,1.
Click to expand...
Out of curiosity, do you happen to know if there was a firmware update for iMac Pro iMac14,2? (Yes, that's a terribly old machine, I realize. A link to a support page listing which did and didn't have those updates so I "Read The Effing Manual" myself is also fine.)

I'm wondering because a) my machine seems to be having occasional wonky sound issues (much like my experience with many Catalina machines) since the update, and b) I can't recall if I even had the sound on when I did this Security Update.

(I can say, though, that this is the first time I've noticed a Security Update listed twice in the Update list, much like @jbarley. I had such terrible sound/CoreAudiod issues with new Catalina machines that -- after quite literally tens of hours on the phone with a particularly skilled Tier II Apple Support rep over a series of weeks, and him checking in with the engineers more than once -- I ended up returning the new machine I'd bought. I'd hate to find out that some of the CoreAudiod issues that the Apple Support forums are littered with may have 'followed' me here due to a firmware update making it more like Big Sur.)
 
chrfr said:
The iMac Pro and iMac14,2 are different computers but I don't know about the 14,2. The iMac Pro definitely got an update.
Click to expand...

Hm, ok. Any idea where one would look this up? Mostly asking because people can get 'the update' without there being the firmware update to Big Sur (see: @jbarley and their Mac Pro).
 
Hombre53 said:
. . . Looks like my CCC clone backups are useless to me now since I can't boot from them on startup. . . .
Click to expand...

CCC Trashed 2 4TB WD Black drives as it was cloning in my MacPro. All the files are present on the new drive, but are corrupt and the source drive is totally corrupt and won't mount or allow any kind of datamining. I have been saying I don't like the new "Fancified" version in forums for a while. Until I got bit, twice. I wrote the Dev and when I called CCC, that has been for decades "The Only App I Could Ever Depend On!", the "New Fancified", version he got all kinds of hurt. I got an eMail from PayPal that I had been sent money, a refund for CCC, and in a reply he called me too "unreasonable" to work with to find and fix the problem. All I said was to call CCC, "Fancified".

Right he's hurt, I lost thousands of hours of work and dollars. Now who's hurtin'?!

Well there goes a good app. But I have found several others that work as it use to. </rant>
 
Circling back to my question to @chrfr, as I finally ended up rebooting my iMac14,2 (late 2013 27").

I can pretty much be assured that my machine has received the firmware update mirroring Big Sur, because my chime sound is grating now. Wow. I can see why someone described it as 'lo-fi'.

I'm probably going to have to eventually get a Mac with an ARM processor, but boy yikes, am I not looking forward to it. So disappointing that Macs have essentially entirely gone downhill (at least in terms of individual user control, and span of programs it uses) since Catalina. OSX was such an innovation, and now I just feel like we're paying 2-3x more for a machine that's losing all the benefits OSX conferred in terms of user self-management.
 
  • Like
Reactions: Mr Todhunter
Curiosity: Did anyone who installed the update notice weird audio / video issues since they've done it?

Wondering because I spent most of late 2020 checking out new Macs and returning them because of MAJOR audio and graphics issues in Catalina and above (as confirmed by a Tier II rep at Apple, and then the engineers).

Since then I've been clinging to my old 2013 Mac running Mojave, but the security update migrated audio and video problems to my older Mac:
  • repeated volume shifts over a broadcast whose volume is steady on another device (and the 'sound' is not displaying as moving back and forth with the volume changes, it's just that it gets quieter, ramps up to louder, and then drops again -- lather, rinse, repeat)
  • broadcast screens flickering white (just the broadcast, not the entire screen) when they're not on another device
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back