Time Machine starts normally, then stalls and freezes iMac

Hello.
Time Machine always worked fine on this system.
Now-it starts to back up, then freezes after about 45 mb. When this happens, the toolbar at the top of the screen ("File", etc.) disappears, I can't run any other functions, and have to push the power button to crash the system.
I have:
--deleted the time machine preferences file
--turned off Virus Barrier background scanning
--tried from scratch with a new back-up disc (same problem)
--done all Software Updates
--repaired permissions
--booted up from the OS X disc, and "repaired disc" on the hard drive.
--deleted "in progress" files on the back-up disc, and started over.
I have seen others with what sounds like a similar problem, but I can't find a suitable solution among the discussions.
Any help much appreciated.
Thank you.

On the MacBook, there was a specific file ("developer pckg") that was crashing back-up. I deleted the file, and I'm back in business.
In the iMac, things seem more complicated, and additional attempts at back-up not only stall--they also freeze the whole computer.
__At the start of the back-up the log reads:__
Oct 5 11:20:35 Susies-Magnificent-New-iMac-2 /System/Library/CoreServices/backupd[259]: Backup requested by user
Oct 5 11:20:35 Susies-Magnificent-New-iMac-2 /System/Library/CoreServices/backupd[259]: Starting standard backup
Oct 5 11:20:35 Susies-Magnificent-New-iMac-2 /System/Library/CoreServices/backupd[259]: Backing up to: /Volumes/Master Back-Up/Backups.backupdb
Oct 5 11:20:36 Susies-Magnificent-New-iMac-2 /System/Library/CoreServices/backupd[259]: Event store UUIDs don't match for volume: Macintosh HD
Oct 5 11:20:36 Susies-Magnificent-New-iMac-2 /System/Library/CoreServices/backupd[259]: Backup content size: 110.6 GB excluded items size: 3.9 MB for volume Macintosh HD
Oct 5 11:20:36 Susies-Magnificent-New-iMac-2 /System/Library/CoreServices/backupd[259]: No pre-backup thinning needed: 132.93 GB requested (including padding), 263.08 GB available
_*Then, there is a VERY long string of "bad alias" messages, and then the back-up freezes at 45.2 mb:*_
The back-up doesn't actually cancel itself--I did that.
The last several lines before the freeze at 45.2 mb are:
Oct 5 11:21:37 Susies-Magnificent-New-iMac-2 com.apple.backupd[259]: LaunchServices: bad alias at 0x2201e84, size 13392, CSStore size 1851417683
Oct 5 11:21:37 Susies-Magnificent-New-iMac-2 com.apple.backupd[259]: LaunchServices: bad alias at 0x2201fe0, size 14392, CSStore size 1932476755
Oct 5 11:21:37 Susies-Magnificent-New-iMac-2 com.apple.backupd[259]: LaunchServices: bad alias at 0x21fd800, size 19561, CSStore size 793999731
Oct 5 11:21:37 Susies-Magnificent-New-iMac-2 com.apple.backupd[259]: LaunchServices: bad alias at 0x21fd970, size 11896, CSStore size 1700881516
Oct 5 11:21:37 Susies-Magnificent-New-iMac-2 com.apple.backupd[259]: LaunchServices: bad alias at 0x21fdbbc, size 29299, CSStore size 1667593007
Oct 5 11:21:37 Susies-Magnificent-New-iMac-2 com.apple.backupd[259]: LaunchServices: bad alias at 0x21fde98, size 30050, CSStore size 1869967971
Oct 5 11:21:37 Susies-Magnificent-New-iMac-2 com.apple.backupd[259]: LaunchServices: bad alias at 0x21fdfa4, size 28263, CSStore size 2004299383
Oct 5 11:21:37 Susies-Magnificent-New-iMac-2 com.apple.backupd[259]: LaunchServices: bad alias at 0x21fe0d4, size 30050, CSStore size 1702326130
Oct 5 11:21:41 Susies-Magnificent-New-iMac-2 com.apple.backupd[259]: LaunchServices: bad alias at 0x21fdaf8, size 29539, CSStore size 1668246831
Oct 5 11:22:11 Susies-Magnificent-New-iMac-2 com.apple.backupd[259]: LaunchServices: bad alias at 0x21fdaf8, size 29539, CSStore size 1668246831
Oct 5 11:23:40 Susies-Magnificent-New-iMac-2 /System/Library/CoreServices/backupd[259]: Copied 2 files (45.2 MB) from volume Macintosh HD.
Oct 5 11:23:45 Susies-Magnificent-New-iMac-2 /System/Library/CoreServices/backupd[259]: Backup canceled.
THANKS for having a look!

Similar Messages

Time machine starts but then freezes during backup

Time machine has been working well using a LaCie external hard drive. However when I start Time Machine, it freezes at 12kB backup. Any ideas?

