I believe the problem might be a sleep problem in either hardware or programming! So users on other board have said buying new high speed USBC cable instead to see if this helps!
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.
"Disk not ejected properly" error - Sandisk Extreme 2TB
- Thread starter 1brajesh
- Start date
- Sort by reaction score
I believe the problem might be a sleep problem in either hardware or programming! So users on other board have said buying new high speed USBC cable instead to see if this helps!
I've had no more issues with USBa port except for the speed.
So I reset my NVRAM according to this link : https://iboysoft.com/howto/disk-not-ejected-properly-mac.html
Now I'm back on the thunderbolt/USBC port and will see if the problem arises again.
So I reset my NVRAM according to this link : https://iboysoft.com/howto/disk-not-ejected-properly-mac.html
Now I'm back on the thunderbolt/USBC port and will see if the problem arises again.
OP:
Since connecting to the USBa port seems to have resolved, I'm thinking the problems with USBc -might- be due to the cable.
Have you EVER tried a DIFFERENT USBc cable, to see if the results would change?
I would recommend a USBc "high-speed, charging" cable that is specifically rated for 10gbps transfers. Something like this:
If the "random disconnection" problems RE-appear now that you've moved back to USBc, again, try a DIFFERENT cable.
Since connecting to the USBa port seems to have resolved, I'm thinking the problems with USBc -might- be due to the cable.
Have you EVER tried a DIFFERENT USBc cable, to see if the results would change?
I would recommend a USBc "high-speed, charging" cable that is specifically rated for 10gbps transfers. Something like this:
Short USB C to USB C Cable (1.5ft 2 Packs), 3.1 Gen 2 10Gbps 100W 4K USB C Video High Speed Data Transfer Fast Charging Cord Compatibile with Samsung Galaxy T5 LaCie SSD, MacBook, Display Monitor
Short USB C to USB C Cable (1.5ft 2 Packs), 3.1 Gen 2 10Gbps 100W 4K USB C Video High Speed Data Transfer Fast Charging Cord Compatibile with Samsung Galaxy T5 LaCie SSD, MacBook, Display Monitor
www.amazon.com
If you had read the other linked post, you might know that the cable is not the issue in my case ( M2 ) cause it works on the Hackintosh and this is a common behavior if it works right and fast while sleep getting ejecting error.
Also same Hardware was working with sleep before on 13.0 and not after 13.0.1.
Did not test it after 13.1 cause now i have Jettison.
What might be the reason for some can sell a Programm like Jettison ?
This behavior is appearing if i remember correctly with the introduction of Thunderbolt since Apple has changed basic Programming in USB.
The good thing with a Hackintosh is, you can declare the Ports ( and have to what can be a PIA ) to avoid this kind of Problem.
If it is not the Cable or Hub or chipset........
Last edited:
OP:
Since connecting to the USBa port seems to have resolved, I'm thinking the problems with USBc -might- be due to the cable.
Have you EVER tried a DIFFERENT USBc cable, to see if the results would change?
I would recommend a USBc "high-speed, charging" cable that is specifically rated for 10gbps transfers. Something like this:
If the "random disconnection" problems RE-appear now that you've moved back to USBc, again, try a DIFFERENT cable.Short USB C to USB C Cable (1.5ft 2 Packs), 3.1 Gen 2 10Gbps 100W 4K USB C Video High Speed Data Transfer Fast Charging Cord Compatibile with Samsung Galaxy T5 LaCie SSD, MacBook, Display Monitor
Short USB C to USB C Cable (1.5ft 2 Packs), 3.1 Gen 2 10Gbps 100W 4K USB C Video High Speed Data Transfer Fast Charging Cord Compatibile with Samsung Galaxy T5 LaCie SSD, MacBook, Display Monitorwww.amazon.com
This is a good suggestion.
The cable that comes with the Sandisk drive is only 6 inches long!
The drive literally hangs off the back of my iMac.
I had to prop the drive up with a small box just so it wouldn't hang and strain the cable.
There is still a twist in the cable because the port on the iMac is vertical, while the drive sits horizontal.
It's possible Sandisk has saved some cost by going with a short cheap cable.
I'll keep this in mind if my other attempts don't work.
Seems like a good price for 2 cables.
Having the exact issue here too but with a MacBook Pro m1. Whether it is or isn’t the cable you would have thought that they tested it before release. I can’t fathom it would be the cable for that very reason.
Btw I was having this issue with Monterrey and I suspect it was shutting the laptop lid. I updated to Ventura but it’s still the same. There are many many people with the exact same issue complaining on the sandisk support forums and what I find disconcerting is that sandisk did not reply to one post!
Whats your configuration? - sorry I just saw your config so ignore this question
I have just stumbled in connection with another problem about a setting which could possibly influence the behavior:
Where is USB Restricted Mode controlled?
- The protection is enabled by default on Apple Silicon Macs.
- The enabled protection is to Ask for new Accessories, additional options include:
- Ask every time.
- Automatically when unlocked.
- Always.
- Asking for new accessories is the minimum protection that should be in place, though highly secure enterprises will want to mandate for permission each time.
- You can disable/enable the setting in System Settings>Security & Privacy>Security.
- Configuring an accessibility Switch Control sets the policy to always allow accessory use.
- Approved devices can connect to a locked Mac for up to three days.
Somehow
look at the Foto from the TE:Yellow Anker
Cable from Power Supply ( Wattage ? ) to Hub Fixed Cable
to Hub from unknown origin USB-C cable to Sandisk
looks not Centered in Sandisk and is not ORIGINAL ( UNI not bad but what Specs ? )What is the Second USB-C cable from the Macbook going to ? And as it is looking to being higher Specs than the UNI USB-C Cable did he try this ?
He tried USB-A on Hub for Sandisk but not USB-C on Macbook direct ?
How many USB connected Devices we have her and what for...........
A very well done unpredictable mess.
You do realize this photo was NOT provided by OP, right?Somehow
Yellow Anker
Fixed Cable
USB-C cable to Sandisk
What is the Second USB-C cable from the Macbook going to ? And as it is looking to being higher Specs than the UNI USB-C Cable did he try this ?
He tried USB-A on Hub for Sandisk but not USB-C on Macbook direct ?
How many USB connected Devices we have her and what for...........
A very well done unpredictable mess.
View attachment 2133940
HobeSoundDarryl
macrumors G5
OP, "unexpected ejections" is commonplace with some third party enclosures since Big Sur. There are multiple threads about this. I have extensively tested this through multiple cables, all jacks, hubs, powered hub, etc and concluded that the problem is almost certainly a bug in macOS. It apparently carries forward from Big Sur to Monterey and now to Ventura.
While people may offer a ton of things for you to try, nothing resolves it for many with the problem. I'm convinced Apple has to do something in macOS to fix this.
HOWEVER, in all of my searching for anything and everything else that I could try, I haven't seen this reaching further back to Catalina. You are the only example I have seen for that. So I can't say for sure that the Big Sur+ cause definitely applies to your situation. I would feel more hope that there may be something ELSE affecting you than the one I'm referencing.
For many, third party enclosures, etc, "just work", especially if it is an SSD single drive but some HDD single drive too. Not all single drives work but some definitely do. This problem seems "larger" when it is a 2+ drive RAID box, mostly HDDs but some SSDs too.
After trying absolutely everything, I resigned myself to buying a new enclosure and have enjoyed a stable connection since. This isn't a brand thing- the problematic one and the stable one for me are BOTH by the same manufacturer. This isn’t an age of enclosure thing, as I dug out some ancient drives (circa 200X) for testing and some of them were stable vs. one I really want/need to work from about 2019. It also isn't a sleep thing, though sleep does seem to contribute to unexpected ejections more frequently than usual (so there may be SOMETHING there).
While you should try anything you easily can, I wouldn't spend too much money on stuff trying to get it working. Instead, you may find you simply need to purchase a different external and try with it... and then maybe again if it does it too. Eventually you find one that works. It shouldn't be this way on the "just works" platform, but it is and has been through now 3 generations of macOS... and now maybe since Catalina too in your case.
I'm confident Apple will eventually debug macOS and USB "just works" will make these work again. WHEN is the question that only Apple might know. Sorry.
While people may offer a ton of things for you to try, nothing resolves it for many with the problem. I'm convinced Apple has to do something in macOS to fix this.
HOWEVER, in all of my searching for anything and everything else that I could try, I haven't seen this reaching further back to Catalina. You are the only example I have seen for that. So I can't say for sure that the Big Sur+ cause definitely applies to your situation. I would feel more hope that there may be something ELSE affecting you than the one I'm referencing.
For many, third party enclosures, etc, "just work", especially if it is an SSD single drive but some HDD single drive too. Not all single drives work but some definitely do. This problem seems "larger" when it is a 2+ drive RAID box, mostly HDDs but some SSDs too.
After trying absolutely everything, I resigned myself to buying a new enclosure and have enjoyed a stable connection since. This isn't a brand thing- the problematic one and the stable one for me are BOTH by the same manufacturer. This isn’t an age of enclosure thing, as I dug out some ancient drives (circa 200X) for testing and some of them were stable vs. one I really want/need to work from about 2019. It also isn't a sleep thing, though sleep does seem to contribute to unexpected ejections more frequently than usual (so there may be SOMETHING there).
While you should try anything you easily can, I wouldn't spend too much money on stuff trying to get it working. Instead, you may find you simply need to purchase a different external and try with it... and then maybe again if it does it too. Eventually you find one that works. It shouldn't be this way on the "just works" platform, but it is and has been through now 3 generations of macOS... and now maybe since Catalina too in your case.
I'm confident Apple will eventually debug macOS and USB "just works" will make these work again. WHEN is the question that only Apple might know. Sorry.
Last edited:
Thanks @HobeSoundDarryl.
If this doesn't work, I'll try the Samsung T7, I still have the return window for the Sandisk.
So much for that, I just got the error again.
Changing the cable made no difference
Time to return the drive and try the Samsung T7
do you have "put hard disk to sleep" enabled by any chance?So much for that, I just got the error again.
Changing the cable made no difference
Time to return the drive and try the Samsung T7
I got a new Mac Studio just a little over a week ago and my Sandisk is attached 24x7 with no issues, latest Ventura.
but funny, I thought I had that disabled and just checking it is enabled, the "put hard disk ..."
Strange, good luck
Yes, I do have it enabled.
Also, I get the error message while I am on the computer not when I am away.
I am having the same issue. Here is the thing. I haver one of these exact drives attached to my Mac Studio for 6 months and have not had this error. I bought a second one and immediately starting having this problem. Tried switching ports and cables to no avail. SanDisk sent me a new cable, still no luck. I decided to return the drive since it was still inside the warranty period and got a new one. No luck same issue. So I am not sure what the deal is. Could just be some variation in the enclosures that they use to make these, maybe different manufactures depending on lot#
Same problem here too. I have a 4TB and a 2TB attached to my new iMac. No problems with the 4TB. I keep them both plugged in all the time. I've switched both cables and ports. It always happens to the 2TB drive. I may ask for a replacement if the conclusion is there is no fix.
Just another interesting update to add to the mystery:So much for that, I just got the error again.
Changing the cable made no difference
Time to return the drive and try the Samsung T7
With the new cable I got the error right away the same day I changed the cable.
However, for the next six days I got no error. Usually I was getting the error twice a day.
I was almost hoping the issue was fixed.
Now today, after six days I got the error again.
So, I still haven't ordered the Samsung T7 yet, but now its definitely time to get rid of this guy.
In addition to this problem, has anyone had a challenge ejecting the disk? Now it says "the disk wasn't ejected because one or more programs may be using it" when I have no other programs running - including a Time Machine backup!