Time Machine initial backup fails OS 10.5 with no reason but 'bus error'

I ran into an error on the last system update and had to go back to Leopard 10.5 just to see my stuff. I managed to move my home directory into the newly installed system and all my files are intact. Now I'm trying to get a Time Machine backup before I proceed (my initial mistake was not keeping up with them in the first place).
I had some trouble early on and at one point decided to reformat the external drive (a Fantom Drives GreenDrive, usb, 500Gb). I formatted as Mac OS Extended (Journaled) as recommended, no partitions, and then tried my first initial Time Machine backup.
It predictably spent a long time 'preparing...' and I followed along in the system log. Eventually, the copying began but early on (within the first 45 min) the backup failed with almost no indications in the log as to why. I've pasted the system log below.
One thought I had was that it was weird that there was an automatic request for backup at 12:36:54. I also included the CrashReport, but I can't make any sense out of it.
any ideas?
System log:
6/23/10 11:57:30 PM /System/Library/CoreServices/backupd[1190] Backup requested by user
6/23/10 11:57:30 PM /System/Library/CoreServices/backupd[1190] Starting standard backup
6/23/10 11:57:30 PM /System/Library/CoreServices/backupd[1190] Backing up to: /Volumes/Deep Green/Backups.backupdb
6/24/10 12:15:13 AM /System/Library/CoreServices/backupd[1190] No pre-backup thinning needed: 173.94 GB requested (including padding), 453.71 GB available
6/24/10 12:15:13 AM /System/Library/CoreServices/backupd[1190] MDBackupBegin() returned result (910) > 0, waiting
6/24/10 12:36:54 AM /System/Library/CoreServices/backupd[1190] Backup requested by automatic scheduler
6/24/10 12:42:17 AM ReportCrash[1431] Formulating crash report for process backupd[1190]
6/24/10 12:42:18 AM com.apple.launchd[1] (com.apple.backupd[1190]) Exited abnormally: Bus error
6/24/10 12:42:24 AM ReportCrash[1431] Saved crashreport to /Library/Logs/CrashReporter/backupd2010-06-24-004204dylan-boyds-macbook.crash using uid: 0 gid: 0, euid: 0 egid: 0
CrashReport:
Process: backupd [1190]
Path: /System/Library/CoreServices/backupd
Identifier: backupd
4 backupd 0x00007525 0x1000 + 25893
5 backupd 0x00002332 0x1000 + 4914
8 backupd 0x00015028 0x1000 + 81960
9 backupd 0x0000ea64 0x1000 + 55908
10 backupd 0x00008bfe 0x1000 + 31742
11 backupd 0x00004c10 0x1000 + 15376
12 backupd 0x000057b8 0x1000 + 18360
0x1000 - 0x3dffb backupd ??? (???) <f50411bdb241b61699aa81b2f3dfb7d1> /System/Library/CoreServices/backupd

