Oh! Pity. But good info for those of us considering doing that.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
In Disk Utility suddenly are 7 Disk Images with strange names. They start with Creedence or Revival and all end with _Cryptex.
- Thread starter Adora
- Start date
- Sort by reaction score
I reinstalled now too without reformatting and before reading here. All seven are still there. At least some problems with Finder/Desktop/iCloud seem to be fixed now.
I just updated my M2 Pro MacBook Pro that was lying around for a while to the same macOS Beta and there is nothing:
And this is my M3 iMac after the reinstall:
I should say that I am a bit OCD most of the time. However, this "bug" doesn't affect the machine at all except this weird annoying "appearance" under Disk Utility. I've then decided to not bother at all...
I've tried a couple of thins mentioned in the Apple forum thread but it didn't disappeared. Next would be a full reinstall but it's not worth it, IMHO and in my particular situation (only one little 4 MB Cryptex volume).
***If you ever decide to reinstall, keep us informed
I know this "OCD" thing very good. There were times I reinstalled Windows and later macOS daily because I installed something that I didn't need and didn't want to have any trace of it left on my Computer. 🙈
Yes, thats the strange thing. I still wonder if it has to do with the external boot drive I use on my iMac. But it wasn't there at the beginning.
When you installed the first version of Sequoia you mean? I didn’t noticed but I am not always using Disk Utility so I couldn’t tell if the volume was present with 15.0.
I saw, in my web searches about it, an occurrence with the first betas of Sequoia:
The seven ones appeared about 2-3 weeks ago all at once and I was using macOS 15 since the first day of Developer Beta 1. Until then I never saw any of this and was in Disk Utility almost daily.
I just installed 15.2 Beta 4 shortly before also on an external drive because cloning didn't work.
Another one from 8 days ago:
apple.stackexchange.com
Definitely some bug from Apple!
Why does my Mac show a disk image named Creedence11M6270.SECUREPKITRUSTSTOREASSETS_SECUREPKITRUSTSTORE_Cryptex after updating the OS?
I noticed after updating Catalina to Sequoia, Disk Utility on my Mac shows a disk image named Creedence11M6270.SECUREPKITRUSTSTOREASSETS_SECUREPKITRUSTSTORE_Cryptex: It does not take up much space...
Definitely some bug from Apple!
Another one from 8 days ago:
Why does my Mac show a disk image named Creedence11M6270.SECUREPKITRUSTSTOREASSETS_SECUREPKITRUSTSTORE_Cryptex after updating the OS?
I noticed after updating Catalina to Sequoia, Disk Utility on my Mac shows a disk image named Creedence11M6270.SECUREPKITRUSTSTOREASSETS_SECUREPKITRUSTSTORE_Cryptex: It does not take up much space...
Definitely some bug from Apple!
I just used the support via iMessage and sent some screenshots. Someone from the Senior Department will call me later today and help to get rid of those. Seems to be not that easy.
Glad you found that, and my very incomplete non-answer.
Ah…Glad you found that, and my very incomplete non-answer.
« No, it is not just Intel. See forums.macrumors.com/threads/… where the OP is using an M3 iMac.
– Gilby
CommentedNov 23 at 5:44 »
Agreed. So far there is nothing consistent. My summary:
1) Intel or Apple silicon.
2) Just the Creedence cryptex for me, for others up to 7 or more!
3) Some see the cryptex(es) only in Disk Utility, others see them on the Desktop too.
4) For those that see it in Disk Utility, the Creedence cryptex is mounted at something like
/System/Library/AssetsV2/com_apple_MobileAsset_PKITrustStore/purpose_auto/6dd...409a.asset. But not for those that don't see our anomaly in Disk Utility.5) Still present after starting in Safe Mode (for me) - that seems to rule out interaction with kexts or system/network extensions.
Hopefully member @Adora will report back after Apple support call… or maybe they’ll fix it in the next release?
I missed the call because I had to sleep. I confused the days because it was already after midnight.
They tried it twice. Maybe they do it again today.I haven't tried save mode yet. Will do that now. I could also boot from the internal drive. Everything is still on it, but that could maybe confuse my iCloud.
But the external drive was handled as another device I think, so I could just try it and also, what happens if I remove the external drive. But that's where they are and I don't think I'll even see any on the internal one.
Trying safe mode now...
So, I'd had enough and just did it the rough way:
Login to root account
Disk Utility
Show in Finder (right click on the cryptex-drive)
Show enclosing folder (right click on the path bar at the bottom that maybe has to be unhidden in the view menu)
Erase Disk to FAT MS DOS (right click in Finder on the cryptex-drive in that folder)
And always deleted everything that was in those folders, when the drives were gone after formatting.
Did this to all seven, they appeared on the desktop, I ejected them, restarted and they are gone now. Everything is still working. Maybe you don't even need the root account for doing this.
Login to root account
Disk Utility
Show in Finder (right click on the cryptex-drive)
Show enclosing folder (right click on the path bar at the bottom that maybe has to be unhidden in the view menu)
Erase Disk to FAT MS DOS (right click in Finder on the cryptex-drive in that folder)
And always deleted everything that was in those folders, when the drives were gone after formatting.
Did this to all seven, they appeared on the desktop, I ejected them, restarted and they are gone now. Everything is still working. Maybe you don't even need the root account for doing this.
I will be very interested in what you find out. My experience with Apple support since I bought this iMac in 2019 has been very poor. And it's not just this iMac, it's other items too. When I bought my Series 9 Watch and was having difficulty with the Blood Oxygen app, the Apple Tech finally said something to the effect of, "Look we didn't designed this stuff for guys as old as you are and as in poor health."
It didn't came to a phone call because I also slept today at the same time. Don't even know yet if they called again.
But since I just deleted everything in the root account they are gone and nothing bad happened, so I think they weren't needed for anything and just some kind of leftover from any operation that was done and maybe got interrupted before it had been finished.
Ok, not sure I follow you correctly… but now, don’t you end up with seven unmounted MS-DOS partitions showing in Disk Utility going this way?
Did that on my one Creedence cryptex. It has now gone from Disk Utility. I have not yet done a restart.
But the
trustd process running under user _trustd crashed when I did the erase. A snippet from the crash report:Exception Type: EXC_BAD_ACCESS (SIGBUS)Exception Codes: KERN_MEMORY_ERROR at 0x00000001034064dcException Codes: 0x000000000000000a, 0x00000001034064dcTermination Reason: Namespace SIGNAL, Code 10 Bus error: 10Terminating Process: exc handler [846]That is potentially worrying, but may tie in with intermittently having similar crashes by
helpd.Interesting.
I've done a nuke and pave aka reformat the internal, install the OS and either install all the software from scratch (on 15.0) or restore via Time Machine on every version--release, public beta or developer beta--since 15.0, and the Creedence drive has been there every time, except after the reformat and before the install of the OS. That doesn't particularly bug me since the Creedence drive is negligible in size and doesn't show on the desktop nor in the Finder. But what does bother me is this:
Sequoia tends to crash and when it does something on the internal gets corrupted. I ran for three days with developer version 15.2 beta four with no issues until yesterday afternoon when Music crashed attempting to connect to a HomePod stereo pair. After rebooting I got this:
Checking snapshot 23 of 24 (com.apple.TimeMachine.2024-11-30-064323.local, transaction ID 52524761)
warning: inode (id 7013415): Resource Fork xattr is missing or empty for compressed file
on every snapshot. And then this:
The volume /dev/rdisk3s4 with UUID 2A63C055-D590-4682-9ED6-90E9D4652899 was found to be corrupt and needs to be repaired.
I had run Disk Utility a couple of hours before Music crashed, and I didn't get any of these errors. So a simple crash of Music did this? Apparently.
Sequoia is just not ready for primetime--or at least should not be run on 2019 Intel 5K iMacs. I'm going to wait until the release version of 15.2 is released, and if doesn't fix all the problems, then I'm going back to Sonoma and it will be my last macOS on this machine, which is only five years old.
Thanks for the details. In my case, MacMini Intel 2018, test driving it is not so bad but notice some glitches and annoying things here and there. Like you, waiting for official 15.2 but Ventura is still installed on the internal SSD along BootCamp Windows 11 so, I have other options.
BTW, Ventura is rock solid and I am more and more thinking that Sequoia is an afterthought for us, Intel Mac owners.
I am glad you are having better luck that I am.
I never thought Sonoma was all that stable. If you are having good results with Ventura, I might do that. Can you update to the latest version of Safari with Ventura?
I think the only reason Apple allows Sequoia to run on certain Intel Macs is it did not want to orphan a five year-old computer. The whole thing really POs me. I got nine years out of my last iMac. This won't happen with this 2019.
Ok, had to reboot in Ventura to look at the version as Safari was not shown in Ventura partition when booted in Sequoia. Same goes when booted in Ventura, no trace of Safari in /Applications looking at the Sequoia partition!!! Weird!
Anyway, Safari is 18.1.1 in Ventura so, yes, latest version supported.