External SSD Disconnects Repeatedly Mac Mini M1 (Big Sur)

I went to a Thunderbolt 3 Cable (40Gbps). Fixed my SSD problem, and got a speed boost. Bit price ($23). https://www.amazon.com/dp/B099DZ4YS5?psc=1&ref=ppx_yo2_dt_b_product_details

One thing to check, especially if this occurs during otherwise idle periods, is the power save settings that allow to put drives to sleep when possible. I disable that when my computer is powered up.

The issues I’ve found are when the SSD is in use for transfers of anywhere from 100GB to over 1TB.

Same: 2020 MacBook Air Monterey. What I noticed was the external drive would work fine with small files. When I tried to work on a larger file like an iMovie backed up on the portable, it would auto eject with the warning. I just purchased the Samsung T7 SSD 1TB and I have not had any problems. I am able to work on iMovies directly off the SDD (Almost with no lag). I'm thinking the issue of external drive ejecting lies with the drive not being fast enough..... IDK. I was perviously using a WD 2TB for Mac. It didn't work. I'm happy now!

FWIW, I'd been having this issue since updating to Catalina (where I still am), but I bought a new Thunderbolt 3 cable, Sabrent brand, and have not had a single disconnect since.

This is quite strange considering that the two cables I'd been using with my external SSD worked fine under Mojave and prior.

But a fix is a fix. If it means I'm not spending 10 minutes of composing time trying to get my SSD connected, I'll take it.

Try purchasing a good quality TB3 cable. That fixed it for me.

I realize that it’s bizarre; really doesn’t make any sense at all: I had been using two other thunderbolt 3 cables (the ones bundled with my enclosure) with my external SSD for 2 years with no issue, and then I upgraded to Catalina and started having these random disconnects. The new cable has fixed it. I’ve had it for about a month and zero disconnects. It was about an eight dollar fix, if I remember the cable price correctly.

Changing cables and hubs is not the solution to the problem, I guarantee the issues will return.

Its clearly a OS/hardware issue. Again we all need to call apple support and hit them on social.

I can't believe that this is still going on, after a year!

I have a ThunderBay 4 that behaved perfectly for 2 years with my Mac mini Intel.

I just replaced it with a new Mac mini M1, and now I experience two variations:

• the common “not properly ejected” warnings
• the drives going to sleep even though the Energy Save box is unchecked for “put hard disks to sleep”.

The cable is an OWC T4 cable. The macOS is the latest Big Sur.

There are a thousand postings about this — from Reddit to StackExchange to Apple Support — but I see no answers.

Could it be that Apple has been ejected? Put to sleep?

Solved!

I had the same issue, and I solved it by changing the disk sleep settings in Terminal. I couldn't go to Energy Saver prefs because on Monterey I don't see the option to not put disks to sleep. So, I followed Item 2 on this page.

Details:

My M2X SSD enclosure from MyDigital SSD would intermittently disconnect. Sometimes in the middle of using it; sometimes when idle. It only did this on my M1 mini, and not when connected to my older Intel iMac (but I'm not sure of that Mac's disk sleep settings). I already tried swapping the USB C cable, but that did not matter. It's a JMicron Tech chip in the enclosure.

This is the most common solution: Choose

System Preferences… > Energy Saver

Check the box for 

Prevent computer from sleeping when the display is off

(There is no need for the computer to go to sleep, since it’s not running on battery.)

If this doesn’t solve the problem the first time, try toggling the setting. Check the box, close System Preferences, re-open Energy Saver, then uncheck the box. This resets a munged value in the .plist file.

This Terminal command is another way to make the change

pmset -a disksleep 0 

View man pmset in Terminal for details.

Hello!

I wish my solution will help somebody. I have M1 Mac Mini 512/8 with Satechi hub (inside it is Samsung EVO 860). And all was fine before last system update (now it is Monterey 12.4). After it external SSD disconnects 20-50 times at evening (I work with it only 2-3 hours a day). It was terrible 'cause I am a photographer and my photos on external disk. I just can't choose some photo 'cause SSD keep disconnects every minute! I read this thread and another on different sites and try all things that people recommends. It not helped (nor cables change or nor system sleep preferences). And I want to try another external hard drive to see will it happen with it. And it worked! I just connect to USB on front of Satechi station my old external Samsung HDD G2 and after that EVO860 not disconnects at all! With this solution I live near 3 weeks and it's all right.

Having updated to Big Sur 11.2 on 1 Feb, the problem, at least for me so far seems to have disappeared. Any change for you dschommer?

I have no idea why but purchasing this cable worked for me. 48 hours with a stable connection.

https://www.amazon.com/dp/B005H3Q52C?psc=1&ref=ppx_yo2_dt_b_product_details

Hi there dschommer,

Thanks for using Apple Support Communities. It sounds like you have an external drive disconnecting when trying to write some files to the drive. Since this issue does not occur when using a different connection method, it may be the port or cord you are using. Check the port for any debris and try replacing the thunderbolt cord.

Try repairing the disk in Disk Utility as well. See how here: Repair a storage device in Disk Utility on Mac.

We hope this helps!

I guess that I had more to add to this.

Under the circumstances where the device is connected directly to the M1 Mac, the enclosure LED lights up solid, and Disk Utility appears to detect the drive, and one is presented with the options to eject, ignore or initialize the drive, it is possible to use DU to do the initialization. In these instances, DU will detect a 97TB drive size and the initialization will fail.

About as often, the enclosure LED may light up solid, and DU does not detect the internal SSD at all, even though the drive electronics will show up in SysInfo under TB or USD depending on the cable being used.

If, after the failed initialization attempt, the enclosure is immediately connected to the OWC hub, the device will connect normally (if it's the Sabrent Rocket inside the Sabrent enclosure) and show a healthy file system, with the previous content, and 2TB in size. That is, the initialization attempt did not touch the SSD.

If there is no drive inside the enclosure at all, the enclosure LED will not light up in any way, at least for the two that I've been using. Controller electronics will show up in the SysInfo panel, as appropriate.

The enclosure LED will never light if there is not drive installed. The enclosure LED will go solid if there is a drive installed when connected to the OWC hub. Often, the enclosure LED will light up solid only on a second connection to the M1; that is, connect the cable and nothing happens, disconnect and immediately reconnect and the enclosure LED will go solid.

If there is a drive, and if the LED blinks once, goes solid and then flickers, there is data connectivity and flow. In general, in my experience with the Rocket 4+ SSD and the two enclosure I have, this desired behavior will happen consistently only when the Sabrent Rocket is in the Sabrent USB-C enclosure and that is connected with a USB-C cable to the OWC hub.

All other bets are off.