I should have added that I've been through about half a dozen sites (including sanctioned apple sites) and their recommendations for getting Time Machine to work properly. I did format the drive once (with extended journaled format and GUID partition scheme, but I didn't zero it out. I'm trying that now and I'll try TM again in about 4 hours.
This morning I tried turning Time Machine's automatic backups off (moved the slider to off in the preferences pane) and manually started a backup (right-clicking the TM icon in the dock and selecting "Backup Now"). It ran further along than before, but stopped again. This time, it gave an error, and I've pasted the log below. I looked but didn't find much helpful on "error 11."
system log:
Jun 24 09:14:08 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Backup requested by user
Jun 24 09:14:08 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Starting standard backup
Jun 24 09:14:08 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Backing up to: /Volumes/Deep Green/Backups.backupdb
Jun 24 09:14:08 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Event store UUIDs don't match for volume: Macintosh HD
Jun 24 09:14:08 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|
Jun 24 09:47:13 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: No pre-backup thinning needed: 175.31 GB requested (including padding), 453.11 GB available
Jun 24 10:13:46 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Error: (-36) SrcErr:YES Copying /Previous Systems.localized/2010-06-22_2236/Applications/iPhoto.app/Contents/Resources/Po intOfInterest.db to (null)
Jun 24 10:13:46 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Error: (-36) SrcErr:NO Copying /Previous Systems.localized/2010-06-22_2236/Applications/iPhoto.app/Contents/Resources/Po intOfInterest.db to /Volumes/Deep Green/Backups.backupdb/Dylan Boyd’s MacBook/2010-06-23-231048.inProgress/E3294B86-62B0-4ABF-9B2B-F5D46B82736D/Macin tosh HD/Previous Systems.localized/2010-06-22_2236/Applications/iPhoto.app/Contents/Resources
Jun 24 10:13:46 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Stopping backup.
Jun 24 10:13:46 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Error: (-8062) SrcErr:NO Copying /Previous Systems.localized/2010-06-22_2236/Applications/iPhoto.app/Contents/Resources/Po intOfInterest.db to /Volumes/Deep Green/Backups.backupdb/Dylan Boyd’s MacBook/2010-06-23-231048.inProgress/E3294B86-62B0-4ABF-9B2B-F5D46B82736D/Macin tosh HD/Previous Systems.localized/2010-06-22_2236/Applications/iPhoto.app/Contents/Resources
Jun 24 10:13:57 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Copied 13360 files (1.5 GB) from volume Macintosh HD.
Jun 24 10:13:57 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Copy stage failed with error:11
Jun 24 10:14:03 dylan-boyds-macbook /System/Library/CoreServices/backupd[444]: Backup failed with error: 11

