I'm seeing rumblings that I'm not the only one here...mid-2015 MBP and upgraded to Monterey and immediately after upgrade my external USB drive (Time Machine) and SD card (in the lost) periodically unmount themselves, give a warning and then randomly remount. This makes these external storages unusable- Time Machine won't even engage in the updated, current state.
MacBook Pro 15″, macOS 12.0
I’ve just had a success with a very simple fix. My external drive got to the point that it was disconnecting every few seconds.
The problem: It was dirt in the connectors.
Solution:
That was two days ago, and the external disc has not disconnected since then.
My dad also has a flush mounted adapter with a microSD card in his MacBook Air. Similar problem. Not sure on age, but he’s only had air a few years, so maybe a 2018 model. Certainly looks like it’s the OS
I need to amend this post. While the USB-C charging cable from Apple will allow the G0Drive to mount and function, its data transfer rates are extremely limited, ~USB 2.0, I believe. I'm going to return the cable and swap it out for an Apple USB-C cable designed for higher speed data transmission, as see how it goes.
Will report back if this proves a better option.
Perryb wrote: "Apple, please fix this..."
Although Apple administers these communities, that doesn't include reading each of thousands of daily posts for possible feedback. However, Apple will "read all feedback carefully" here:
õ¿õ¬
I have the same issue. Mac Pro late 2013 model. I upgraded to Monterey and now two of my USB external hard drives keep unmounting when the computer goes to sleep. Every single day I have to unplug them and plug them back in. Same computer, same drives. It's Monterey, not the drives.
Iv'e also noticed that sometimes the computer can't wake up the monitor, which is an Apple Thunderbolt display. The monitor sleeps and won't wake up. Unplugging it and plugging back in will wake the computer. It's Monterey. It seems that all the USB ports and thunderbolt ports are flakey after the upgrade.
Please Apple, you need to do much better. I feel like I'm using older version of Windows, needing to know all kinds of secret key presses and reboot techniques and VRAM and things I shouldn't need to know or do. This is not quality and it's extremely annoying.
I have a 2020 MBP 13" and since Monterey - my USB-C hubs and connection are disconnecting.
Tried 2 of the same i-Tec USB-hubs that worked fine before, tried an Anker hub, and dell hub. I mainly need a USC-C ethernet connection. Only the Dell works a bit, it at least does not disconnect the ethernet and the usb-c external drive but it still disrupts them. I cannot do a proper video call while on ethernet. The other hubs keep disconnecting and keep giving the "usb-c device was not disconnected safely)".
Any ideas how to solve this?
2017 iMac Pro, 32GB, 1T SSD, macOS 12.2 (21D49).
Two Sabrent 2T SSDs configured as RAID 0, and are randomly “not mounted” when my backup tries to run, yet are mounted later.
An external WD Red in an enclosure randomly posts “deject before disconnecting” messages, yet is always connected and mounted when I check.
All drives directly connected.
This didn’t happen on Big Sur or before (“up”graded a few weeks ago).
Sounds like Monterey is shutting things down that it shouldn’t.
All the other answers to this issue notwithstanding, I have to believe this is a Monterey issue. It began only after upgrading to Monterey with no other changes to cables, wi-fi or any other connections, and no changes to any settings, whether for Time Machine or other external devices. TM backups continue to be successfully made. But the Disk Not Eject Properly notification show up every time I wake up my iMac. Since nothing changed except the macOS, I can only conclude that it is Monterey that is the problem, and Apple should take note.
That was me! Thanks for confirming that different cables worked. My working hypothesis is as follows:
Insight: I unintentionally did exactly the above but with a brand-new, non-apple laptop and the manufacturer replaced it because they had no way of knowing if it was an issue with an accessory or their device.
True enough. However, an SD-Card slot is a device that will sit on the USB bus, so I suspect these are things that have unintentionally gotten caught in the cross fire of the changes, that apple implemented in Monterey, to tackle the issue I raise above.
Whitey012001 wrote:
that may be the case for external hard drivers, but this also happens to older MacBooks with sd cards mounted to the sd slot. Think there are 2 issues on this thread
This has been discussed in the private level 6+ forum (“the Lounge” if you see other references to it), and it seems to be a problem with some SD card slots. I have an external OWC 14 port hub with an SD slot, and I just confirmed that it worked with Monterey, so it is only some slots.
"This has been discussed in the private level 6+ forum (“the Lounge” if you see other references to it), and it seems to be a problem with some SD card slots. I have an external OWC 14 port hub with an SD slot, and I just confirmed that it worked with Monterey, so it is only some slots."
Those in the private club should read this thread and understand we are talking about (and kindly refer to the first post in the thread) the internal sd card reader.
The reason why *these* slots are important are clearly too obvious to mention - personally I couldn't give a monkey's if some external connected hub with an SD slot lost its connection on occasion, but again refer to the thread for information on why the *internal* slot autonomously-force-ejecting an sd card might be an issue. To very many.
Kindly refrain from corrupting this thread further by bringing external readers/hubs into the mix. Thanks
Good questions. I’ll answer what I can. Yes, I meant volumes, not drives in one case; the other is actually a RAID drive configured as 2 separate drives.
My M1 has an OWC 14 port powered hub (which actually powers the MBP through USB-C/Thunderbolt 3). I have 1 drive (2 volumes) plugged directly into the other Thunderbolt 3 port on the MBP. the 2nd & 3rd drives (the split RAID) plugged into a USB-C port on the hub. The last drive is a hardware mirrored RAID drive pair plugged into a USB-A port (a very old WD MyBook, probably 10 years old or more) as one of the TM drives; the other TM drive is one drive of the split RAID. The OWC also has SD and micro-SD slots. I’ve used these slots with no problem, either. I use 2 volumes for alternating CCC backups (yes, I’m really big on backing up).
I don’t doubt there are configurations that have a problem and tracking it down should be Apple’s responsibility, but I’m happy to work on narrowing down the problem. But the more interesting question is what is the commonality between the Macs that DO have this issue. And are all of them configured to NOT shut down drives to save power when the Mac is idle; that is an available option.
Our experience with card and slots on any of our three iMacs is ... well, we ditched using them. We use inexpensive SSDs (PNY by brand) as transfer media. External HDDs and SSDs for backups and long term storage.
BPBear544 wrote:
The 'Energy Saver Preference' approach may work for internal drives, but it certainly doesn't work for Ethernet-connected drives (which is how my TimeMachine is linked). Again, this wasn't an issue before Monterey, and doesn't appear to affect TM backups. It's just a nuisance that appears to be collateral damage with Monterey.
Quite right, Bpbear, energy saver has no effect on networked drive, but then it wouldn't, as the whole point of energy saver is to reduce the power to spinning or otherwise attached drives. I don't have numbers, but I would imagine the energy consumed by your computer keeping a networked drive 'up' is negligible - though still a non-zero figure - even if that same drive is consuming power attached to a different computer.
In any case, as you say, it will not work for you, so it is a separate, albeit undoubtedly equally annoying, issue.
Lawrence is absolutely right though, we must ALL let apple know of these issues, so that by being aware they exist, they might, just might, try to fix them.
File those bug reports, and repeat for each iteration of OS12, or each computer, if you have several. The squeaky wheel gets oiled :)
I'm still having this issue.
Drives randomly are 'not available' or 'not mounted'.
Just found out today that all my backups (including Backblaze) are two days behind because of this.
Arq backups to a WD Red in an enclosure stopped because the drive was unmounted (but still appears in Disk Utility).
Arq backups from my RAIDed SSDs fail because the backup is unavailable, yet I've been working in folders on this drive from the command line for days.
Had zero problems with Big Sur, it's not hardware.
Kernel panics have subsided this week.
Reported to Apple.
Just letting people know, check your backups, etc.
2017 iMac Pro --> CalDigit TS3+ --> 2x Thunderbolt SSDs in RAID0
+---> Sabrent HB-U93W --> multiple wall-wart powered USB drives
macOS 12.3 (21E230)
External Drives in Monterey