External SSD keeps disconnecting after upgrading to Sonoma

There really is not way to fix this for people who have the issue - because it is not the hardware. For some reason, the issue disappeared on my Mac mini M2 and the Samsung SDD after a while - until I was stupid enough to update to Sonoma 14.1. Same issue all over again. I am so upset!

Yeah.

Almost the same problem.

Running M1, everything was smooth until I updated to Sonoma.

My problem is that I usually edit videos with files on an external SSD, it lets me edit everything well, but when I try to export something to the SSD, it completes the process, but, I cannot see the file on Finder, same problem with downloading anything from Chrome to the SSD directly, cannot find the file, then, I disconnect the SSD, connect again and voilá my files are in fact, inside the SSD.

So, it's very annoying to work like this, connecting and disconnecting the SSD constantly.

I work in a similar way, editing photographic files on an external SSD. I have also experienced exactly this on Monterey, reported it as an issue with the thunderbolt four slots, was told its software not hardware (which I still doubt), and was forced to upgrade to Ventura but the problem persists. It extends beyond files not displaying in Finder: I find images also don’t display properly in photographic applications such as Photoshop, Lightroom, and InDesign.

Here's my experience: Since upgrading to Sonoma i have a Samsung T7 not properly ejecting after sleep. This happens on both of my machines: a mini M2 Pro and a Studio M2 Ultra. It happens consistently, regardless of cables and ports used. I also have four (externally powered) Sabrent NVME enclosures, they stay always mounted even after upgrading to Sonoma. Hoping for a fix, because it seems this is an OS issue.

Same issue here... 4TB SSD external hard drive working fine on my macbook pro 2021 until the update. Tried multiple cables (Angelbird, KondorBlue, Kingston) no luck. Works fine on windows. I edit videos off of my SSD and this is a nightmare.

Drives like the MyBook came with software, and the manufacturer suggested you install that software.

What that software does is to "spare you the annoyance of having to re-initialize the drive" from its factory set Windows New Technology File System (NTFS, the W is silent because there are no other Operating Systems) or similar unusual (on a Mac) format. Instead, the software they provided would simulate a MacOS drive inside an NTFS file for your Mac.

The downside of using the manufacturer's software is that if the manufacturer's software is not loaded, the Macintosh Volume may not be readable, or may not be writable. This means that in startup manager, Installer, and in Recovery such as after a data loss, the Macintosh Volume may not be visible.

The standard advice given here to all users, including novice users, is to discard the manufacturers software and NEVER use it. "Best Practice" is to erase the physical device when new, using only MacOS Disk Utility, and create the fundamental data structures needed for consistent, reliable use by MacOS.

Be sure to "show all devices" which will allow you to ERASE the entire Physical Device by its immutable manufacturer-given device-name, not just user created Volume-name such as ‘Macintosh HD’.

--------

The litmus test for 'what format is that drive' is to run this Terminal command, and look for the NAME of your drive in the list. This is the output for an Apple File system drive, first for the (Physical), then for the (synthesized) APFS container-scheme:

diskutil list

...
/dev/disk6 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *240.1 GB   disk6
   1:                        EFI ⁨EFI⁩                     209.7 MB   disk6s1
   2:                 Apple_APFS ⁨Container disk7⁩         239.8 GB   disk6s2

/dev/disk7 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +239.8 GB   disk7
                                 Physical Store disk6s2
   1:                APFS Volume ⁨X14-SSD240⁩              97.5 GB    disk7s1
   2:                APFS Volume ⁨Preboot⁩                 26.5 MB    disk7s2
   3:                APFS Volume ⁨Recovery⁩                507.6 MB   disk7s3
   4:                APFS Volume ⁨VM⁩                      20.5 KB    disk7s4

my MacOS volume named X14-SSD240 is on a physical SSD drive about 240 GB in size.

I've been into this with Apple repeatedly and also been told they haven't had any other reports. Guess either stock response, or maybe the bot only matches identical issues with specific h/w in specific O/S. I agree though, if every one of us on this thread reported it it might be helpful. I'll report again with less precise parameters.

Same story with Transcend 1TB SSD (ESD230C).

Initially used for photo backups (as exFAT), but then I've started to see these "not properly ejected" issues on Sonoma. I took a risk and deleted everything to get it reformatted to APFS. After that those random disconnection issues were gone for a while, but after ~24 hours got back again.

Thought the thing is broken and was going to replace it already, but then came across this thread. I see there are very similar issues with other SSDs (and not only them - HDDs are also impacted). So that seriously needs to be looked at.