Similar Messages

  • Time Machine reports, "backup failed." What do I do?

    Time Machine reports, "backup failed." What should I do?

    See if Pondini's great site helps...
    http://Pondini.org/TM/Troubleshooting.html

  • On imac 10.6.8 using current version of Aperture.  How can I access the Aperture Library  on my external hard drive that I use with time machine for backup?  I can only access the application but not the library..

    On imac 10.6.8 using current version of Aperture.  How can I access the Aperture Library  on my external hard drive that I use with time machine for backup?  I can only access the application but not the library..

    Go into Time Machine (the program not the bundle on the extrnal disk) and using Time Machine's browser go to the Folder where the library lives. You could look in the library bundle in Time Machine but that won't really tell you much,
    If you want to make sure it truely has backed up your library you will need to restore it and open the restored library with Aperture.
    If all this still has you confused you need to read up on Time Machine in order to get a feel for how it works, for what it is doing and for how to restore files from it.

  • FYI: No Sleep during Time Machine initial backup

    Just an FYI - I noticed that during the first Time Machine full backup, the computer does not go to sleep.
    I would also assume that if you computer is asleep, it will not wake for each hourly backup.

    Hi, and welcome to the forums.
    You need to know that backing-up that way is "iffy" and +*not supported by Apple.+* See Using Time Machine with an Airport Extreme Air Disk (or use the link in *User Tips* at the top of this forum).
    Kernel panics are usually caused by hardware problems, but can be software.
    Disconnect all peripherals, except keyboard and mouse. Reconnect one at a time to see if you can find the culprit.
    If that's no help, run the Apple Hardware Test: http://support.apple.com/kb/HT1509
    And perhaps a heavy-duty memory test, such as the free Rember: http://www.kelleycomputing.com/
    More kernel panic info:
    Apple Support - About kernel panic messages
    Mac OS X Kernel Panic FAQ
    The X Lab - Resolving Kernel Panics
    Apple Developer - Technical Note TN2063: Understanding and Debugging Kernel Panics
    Tutorial: Avoiding and eliminating Kernel panics
    |
    If you still want to back up via the Airport, the first backup will be much faster if you connect via Ethernet.

  • Time Machine only shows "Today". Can't access old stuff but no errors

    Maybe I am missing something but I plugged in an external HD and the first time machine went well. It does its thing each hour but when I go into time machine all I see is Today/Now with no ability to restore anything or anything older than today. I know it has older stuff since yesterday it said the same thing and it has taken the proper space on my external hard drive.

    It does sound like you're using a networked attached TM backup device wrt the disk image mounting on your Desktop. This is the case when people have hacked the system to be able to employ a USB2 device to their AirPort Extreme Base Station (AEBS).
    In the case of the dmg image - when it's mounted via doing a Back Up Now quickly invoke the TM browser and you should immediately see all the TM backups/snapshots. If you keep the TM browser active even after the Back Up Now has completed then browsing will still be possible. However, once you terminate the TM browser you will be back to not being able to use it unless you do another Back Up Now. This is the rather cumbersome method that exists today with networked and AEBS connected USB2 devices, and clearly one of the reasons why Apple pulled the use of networked and AEBS connected Volumes from their web site one week before releasing Leopard GM on Oct 26.

  • Time Machine. Backup failed with error code: 21

    Hi,
    I recently upgraded to Leopard 10.5.4 mainly for the time machine backup. I'm using a DNS-323 in a RAID1 configuration as the TM backup drive. Also I have the DNS-323 connected to my Airport Extreme through the ethernet to give NAS ability to my home network.
    After much hunting around the forums I got the sparsebundle created and copied to the DNS-323 share volume. See http://www.flokru.org/2008/02/29/time-machine-backups-on-network-shares-in-leopa rd/ My thanks to flokru.
    However, TM is still not working. The console messages have the following:
    Network mountpoint /Volume/Volume_1 not owned by backupd... remounting
    Network volume mounted at /Volume/Volume11
    Failed to mount disk image /Volume/Volume1_1/MacBook001b6334c307.sparebundle
    Backup failed with error: 21
    It would appear this error lies in the way TM is trying to mount the volume, specifically that Volume_1, the DNS-323 volume name, is not owned by TM. TM then tries to create a new volume, Volume11 and stick the sparebundle on it.
    Is there a way of making TM "own" the volume, Volume_1?
    Has anybody else seen this error or better yet, got a fix for it?

    James,
    It would appear this error lies in the way TM is trying to mount the volume, specifically that Volume_1, the DNS-323 volume name, is not owned by TM. TM then tries to create a new volume, Volume11 and stick the sparebundle on it.
    Is there a way of making TM "own" the volume, Volume_1?
    Actually, it is not TMs failure to mount the volume that is causing your failure to backup. I have received the same Console message using a Time Capsule. However, Time Machines' attempt to 'remount' the volume always succeeds and the backup goes through. That appears not to be your experience, but it is NOT because the volume is not being mounted. It is.
    *Mount Point Conflict (TMDisk-1)*
    NOTE: the following distinguishes “network drive” (the physical hard disk) from “disk image” (the sparsebundle file TM uses to backup to).
    First of all, I am convinced that the second mount point that is created (in your case Volume11) is due to the fact that you already had the network drive mounted on your desktop at the time of the attempted backup. Was that the case?
    When you manually mount a network drive the system creates a mount point in the /Volumes folder (Let’s call it TMDisk ). While that exists any attempt by Time Machine to mount the same disk will created a second mount point ( TMDisk-1 )
    Nevertheless, as I have observed, this doesn't seem to prevent backups from taking place successfully, at least on the Time Capsule. And according to your Console logs it appears that your volume is being ‘remounted’ successfully.
    *”The Backup Disk Image Could Not Be Mounted”*
    The real issue is Time Machines' failure to mount the disk image (sparsebundle) contained on your network drive.
    +Failed to mount disk image /Volume/Volume1_1/MacBook001b6334c307.sparebundle+
    +Backup failed with error: 21+
    More often than not this is due to having the Time Machine backup disk image (sparsebundle) mounted on your desktop during a backup attempt.
    Eject the backup disk image (sparsebundle) by either clicking the little Eject icon to the right of the disk image in the Finders’ Sidebar, or Ctrl-Click the drive icon on the desktop and select “Eject” from the contextual menu. Now try backing up again or launching Time Machine to view previous backups.
    For more information, see an article on this here:
    [http://discussions.apple.com/thread.jspa?threadID=1715977]
    Alternatively, a backup disk image can fail to mount if there is a problem with your computer name.
    *Proper Computer Name* #
    Make sure your computer has a proper name. Go to System Preferences --> Sharing. Time Machine needs to differentiate your computer from others on your network (i.e. "Bills MacBook" or "Office iMac"). If the "Computer Name" field is blank, create a name. Realize that if this step is necessary, you will likely have to start the Time Machine backup process over again and do another full initial backup.
    According to THIS article [http://support.apple.com/kb/TS1760], Time Machine may experience problems if your computer name includes certain characters. Make sure the computer name only includes ASCII characters from the following set.
    (0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ)
    Once a change in the computer name occurs, you should stop and restart Sharing on the affected computer. Uncheck and then recheck Sharing in the Services list on the left.
    Let me know if any of this helps.
    Cheers!

  • Time machine - Last backup failed - how i fixed it...

    I woke up this morning to see that time machine had failed to backup. It has been a couple of days since installing 10.5.3, so I'm not sure if it's related to the update or if it's just the way that time machine works.
    I ran diskwarrior, www.alsoft.com
    and it came back with more file structure errors than i have ever seen on a hard drive! instead of tell you, here is an picture.
    needless to say, once i replaced the directory time machine began working again, and it's way faster than it ever has been before.

    I promise this thread is not an ad for diskwarrior
    it has just saved my *** so many times that i wanted to share the information. apple disk utility does not do as good of a job at repairing HFS+.
    here is a link to get latest version (4.1 for 10.5)...
    http://thepiratebay.org/tor/4000433/DiskWarrior4.1___serial_for_Leopard10.5

  • Time Machine Initial Backup - Partial Only

    I have a WD external drive that was erased by Time Machine. But the initial backup stops at about 1 gig of data (out of the 38 gig that is there). Then schedules another backup in an hour. Why doesn't

    Hi!
    Time Machine has worked for several months now but since yesterday i have the same issue. After reformatting the backup disk (file system was corrupt) time machine works but stops backing up after about 100MB.
    Cheers
    Silvan

  • Time Machine initial backup

    I just used Time Machine for the first time.  I expected it to backup about 35GB (and it estimated a full backup at 35.54GB) but it actually backed up 30.06GB.  I looked at the Options screen and the only thing listed as "do not backup" is my backup drive which it lists as 2.52GB.  Any thoughts on why the initial full backup does not seem to be the size expected?

    The comment from Steve Holton i think has your answer on https://discussions.apple.com/message/7884490?messageID=7884490
    In short there are some things skipped by Time Machine have a look at /Library/Preferences/com.apple.TimeMachine.plist in the ExcludeByPath

  • Kernel panic during Time Machine initial backup

    Hi all!
    I've got the Airport Extreme 2009 and external WD My Passport 320GB attached to it via USB and shared to the LAN. While initial backup with Time Machine via WiFi my MacBook Pro gets kernel panic.
    My Passport has been formatted as Extended Journaled Case-sensitive file system.
    Did anybody stumble upon such problem?

    Hi, and welcome to the forums.
    You need to know that backing-up that way is "iffy" and +*not supported by Apple.+* See Using Time Machine with an Airport Extreme Air Disk (or use the link in *User Tips* at the top of this forum).
    Kernel panics are usually caused by hardware problems, but can be software.
    Disconnect all peripherals, except keyboard and mouse. Reconnect one at a time to see if you can find the culprit.
    If that's no help, run the Apple Hardware Test: http://support.apple.com/kb/HT1509
    And perhaps a heavy-duty memory test, such as the free Rember: http://www.kelleycomputing.com/
    More kernel panic info:
    Apple Support - About kernel panic messages
    Mac OS X Kernel Panic FAQ
    The X Lab - Resolving Kernel Panics
    Apple Developer - Technical Note TN2063: Understanding and Debugging Kernel Panics
    Tutorial: Avoiding and eliminating Kernel panics
    |
    If you still want to back up via the Airport, the first backup will be much faster if you connect via Ethernet.

  • Very slow Time Machine Initial Backup to Leopard Server on Xserve with RAID

    I'm having trouble backing up my iMac to my Xserve running leopard with dual drobos as my time machine drives
    So here is the setup:
    Server: Xserve (dual quad 2.8 xeons) backing up to Drobo array with 4x1tb drives running (dual drobos on server) fully patched 10.5 server with 16gb/RAM (showing 8gb free)
    Network: 1gbs via catalyst switches on essentially unloaded segment (a couple of folks reading emails)
    Source Machine: iMac 24" 3.06 Core2Duo with 8gb RAM
    Most important fact: nothing has changed on the server (other than usual updates)
    Doing an initial backup of the iMac over the network, and getting peak of about 100Kb/sec, and much of the time it seems to have stalled. Given that the machine has like 230GB to backup, this is going to take a real long while. When I query activity monitor on both the client and Xserve, they are both virtually idle with all resources free (lots of free RAM/Disk/CPU). Neither machine is running any apps right now during the test (other than filesharing, but nobody is using as the office is empty today)
    Now one thing to note is the staggering number of files (iPhoto library is ~120gb and holds over 500,000 files [faces?]) giving a total of 1.2M files.
    As a point of testing, copied a 500mb quicktime movie to same partition, took <5 seconds.

    Should I be concerned that the TimeMachineBuddy widget is producing tons of error messages in the system console (and doesn't seem to work)
    8/4/09 3:34:01 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:01.438 DashboardClient[381:10b] com.bluedog.tmwidget.TimeMachine: ERROR: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma
    8/4/09 3:34:01 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:01.439 DashboardClient[381:10b] (com.bluedog.tmwidget.TimeMachine) file:///Users/henryhbk/Library/Widgets/Time%20Machine%20Buddy.wdgt/Utilities.js: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma (line: 33)
    8/4/09 3:34:02 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:02.359 DashboardClient[381:10b] com.bluedog.tmwidget.TimeMachine: ERROR: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma
    8/4/09 3:34:02 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:02.360 DashboardClient[381:10b] (com.bluedog.tmwidget.TimeMachine) file:///Users/henryhbk/Library/Widgets/Time%20Machine%20Buddy.wdgt/Utilities.js: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma (line: 33)
    8/4/09 3:34:02 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:02.620 DashboardClient[381:10b] com.bluedog.tmwidget.TimeMachine: ERROR: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma
    8/4/09 3:34:02 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:02.621 DashboardClient[381:10b] (com.bluedog.tmwidget.TimeMachine) file:///Users/henryhbk/Library/Widgets/Time%20Machine%20Buddy.wdgt/Utilities.js: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma (line: 33)
    8/4/09 3:34:02 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:02.885 DashboardClient[381:10b] com.bluedog.tmwidget.TimeMachine: ERROR: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma
    8/4/09 3:34:02 PM [0x0-0xb00b].com.apple.dock[233] 2009-08-04 15:34:02.885 DashboardClient[381:10b] (com.bluedog.tmwidget.TimeMachine) file:///Users/henryhbk/Library/Widgets/Time%20Machine%20Buddy.wdgt/Utilities.js: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma: Unrecognized message format: Aug 4 14:31:01 Henry-Feldma (line: 33)

  • Time machine initial backup is taking over 3 days

    I have an external network drive which I am trying to back up my MacBook Pro OS X 10.6.8 to using Time Machine.  Why after 2 days is the backup only 40% done?  I know it can take time to set it up but... really?
    I had to start over since it is a laptop computer and I do need to take it with me... but I really can't afford more than 24 hours of keeping it on the network.
    What's the deal?  Thanks!

    https://discussions.apple.com/docs/DOC-4055

  • Time machine initial backup duration

    How long should it take for Time Machine to make it's first full back up of data? I'm 92GB into a save of 496GB, and it's predicting 11 more DAYS of copying before it's done.  I did have to stop it once, but seems to have restarted.  Is this typical, or should I have just reformatted and started over? Or is this the first sign of HD failure somewhere? My HDs is WD connected via USB2, I think. 
    Jack

    How long should it take for Time Machine to make it's first full back up of data? I'm 92GB into a save of 496GB, and it's predicting 11 more DAYS of copying before it's done.  I did have to stop it once, but seems to have restarted.  Is this typical, or should I have just reformatted and started over? Or is this the first sign of HD failure somewhere? My HDs is WD connected via USB2, I think. 
    Jack

  • HT3275 I am backing up my iMac using TIME MACHINE and red FAILED occured stating "unable to complete back up. an error acccured while creating back up folder" can anybody help me pls. =Mochincess

    Backing up Problem: Using time Machine to back up my iMac, and failed occured stating" unable to complete backup. An error occured while creating backup folder. Pls. help....using reformatted WD 2TB Passport

    Hello...
    https://discussions.apple.com/thread/4413173?start=0&tstart=0

  • Time Machine: Latest  Backup: Failed  (Unable to complete backup)

    Unable to complete backup. An error occurred while copying files to the backup volume.
    some messages from the console log:
    6/22/08 6:15:23 kernel disk3s2: 0x23 (UNDEFINED).
    6/22/08 6:15:25 kernel HFS resolvelink: can't find iNode87587
    6/22/08 6:15:26 kernel HFS resolvelink: can't find dir_487832
    6/22/08 6:15:54 /System/Library/CoreServices/backupd[61444] No pre-backup thinning needed: 80.00 GB requested (including padding), 300.19 GB available
    6/22/08 6:15:54 /System/Library/CoreServices/backupd[61444] Waiting for index to be ready (915 > 0)
    6/22/08 6:18:59 mds[39] (Error) DiskStore: Unable to create/find index location
    6/22/08 7:21:27 kernel AirPort: Roam (Beacons Lost)
    6/22/08 7:21:40 /System/Library/CoreServices/backupd[61444] Waiting for index to be ready (915 > 0)
    6/22/08 7:21:42 kernel AirPort: Roam (Beacons Lost)
    6/22/08 8:10:00 com.apple.launchd[1] (0x10d550.cron[62330]) Could not setup Mach task special port 9: (os/kern) no access
    Any ideas?

    robrobrobrob wrote:
    Aug 14 18:33:28 iMac mds[44]: (Error) DiskStore: Unable to create/find index location
    While you got the same type of message as while(fork()) it's not clear to me that they represent the same underlying problem.
    In your case the Time Capsule and the actual Backup seem to mount OK as seen here:
    Aug 14 18:33:20 Robert-Schattners-iMac /System/Library/CoreServices/backupd[301]: Network volume mounted at: /Volumes/Time Capsule
    Aug 14 18:33:25 iMac /System/Library/CoreServices/backupd[301]: Disk image /Volumes/Time Capsule/ iMac_001ff3543f94.sparsebundle mounted at: /Volumes/Backup of iMac
    Aug 14 18:33:25 iMac /System/Library/CoreServices/backupd[301]: Backing up to: /Volumes/Backup of iMac/Backups.backupdb
    What follows indicates to me that the backup proceeded. Once it decides to do a deep traversal,it take s Loooonng time.
    Aug 14 18:33:31 iMac /System/Library/CoreServices/backupd[301]: Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
    What happened after this?

Maybe you are looking for