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.
Apple Releases macOS 13.2.1 With Bug Fixes and Security Updates
- Thread starter MacRumors
- Start date
- Sort by reaction score
My HyperDrive USB-C Hub is still working fine, along with the 2 Time Machine backup drives and small USB thumb drive connected to it... If there was more of a widespread issue, we'd be hearing about it for sure.
It took four attempts of a recovery mode install overnight and a couple of reboots this morning to finally get my iMac to come back to life. Maybe this install is just buggy on Intel Macs?
Dear Apple, the "dropping file sharing" issue is a major bug for businesses, please fix ASAP!
I updated my 16-inch M2 Max to 13.2.1 last night, and a few minutes ago, after working on it all day, I restarted the computer. After the computer had restarted and everything was back to normal (the MagSafe cable was connected to the machine the whole time) the screen randomly dimmed as if I'd unplugged it from power and I heard a faint charging chime sound as if I had just plugged in my charger. The light on the MagSafe connector remained green and the computer indicated it was still plugged in. I thought this was weird but didn't notice it more than this single time. Did you have a similar experience?
Yes. It was an error. They finally relented and changed it back to 16.3 on the webpage https://support.apple.com/en-us/HT213638 and added the build numbers.
Unfortunately the build numbers are now incorrect.
They are 16614.4.6.11.6 for Big Sur and 17614.4.6.11.6 for Monterey but on the webpage it says "167614.4.6.11.6 on macOS Big Sur and 177614.4.6.11.6 on macOS Monterey".
Apple have been informed about these new errors.
I find it ironic that it also says on the webpage
"Description: A type confusion issue was addressed with improved checks."
Apple ................. Your typing is confusing everybody right now!
I am so glad I'm not the only one experiencing this problem on Ventura. It's driving me NUTS!
Also, even if I have my settings set to prevent macOS from sleeping at all, it STILL sleeps!
Yeah, it’s maddening ! I experienced it since Monterey when i switched to M1 from my intel iMac.
If i keep my external HDDs connected (usb-c G-drive 6TB) when Mac resumes from sleep, the hdds wakes up and enter into a sleep-wake-sleep cycle , spinning up and down every 10 seconds if they are idle. This thing is killing them …
A reboot solves the problem but it happens again next time when Mac sleeps.
So basically you have to reboot it on every wake from sleep or shut everything down entirely and perform a cold start every time.
I have disabled the option to put external hdds to sleep whenever possible … no effect !
I am afraid it has something to do with M1 architecture and the thunderbolt / usb controller and it may be hardware related.
On my intel iMac running Monterey, the same HDDs did not behave this way. As soon as i switched to M1 i noticed this crazy thing …
I've been having this External Disk issue, too, and from what I can see I'm convinced it's an Apple Silicon "feature" to help save on power consumption and battery. And the reason it happens to AS Mac minis is because the architecture is just baked into macOS.
What leads me to believe this is from having the M1 MBP for about 1½ years, using it connected to a Dock or a Hub. I've tried at least 4-5 different Docks & Hubs and have found all to behave roughly the same- Drives disconnecting, being unsure if you'll have a corrupt Time Machine backup, even using the Ethernet Port on the Dock and seeing the Network Connection Time Out over time. It's like Apple is doing TOO much to save on Power.
And I have an additional MagSafe 3 cable so I just plugged that in and within a minute it did the exact same thing. Light on the connector turned off momentarily and computer showed as running on battery. Then MagSafe connector turned orange and I heard the computer make a chime sound like I'd just connected it to power. Must be the firmware updating.
It’s interesting in my case because during a cold boot or reboot (restart) it seems that when MacOS boots “from scratch” the issue is gone … but when it resumes from sleep it goes nuts.
Like if the OS “properly” boots it recognizes the devices as HDDs and keep them spinning but after a resume from sleep it constantly trying to put them to sleep and wake them back again.
Yeah, it might be somehow hardware related. It’s strange why they didn’t modify the underlying firmware to fix this thing … or maybe it’s a hardware design fault.
Like if the OS “properly” boots it recognizes the devices as HDDs and keep them spinning but after a resume from sleep it constantly trying to put them to sleep and wake them back again.
Yeah, it might be somehow hardware related. It’s strange why they didn’t modify the underlying firmware to fix this thing … or maybe it’s a hardware design fault.
Mine was in the mode where it drains down to 80%, got to 78% after the update. And within a few minutes of logging back in after the update, the screen dimmed, connector flashed and played the charge dime. And then it started charging back to 100%. I double checked the cables and unplugged it to check the head+port until I plugged it back in.
Ah, that might've been it! I was quite concerned after that, and I couldn't find anything in the Console app either. Would've been nice if macOS displayed a message before and/or after the firmware update... Or do they just assume people will ignore it?
Thanks for the find!
Yeah this firmware update must be the answer to this. Sounds like the exact same thing happened in both our cases. Glad I had that second MagSafe 3 cable to test the theory and the AppleInsider article affirms it.
So either Apple is grossly underestimating the number of users still / out of necessity running Monterey and don't think it's worth the trouble to issue a patch (sorry...'update'), or Monterey isn't affected by this issue.
Either way, it's an interesting revelation.
Either way, it's an interesting revelation.
Last edited:
So here is what I did to make it work. I connected a 512GB spare SSD with a USB C to SATA cable. Formatted it for APFS. It mounted on the desktop as expected. I added it to the File Sharing panel in System Settings and rebooted the M2 Mac Pro Mini. It came up and then I went to my MacBook Pro and immediately connected to it and transfer a 10GB file back and forth. It worked as expected.
So -- I removed my 8TB SSD RAID from File Sharing. I moved the Contents of my 8TB SSD RAID0 (About 4TB worth of data) to a spinning RAID array. I then Deleted the RAID set using Disk Utility. I rebooted the M2 Pro Mac mini and then fired up Disk Utility. I recreated the 8TB SSD RAID0 and named it "SOLID_RAID." I shared it in File Sharing and then it immediately mounted on the MacBook Pro. I was able to move a 10GB file back and forth between the computers with no issue.
So... It would appear that there is an issue with existing drives or RAID arrays that prevent them from being properly shared over a SMB connection.
Let me know if you have the ability to duplicate this.
Good luck.
UPDATE 2/15/2023 4:09PM EST - It worked for a while, now it is back to the same failure mode. Connected on the client side and Finder times out "Loading..."
Last edited: