"File Not Found (-43)"

[mikehalloran]

OK, so do APFS Snapshots record other volumes on the drive regardless of their content? (with or without an OS version)

The startup volume, yes. I just did an instant Restore of some files that were accidentally deleted thanks to a really weird bug.

APFS Snapshots never captured attached drives or additional Volumes but they're backed up in Time Machine unless excluded in Options. That Restore works as it always did sorta… Enter Time Machine is gone from the menu but the replacement menu is easy to figure out but Whyyyy Apple???

The weird bug shows duplicate files in Find File — except that they're not. Trash one and Empty, they all go away. Yikes! Fortunately, Time Machine lets me recover immediately if on the System Drive, a bit longer if not.

[Rick Cornish]

Well, FWIW—I turned Time Machine auto-saves back on yesterday and got the error about an hour later.

Perhaps this isn't monocausal, but thus far, my observations are that the error doesn't happen when I turn off automatic TM backups and it starts happening again when I turn them back on.

I did get a (kind of) response to my MOTU Support Ticket (I guess they no longer call them "TechLinks") a couple days ago, merely asking me if it's still happening. I replied and crickets since then.

Continuing to monitor.

[mikehalloran]

What does the Activity Monitor show? Something should turn red right before the message appears. If it does, you should be able to drill down until the culprit reveals itself.

I’ve not seen -43 for two weeks now.

[James Steele]

Well, FWIW—I turned Time Machine auto-saves back on yesterday and got the error about an hour later.

Perhaps this isn't monocausal, but thus far, my observations are that the error doesn't happen when I turn off automatic TM backups and it starts happening again when I turn them back on.

You know, there could be more to it than that, but if it fixes it for you, keep doing it. If turning around three times and throwing salt over my shoulder made it go away—I don't care. I'd keep doing that.

I haven't run into this issue myself, but I haven't been heavily involved in a project and may just not have encountered it. And although I know that in theory, there's nothing wrong with Time Machine running a backup while I'm working in DP, I don't like the *idea*. Like I said, I haven't been hot and heavy into a project lately, but I feel that when I am, I might manually run a Time Machine backup prior to a session, then turn it off, and rely on DP autosave until the session is over and then do another Time Machine backup.

[EMRR]

OK, just happened first time in forever. While recording. Wouldn't dismiss, couldn't stop transport. 'Saved as', got control back, file was recording the whole time, nothing lost.

[mikehalloran]

OK, just happened first time in forever. While recording. Wouldn't dismiss, couldn't stop transport. 'Saved as', got control back, file was recording the whole time, nothing lost.

Yep. You can Save as DP is running, thank goodness.

Was it the first build of 9 or 10 when you couldn't? What a pain that was till MOTU fixed it.

[mikehalloran]

Again, there are two problems: Sometimes, when saving manually, my only option is Save As. The workaround is to find the original Project. let it overwrite and copy all the audio files. -43 usually does not show up.

When -43 shows up, it's when AutoSave is attempting to write but is unsuccessful. Since the workaround is identical, I'm certain that the cause ie the same.

Although MOTU is acting like this is brand new, It's been going on awhile. Thanks to James's recent work, I was able to search and find these threads with -43 in them (I ignored -7, -193 and -10). I just now uploaded this to my Techlink:

2008  version? OS?
https://www.motunation.com/forum/viewtopic.php?t=28320

2015 DP 8 / Yosemite
https://www.motunation.com/forum/viewtopic.php?t=59454

2015 Version? / OS?
https://www.motunation.com/forum/viewtopic.php?p=497163

2019 DP 10.1 / Mojave
https://www.motunation.com/forum/viewtopic.php?t=66377

2020  DP 10 / Catalina
https://www.motunation.com/forum/viewtopic.php?t=67636

2021 DP 11 / Monterey?
https://www.motunation.com/forum/viewtopic.php?t=68998

2023 Other recent thread DP 11.21 / Monterey 10.4.5
https://www.motunation.com/forum/viewtopic.php?t=72959

2023 Current thread DP 11 / Monterey/Ventura
https://www.motunation.com/forum/viewtopic.php?t=72965

I suspect that it may be one of the many daemons running in the background from Adobe, Microsoft, plug-in makers, licensing agents etc. Unfortunately, except for the crash below, I've not been able to find anything.

