Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

ethandt72

macrumors newbie
Original poster
May 10, 2016
12
2
I have a relatively new Sandisk Professional 2TB SSD that I purchased in May. It's been rock solid and super fast. Within the last two weeks, it started giving me issues when I would try to unmount the drive from my MacBook Pro (M3 Pro). It would say that it couldn't be ejected because there were applications in use that were accessing the drive, even though I had closed out of all running applications. It would give me the option to Force Eject it.

So I got on the phone with customer support and we tried a few things and nothing was working so we decided to erase the drive and start over. At that point I connected my WD Black 8TB HDD to back up the SSD before erasing.

Once that was backed up we went to erase the SSD using Disk Utility and it gave me an error and said it couldn't be erased. So then I went to disconnect my WD Black, never has given me any issues, and that one all of as sudden wouldn't disconnect from my Mac without having to Force Eject it.

At that point I realsized that I just updated to 15.2 within the last few weeks, so we determined that was probably the issue, something in the new Mac OS that was causing these issues.

Anyone have any thoughts on this?

Cheers
 
I think that's about 8x more troubleshooting than I'd have done on Beta software. Not sure whether to be impressed or appalled 😏
LOL. Well, to be fair, it wasn't the Beta release, it was the non-Beta 15.1 that started it. Error in the title of the post. I updated to 15.2 beta just to see if that fixed it, and it didn't.
 
I'm going to chime in here. I have a dual drive enclosure that I use to backup all my photos & videos. Two separate drives - one for photos and one for videos/music. I have seven other bare drives that I use for backups with a dock also that I keep off site. I was backing up to all these drives today before updating to 15.2 and most of them required to be force ejected. I finished all the backups and installed 15.2 and no change. Even if I start the computer from being turned off (the drives in the enclosure will mount at startup) the Movies drive always needs to be force ejected. This only started happening after updating to 15.1. Something odd is going on. All drives are formatted as APFS.
 
I'm going to chime in here. I have a dual drive enclosure that I use to backup all my photos & videos. Two separate drives - one for photos and one for videos/music. I have seven other bare drives that I use for backups with a dock also that I keep off site. I was backing up to all these drives today before updating to 15.2 and most of them required to be force ejected. I finished all the backups and installed 15.2 and no change. Even if I start the computer from being turned off (the drives in the enclosure will mount at startup) the Movies drive always needs to be force ejected. This only started happening after updating to 15.1. Something odd is going on. All drives are formatted as APFS.
See the link in post #2 in this thread. I followed the information in the linked thread post #12. I added my external drives to the System Settings>Spotlight>Search Privacy...button>Privacy window to stop Spotlight indexing/searching my external drives to solve the can't eject problem. My external drives had to be connected, drug the external drive to Privacy window, clicked Done, Shut Down the Mac, disconnected the drives, Started the Mac. It worked for me.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.