Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I've got an Areca 8050T2 (Thunderbolt 2) 8-bay hardware RAID connected to an M1 Mini via TB2/TB3 adapter. No connection issues of any kind. Been staying current, but this update doesn't show for me yet.

You running SoftRAID? Could be sw vs. hw setups...
No SoftRaid, formatted by Disk Utlity as APFS years ago. It's been perfectly stable for several years attached to my now dying Intel iMac. It will not stay attached to my new Studio for longer than a few hours, even if I prevent both from sleeping. Had a couple incidents of it unexpectedly ejecting while transferring files from it to the Studio, so both definitely awake during a file transfer. But sleep does seem to be a more dependable trigger.

I've tried both USB A jacks and the Thunderbolt USB-C jacks too. Drive end is USB-B 3.1.

I'm very confident it is not the drive or cable because I've been through 3 cables already and if I unhook it from Studio and hook it back to Intel iMac or Intel MBp NEITHER running Monterey, stable connection resumes- including through Mac sleep. I'd simply like to get this big RAID storage working with this new Studio... and wish I didn't have to buy a new enclosure to do it... but it's seeming like that more and more now.

And yes, I understand the risk of RAID-0 but this is fully backed up and mostly a video editing scratch disk for gigantic pro-res files. The big loss about consistent connection is that it also holds all of the home movies, movie collection, etc to feed AppleTVs around the home.
 
No SoftRaid, formatted by Disk Utlity as APFS years ago. It's been perfectly stable for several years attached to my now dying Intel iMac. It will not stay attached to my new Studio for longer than a few hours, even if I prevent both from sleeping. Had a couple incidents of it unexpectedly ejecting while transferring files from it to the Studio, so both definitely awake during a file transfer. But sleep does seem to be a more dependable trigger.

I've tried both USB A jacks and the Thunderbolt USB-C jacks too. Drive end is USB-B 3.1.

I'm very confident it is not the drive or cable because I've been through 3 cables already and if I unhook it from Studio and hook it back to Intel iMac or Intel MBp NEITHER running Monterey, stable connection resumes- including through Mac sleep. I'd simply like to get this big RAID storage working with this new Studio... and wish I didn't have to buy a new enclosure to do it... but it's seeming like that more and more now.

And yes, I understand the risk of RAID-0 but this is fully backed up and mostly a video editing scratch disk for gigantic pro-res files. The big loss about consistent connection is that it also holds all of the home movies, movie collection, etc to feed AppleTVs around the home.
Interesting... so you're running APFS on that box, are they SSDs? I'm formatted HFS+ (Journaled) with a stack of spinners. I don't ever let the machine sleep (this Mini replaces a 2013 trashcan), only display sleep. Restarts for deep-cleaning or software updates only.
 
Available and installed on 2019 iMac19,1 as 12.3.1 (21E258). No real issues with install, but same exact thing with AirPrint printers somehow or for some reason being un-installed during the update and needing to be setup again. It has been this way for many of the latest updates since 12.2 release. Easy to resolve, just probably shouldn't be happening with each and every point update.

Not available on MBP16,1 at this time.
 
  • Wow
Reactions: Babygotfont
Interesting... so you're running APFS on that box, are they SSDs? I'm formatted HFS+ (Journaled) with a stack of spinners. I don't ever let the machine sleep (this Mini replaces a 2013 trashcan), only display sleep. Restarts for deep-cleaning or software updates only.

Yes APFS. No they are HDDs. It was originally HFS+ but I reformatted it several years ago. Worked great right up to when I switched the connection to this Studio. File transfers to/from it are mostly fine now too but I just can't depend on it to stay connected. At any given time, it disconnects and I get the notification like I've pulled the plug without first ejecting. Every First Aid run comes back as fine.

I've got fairly reliable confirmation that there IS a problem with Monterey and RAID externals, though your post and an earlier one in this thread seems to imply that it's only SOME RAID externals... which is why any "noise" about it seems relatively low. Searches for Monterey or macOS and "unexpectedly ejects" will reveal many links... including many posts on Apple's support forums. So I know this is not a single issue with a single box and single user.