To add, the SSD seems to be fine, as it can be recognised and accessed absolutely okay when plugged in to the iPhone 15 Pro. Can't sufficiently test on other laptops, as they are all on Sonoma as well.

I had been using a Mac Mini w Intel processor sunning Sonoma and 5 HD's (3- 3.5" and 1-2.5" portable , all SeaGate, AND 1 2TB SanDisk SSD. One HD was periodically unmounting. Ran TechTools and confirmed it was dying, so discarded it. All the rest were operating fine including an 8TB Time Machine Backup drive.

I then upgraded to a MacBook M3 Pro Max. Migration was a pain. It would not connect to my MacMini, so, I chose to migrate from the Time Machine backup. This when smoothly.

Then I connected my other drives. Soon, there were reported problems with ALL drive! Time Machine could not backup to the Time Machine HD. It reported that it didn't have permission. The other drives continuously got the Improper removal message. The SSD gave a message that it could not be repaired (never asked it to be repaired), that I could copy files from the SSD, but could not alter them

All drives were formatted in the MacOS Extended Journaled format. Connecting the 3.5" drives would take 10-20 minutes topper in the finder. Connecting the 2.5' Portable HD connected quickly, but them started reporting improper removals. The SSD mounted quickly, but with the aforementioned error message.

Spent two sessions with online Apple Support, reinstalled the MacOS Sonoma, removed all potential interfering software (Sophos Antivirus, PIA VPN, TechTools, etc), then went to the Genius Bar.

They confirmed everything I've reported, with no solution.

In frustration, I purchased a LeCie HD in the Apple Store, reformatted it to APFS, and it mounted immediately. So, I went home, set the LaCie drive as my new Time Machine drive, backed up my MacBook.

I've now spend a few days trying to solve the remaining problems. The original TM backup file could not be copied from the original drive to the new TM drive. Eventually I had to give up and reformat the old TM drive to APFS, losing years backups. BUT, that drive has been performing flawlessly for 3 plus days now. I transferred files from problematic drive to the recently reformatted drives, then reprobated to problematic drive , then repeated the problem with the ned problematic drive. Each time a drive was formatted, it instantly mounted when connected to the MB Pro. BTW, the SanDisk SSD could NOT be formatted to the APFS format, but was reformatted to macOS Extended and is also working just fine.

Fingers crossed...

I ran into this problem with my new Crucial SSD that I was using for time machine on my new Studio/ Sonoma. How I solved it was: instead of inserting the cable into a back usb port, I used the front. It no longer disconnects. I have no idea why this worked but maybe this idea will help others.

You really think Apple is purposely writing code specifically to unmount external storage drives...? And you think they are doing that especially on the 2023 Mac Mini, for some reason?

No. This is a bug.

I've been experiencing disconnects of my Sabrent Thunderbolt dual NVMe enclosure (Mac mini M2 Pro, Sonoma 14.2.1). As strange as this may sound, my problem seems to be related to wifi. I use a wired network connection and keep wifi turned on (but not connected to an SSID) only to allow my Apple Watch to unlock the computer. So far while wifi is turned off, I have not had a disconnect. However, the act of turning wifi back on causes the drives to disconnect. This is repeatable behavior. Whether it applies to anyone else's situation I'm not sure, but it might be worth checking to see if it is a workaround if you are facing this issue.

Apple is doing this on purpose because the company does not want you to buy cheap non-apple external drives. They want you to upgrade the internal drive where they make money. If you buy external drives from other non-apple Companies they lose money. They can easily put the blame on the other 100 things that cause the problem. APPLE is a greedy company that lives on hardware (look at the iPhone releases). They will never fix it. The drive will keep disconnecting until it gets corrupted and eventually dies. They are doing this on purpose. People just don't know. They have advanced technologies making their chips, and you think they can't create a driver to support the drive from disconnecting and functioning properly ??? This is laughable. It's all about money.

Can You tell more information about this, which FS, if this is NVME M2. Because for me this still not work if FS is ExFAT and M2 device and direct connection to USB. I have some solution, but it works slow, use connection via USB HUB. First initialisation of disk took about 8-10 min but work without disconnections. Kingston Fury 4TB + Anker USB\HDMI HUB.

Nikolas0980 wrote:

Apple is doing this on purpose because the company does not want you to buy cheap non-apple external drives.

I am not an Apple employee, so I am free to say what I want.

Apple behavior does Not follow your conspiracy theory.

Instead, Apple appears to take whatever reasonable steps they can take to make you a "Happy Customer". "Happy Customers" buy more stuff from Apple in the long run, and that is where Apple applies its energy.