Getting multiple Disc not properly ejected notifcations since 12.5 upgrade

[BuddyRich]

I have a WD Blue M2 SATA SSD in the Satechi Mac Mini Hub (https://www.amazon.com/Satechi-Type-C-Stand-Enclosure-USB/dp/B097CJMY9M) under my Mac Mini M1.

Since upgrading to 12.5 yesterday, I have been getting multiple "Disc Not Ejected Properly" notifications anytime my Mini goes to sleep (not even sleep because in my power settings I have it set to not sleep, basically anytime I idle the computer for awhile (after my display dims). The drive (or dock) autoremounts itself since it connected but for whatever reason MacOS is turning the disc or dock off for some reason multiple times overnight.

Prior to 12.5 it would only give me the "Disc Not Ejected Properly" if I lost power never like this.

In my power settings (pmset):

System-wide power settings:

Currently in use:

standby 1
Sleep On Power Button 1
womp 0
autorestart 1
hibernatefile /var/vm/sleepimage
proximitywake 1
powernap 0
gpuswitch 2
networkoversleep 0
disksleep 0
standbydelayhigh 86400
sleep 0 (sleep prevented by sharingd)
hibernatemode 3
ttyskeepawake 1
displaysleep 10
tcpkeepalive 1
highstandbythreshold 50
standbydelaylow 86400

I know plenty of people have had this issue in the past, but wondering if anyone has noticed it more frequently since 12.5?

 

[HobeSoundDarryl]

12.5 gave me a temporary dose of hope as it seemed to buy me the LONGEST time a trusty HDD RAID box remained attached since I have owned Studio Ultra (and thus used Monterey): upwards of 5 hours!!! Previously, it seemed about 3 hours was MAX and as little as only minutes could trigger ejections too.

This drive using the exact same cable has maintained a steady connection to Intel Macs for a few years and has shown that it can do so again when I tested it on Intel Macs to see if perhaps it had suddenly gone bad with these "unexpected ejections." Basically, it is fine hooked to Intel Macs using the same cable. It will simply NOT stay connected to a Monterey and/or Silicon "latest & greatest" Mac.

I have tried every option referenced all over the internet and yes there are seemingly countless threads with select hardware having this issue (while other hardware seems to work fine). As I've mentioned in other threads, as is right now, the U in USB does not mean what it is supposed to mean with Monterey and/or Silicon-based Macs. "Just works" does not 'universally' apply here. The ports on Silicon Macs don't even run at their full speed.

There does seem to be SOME relationship with power savings/sleep but not all of it is there, as I've even suffered unexpected ejections while transferring files to/from it (so obviously not asleep by any definition of the word).

My best guess: there are SEVERAL bugs in Monterey port handling, at least one of which is related to power management/sleep. I "feel" like ALL of the ports can momentarily crash or reset and- if true- that may explain why they can lose their connection with even currently-transferring drives.

I notice what seems like regular hangs- several times each day- with the ethernet port too. These may last up to a minute or three and are definitely not modem or router, as trying to access the same on Intel Macs shows neither is down, as does quickly switching to wifi on the Silicon Mac. The port connection is temporarily "clogged..." presumably while re-booting, waking or similar.

I've concluded that users will not solve these issues in full with cables/settings tweaks... that Apple needs to address whatever the cause(s) in an update to macOS (while hoping it is not some hardware flaw with Silicon itself). For me, this is month 5 of NOT being able to reliably use a trusty piece of important equipment with my new Mac... but online information all over the web- including Apple's own support forums- implies this has been a problem dating back into Big Sur too.

Again, some hardware is apparently perfectly fine and other stuff won't work. There's no obvious way to tell which is which other than simply trying different tech and getting lucky. There seems to be at least a few dozen potential remedies recommended in various posts all over the web... from alt cables to dock middlemen tech to tweaking something(s) with terminal, etc... but having thoroughly tried everything, I have deduced it back to bugs in macOS Monterey and/or issues with Silicon ports. I miss "just works."

 

[BuddyRich]

12.5 gave me a temporary dose of hope as it seemed to buy me the LONGEST time a trusty HDD RAID box remained attached since I have owned Studio Ultra (and thus used Monterey): upwards of 5 hours!!! Previously, it seemed about 3 hours was MAX and as little as only minutes could trigger ejections too.

This drive using the exact same cable has maintained a steady connection to Intel Macs for a few years and has shown that it can do so again when I tested it on Intel Macs to see if perhaps it had suddenly gone bad with these "unexpected ejections." Basically, it is fine hooked to Intel Macs using the same cable. It will simply NOT stay connected to a Monterey and/or Silicon "latest & greatest" Mac.

I have tried every option referenced all over the internet and yes there are seemingly countless threads with select hardware having this issue (while other hardware seems to work fine). As I've mentioned in other threads, as is right now, the U in USB does not mean what it is supposed to mean with Monterey and/or Silicon-based Macs. "Just works" does not 'universally' apply here. The ports on Silicon Macs don't even run at their full speed.

There does seem to be SOME relationship with power savings/sleep but not all of it is there, as I've even suffered unexpected ejections while transferring files to/from it (so obviously not asleep by any definition of the word).

My best guess: there are SEVERAL bugs in Monterey port handling, at least one of which is related to power management/sleep. I "feel" like ALL of the ports can momentarily crash or reset and- if true- that may explain why they can lose their connection with even currently-transferring drives.

I notice what seems like regular hangs- several times each day- with the ethernet port too. These may last up to a minute or three and are definitely not modem or router, as trying to access the same on Intel Macs shows neither is down, as does quickly switching to wifi on the Silicon Mac. The port connection is temporarily "clogged..." presumably while re-booting, waking or similar.

I've concluded that users will not solve these issues in full with cables/settings tweaks... that Apple needs to address whatever the cause(s) in an update to macOS (while hoping it is not some hardware flaw with Silicon itself). For me, this is month 5 of NOT being able to reliably use a trusty piece of important equipment with my new Mac... but online information all over the web- including Apple's own support forums- implies this has been a problem dating back into Big Sur too.

Again, some hardware is apparently perfectly fine and other stuff won't work. There's no obvious way to tell which is which other than simply trying different tech and getting lucky. There seems to be at least a few dozen potential remedies recommended in various posts all over the web... from alt cables to dock middlemen tech to tweaking something(s) with terminal, etc... but having thoroughly tried everything, I have deduced it back to bugs in macOS Monterey and/or issues with Silicon ports. I miss "just works."

FWIW, it was a hardware issue with Satechi dock... Got a new revision of it under warranty and it seems to have fixed the issue (so far).

As far as I can tell, its uses a different SATA chipset for the dock... first one was JMicron that was giving errors, the revision uses Via Labs. Might still have been an OS error, as I didn't have the errors with older OSes... Apple could have changed something that some enclosures have an issue with. The Ports and SD Card reader are still OK, just not the M2 SATA port.

 

[svenmany]

I was doing very well on 12.5. 12.5.1 has started causing disconnects again. This applies to disks connected through a CalDigit TS3 as well as an SSD connected directly to the Mac.

I've also noticed that my keyboard which is connected to the hub has also started to lose connectivity on waking from sleep; I have to disconnect and reconnect to get it working. This used to be a problem which only started up again since 12.5.1.

When I last researched the issue, I noticed the problem occurs on waking from sleep, not going to sleep. The USB system is just a bit slow waking up, and other components fail to find the required devices in time. It was pretty obvious in the logs that the USB initialization was happening just after the disk errors occurred.

And, I do like Buddy Rich.