TM backup disk: how to make sure it ejects

[ChangeAgent]

I have a USB SSD connected to a Mac Mini in my network (everything is hard-wired) that is set up to be a Time Machine disk for one of my computers (a M1 MBP).

Often after the MBP sleeps, I get a message that the disk was not properly ejected. Can one make sure that as soon as TM is finished with the backup, the disk gets ejected?

All Macs are on the latest OS.

Thanks.

 

[IWT]

One thing to do is make sure that when your Mac sleeps, it still allows TM and similar EHDs to remain open, by which I mean don’t let it go to sleep even though your Mac is in sleep mode.

This is a common cause for “the Disk was not properly ejected”.

You can check this by going into Settings.

See this article: Google Search

Ian

 

[Rod]

I think Ian has given you the top answer. ie. Don't let your internal drive Sleep. It does no harm it simply ensures the internal SSS receives a trickle of power to keep it "awake."

This issue of External Hard Drives (EHDs) switching themselves off during sleep has been a thorn in the side for many users for ages.
Some have even resorted to utilities like Amphetamine to prevent sleep.

I have exactly the same Mac as you, an M1 14" MBP and I have two backup EHDs permanently connected, an SSD which I use for a CCC clone and a HDD which I use for Time Machine (TM).
I have found that this persistant problem has improved somewhat over recent macOS especially macOS Sequoia 15.4.1 so if you're not already updated to that I would stongly suggest that you do.

Here are my energy settings found under Battery in System Settings:



Note: I only have "Put hard disks to sleep when possible" set to "Only on Battery". because I do not have EHDs plugged in on Battery power, you might wish to choose "Never."

This is the best setup I can suggest and it seldom fails me but I still occasionally find if the lid is closed o/night I will still get the "the disk... was not properly ejected" message but only for the SSD, not the HDD.

 

[ChangeAgent]

Thanks, IWT and Rod for answering. Good info. One thought if I may.

I had thought about this solution too. And I am/was not sure it would work on my external SSD. Remember the SSD is connected to a Mac Mini in the network. The Mac Mini never sleeps. And what is more, I use 2 SSDs to make TM backups for my M1 MBP. Let’s call them disk 1 and disk 2. Disk 1 never causes this problem; it is always disk 2 that gets the error and that without exception. That is why I did not implement the solution I thought of, and you suggest.

Any thoughts on it?

 

[Jimmysb]

Thanks, IWT and Rod for answering. Good info. One thought if I may.

I had thought about this solution too. And I am/was not sure it would work on my external SSD. Remember the SSD is connected to a Mac Mini in the network. The Mac Mini never sleeps. And what is more, I use 2 SSDs to make TM backups for my M1 MBP. Let’s call them disk 1 and disk 2. Disk 1 never causes this problem; it is always disk 2 that gets the error and that without exception. That is why I did not implement the solution I thought of, and you suggest.

Any thoughts on it?

How are disk 1 and 2 connected, i.e. USB A, USB C, and and do they go via a hub or adaptor.

 

[ChangeAgent]

USB C and direct in one of the ports in the MM. So each one its own port.

 

[ferrarr]

Check the Settings on the MM, to be sure external drives aren't going to sleep there either.

 

[ChangeAgent]

nope all set as suggested.

 

[Jimmysb]

USB C and direct in one of the ports in the MM. So each one its own port.

And which is giving you the problem.

 

[ChangeAgent]

And which is giving you the problem.

say more? not sure what you mean and how to solve it.

 

[Rod]

2 SSDs to make TM backups for my M1 MBP. Let’s call them disk 1 and disk 2. Disk 1 never causes this problem; it is always disk 2 that gets the error and that without exception.

I think having two EHD's performing the same TM task may well be causing a conflict that may be the root cause of the disconnect. Either way, with respect I think it's overkill. I do have two Backups of my M1 MBP (my only computer at the moment) but they are using different backup applications. One is TM the other is Carbon Copy Cloner.
Given that so much of my data is backed up to iCloud, (even my Password Manager has an encrypted copy on iCloud) it is highly unlikely that I would loose any data in the event of a total failure of my Mac. In fact that has happened twice already over the years and with no loss.

 

[Jimmysb]

say more? not sure what you mean and how to solve it.

You say you have 2 drives:

Let’s call them disk 1 and disk 2. Disk 1 never causes this problem; it is always disk 2 that gets the error and that without exception.

