Mojave time machine back up failing

I get an "account not found" error when I attempt to log in to the Bug Reporter with my Apple ID (same one I use here). On the Bug Reporter page, it mentions signing in with a developer account, so I'm guessing that's why I can't sign in.

Apple Bug Reporter is a web-based tool that developers can use to report issues with Apple software and services, request enhancements to APIs and tools, and track the status of their feedback. To access Apple Bug Reporter, sign in with the Apple ID associated with your developer account.

In any case, hopefully those who have reported it via the Bug Reporter will get more traction with the defects with Time Machine.

Yes, I've tried entering my Apple ID several times with the same result. It's the same Apple ID that I use to sign in here, which I did right after my failed attempt to reach the Bug Reporter, so I know my username and password work.

You may require (or have required) a Developer Account, sjordi. I did not require a Developer Account, I have not got a Developer Account, I do not need a Developer Account, I am not a Developer and I do not intend to get a Developer Account.

As for having to produce and submit a sysdiagnose file, I mentioned this earlier in this string. I at first failed to do so, and the Apple people replied, both in the Bug Reporter and by email, asking for one (proving that they do read these bug reports), which I then did create and submit, twice over, at two stages during the very lengthy TM backup process.

Interesting because I could not submit a bug as long as I wasn't logged with my dev account.

And I couldn't send the bug report as long as the sysdiag file was not attached. Only that operation made the submit button available (without attach, it was just grayed out). Funny

Anyway, as much as more people post a bug, no matter which account or technics, the better.

Yes, that’s a very odd inconsistency. I can see why they would (attempt to) limit it to developers where you would expect a certain level of expertise prior to reporting a “bug.”

I can only imagine what they receive on their public feedback page. :)

Hopefully, the efforts those of you with access to the Bug Reporter have been putting in will help Apple squash this fairly serious bug.

I thought my problem was solved with the reformat as case-sensitive tip, but my iMac is freezing again when a TM backup begins. It's not every backup -- and it had been working fine for a couple of weeks.

I'm just turning TM off for now. Defeats the purpose of automated, incremental backups, but I'm tired of troubleshooting. It's interesting to read how many hours of time, and purchases of new hard drives, have been incurred by TM users.

Yeah, thanks, but I'll stick with SUPER DUPER from now on. It works, and the disk can also be used as a startup disk. This workaround, above, is a bit too "nerdy" for this 83 year-old. (It sounds to me like Apple's new OSX is suffering from an autoimmune disease. Why should it fight itself?) ;-)

Today (16 January) I tried backing up with TM again, but only closing SyncFoldersPro first. This time TM got stuck when 174.9 MB of 5.41 GB had been backed up. I have reported this in Bug Reporter, attaching a sysdiagnose. 

I shall wait for the next MacOS update in the hope that this TM problem will have been solved, and in the meantime shall rely on Carbon Copy Cloner. But it might be worth trying to disable System Security Protection before running TM as suggested by someone else in this string. Or even starting up in Safe Mode?

I have this problem too and have read various "solutions" - involving deleting files from the library and excluding items from backups, all of which I've tried and none of which have worked. I STILL cannot back up to time machine with Mojave. It looks like Apple have addressed this problem in recent weeks or am I wrong? If anyone can suggest a definitive solution to this problem I'd appreciate it.

Not fixed yet. In fact, while I was typing this reply, my system completely froze and I was forced to do a hard reboot. I forgot that I had turned Time Machine back on to test something and didn't turn it off. I was able to complete a manual backup, but automatic backups are still causing random freezes for me.

Maybe the Time Machine developers were all repurposed to work on Apple's autonomous driving efforts...

Updated yesterday to 10.14.2 without beeing able to backup via TM, always excluded the sharded folder, added appcleaner exclusion, still doesnt backup, will stop after a few gigs.

And btw - Apple Support removed my earlier post because i was criticizing Apple´s quality change over the last 21 years.

Deinstalled App Cleaner manually from Applications and Library containers, restarted and after backing up 6 mb from 250 gb it stopped working with the well known error log. Will Apple pay me for using my precious time trying to fix their problem? ;)

No! I updated to 10.14.3, erased the external 1TB USB3 disc and started a (first) backup (130 GB to backup).

It took the whole night and in the morning the backup finished, but the backup disc was full !!!

Only 4.81 MB !! available!

No more (incremental) backups possible!

The TM **** still doesn't work!!!

Unbelievable!

Updating to 10.14.3 did not help me. The backup job starts, thinks for a long time, actually writes for about 20 MB, then stops. The error message says that it could not backup to the backup drive, which is the TM.

Hello mensadoc,

Why do you use Norton or any other security software? Many writers have said that security software causes problems. I ask only because I really want to understand and you seem knowledgeable. Thank you.