Hello
I've the same probleme using time machine with my imac under mountain lion : it freezes the computer and i need to reboot it
here the log :
Nov 28 20:01:55 iMac.local com.apple.backupd[3136]: Starting automatic backup
Nov 28 20:01:55 iMac.local com.apple.SecurityServer[15]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [11] for authorization created by '/usr/libexec/UserEventAgent' [11] (100012,0)
Nov 28 20:01:55 iMac.local com.apple.backupd[3136]: Attempting to mount network destination URL: afp://;AUTH=No%20User%20Authent;[email protected]/Data
Nov 28 20:01:55 iMac.local com.apple.backupd[3136]: Mounted network destination at mount point: /Volumes/Data using URL: afp://;AUTH=No%20User%20Authent;[email protected]/Data
Nov 28 20:01:55 iMac.local CleanMyMacHelperTool[3140]: Mounted devices (
Nov 28 20:01:55 iMac.local CleanMyMacHelperTool[3140]: CleanMyMacHelperTool started as volume cleaner with cleanTrashes 1 cleanMacOSJunk 1 cleanWinJunk 1
Nov 28 20:01:55 iMac.local CleanMyMacHelperTool[3140]: Mounted devices (
Nov 28 20:01:55 iMac.local CleanMyMacHelperTool[3140]: Wont clean mounted devices.
Nov 28 20:01:55 iMac.local CleanMyMacHelperTool[3140]: CleanMyMacHelperTool exited...
Nov 28 20:01:55 iMac kernel[0]: ASP_TCP asp_tcp_usr_control: invalid kernelUseCount 0
Nov 28 20:01:55 iMac kernel[0]: AFP_VFS afpfs_mount: /Volumes/Data, pid 3138
Nov 28 20:01:55 iMac kernel[0]: AFP_VFS afpfs_mount : succeeded on volume 0xffffff80706ff008 /Volumes/Data (error = 0, retval = 0)
Nov 28 20:01:55 iMac kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=3140[CleanMyMacHelper] clearing CS_VALID
Nov 28 20:02:05 iMac.local AddressBookSourceSync[3135]: *** -[IADomainCache init]: IA domains cache is out of date.
Nov 28 20:02:05 iMac.local mdworker[3145]: Unable to talk to lsboxd
Nov 28 20:02:05 iMac.local sandboxd[3146] ([3145]): mdworker(3145) deny mach-lookup com.apple.ls.boxd
Nov 28 20:02:06 iMac kernel[0]: Sandbox: sandboxd(3146) deny mach-lookup com.apple.coresymbolicationd
Nov 28 20:02:06 iMac.local AddressBookSourceSync[3135]: -[ABPerson valueForProperty:com.apple.Messages.FontSize] - unknown property. This warning will be displayed only once per unknown property, per session.
Nov 28 20:02:06 iMac.local AddressBookSourceSync[3135]: -[ABPerson valueForProperty:com.apple.Messages.FontColor] - unknown property. This warning will be displayed only once per unknown property, per session.
Nov 28 20:02:07 iMac.local AddressBookSourceSync[3135]: -[ABPerson valueForProperty:com.apple.Messages.BalloonColor] - unknown property. This warning will be displayed only once per unknown property, per session.
Nov 28 20:02:07 iMac.local AddressBookSourceSync[3135]: -[ABPerson valueForProperty:com.apple.Messages.FontFamily] - unknown property. This warning will be displayed only once per unknown property, per session.
Nov 28 20:02:11 iMac.local com.apple.SecurityServer[15]: Succeeded authorizing right 'system.hdd.smart' by client '/Library/Application Support/iStat local/iStatLocalDaemon' [62] for authorization created by '/Library/Application Support/iStat local/iStatLocalDaemon' [62] (B,0)
Nov 28 20:02:25 --- last message repeated 1 time ---
Nov 28 20:02:25 iMac kernel[0]: jnl: disk3s2: replay_journal: from: 9666560 to: 21950464 (joffset 0x3a2b000)
Nov 28 20:02:42 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 304 wr: 304 q_size: 1024 flags: 0x1
Nov 28 20:02:50 iMac kernel[0]: jnl: disk3s2: journal replay done.
Nov 28 20:02:50 iMac.local CleanMyMacHelperTool[3168]: Mounted devices (
        "/Volumes/Copies de sauvegarde Time machine"
Nov 28 20:02:50 iMac.local CleanMyMacHelperTool[3168]: DiskUtilities (
        "com.apple.finder",
        "com.twitter.twitter-mac",
        "com.apple.iChat",
        "org.mozilla.firefox",
        "org.videolan.vlc",
        "com.microsoft.Powerpoint",
        "com.apple.Notes",
        "com.apple.mail"
    ) diskUtilityIsRunning 0
Nov 28 20:02:50 iMac kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=3168[CleanMyMacHelper] clearing CS_VALID
Nov 28 20:02:50 iMac.local fseventsd[47]: event logs in /Volumes/Copies de sauvegarde Time machine/.fseventsd out of sync with volume. destroying old logs. (3435 26 7388)
Nov 28 20:02:50 iMac.local CleanMyMacHelperTool[3168]: Wont clean /Volumes/Copies de sauvegarde Time machine because it's Time Machine Volume
Nov 28 20:02:50 iMac.local CleanMyMacHelperTool[3168]: CleanMyMacHelperTool started as volume cleaner with cleanTrashes 1 cleanMacOSJunk 1 cleanWinJunk 1
Nov 28 20:02:50 iMac.local CleanMyMacHelperTool[3168]: Mounted devices (
        "/Volumes/Copies de sauvegarde Time machine"
Nov 28 20:02:50 iMac.local CleanMyMacHelperTool[3168]: DiskUtilities (
        "com.apple.finder",
        "com.twitter.twitter-mac",
        "com.apple.iChat",
        "org.mozilla.firefox",
        "org.videolan.vlc",
        "com.microsoft.Powerpoint",
        "com.apple.Notes",
        "com.apple.mail"
    ) diskUtilityIsRunning 0
Nov 28 20:02:50 iMac.local CleanMyMacHelperTool[3168]: Wont clean /Volumes/Copies de sauvegarde Time machine because it's Time Machine Volume
Nov 28 20:02:50 iMac.local CleanMyMacHelperTool[3168]: Wont clean mounted devices.
Nov 28 20:02:50 iMac.local CleanMyMacHelperTool[3168]: CleanMyMacHelperTool exited...
Nov 28 20:02:51 iMac.local com.apple.backupd[3136]: Disk image /Volumes/Data/iMac.sparsebundle mounted at: /Volumes/Copies de sauvegarde Time machine
Nov 28 20:02:51 iMac.local com.apple.backupd[3136]: Backing up to: /Volumes/Copies de sauvegarde Time machine/Backups.backupdb
Nov 28 20:02:52 iMac.local fseventsd[47]: log dir: /Volumes/Copies de sauvegarde Time machine/.fseventsd getting new uuid: 6E582DCF-14FA-43D8-9F36-353E2E4FCD17
Nov 28 20:02:55 iMac.local WindowServer[91]: Created shield window 0x23c for display 0x04272340
Nov 28 20:02:55 iMac.local WindowServer[91]: device_generate_desktop_screenshot: authw 0x0(0), shield 0x0(0)
Nov 28 20:02:55 iMac.local WindowServer[91]: device_generate_lock_screen_screenshot: authw 0x0(0), shield 0x0(0)
Nov 28 20:03:05 iMac.local Notes[3055]: [IMAP] Expected untagged initial response from pop.laposte.net
Nov 28 20:03:22 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd:   49 wr:   49 q_size: 1024 flags: 0x1
Nov 28 20:03:22 iMac.local com.apple.PassXPCService[3099]: PAPassValidator: _signatureIsValid failed to load signature file
Nov 28 20:03:35 --- last message repeated 4 times ---
Nov 28 20:03:35 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 818 wr: 818 q_size: 1024 flags: 0x1
Nov 28 20:04:06 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 563 wr: 563 q_size: 1024 flags: 0x1
Nov 28 20:04:07 iMac.local mdworker[3180]: Unable to talk to lsboxd
Nov 28 20:04:07 iMac.local sandboxd[3181] ([3180]): mdworker(3180) deny mach-lookup com.apple.ls.boxd
Nov 28 20:04:07 iMac kernel[0]: Sandbox: sandboxd(3181) deny mach-lookup com.apple.coresymbolicationd
Nov 28 20:04:16 iMac.local com.apple.backupd[3136]: Event store UUIDs don't match for volume: Mac OS X Lion
Nov 28 20:04:18 iMac.local com.apple.backupd[3136]: Deep event scan at path:/ reason:must scan subdirs|new event db|
Nov 28 20:05:20 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 308 wr: 308 q_size: 1024 flags: 0x1
Nov 28 20:06:11 iMac.local mdworker[3185]: Unable to talk to lsboxd
Nov 28 20:06:11 iMac kernel[0]: Sandbox: sandboxd(3186) deny mach-lookup com.apple.coresymbolicationd
Nov 28 20:06:12 iMac.local sandboxd[3186] ([3185]): mdworker(3185) deny mach-lookup com.apple.ls.boxd
Nov 28 20:07:05 iMac.local Notes[3055]: [IMAP] Expected untagged initial response from pop.laposte.net
Nov 28 20:07:12 iMac.local com.apple.SecurityServer[15]: Succeeded authorizing right 'system.hdd.smart' by client '/Library/Application Support/iStat local/iStatLocalDaemon' [62] for authorization created by '/Library/Application Support/iStat local/iStatLocalDaemon' [62] (B,0)
Nov 28 20:07:42 --- last message repeated 1 time ---
Nov 28 20:08:26 iMac kernel[0]: (default pager): [KERNEL]: ps_select_segment - send HI_WAT_ALERT
Nov 28 20:08:26 iMac kernel[0]: macx_swapon SUCCESS
Nov 28 20:08:29 iMac.local mdworker[3190]: Unable to talk to lsboxd
Nov 28 20:08:29 iMac.local sandboxd[3193] ([3190]): mdworker(3190) deny mach-lookup com.apple.ls.boxd
Nov 28 20:08:29 iMac kernel[0]: Sandbox: sandboxd(3193) deny mach-lookup com.apple.coresymbolicationd
Nov 28 20:10:44 iMac.local com.apple.backupd[3136]: Finished scan
Nov 28 20:12:12 iMac.local com.apple.SecurityServer[15]: Succeeded authorizing right 'system.hdd.smart' by client '/Library/Application Support/iStat local/iStatLocalDaemon' [62] for authorization created by '/Library/Application Support/iStat local/iStatLocalDaemon' [62] (B,0)
Nov 28 20:12:19 --- last message repeated 1 time ---
Nov 28 20:12:19 iMac.local com.apple.backupd[3136]: Found 3052 files (597.4 MB) needing backup
Nov 28 20:12:21 iMac.local com.apple.backupd[3136]: 3.65 GB required (including padding), 1.41 TB available
Nov 28 20:12:32 iMac.local mdworker[3200]: Unable to talk to lsboxd
Nov 28 20:12:32 iMac.local mdworker[3201]: Unable to talk to lsboxd
Nov 28 20:12:33 iMac kernel[0]: Sandbox: sandboxd(3202) deny mach-lookup com.apple.coresymbolicationd
Nov 28 20:12:33 iMac.local sandboxd[3202] ([3200]): mdworker(3200) deny mach-lookup com.apple.ls.boxd
Nov 28 20:12:33 iMac.local sandboxd[3202] ([3201]): mdworker(3201) deny mach-lookup com.apple.ls.boxd
Nov 28 20:12:51 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd:   53 wr:   53 q_size: 1024 flags: 0x1
Nov 28 20:12:52 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 822 wr: 822 q_size: 1024 flags: 0x1
Nov 28 20:12:52 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 567 wr: 567 q_size: 1024 flags: 0x1
Nov 28 20:12:52 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 312 wr: 312 q_size: 1024 flags: 0x1
Nov 28 20:13:03 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd:   57 wr:   57 q_size: 1024 flags: 0x1
Nov 28 20:13:11 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 826 wr: 826 q_size: 1024 flags: 0x1
Nov 28 20:13:21 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 571 wr: 571 q_size: 1024 flags: 0x1
Nov 28 20:13:38 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 316 wr: 316 q_size: 1024 flags: 0x1
Nov 28 20:13:55 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd:   61 wr:   61 q_size: 1024 flags: 0x1
Nov 28 20:14:10 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 830 wr: 830 q_size: 1024 flags: 0x1
Nov 28 20:14:21 iMac.local mdworker[3214]: Unable to talk to lsboxd
Nov 28 20:14:22 iMac.local sandboxd[3215] ([3214]): mdworker(3214) deny mach-lookup com.apple.ls.boxd (pre-ls-info fstype:hfs fsflag:480D000 flags:48200000056 diag:0 uti:com.netscape.javascript-source plugin:/Library/Spotlight/RichText.mdimporter - find suspect file using: sudo mdutil -t 13586206)
Nov 28 20:14:22 iMac kernel[0]: Sandbox: sandboxd(3215) deny mach-lookup com.apple.coresymbolicationd
Nov 28 20:14:24 iMac.local mdworker[3211]: Unable to talk to lsboxd
Nov 28 20:14:24 iMac.local sandboxd[3215] ([3211]): mdworker(3211) deny mach-lookup com.apple.ls.boxd (pre-ls-info fstype:hfs fsflag:480D000 flags:48200000056 diag:0 uti:com.netscape.javascript-source plugin:/Library/Spotlight/RichText.mdimporter - find suspect file using: sudo mdutil -t 13593446)
Nov 28 20:14:27 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 575 wr: 575 q_size: 1024 flags: 0x1
Nov 28 20:14:52 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 320 wr: 320 q_size: 1024 flags: 0x1
Nov 28 20:14:56 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd:   65 wr:   65 q_size: 1024 flags: 0x1
Nov 28 20:15:04 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 834 wr: 834 q_size: 1024 flags: 0x1
Nov 28 20:15:04 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 579 wr: 579 q_size: 1024 flags: 0x1
Nov 28 20:15:04 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 324 wr: 324 q_size: 1024 flags: 0x1
Nov 28 20:15:04 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd:   69 wr:   69 q_size: 1024 flags: 0x1
Nov 28 20:15:05 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 838 wr: 838 q_size: 1024 flags: 0x1
Nov 28 20:15:06 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 583 wr: 583 q_size: 1024 flags: 0x1
Nov 28 20:15:06 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 328 wr: 328 q_size: 1024 flags: 0x1
Nov 28 20:15:12 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd:   73 wr:   73 q_size: 1024 flags: 0x1
Nov 28 20:15:17 iMac kernel[0]: Sandbox: sandboxd(3221) deny mach-lookup com.apple.coresymbolicationd
Nov 28 20:15:17 iMac.local sandboxd[3221] ([3220]): mdworker(3220) deny file-write-owner /Users/nicolas/Library/Containers/com.apple.Notes/Data/Library/Notes/NotesV1.st oredata-wal (import fstype:hfs fsflag:480D000 flags:48200000056 diag:0 uti:com.apple.notes.externalrecord plugin:/Library/Spotlight/Notes.mdimporter - find suspect file using: sudo mdutil -t 13562288)
Nov 28 20:15:17 iMac.local sandboxd[3221] ([3220]): mdworker(3220) deny file-write-owner /Users/nicolas/Library/Containers/com.apple.Notes/Data/Library/Notes/NotesV1.st oredata-shm (import fstype:hfs fsflag:480D000 flags:48200000056 diag:0 uti:com.apple.notes.externalrecord plugin:/Library/Spotlight/Notes.mdimporter - find suspect file using: sudo mdutil -t 13562288)
Nov 28 20:15:17 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 842 wr: 842 q_size: 1024 flags: 0x1
Nov 28 20:15:20 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 587 wr: 587 q_size: 1024 flags: 0x1
Nov 28 20:15:25 iMac.local mdworker[3222]: *** Failed to decode 7 bit data, treating as binary
Nov 28 20:15:28 --- last message repeated 3 times ---
Nov 28 20:15:28 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 332 wr: 332 q_size: 1024 flags: 0x1
Nov 28 20:15:33 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd:   77 wr:   77 q_size: 1024 flags: 0x1
Nov 28 20:15:33 iMac.local mdworker[3224]: Unable to talk to lsboxd
Nov 28 20:15:33 iMac.local sandboxd[3221] ([3224]): mdworker(3224) deny mach-lookup com.apple.ls.boxd
Nov 28 20:15:37 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 846 wr: 846 q_size: 1024 flags: 0x1
Nov 28 20:15:47 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 591 wr: 591 q_size: 1024 flags: 0x1
Nov 28 20:15:48 iMac com.apple.launchd[1] (com.apple.PassXPCService[3099]): Exited: Killed: 9
Nov 28 20:15:48 iMac kernel[0]: memorystatus_thread: idle exiting pid 3099 [com.apple.PassXP]
Nov 28 20:15:51 iMac kernel[0]: (default pager): [KERNEL]: ps_select_segment - send HI_WAT_ALERT
Nov 28 20:15:51 iMac kernel[0]: macx_swapon SUCCESS
Nov 28 20:15:57 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 336 wr: 336 q_size: 1024 flags: 0x1
Nov 28 20:16:00 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd:   81 wr:   81 q_size: 1024 flags: 0x1
Nov 28 20:16:01 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 850 wr: 850 q_size: 1024 flags: 0x1
Nov 28 20:16:05 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 595 wr: 595 q_size: 1024 flags: 0x1
Nov 28 20:16:08 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 340 wr: 340 q_size: 1024 flags: 0x1
Nov 28 20:16:10 iMac.local mdworker[3226]: *** Failed to decode 7 bit data, treating as binary
Nov 28 20:16:13 --- last message repeated 3 times ---
Nov 28 20:16:13 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd:   85 wr:   85 q_size: 1024 flags: 0x1
Nov 28 20:16:18 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 854 wr: 854 q_size: 1024 flags: 0x1
Nov 28 20:16:19 iMac.local mdworker[3226]: *** Failed to decode 7 bit data, treating as binary
Nov 28 20:16:24 --- last message repeated 3 times ---
Nov 28 20:16:24 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 599 wr: 599 q_size: 1024 flags: 0x1
Nov 28 20:16:32 iMac.local mdworker[3226]: *** Failed to decode 7 bit data, treating as binary
Nov 28 20:16:34 --- last message repeated 3 times ---
Nov 28 20:16:34 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 344 wr: 344 q_size: 1024 flags: 0x1
Nov 28 20:16:39 iMac.local mdworker[3226]: *** Failed to decode 7 bit data, treating as binary
Nov 28 20:16:40 --- last message repeated 3 times ---
Nov 28 20:16:40 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd:   89 wr:   89 q_size: 1024 flags: 0x1
Nov 28 20:16:48 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 858 wr: 858 q_size: 1024 flags: 0x1
Nov 28 20:17:01 iMac kernel[0]: fsevents: watcher failing behind: scxfsmond (pid: 460) rd: 603 wr: 603 q_size: 1024 flags: 0x1
Nov 28 20:39:07 localhost bootlog[0]: BOOT_TIME 1354131547 0
Nov 28 20:39:28 localhost kernel[0]: Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
Nov 28 20:39:28 localhost kernel[0]: vm_page_bootstrap: 919981 free pages and 120403 wired pages
Nov 28 20:39:28 localhost kernel[0]: kext submap [0xffffff7f80741000 - 0xffffff8000000000], kernel text [0xffffff8000200000 - 0xffffff8000741000]
Nov 28 20:39:28 localhost kernel[0]: zone leak detection enabled
Nov 28 20:39:28 localhost kernel[0]: standard timeslicing quantum is 10000 us
Nov 28 20:39:28 localhost kernel[0]: standard background quantum is 2500 us
Nov 28 20:39:28 localhost kernel[0]: mig_table_max_displ = 74
Nov 28 20:39:28 localhost kernel[0]: corecrypto kext started!
Nov 28 20:39:28 localhost kernel[0]: Running kernel space in FIPS MODE
Imac 8,1 4Go RAM early 2008
Time Capsule 2To
Thanks for your help

Time Machine starts backup then fails

I'm trying to use Time Machine to backup wirelessly to Time Capsule. It starts but then fails after about 40 Mb, telling me an error occurred.
I've browsed these forums and tried reading Console Messages, but they don't mean much to me.
This is the first of 6 similar messages.
07/03/08 7:11:02 com.apple.backupd[49744] 2008-03-07 07:11:02.298 diskimages-helper[49755:1603] Error loading /Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/MacOS/Vir tualPCDiskImagePlugin: dlopen(/Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/Ma cOS/VirtualPCDiskImagePlugin, 262): no suitable image found. Did find:
Does anyone have any suggestions ? Am I on the right track ?

I'm trying to use Time Machine to backup wirelessly to Time Capsule. It starts but then fails after about 40 Mb, telling me an error occurred.
I've browsed these forums and tried reading Console Messages, but they don't mean much to me.
This is the first of 6 similar messages.
07/03/08 7:11:02 com.apple.backupd[49744] 2008-03-07 07:11:02.298 diskimages-helper[49755:1603] Error loading /Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/MacOS/Vir tualPCDiskImagePlugin: dlopen(/Library/Plug-ins/DiskImages/VirtualPCDiskImagePlugin.bundle/Contents/Ma cOS/VirtualPCDiskImagePlugin, 262): no suitable image found. Did find:
Does anyone have any suggestions ? Am I on the right track ?

Time Machine Restore at 149.7% and freezes.

Hi there,
Yesterday I had a bit of trouble with my Macbook - took a long while to start up, and it showed this "progress bar" under the little Apple at start-up etc. Had this before and the Mac store changed the HD saying it was damaged.
So, fortunately I could start up, but not everything was working well enough. I managed to make a Time Machine back-up of my HD (some 250 Gb).
Did a disk check after starting up from the OSX CD, which recommended I should erase and restore.
Now, the HD has been erased now, and I started to do a Time Machine Restore.
But, after some 5-6 hours, it appears to have frozen up, at 149.7% (why did it exceed 100%?).
It's not doing anything now. I don't hear my laptop working, nor the external drive (and that one makes quite some noise when active). It's just sitting there at 149.7%. All I can do, is press a "Stop" button which I haven't done so far.

Hi, and welcome to the forums.
It's possible that whatever was going wrong on your system damaged or corrupted some of the data. Time Machine may have backed-up the corrupted files, so now it's trying to reload the same problem(s).
By the way, be sure you're using a Snow Leopard Install disc to restore a Snow Leopard backup.
It sounds like this was your very first Time Machine backup -- if not, and the restore fails, try again from an earlier one, done before the problems started.
If you only have the single backup, and the restore fails, first run this: this: Intel-based Macs: Using Apple Hardware Test
If that shows a problem, take it to Apple for repair.
If not, about all you can do is start up again from the Installer disc, but instead of selecting +Restore System From Backup+ in the Utilities menu, select +Disk Utility,+ and use it to erase your internal HD. Then quit Disk Utility, back to the Installer, and install a fresh copy of OSX.
When your Mac starts up again, use +Setup Assistant+ to restore everything else from your backups. See #19 in Time Machine - Frequently Asked Questions (or use the link in *User Tips* at the top of this forum), for details.
If some of that data was damaged, that may not work well. If it doesn't, post back and we'll try a workaround.
Then download and install the "combo" update to get back to 10.6.4. Info and download available at: http://support.apple.com/kb/DL1048 Be sure to do a +Repair Permissions+ via Disk Utility (in your Applications/Utilities folder) afterwards.

Time Machine start then stop after few seconds

Hi,
I've tried to reset Time Machine (trashed the library plist file, erased the backup HD), also installed Time Machine Buddy widget.
When I start a fresh new backup, Time Machine start indexing, then stops without backup anything.
The error log of Time Machine Buddy widget is this:
Starting standard backup
Backing up to: /Volumes/TimeMachine/Backups.backupdb
Backup content size: 156.0 GB excluded items size: 1.8 GB for volume Mastoidontico
No pre-backup thinning needed: 185.11 GB requested (including padding), 1.82 TB available
Waiting for index to be ready (101)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
Waiting for index to be ready (100)
LaunchServices: bad alias at 0x1041d7094, size 104, CSStore size 4391026
* process 240 exceeded 500 log message per second limit - remaining messages this second discarded *
2010-02-02 18:47:12.920 ReportCrash[271:2703] Saved crash report for backupd[240] version ??? (???) to /Library/Logs/DiagnosticReports/backupd2010-02-02-184712localhost.crash
Any help to solve my problem?
Thanks!

Process: backupd [240]
Path: /System/Library/CoreServices/backupd
Identifier: backupd
Version: ??? (???)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
Date/Time: 2010-02-02 18:47:12.319 +0100
OS Version: Mac OS X 10.6.2 (10C540)
Report Version: 6
Exception Type: EXCBADACCESS (SIGSEGV)
Exception Codes: KERNINVALIDADDRESS at 0x000000014c486000
Crashed Thread: 2
Thread 0: Dispatch queue: com.apple.main-thread
0 libSystem.B.dylib 0x00007fff80044e3a machmsgtrap + 10
1 libSystem.B.dylib 0x00007fff800454ad mach_msg + 59
2 com.apple.CoreFoundation 0x00007fff868377a2 __CFRunLoopRun + 1698
3 com.apple.CoreFoundation 0x00007fff86836c2f CFRunLoopRunSpecific + 575
4 com.apple.CoreFoundation 0x00007fff868369b6 CFRunLoopRun + 70
5 backupd 0x000000010000d2f1 0x100000000 + 54001
6 backupd 0x0000000100004014 0x100000000 + 16404
Thread 1: Dispatch queue: com.apple.libdispatch-manager
0 libSystem.B.dylib 0x00007fff8005dbba kevent + 10
1 libSystem.B.dylib 0x00007fff8005fa85 dispatch_mgrinvoke + 154
2 libSystem.B.dylib 0x00007fff8005f75c dispatch_queueinvoke + 185
3 libSystem.B.dylib 0x00007fff8005f286 dispatch_workerthread2 + 244
4 libSystem.B.dylib 0x00007fff8005ebb8 pthreadwqthread + 353
5 libSystem.B.dylib 0x00007fff8005ea55 start_wqthread + 13
Thread 2 Crashed:
0 ...ple.CoreServices.CarbonCore 0x00007fff85070987 CSStoreGetUnit + 84
1 com.apple.LaunchServices 0x00007fff85df44a3 _LSBundleFindWithNode + 544
2 com.apple.LaunchServices 0x00007fff85decc79 _LSFindOrRegisterBundleNode + 219
3 com.apple.LaunchServices 0x00007fff85decb2d _LSCopyItemAttributeForRefInfoWithOptions + 201
4 com.apple.LaunchServices 0x00007fff85deea77 prepareAttributeValueForKey(__CFURL const*, __FileCache*, __CFString const*, void const**, __CFError**) + 79
5 com.apple.LaunchServices 0x00007fff85dee9dc prepareDistinctLocalizedNameValue(__CFURL const*, __FileCache*, __CFError**) + 36
6 com.apple.LaunchServices 0x00007fff85dee9b3 prepareLocalizedNameValue(__CFURL const*, __FileCache*, __CFError**) + 9
7 com.apple.LaunchServices 0x00007fff85dee7bc LSPropertyProviderPrepareValues(__CFURL const*, __FileCache*, __CFString const* const*, void const**, long, void const*, __CFError**) + 51
8 ...ple.CoreServices.CarbonCore 0x00007fff85081c90 prepareValuesForBitmap(__CFURL const*, __FileCache*, _FilePropertyBitmap*, __CFError**) + 264
9 ...ple.CoreServices.CarbonCore 0x00007fff85080779 _FSURLCopyResourcePropertiesForKeys + 980
10 com.apple.CoreFoundation 0x00007fff8683f402 CFURLCopyResourcePropertiesForKeys + 98
11 com.apple.DesktopServices 0x00007fff84b30169 TCFURLInfo::FetchProperties(bool) + 91
12 com.apple.DesktopServices 0x00007fff84b2ffbd TCFURLInfo::Initialize(__CFURL const*, bool, bool) + 183
13 com.apple.DesktopServices 0x00007fff84b8e07f TCFURLIterator::NextRaw(TCountedPtr<TCFURLInfo>&) + 79
14 com.apple.DesktopServices 0x00007fff84b8e11a TCFURLIterator::Next(TCountedPtr<TCFURLInfo>&) + 40
15 com.apple.DesktopServices 0x00007fff84b8f517 TDeepCFURLIterator::NextInternal(TCountedPtr<TCFURLInfo>&, int&, int&, bool&) + 73
16 com.apple.DesktopServices 0x00007fff84b8f651 TDeepCFURLIterator::Next(TCountedPtr<TCFURLInfo>&, int&, int&, bool&) + 49
17 com.apple.DesktopServices 0x00007fff84b95629 TCopyReader::GetNextItem() + 1039
18 com.apple.DesktopServices 0x00007fff84b95fac TCopyReader::Read(unsigned long long, TCountedPtr<TCFURLInfo> const&, TCountedPtr<TCFURLInfo> const&) + 128
19 com.apple.DesktopServices 0x00007fff84b80f27 TFSCopyOperation::CopyToTarget() + 607
20 com.apple.DesktopServices 0x00007fff84b82d9f TFSCopyOperation::DoCopy(TCountedPtr<TCFURLInfo> const&) + 595
21 com.apple.DesktopServices 0x00007fff84b78a68 _NodeOperation + 469
22 backupd 0x00000001000164af 0x100000000 + 91311
23 backupd 0x0000000100015923 0x100000000 + 88355
24 backupd 0x000000010000ffc7 0x100000000 + 65479
25 backupd 0x000000010000a7e2 0x100000000 + 42978
26 backupd 0x0000000100006927 0x100000000 + 26919
27 com.apple.Foundation 0x00007fff88a2be99 _NSThread__main_ + 1429
28 libSystem.B.dylib 0x00007fff8007df8e pthreadstart + 331
29 libSystem.B.dylib 0x00007fff8007de41 thread_start + 13

Since upgrade, Time Machine starts and stalls. Waited 24 hours. Formatted disk-no change.

Since upgrade to Mavericks on Mini, Time Machine starts and stalls. Says "292 Mb of 147.68 Gb", wheel spins. Waited 24 hours, no change. Formatted disk-no change. Tried every solution found in threads; no fix. Doing manual backups. Help!

If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message that corresponds to an abnormal backup. Now
CLEAR THE WORD "Starting" FROM THE TEXT FIELD
so that all messages are showning, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them to the Clipboard by pressing the key combination command-C. Paste (command-V) into a reply to this message.
If all you see are messages that contain the word "Starting," you didn't clear the text field.
If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Some personal information, such as the names of your files, may be included — anonymize before posting.

Im having trouble with my i mac it freezes up an some times wont start normally it will jus display a gray and white fuzzy screen (any Help Out there)

im having trouble with my i mac it freezes up an some times wont start normally it will jus display a gray and white fuzzy screen (any Help Out there)

Hello there, DJ ROb E Rob.
The following Knowledge Base article offers up some great recommendations for troubleshooting the gray screen at startup:
Mac OS X: Gray screen appears during startup
http://support.apple.com/kb/ts2570
Thanks for reaching out to Apple Support Communities.
Cheers,
Pedro.

I have a mid2009 MacBook Pro for which I have been using a USB WD HD for Time Machine. I'd like to get a wireless HD and start a new Time Machine backup for this Mac and retire the 5 year old WD drive. Can I start over?

I have a mid2009 MacBook Pro running Mavericks for which I have been using a USB WD HD for Time Machine. I'd like to get a wireless HD and start a new Time Machine backup for this Mac and retire the 5 year old WD drive. Can I start over?

no archive/ backup is perfect, HD clones can be set to make incremental additions, same as time machine however, though they are more time involved in doing so.
See the + and - of all data backup/ archives below and "spread it around".... or the "dont put your eggs all in one basket" philosophy.
Peace
Data Storage Platforms; their Drawbacks & Advantages
#1. Time Machine / Time Capsule
Drawbacks:
1. Time Machine is not bootable, if your internal drive fails, you cannot access files or boot from TM directly from the dead computer.
2. Time machine is controlled by complex software, and while you can delve into the TM backup database for specific file(s) extraction, this is not ideal or desirable.
3. Time machine can and does have the potential for many error codes in which data corruption can occur and your important backup files may not be saved correctly, at all, or even damaged. This extra link of failure in placing software between your data and its recovery is a point of risk and failure. A HD clone is not subject to these errors.
4. Time machine mirrors your internal HD, in which cases of data corruption, this corruption can immediately spread to the backup as the two are linked. TM is perpetually connected (or often) to your computer, and corruption spread to corruption, without isolation, which TM lacks (usually), migrating errors or corruption is either automatic or extremely easy to unwittingly do.
5. Time Machine does not keep endless copies of changed or deleted data, and you are often not notified when it deletes them; likewise you may accidently delete files off your computer and this accident is mirrored on TM.
6. Restoring from TM is quite time intensive.
7. TM is a backup and not a data archive, and therefore by definition a low-level security of vital/important data.
8. TM working premise is a “black box” backup of OS, APPS, settings, and vital data that nearly 100% of users never verify until an emergency hits or their computers internal SSD or HD that is corrupt or dead and this is an extremely bad working premise on vital data.
9. Given that data created and stored is growing exponentially, the fact that TM operates as a “store-it-all” backup nexus makes TM inherently incapable to easily backup massive amounts of data, nor is doing so a good idea.
10. TM working premise is a backup of a users system and active working data, and NOT massive amounts of static data, yet most users never take this into consideration, making TM a high-risk locus of data “bloat”.
11. In the case of Time Capsule, wifi data storage is a less than ideal premise given possible wireless data corruption.
12. TM like all HD-based data is subject to ferromagnetic and mechanical failure.
13. *Level-1 security of your vital data.
Advantages:
1. TM is very easy to use either in automatic mode or in 1-click backups.
2. TM is a perfect novice level simplex backup single-layer security save against internal HD failure or corruption.
3. TM can easily provide a seamless no-gap policy of active data that is often not easily capable in HD clones or HD archives (only if the user is lazy is making data saves).
#2. HD archives
Drawbacks:
1. Like all HD-based data is subject to ferromagnetic and mechanical failure.
2. Unless the user ritually copies working active data to HD external archives, then there is a time-gap of potential missing data; as such users must be proactive in archiving data that is being worked on or recently saved or created.
Advantages:
1. Fills the gap left in a week or 2-week-old HD clone, as an example.
2. Simplex no-software data storage that is isolated and autonomous from the computer (in most cases).
3. HD archives are the best idealized storage source for storing huge and multi-terabytes of data.
4. Best-idealized 1st platform redundancy for data protection.
5. *Perfect primary tier and level-2 security of your vital data.
#3. HD clones (see below for full advantages / drawbacks)
Drawbacks:
1. HD clones can be incrementally updated to hourly or daily, however this is time consuming and HD clones are, often, a week or more old, in which case data between today and the most fresh HD clone can and would be lost (however this gap is filled by use of HD archives listed above or by a TM backup).
2. Like all HD-based data is subject to ferromagnetic and mechanical failure.
Advantages:
1. HD clones are the best, quickest way to get back to 100% full operation in mere seconds.
2. Once a HD clone is created, the creation software (Carbon Copy Cloner or SuperDuper) is no longer needed whatsoever, and unlike TM, which requires complex software for its operational transference of data, a HD clone is its own bootable entity.
3. HD clones are unconnected and isolated from recent corruption.
4. HD clones allow a “portable copy” of your computer that you can likewise connect to another same Mac and have all your APPS and data at hand, which is extremely useful.
5. Rather than, as many users do, thinking of a HD clone as a “complimentary backup” to the use of TM, a HD clone is superior to TM both in ease of returning to 100% quickly, and its autonomous nature; while each has its place, TM can and does fill the gap in, say, a 2 week old clone. As an analogy, the HD clone itself is the brick wall of protection, whereas TM can be thought of as the mortar, which will fill any cracks in data on a week, 2-week, or 1-month old HD clone.
6. Best-idealized 2nd platform redundancy for data protection, and 1st level for system restore of your computers internal HD. (Time machine being 2nd level for system restore of the computer’s internal HD).
7. *Level-2 security of your vital data.
HD cloning software options:
1. SuperDuper HD cloning software APP (free)
2. Carbon Copy Cloner APP (will copy the recovery partition as well)
3. Disk utility HD bootable clone.
#4. Online archives
Drawbacks:
1. Subject to server failure or due to non-payment of your hosting account, it can be suspended.
2. Subject, due to lack of security on your part, to being attacked and hacked/erased.
Advantages:
1. In case of house fire, etc. your data is safe.
2. In travels, and propagating files to friends and likewise, a mere link by email is all that is needed and no large media needs to be sent across the net.
3. Online archives are the perfect and best-idealized 3rd platform redundancy for data protection.
4. Supremely useful in data isolation from backups and local archives in being online and offsite for long-distance security in isolation.
5. *Level-1.5 security of your vital data.
#5. DVD professional archival media
Drawbacks:
1. DVD single-layer disks are limited to 4.7Gigabytes of data.
2. DVD media are, given rough handling, prone to scratches and light-degradation if not stored correctly.
Advantages:
1. Archival DVD professional blank media is rated for in excess of 100+ years.
2. DVD is not subject to mechanical breakdown.
3. DVD archival media is not subject to ferromagnetic degradation.
4. DVD archival media correctly sleeved and stored is currently a supreme storage method of archiving vital data.
5. DVD media is once written and therefore free of data corruption if the write is correct.
6. DVD media is the perfect ideal for “freezing” and isolating old copies of data for reference in case newer generations of data become corrupted and an older copy is needed to revert to.
7. Best-idealized 4th platform redundancy for data protection.
8. *Level-3 (highest) security of your vital data.
[*Level-4 data security under development as once-written metallic plates and synthetic sapphire and likewise ultra-long-term data storage]
#6. Cloud based storage
Drawbacks:
1. Cloud storage can only be quasi-possessed.
2. No genuine true security and privacy of data.
3. Should never be considered for vital data storage or especially long-term.
4. *Level-0 security of your vital data.
Advantages:
1. Quick, easy and cheap storage location for simplex files for transfer to keep on hand and yet off the computer.
2. Easy source for small-file data sharing.

Time Machine deletes entire previous backup and then back it up from zero!

my configuration :
Time Machine : USB external HD 500G
Backing up : 1. internal 160G (90G used) 2. USB external HD 500G (290G used)
the problem is, every time I hook up the TM, it backup the internal HD smoothly but deletes its entire previous backup of the external HD and starts all over ... and naturally it takes forever to do 290G....
anybody get any idea where the problem seem to be ?
Thanks!!

Welcome to Discussions.
It could be that your drive isn't formatted correctly for Time Machine. Launch Disk Utility which is in your Applications > Utilities folder. Choose the upper icon (the one that is not indented) for your Time Machine drive. At the bottom of the window the Partition Map Scheme should be GUID for Intel Macs and Apple Partition Map for PPC Macs. Next click on the indented icon for your Time Machine drive. The format should be Mac OS Extended (Journaled).
If the formatting is not correct on your Time Machine drive you will need to reformat your drive which will erase everything on it. Copy any files you might need from your Time Machine drive. Then format your Time Machine disk following the directions in this article. People with PPC Macs should substitute Apple Partition Map for GUID when following the directions.
If your Time Machine disk is formatted correctly there might be some hints in the Time Machine log as to what has gone wrong. Launch Console which is in Applications > Utilities. Choose All Messages in the left pane of Console and type in "backupd" without the quotes in the search window. Post back any errors or complaints that you find in the log.

Can I back up computer with time machine on lion then reinstall snow leopard and restore from backup safely

Can I back up computer with time machine on lion then reinstall snow leopard and restore from backup safely?

If your machine came with Snow Leopard or earlier and you have your install disks, yes, you can reinstall SL. However, you will need to erase the entire hard drive so you will lose all your files. Also note that there are some apps (such as Mail) which can't be downgraded "automatically" such as with a restore from Time Machine. Here is some info on TM:
http://pondini.org/TM/14.html

Stalling and Freezing

I run Indesign CS4. It use to run perfectly for months, but in the last few weeks it has started to stall and freeze when I open old documents or even start new ones. I have tried to un/reinstalling useing the cleaning tool per trouble shoot. I have updated everything, drivers ect. I am running Windows Vista 64.
I have, i think narowed it down to a few issues/causes, but I cannot seem it find a fix for them.
1) InDesign is slow moving/stalling happens prefight is on (turn it off InDesign responds normally)
2) I cannot use auto hyphen or InDesign will stall.....why? (I work with books and use this feature all the time, it is a have to have-that i can't seem to use)
Overall since the latest Windows updates and/or the latest Adobe updates, InDesign seems to run slower.....Why? The other programs in the suite do not seem to be affected by whatever is causing this.

I run Indesign CS4. It use to run perfectly for months, but in the last few weeks it has started to stall and freeze when I open old documents or even start new ones. I have tried to un/reinstalling useing the cleaning tool per trouble shoot. I have updated everything, drivers ect. I am running Windows Vista 64.
I have, i think narowed it down to a few issues/causes, but I cannot seem it find a fix for them.
1) InDesign is slow moving/stalling happens prefight is on (turn it off InDesign responds normally)
2) I cannot use auto hyphen or InDesign will stall.....why? (I work with books and use this feature all the time, it is a have to have-that i can't seem to use)
Overall since the latest Windows updates and/or the latest Adobe updates, InDesign seems to run slower.....Why? The other programs in the suite do not seem to be affected by whatever is causing this.

Time Capsule crashes when Time Machine starts a backup

I've not searched through the postings here to see if other people have seen a similar problem. I've not attempted to repeat the problem I've seen here so I'm not very clear about the cause.
I'm using a MacBook Pro with OS 10.5.4 connected via a network cabled directly to a Time Capsule which is connected to a DSL/Cable modem. The Time Capsule is updated with v 7.3.2 of the firmware. I've got Time Machine enabled but I'm also using the Time Capsule disk (1TB) to store photos that I've previously archived to CD. I'm in the process of copying all the data from CD to the Time Capsule.
Having copied some photo data to the Time Capsule I was trying out some photo cataloguing SW to see if it was any good (iPhoto is no good to me as I don't want to store photos on the local drive of my machine) - Kodak EasyShare v6.1. Having loaded some images into EasyShare I tried to use finder to search for the file names of some of the images to check that EasyShare was not copying images to my local drive. While I was doing this I think Time Machine tried to kick in and start doing a backup. I believe that Time Capsule crashed at this point. Finder froze and after I restarted it (via Force Quit not a re-boot) I discovered that I had no network connection and Mac OS couldn't see the Time Capsule under FInder or via AirPort Utility (the Time Machine backup also timed out and failed). Time Capsule just sat there with the disk spinning and a green light on the front as if all was OK. Actually - the disk just kept spinning (Time Capsule normally shuts down the drive after it is idle for a while). Because of this I'm pretty sure that Time Capsule had crashed.
I experimented with re-booting my Mac but still no network etc so I tried power cycling the Time Capsule and everything came back to life.
I'm guessing that my doing a search (or some other drive activity on Time Capsule) at the same time as Time Machine kicking in with a backup caused Time Capsule to crash.
Perhaps this is not a very interesting point if this problem is not repeatable but - well, I'd be interested to know if others have seen similar behavior...

I'm having a very similar problem and it is detrimental.
Here is the scenario: I have a 1TB Time Capsule as my primary router. I am able to perform backups on all but one of my machines. My iMac backs up via 1GB ethernet to the TC, my MacBookAir (60GB,SS) backs up via wireless N (270mb) and my other MacBookAir (80GB,IDE) also backs up via wireless N without any problems.
I used to use a 500mb external drive to backup my iMac but outgrew it, so I started backing up to the TC instead. No problems at all.
I also used to back up my Intel MacMini running Mac OS X Server 10.5.5 to a similar external hard-drive but haven't in a while.
I decided it finally made sense to backup ALL my Mac's to the same 1TB TimeCapsule but it's just not working out!
On the MacMini; I turn on TimeMachine, the TimeCapsule has been chosen as a backup location, it prepares backup for a moment, mounts the backup drive and then appears to begin backup up... No...! First I get a message the the TimeCapsule closed the connection, next I lose Internet connection across my entire network both wired and wireless and then the TimeCapsule light turns amber, flashes and essentially does a completel crash / reset and then comes back to life a few moments later. I can backup any other computer except the MacMini to the TimeCapsule without "crashing" it and it makes no sense! Every computer is completely up to date with all the latest patches and the TimeCapsule is running 7.3.2
I sure hope this gets resolved, seems like other people are pretty disgusted with the performance of the TimeCapsule with problems that have no resolution.

External WD Passport won't recognize after Time Machine start.

I bought a WD passport 500 gb drive and when I initially plugged it in time machine saw it and when I asked it to use it- something happened and now NO icon appears in order to be selected nor does an icon show anywhere to even select. I changed the drive and the new one does the same. Cycles continously and never mounts. Did the usual- changed ports and changed wires. It just isn't recognized no matter what. What to do?

jimmyb12015 wrote:
No. The drive is not reflected in any window. Not on my computer or disk utility. It initially was shown just before Time Machine started. It was then I escaped from time machine and I eventually returned the first drive after reformating it to fat 32 (on a windows machine) and it still wouldn't show up the MAC. The second drive now does the same as the first (doesn't show and cycles) but never showed up in any form on the MAC.
If the MAC has a register then my guess is some information about any external disk has been altered and I should need to to return it to it's original setting. That is because the second drive is doing the same as the first. I just don't know how to do that or even look.
If it uses the MBR (Master Boot Record) partition scheme, for Windoze, TM may have started to reformat it to GUID, but had that interrupted when you cancelled. If DU can't see it at all, there's not much you can do from your Mac. You may need to reformat it on a PC, then do it over on your Mac, via item #5 in the FAQ.
There are reports of problems with some WD drives having not working well on Macs. You might want to check their website support/forums, etc.

HT201250 once time machine starts running, it never stops. what could cause this?

Using WD, My Passport for Mac, 2TB with Time-Machine. Updated software on MacBook, now once time machine starts running an update it does not stop untill cancel it!

1. The first time takes very long always, after that it will only do changes very hour and you will not notice it. The drive must be correctly formatted, Guid Partition Table, Mac Os Extended (journaled).
2. If you installed any of the 'smart' software that came with the disk (specifically with the WD disk), you have to uninstall it completely immediately, because it will cause data loss and speed at the minimum: in macs you do not not need such additional software, just make sure that the disk is correctly formatted. If you had such software installed, and now uninstalled, you better reformat the drive, restart the mac, and then start all over again with TM.
Lex

Troubleshooting 10.7.2 Intermittent System Stalls and Freezes

Context
Problem is occurring on a PowerMac 2.66 GHz Dual Core Intel Xeon running OS 10.7.2 with 6 GB RAM.
4 Hard drives installed. Normal startup drive is a 600 GB Western Digital VelociRaptor 3.5" drive. Other drives are Western Digital Caviar Black and Caviar Green drives.
No airport or bluetooth cards installed.
Internet access through ethernet connection to Netgear Gigabit Wireless router.
30 inch Cinema Display, wired mouse and keyboard.
Problem Description
For sometime I have been experiencing intermittent system stalls and freezes. None of my troubleshooting has identified the problem. Sometimes when I am doing something, the system will freeze for a few seconds. There is no spinning ball. I am able to move the cursor but it retains the shape it was for the document I was working in but I can neither shift to another application nor shift to another command with the application I am in. Sometimes this behavior will end and normal operation resume. Or it will continue into a system freeze. The system freezes are such that only a power down will work. Sometimes they occur when the computer is asleep and sometimes when I am actively using it. This morning I did receive a spinning ball but it disappeared but the stall continued until, after a minute, I treated it as a freeze since nothing worked except the ability to move the cursor around the screen.
When I became aware of this behavior, it was after I had incrementally upgraded to OS 10.7.2. I later used the Mac OS 10.7.2 version 1.1 combo update. The problem continued.
Troubleshooting
I have been systematically reviewing the console log to identify messages that might identify problems. For example, I located and removed a couple of files in the Library/StartupItems, Library/LaunchAgents, and Library/LaunchDaemons folders that were associated with applications already removed. I have also dropped several apps from my automatic launch sequence.
I have used several utilities to test RAM and other hardware and all tests have passed.
I have switched drives to startup and while I did not stay on a drive using 10.6.8 long enough to experience a system freeze, I did experience a system stall lasting for several seconds. Therefore I do not think it is a drive problem.
I have reduced to minimum the software being used and system has lots of free memory. Memory tests are good. (In Single User mode ran memtest for 2 runs.) Memory problem is unlikely.
=> Reviewing console messages, I find no correlation between the freezes and what is recorded in the logs.
Any suggestions as to how to proceed at this point?

The problem has been solved. In addition to the bad DIMMs, I had a defective video card and there were some software problems. The defective card was replaced and ran well for over 24 hours under intense computing tasks without problems using a Technican personailty. When I used it, I had problems right away. In consultation with Apple, I made the decision to erase (after cloning everything) and do a clean installation of Lion and all of my software. I have not completed installing everything but I have those tools I use on a daily basis now available.
Some Lessons Learned
If you are doing something like this, do not use Migration Assistant to speed up the process. It will bring in everything and you will not really have a clean install.
It is easier if you make the Library on your new Lion drive visible and make the one on your old clone visible too. To avoid permission problems, you need to copy files into a Shared User folder and then copy them into the new destination folder.
If you don't do it right and you find you have problems, check out this link on how to repair User Permissions in Mac OS Lion: http://osxdaily.com/2011/11/15/repair-user-permissions-in-mac-os-x-lion/

Time Machine starts normally, then stalls and freezes iMac

Similar Messages

Maybe you are looking for