What's aggravating is going from "just works" to not in a move from Intel Mac running older macOS version to "latest-greatest" Mac running latest macOS.
 
Last edited:
  • Like
Reactions: amartinez1660
Yes APFS. It was originally HFS+ but I reformatted it several years ago. Worked great right up to when I switched the connection to this Studio. File transfers to/from it are mostly fine now too but I just can't depend on it to stay connected. At any given time, it disconnects and I get the notification like I've pulled the plug without first ejecting.
Are they spinners or SSDs? I've had horrific performance with spinning drives formatted APFS, so much so that I will only use APFS on SSDs.

EDIT - Which box are you using? Did you build the RAID with DU, or just format a hardware volume?
 
I wish all bugs would manifest only when Beats headphones are nearby.

I wonder why it's always kids or adults with those beat headphones why they always play rap/hiphop music?

Just because a music style is popular doesn't mean everyone wants to hear the stuff.

Me, play something like classic punk rock like the Ramones or classic heavy metal like Iron Maiden or Judas Priest, i personally grew up on rock and metal.
 
Apparently it removes Rosetta 2 again, so anyone running apps that require it may want to hold off. I see in the Macadmins Slack channel someone saying the following:

"After an update & first post-update/install restart, let it sit at the desktop for a couple of minutes & restart again, Rosetta2 should automagically reappear."
"Rosetta2 isn't part of the standard Secure System Container snapshot, so when you update/upgrade the existing version doesn't match up & gets dropped, but the post-install routines go "Oh hey, they had Rosetta, I'd better grab the new one off the servers & build a new SSC snapshot"."
 
  • Like
Reactions: polee
MBP 14 M1 Max - nothing. I was hoping for the update to fix.... well nothing....

Everything is actually working fine to be honest....
 
Normally updates are lagging 2 hours behind in Europe. This is normal for macOS updates, not iOS/iPadOS/watchOS/tvOS/audioOS. I would suspect we'll see it within the next 30 minutes.
 
Are they spinners or SSDs? I've had horrific performance with spinning drives formatted APFS, so much so that I will only use APFS on SSDs.

EDIT - Which box are you using? Did you build the RAID with DU, or just format a hardware volume?

Spinners. Been formatted as APFS for at least 2, maybe 3 years with no issues hooked to the former main (Intel iMac) machine.

Having worked through countless possibilities, the only one left that I think I can try is to reformat with Monterey. However, I've been reluctant to try that because I don't want to potentially lose the drives if it randomly ejects during the formatting process. I don't trust it to stay connected long enough to reformat.

Box is an OWC dual bay, Hardware-selected RAID, set to RAID 0. I think it was a process of selecting RAID-0 on the box, install 2 drives and then use Disk Utlity to format it. Been super stable for a couple of years with none of this unexpected eject stuff. Now I would not bet much on a connection of even 3-4 hours... unless I take it and same cable back to an Intel Mac and then it is as stable as it has been.
 
Last edited:
Look...everyone....

Software updates get propagated to servers across the world, slowly. It usually takes many hours for everyone in the world to get the update to appear on their particular machine. This is the same as every software update has always been since time began. It's just how they work.

We don't need updates on who's seen it and who hasn't, and incorrect predictions regarding who is and who isn't going to get it, according to country and machine type :)

You'll all get it in time. Maybe in 2 minutes, maybe 2 hours, maybe 10 hours. Patience, grasshopper.
 
Still no update here in Italy MacBook Pro 14...
Look...everyone....

Software updates get propagated to servers across the world, slowly. It usually takes many hours for everyone in the world to get the update to appear on their particular machine. This is the same as every software update has always been since time began. It's just how they work.

We don't need updates on who's seen it and who hasn't, and incorrect predictions regarding who is and who isn't going to get it, according to country and machine type :)

You'll all get it in time. Maybe in 2 minutes, maybe 2 hours, maybe 10 hours. Patience, grasshopper.

I do not think is about fear of missing out, it's more about letting people know when and where it is available....wich is the purpose of this thread.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.