I still don't believe that Time Machine has anything to do with this—not enough of us are affected for one thing. I'd not seen it in a month and my TM backups are unchanged.

Until yesterday, it had not caused a crash but I saw this on startup. IIt would surprise me if this was the culprit.

[daniel.sneed]

Well, FWIW—I turned Time Machine auto-saves back on yesterday and got the error about an hour later. [...] Perhaps this isn't monocausal, but thus far, my observations are that the error doesn't happen when I turn off automatic TM backups and it starts happening again when I turn them back on. [...]

Thanks Rick for pointing us to Time Machine.
I disabled automatic TM backups, and no more *File Not Found Error -43* here.
Motunation is such a great place to be!

[mikehalloran]

As of Ventura, the MacOS is saved in a separate Volume now. APFS Snapshots does not record this volume. Otherwise, it works the same as before.

OK, so do APFS Snapshots record other volumes on the drive regardless of their content? (with or without an OS version)

I was told that part is unchanged but my Ventura drive has only one volume these days. I can try calling Apple tomorrow to confirm.

I’ve done a few APFS Snapshots rollbacks without incident when I was testing something that I don’t recall (in a dentist chair at the moment).

The only boot drive I have with multiple volumes is a Mojave SSD. I can test this but it takes a few days that I’ll have beginning tomorrow.

[bayswater]

As of Ventura, the MacOS is saved in a separate Volume now. APFS Snapshots does not record this volume. Otherwise, it works the same as before.

OK, so do APFS Snapshots record other volumes on the drive regardless of their content? (with or without an OS version)

I was told that part is unchanged

Does that mean, as far as you know, macOS 12.6 will record snapshots on other volumes on the same disk? E.g., if you have a 10.14 and at 12.6 startup volume on one internal SSD, when 12.6 is running it will create snapshots of the 10.14 volume?

[mikehalloran]

OK, so do APFS Snapshots record other volumes on the drive regardless of their content? (with or without an OS version)

I was told that part is unchanged

Does that mean, as far as you know, macOS 12.6 will record snapshots on other volumes on the same disk? E.g., if you have a 10.14 and at 12.6 startup volume on one internal SSD, when 12.6 is running it will create snapshots of the 10.14 volume?

Good question. I tried getting an answer from Apple but couldn't find anyone who actually knew.

It's easy to test. Note the time. Run Back Up Now from the TM menu. Put a dummy file on the volume you aren't booting from—don't do any other work. Run Back Up Now again, perhaps a couple more times. Every time you do this, the first thing that TM does is create an APFS Snapshot.

Now shut down, boot holding the Command r keys. Restore to that backup from before you created that dummy file. It should now be gone.

The reason the same test will take a few days for me is that I rarely boot from my Mojave drive and never long enough for a TM backup. It will take a few days before I have the time to do the same thing. Otherwise, Mojave and Monterey behave the same (as does High Sierra, Catalina and Big Sur).

[bayswater]

Good question. I tried getting an answer from Apple but couldn't find anyone who actually knew.

It's easy to test.

I’ll try it out.

[HCMarkus]

I run TM continuously and have not run into this issue.

[mikehalloran]

I run TM continuously and have not run into this issue.

Likewise, I never run without Time Machine on and am convinced it has absolutely nothing to do with this.

I've not seen -43 in months — but it knows that I have the Activity Monitor open in another monitor and am waiting to drill down if it reappears.

[mikehalloran]

…
Does that mean, as far as you know, macOS 12.6 will record snapshots on other volumes on the same disk? E.g., if you have a 10.14 and at 12.6 startup volume on one internal SSD, when 12.6 is running it will create snapshots of the 10.14 volume?

I finally have an answer.

I was setting up a recent Intel MBP for a friend whose 2012 MBPs died (those 2012 2.5" HDDs were horrible). Since her husband's had a few 32 bit apps still, I set this one up with a Ventura Volume for her and a Mojave Volume in case they ever needed to access it.

When it came time to set up Time Machine, I noticed that much of the Mojave Volume was sitting in the Options window meaning that they would be excluded. I clicked on each line and hit the minus sign - at the bottom of the window till it was empty.

After running Time Machine a few times, I booted into the Recovery Partition and went to Restore from Time Machine. Logging into the backup disk, I saw APFS Snapshots for each volume — surprising as I ran TM from the Ventura Volume only.

I have not tried a System Restore but I now know that it can be done.