Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Level 1

7 points

Failing Time Machine Backups?

I've been manually backing up wifi to an external Seagate NAS 3TB drive for about 2-3 years - successfully. About 2 weeks ago I found my TM backups going back about a month had not been successful. Attempts to backup produced hanging on "preparing backup". I then went to the web and found this solution: http://osxdaily.com/2014/03/31/time-machine-stuck-preparing-backup-mac-fix/

After doing the above I got past the hanging on "preparing backup" and was able to see the backup working, however the backup never completes and there are no error messages on TM telling me why the backup failed.

The above "fix" actually got me back as if I was doing my first backup, all previous backups were wiped out.

This started before the High Sierra update, but continues.

Can someone tell me how to proceed to solve this?

Thanks

Peter

MacBook Pro, macOS High Sierra (10.13.2)

Posted on Dec 15, 2017 3:05 PM

25 replies

whyamac Author

Level 1

7 points

Dec 17, 2017 11:38 AM in response to Grant Bennet-Alder

Here's Dec 15th. I've trying and failing for a couple of days.

Dec 15 15:25:39 macbook backupd[699]: objc[699]: __weak variable at 0x7fac8d4285e0 holds 0x65006e0069 instead of 0x7fac8d43a630. This is probably incorrect use of objc_storeWeak() and objc_loadWeak(). Break on objc_weak_error to debug.

Dec 15 15:25:39 macbook backupd[699]: objc[699]: __weak variable at 0x7fac8d5077c0 holds 0x2 instead of 0x7fac8d43a630. This is probably incorrect use of objc_storeWeak() and objc_loadWeak(). Break on objc_weak_error to debug.

Dec 15 15:57:42 192 KernelEventAgent[110]: tid 54485244 type 'hfs', mounted on '/Volumes/Time Machine Backups', from '/dev/disk1s2', low disk, very low disk

Dec 15 15:57:45 192 backupd[983]: objc[983]: __weak variable at 0x7f8fd1c2c2a0 holds 0x7f8fd1c20003 instead of 0x7f8fd1c23980. This is probably incorrect use of objc_storeWeak() and objc_loadWeak(). Break on objc_weak_error to debug.

Dec 15 15:57:45 192 backupd[983]: objc[983]: __weak variable at 0x7f8fd1d1ff10 holds 0x72772f646165720a instead of 0x7f8fd1c23980. This is probably incorrect use of objc_storeWeak() and objc_loadWeak(). Break on objc_weak_error to debug.

Dec 15 15:57:45 192 backupd[983]: objc[983]: __weak variable at 0x7f8fd1c28e40 holds 0x772820402431250e instead of 0x7f8fd1c23980. This is probably incorrect use of objc_storeWeak() and objc_loadWeak(). Break on objc_weak_error to debug.

Dec 15 17:45:41 192 com.apple.xpc.launchd[1] (com.apple.prefs.backup.remoteservice[1196]): Service exited due to signal: Killed: 9 sent by com.apple.prefs.backup.remoteser[1196]

Dec 15 17:46:21 192 com.apple.xpc.launchd[1] (com.apple.prefs.backup.remoteservice[1203]): Service exited due to signal: Killed: 9 sent by com.apple.prefs.backup.remoteser[1203]

whyamac Author

Level 1

7 points

Dec 17, 2017 11:53 AM in response to Grant Bennet-Alder

I don't know what you're looking for. All the logs show my failed backup attempts. As I said the progress bar shows backing up but gets to a point where it says "stopping", for no reason and no error messages.

I'm done here. I'll make an appointment at the Apple Genius Bar.

whyamac Author

Level 1

7 points

Dec 22, 2017 11:34 AM in response to whyamac

Genius Bar was "almost" useless. Before he looked at the computer he said I should replace my router to backup drive ethernet cable, my backup drive, my router. He also had no experience with "Monitor" logs. Did not inspire confidence.

Came home and tried another backup, got to 4GB of 60GB then it just stopped again. Internet suggested clicking "Verify Backup", did that and IT failed. Article said look for connection failure. So I connected the backup drive directly to the MAC (no wifi) and it completed the backup.

This is very odd. My wifi never failed during any of the backup attempts. As well my PC is wired to the backup drive through my router (no wifi) and it completes those backups.

I've ordered a new router. Will post back with results.