Disk 2 has the problem, disk 1 doesn't, I am trying to find out how each is specifically connected, as it may be the connection type that is the issue, or are the connection identical for both drives.

 

[ChangeAgent]

Understood. I have over the (many) years of the existence of TM found myself (and seen in forums) that the TM backups get corrupted. Apple itself suggested to me to have two TM SSDs to back up to. After all, TM can do this.

And yes, I have other backups, I learned over the years. Still, I would like it to work properly as TM is an easy way to quickly restore something.

So the search for the solution continues.

 

[ferrarr]

One backup is connected to the Mac, and the other backup is connected to the Mini? Have you tried switching the backup drives to the other computer? I feel like there is a Network setting we are overlooking.

I used to use 2 backup drives, and TM always worked for me. But both drives were connected directly to the 2014 MM, and even the M1 Studio. Right now I am back to 1 TM SSD for my M4 MBP.

 

[ChangeAgent]

No incorrect ferrarr, both are connected to the Mac mini and the MBP accesses it over the wired network and all have fixed IP addresses.

 

[MacInWin]

Some of the things in this thread are very confusing to me. In post #1 you said "everything is hard-wired." That phrasing generally means that the backup drives are directly attached to the Mac by USB cables. But the MBP accesses the TM drives over your local network, which uses SMB protocols and is NOT hard-wired. And from your description, when the MBP sleeps, that connection is lost.

I had thought about this solution too. And I am/was not sure it would work on my external SSD. Remember the SSD is connected to a Mac Mini in the network. The Mac Mini never sleeps. And what is more, I use 2 SSDs to make TM backups for my M1 MBP. Let’s call them disk 1 and disk 2. Disk 1 never causes this problem; it is always disk 2 that gets the error and that without exception. That is why I did not implement the solution I thought of, and you suggest.

That paragraph is very confusing to me. You seem to have three drives involved. One is an SSD attached to the Mini but it is NOT clear if it's really attached or "in the network," whatever that means. Then you have two more SSDs for backups of the MBP. How are they connected? From Post #15, it seems to be that they are somehow in the network and are attached as network drives, NOT directly attached. And no clarity on what disk 1 or disk 2 might be, or where they are attached. I'm totally lost. You had said that the drives were attached by USB-C to the Mini, but then said they had IP numbers, which implies network attached.

So, can you start from the beginning, please, and describe exactly what you are using for the TM backups? What drives, what are they attached to, how are they attached, how are they connected (what protocols), how is TM set up, etc? Remember, we cannot see the setup, so you have to describe it as if we are blind.

 

[Jimmysb]

So, can you start from the beginning, please, and describe exactly what you are using for the TM backups? What drives, what are they attached to, how are they attached, how are they connected (what protocols), how is TM set up, etc? Remember, we cannot see the setup, so you have to describe it as if we are blind.

Just what i was trying to find out, it is vague, and the precise configuration could identify where the issue may lay.

 

[ChangeAgent]

Hi Folks, I am sorry it is confusing probably my wrong. I give it another go.

MBP in a hard-wired network (all Cat 6 or above). Fixed IP.

Mac mini is in the same network. Fixed IP. Hard-wired.

All other things in the network have fixed IP’. Hard-wired.

Mac mini has 2 separate 1TB SSD’ attached to it, disk 1 and disk 2. Both disks are USB powered. Each uses its own port in the Mac mini, USB C. Those disks are exclusively used for Time Machine backing up the MBP.

No hubs are involved.

From time to time my MBP reports that one of the disks is not properly ejected. This is always the same disk (disk 1) and never the other disk (disk 2). This seems to be damaging the disk, as I can no longer access it with Time Machine and must erase it and start again.

Am I clear now? I hope so.

 

[ferrarr]

Mac mini has 2 separate 1TB SSD’ attached to it, disk 1 and disk 2. Both disks are USB powered. Each uses its own port in the Mac mini, USB C. Those disks are exclusively used for Time Machine backing up the MBP.

Are they both exactly the same drives? Or are they different models, mfg, or other differences? What models, specs are they? Are they different ages?

Instead of erasing the drive, try to direct connect it to the MBP, it may solve the issue.

 

[ChangeAgent]

Both are Samsung T7 disks bought at the same time, ±14 months old. Using the cables they came with. Tried other cables, same problem.

Good tip to try connecting directly. I try that next time.