User profile for user: alberti-nl
alberti-nl Author
User level: Level 1
36 points

Randomly, or often, after waking, I get DISK NOT EJECTED PROPERLY error on my SATA TM disk

I am bothered with a random DISK NOT EJECTED PROPERLY error on my mac studio 2022.

  • the disk is a 2.5" Crucial SATA disk (1Tb), that is perfect for a time machine
  • I had it connected to the 'hub' in my screen (LG).

Thinking that connection via the monitor was the problem, I bought a Hagebis hub (hey, great form factor!!!), put the disk there, and while for some days I did not have the messages, all at once I see the messages after wakeup again, this morning even two beneath each other.


The time machine disk loads directly after the message, at least I mean, I see it in devices; before - with the connection in the monitor it would sometimes not be found at all. I don't like it.


I regularly shut-down the computer, say once a week. Now this time I stopped it for 60 secs (some say this helps) but I'm not sure.


What is a good remedy?


Studio 2022, Ventura 13.4.1 (22F82)

Mac Studio, macOS 13.4

Posted on Jul 1, 2023 2:48 AM

Reply
Question marked as Top-ranking reply
User profile for user: Owl-53
Owl-53
User level: Level 10
104,413 points

Posted on Jul 1, 2023 7:14 AM

Although this Hub is marketed as Designed specifically for the 24 " Apple Silicon computer.




No doubt your are aware, that since macOS 12 Monterey, Self Powered or USB Powered Hubs have been a Hot Topic in regards working or not working.


It became more apparent in later versions of Monterey that the Chip Set within the Hub was a " Roll of the Dice " if it would or would not work as expected or at all.


As an experiment only, how well does the TM Backup Drive perform when Directly attached to the computer.


Any change for the better or no change.


As for Terminal and pmset, agree one should not have to do a trial and error to get the annoying DISK NOT EJECTED PROPERLY to cease but . . .


You can implement the No Sleep via terminal and if that dos not show improvements - switch it back to the default setting


At least you may get a more clear picture where the real issue is ?

View in context

Similar questions

24 replies
Question marked as Top-ranking reply
User profile for user: Owl-53
Owl-53
User level: Level 10
104,413 points

Jul 1, 2023 7:14 AM in response to alberti-nl

Although this Hub is marketed as Designed specifically for the 24 " Apple Silicon computer.




No doubt your are aware, that since macOS 12 Monterey, Self Powered or USB Powered Hubs have been a Hot Topic in regards working or not working.


It became more apparent in later versions of Monterey that the Chip Set within the Hub was a " Roll of the Dice " if it would or would not work as expected or at all.


As an experiment only, how well does the TM Backup Drive perform when Directly attached to the computer.


Any change for the better or no change.


As for Terminal and pmset, agree one should not have to do a trial and error to get the annoying DISK NOT EJECTED PROPERLY to cease but . . .


You can implement the No Sleep via terminal and if that dos not show improvements - switch it back to the default setting


At least you may get a more clear picture where the real issue is ?

Reply
User profile for user: alberti-nl
alberti-nl Author
User level: Level 1
36 points

Jul 25, 2023 9:13 AM in response to satcomer

I reconfigured the volume (erased) and reconfigured with APFS. --> It originally was APFS/Case sensitive. I called it Crucial TM (like it was); it is a SSD/SATA drive


After I selected it for TM, the TM configures the volume again itself as APFS/Cs. The container is APFS. And the drive is GUID.


