TM backup disk: how to make sure it ejects

[MacInWin]

TM really doesn't like networked drives. Cloning to networked drives works well, usually, but TM treats networked drives very differently and gets really finicky. Direct attached should work much better.

 

[ferrarr]

Did you follow these instructions to set up TM, using another networked Mac for destination?

Backup disks you can use with Time Machine - Apple Support

To make a Time Machine backup of your Mac, you need a storage device that is compatible with Time Machine.

support.apple.com

 

[Jimmysb]

So have you swapped the ports the drives are on, and if so does the same drive fail, or the same port.

 

[ChangeAgent]

TM really doesn't like networked drives. Cloning to networked drives works well, usually, but TM treats networked drives very differently and gets really finicky. Direct attached should work much better.

Thanks. Good thought. And... I have been doing this for, well a decade. Longer? And it works fine. This is the first time I have problems of this kind. And what is more I have another MBP in the network backing up to the same MM and its own external SSD and it never has a problem.

 

[ChangeAgent]

Did you follow these instructions to set up TM, using another networked Mac for destination?

Backup disks you can use with Time Machine - Apple Support

To make a Time Machine backup of your Mac, you need a storage device that is compatible with Time Machine.

support.apple.com

I never seen this, but according to it I am set up correctly. Thanks for the tip.

 

[ChangeAgent]

So have you swapped the ports the drives are on, and if so does the same drive fail, or the same port.

I have, same drive. Good thinking though. Also used different USB cables. no difference.

 

[ferrarr]

Were you able to test, by connecting the drive with the issue directly to the MBP backing up to it? To see it you wouldn't have to erase and set up as new?

 

[Jimmysb]

I have, same drive. Good thinking though. Also used different USB cables. no difference.

So this suggests it is the drive that is at fault, and not the Mac, otherwise the problem would have stayed with the same port, and not moved with the drive.

 

[ChangeAgent]

hi ferrarr.
No I have not. why not? The disk is presently working fine as is, I need to wait for the next time it locks me out.

 

[ChangeAgent]

So this suggests it is the drive that is at fault, and not the Mac, otherwise the problem would have stayed with the same port, and not moved with the drive.

What could be with the drive? It is partitioned (2 partitions) and the other side works fine.

 

[ferrarr]

When you used different cables, did you use the cable from the drive that isn't having the issue, or was it just another cable all together? Did you test the problem drive cable on the other good drive?

 

[Jimmysb]

What could be with the drive? It is partitioned (2 partitions) and the other side works fine.

This is how fault diagnosis takes place, first identify the faulty item, as for, what the fault is, I would have no idea.

 

[ChangeAgent]

When you used different cables, did you use the cable from the drive that isn't having the issue, or was it just another cable all together? Did you test the problem drive cable on the other good drive?

tested with several cables, including original cable, all work with other drives.

 

[ChangeAgent]

This is how fault diagnosis takes place, first identify the faulty item, as for, what the fault is, I would have no idea.

I meant since it works flawlessly with one partition also doing TM backup for an other machine, I would be surpriced if it is the disk.

 

[Slydude]

Perhaps I missed it but what version of macOS are on the two machines? I ask because I have a drive that causes finder to throw out an error with the message thee disk wasn't ejected properly...

 

[ChangeAgent]

Perhaps I missed it but what version of macOS are on the two machines? I ask because I have a drive that causes finder to throw out an error with the message thee disk wasn't ejected properly...

15.3.2 all machines.

 

[ferrarr]

macOS is up to 15.4.1 now. Just saying.

 

[ChangeAgent]

macOS is up to 15.4.1 now. Just saying.

Indeed, I just saw this morning that it flagged the update. I will fix it today. I still do expect that it will not solve my problem. If it does, I will report it.

 

[Slydude]

Indeed, I just saw this morning that it flagged the update. I will fix it today. I still do expect that it will not solve my problem. If it does, I will report it.

I'm on 15.4 and get this error with at lest one of my drives though it's not the drive I use for Time Machine. The update doesn't seem to have fixed things for me but your results may be different.

 

[ChangeAgent]

I'm on 15.4 and get this error with at lest one of my drives though it's not the drive I use for Time Machine. The update doesn't seem to have fixed things for me but your results may be different.

Ha, thanks. Have not had time to upgrade, but will report.