NOTE: now I got the message: can I use CrucialTM3 for the backup?

  • SO: I see a possible origin of the problem: somewhere in the BigBrain (some registry keys) there are TM1, TM2, TM3 even though I just have one Crucial TM volume.
  • Could that be the root problem?
  • It is now backupping (yes I now lost old backup data, but look, I've had that so often on my Windoze machines..)


Reply
User profile for user: alberti-nl
alberti-nl Author
User level: Level 1
36 points

Jul 1, 2023 11:13 AM in response to alberti-nl

I replaced the drive inside the Dock.

FIRST I threw out the drive from Locations (hmmm)

Inserted it in the Dock, attached the USB-C cable (to the socket most left on front - maybe there is difference?)

Had no problem since. (three times I did a wake-up, but tomorrow morning I'll see again)


Me-guessed: that I had just unplugged the Dock before inserting it back in the uGreen USB-C adapter. Could such mismanagement be the cause???? Ohhh those users.

Reply
User profile for user: dialabrain
dialabrain
User level: Level 10
136,385 points

Jul 1, 2023 5:11 AM in response to alberti-nl

alberti-nl wrote:

I have done this, thanks; but still have hope on some fix.

You're welcome. A "fix" would have to come from Apple in a future version of Ventura or later. Assuming it's something that is a macOS issue and not the drive's manufacturer's issue.


FWIW, for as long as I had the problem, disconnecting and reconnecting the drive, never seemed to affect Time Machine backups.

Reply
User profile for user: alberti-nl
alberti-nl Author
User level: Level 1
36 points

Jul 1, 2023 8:32 AM in response to Owl-53

Thanks for the questions.

OLD: The SATA SSD was first connected to the monitor LG Superfine monitor - that is connected to the Studio via a Thunderbolt cable (on the back of the Studio). It was in a normal 2.5 inch case, that has USB 3.1 cable. The LG monitor has a USB 3.1 bus. There it had two problems: it did not wake up and also I could not see it after waking.


Now I have the SATA inserted it in a Hagebis 'dock/hub', it is internal, and the hub is connected to the front of the Studio via a USB-C to USB-C cable. When the computer wakes up, often the disk wakes up late, and later can be seen in the list of devices.

  • By reference I give it the name dock/hub as Hagebis gives it, technically the incoming signal of course first goes through a reciever chip that allows multiple outports. The Studio-outport is 3.1 and 10Gbs, [then follows a Fresco 5Gbs USB3.0 Hub in the Hagebis]; [and the drive has as Media-driver ASM225.]
  • This dock is designed to work with the M1.


The Satechi/Hagebis hub/dock was made for the Mini M1, and it further works excellently for the Studio too. It is different from the one you picture.


About No Sleep - can that be set to work for one device only (the TM drive)?

Is it the same as Hibernate?

  • I have hibernate on because my external drives get hot, bloody hot. One dual has two 2TB NVME SSD's. I attached a big cooling fin. With hibernate they keep cool; another drive also stays cool now too. The Thunderbolt drives even stay cold (one with 2Tb has a ventilator inside, the other 1Tb is plain).
  • None of these drives give a problem of drives not loading.
Reply
User profile for user: fiberhome
fiberhome
User level: Level 1
42 points

Jul 8, 2023 2:02 PM in response to alberti-nl

I had been having "disk not ejected properly" with increasing frequency on a 500 Gig My Passport running on my 2018 MacMini on Monterey plugged into external USB powered and self powered hubs, and when Disk Utility began to reporting errors with the drive, I replaced it, using a Carbon Copy Cloner backup drive to transfer the data to a 1 TByte Crucial X6 portable solid state drive. That was less than a week ago, and now I am getting reports the error was not ejected properly even when the Mac still says it's Mounted. It's plugged directly into one of the 4 Thunderbolt 3 (USB-C) ports so this is not related to problems with USB hubs.

I had not intended to get a solid-state drive, but the online seller (B&H) added it to the list after I had tried to select spinning drives. That's probably not relevant to this problem, but it does mean that the problem can appear for solid-state drives as well as drives plugged directly into the Mac.


What troubles me is that this problem appeared almost immediately after installing the new drive (the error lists the two partitions on the drive), and is now only on the single disk. When I run Disk Utility on it it checks okay. I previously only had the problem only on the older original external disk. I have two other external spinning hard drives attached, one a CCC copy, the other a Time Machine drive, and neither of those have reported ejection errors. I loaded the new drive with data from the CCC copy, which shows no errors.


There's something wrong here and this is my entire music collection as well as some other important old files. Any ideas?

Reply
User profile for user: alberti-nl
alberti-nl Author
User level: Level 1
36 points

Jul 9, 2023 2:11 AM in response to fiberhome

I do not think the drive contents are at risk. I think it is a protocol/timing issue. The OS expects a faster wakeup or so than the drive does.


It is a weird thing.

My TM SSD disk was OK for a few days (no messages) but now again I get those messages.

Why they stopped?

Maybe due to 1) manual eject, 2) plugout USB-C - 3) plugin USB-C sequence? No, I did that yesterday. This morning : an error message.

Reply

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Randomly, or often, after waking, I get DISK NOT EJECTED PROPERLY error on my SATA TM disk

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.
Learn more Sign up