Time machine crashes Wifi network

I have a new time machine which constantly crashes my wireless network.
I have tried to contact apple express lane support but the email they have sent me gives a phone number which is unrecognisable from my phone (I think it's a US not a UK number)

http://www.apple.com/uk/buy/locator/
This site will provide both retail and authorized servicer/support info.

Similar Messages

Time machine kills Wifi network!!

I had recently posted a thread on TC forum "Weird shut down of TC" that my TC just shuts down routinely.
I have a 1TB TC that has been working very well. I bought the new unibody MBP and the Time machine has been backing up quite nicely for past one month.
I now have a problem that the TM aborts with a message the the drive could not be accessed due to network problems.
My Wifi would be down, status light amber, after a while the status light would go off completely but the disk in TC would be spinning as can feel the spin vibrations. This would happen about every 45 minutes and only way to go back up was to unplug and plug.
I now find that the culprit is time machine. This is what I tried sequentially:
A. Rolled back to 7.3.1 firmware. Same problem.
B. Switched off the TM from prefrences. It worked well for a day.
C. Switched on the TM. As soon as TM backup started, I had the TC wifi freeze.
D. updated to firmware 7.3.2 with TM turned on. Same problem
E. Turned off the airport card, plugged in ethernet cable so now was not using the wifi but wired connection to the TC. Started the TM and again. SAME PROBLEM.
F. Turned off TM, all was well for the entire day.
G. Turned it back on and on the first back up attempt, the WiFi was killed again.
I think now the problem may be with the size of the back up that TM is attempting. It does the 'prepare for back up' pretty quickly but once the back up starts, it kills the WiFi and aborts with a message that there is no network.
Anyone have any idea if I should troubleshoot differently or diagnose this differently?
Has anyone had a problem with TM with large back ups?

Hi Alexandre,
Thanks for the input. Sorry my profile was not updated. I am using MBPro 10.5.5.
Here is the output from console which I think is the portion till the network went down. Could not find a way to attach the file.
Thanks for any help you can give:
Dec 7 08:50:36 Mehers-MB-Pro-2 kernel[0]: AFPSleepWakeHandler: waking up
Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: Computer did wake up from sleep. Reschedule our timers!
Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBack Engine MaxBackEngineController-- MoreSecCopyHelperToolURLAndCheckBundled #1
Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBackEngineController-- calling MoreSecExecuteRequestInHelperTool
Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBackEngineController-- back from MoreSecExecuteRequestInHelperTool
Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBack Engine MaxBackEngineController-- MoreSecCopyHelperToolURLAndCheckBundled #1
Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBackEngineController-- calling MoreSecExecuteRequestInHelperTool
Dec 7 08:50:36 Mehers-MB-Pro-2 MaxBack Engine[301]: MaxBackEngineController-- back from MoreSecExecuteRequestInHelperTool
Dec 7 08:50:40 Mehers-MB-Pro-2 configd[14]: AppleTalk startup complete
Dec 7 09:26:38 Mehers-MB-Pro-2 ntpd[27]: time reset -0.527369 s
Dec 7 09:34:27 Mehers-MB-Pro-2 SyncServer[3340]: SyncServer: Truth vacuumed. Next vacuum date 2008-12-21 09:34:24 +0500
Dec 7 09:51:20 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Data-1
Dec 7 09:51:20 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 09:51:20 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Data-1
Dec 7 09:51:20 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Data-1
Dec 7 09:51:20 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: primary reconnect failed 5, trying secondary /Volumes/Data-1
Dec 7 09:51:20 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 received VQ_NOTRESP event (1)
Dec 7 09:51:33 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Backup requested by user
Dec 7 09:51:33 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Starting standard backup
Dec 7 09:51:33 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Network mountpoint /Volumes/Data-1 not owned by backupd... remounting
Dec 7 09:51:34 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_mount: /Volumes/Data, pid 3360
Dec 7 09:51:34 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Network volume mounted at: /Volumes/Data
Dec 7 09:51:36 Mehers-MB-Pro-2 hdiejectd[3374]: running
Dec 7 09:51:37 Mehers-MB-Pro-2 kernel[0]: jnl: disk1s2: replay_journal: from: 75690496 to: 75768832 (joffset 0x1d0f000)
Dec 7 09:51:38 Mehers-MB-Pro-2 kernel[0]: jnl: disk1s2: journal replay done.
Dec 7 09:51:38 Mehers-MB-Pro-2 fseventsd[44]: event logs in /Volumes/Backup of Meher’s MB Pro/.fseventsd out of sync with volume. destroying old logs. (524 2 54320)
Dec 7 09:51:38 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Disk image /Volumes/Data/Meher’s MB Pro_002332b0b0ea.sparsebundle mounted at: /Volumes/Backup of Meher’s MB Pro
Dec 7 09:51:38 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Backing up to: /Volumes/Backup of Meher’s MB Pro/Backups.backupdb
Dec 7 09:51:38 Mehers-MB-Pro-2 fseventsd[44]: log dir: /Volumes/Backup of Meher’s MB Pro/.fseventsd getting new uuid: 2EF5457F-ED49-4E27-A818-A80F61BCCB86
Dec 7 09:51:47 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Waiting for index to be ready (906 > 0)
Dec 7 09:51:52: --- last message repeated 1 time ---
Dec 7 09:52:02 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Waiting for index to be ready (905 > 0)
Dec 7 09:52:17: --- last message repeated 1 time ---
Dec 7 09:52:37 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Waiting for index to be ready (905 > 0)
Dec 7 09:52:51 Mehers-MB-Pro-2 kernel[0]: AirPort: No beacon for too long time
Dec 7 09:52:51 Mehers-MB-Pro-2 configd[14]: AppleTalk shutdown
Dec 7 09:52:51 Mehers-MB-Pro-2 kernel[0]: AirPort: Link Down on en1
Dec 7 09:52:51 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: interface en is going DOWN
Dec 7 09:52:51: --- last message repeated 1 time ---
Dec 7 09:52:51 Mehers-MB-Pro-2 configd[14]: AppleTalk shutdown complete
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetDisconnect called for port 0x9d22100
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: filter detached
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: down
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: detached
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: Freeing hub at 0x4bb4800.
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x9d22100.
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetConnect: returning port 0x9d22100
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: Allocated hub 0x4bb4800 for hubNum 0.
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:e6:2a:6e
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: Port 0
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: got dev 0x5d1be04
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: up
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: attached
Dec 7 09:52:55 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x9d22100.
Dec 7 09:52:55 Mehers-MB-Pro-2 configd[14]: rtmsg: error writing to routing socket
Dec 7 09:53:02 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Waiting for index to be ready (905 > 0)
Dec 7 09:53:03 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Data
Dec 7 09:53:03 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
Dec 7 09:53:03 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
Dec 7 09:53:03 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
Dec 7 09:53:04 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
Dec 7 09:53:04 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
Dec 7 09:53:04 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 2 seconds and then try again
Dec 7 09:53:06 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
Dec 7 09:53:06 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
Dec 7 09:53:06 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 4 seconds and then try again
Dec 7 09:53:09 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_Reconnect: soft mounted and hidden volume so do not notify KEA for /Volumes/Data
Dec 7 09:53:10 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
Dec 7 09:53:10 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
Dec 7 09:53:10 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 8 seconds and then try again
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: No Ack
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
Dec 7 09:53:17 Mehers-MB-Pro-2 configd[14]: AppleTalk startup
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data failed 49.
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: MAC AUTH succeeded
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: AirPort: Link Up on en1
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetDisconnect called for port 0x4fd2300
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: filter detached
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: down
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: detached
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: Freeing hub at 0x4bb4800.
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x7c92a00.
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetConnect: returning port 0x7c92a00
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: Allocated hub 0x4bb4800 for hubNum 0.
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:e6:74:89
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: Port 0
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: got dev 0x4dd6604
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: wireless interface detected.
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: up
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: attached
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x7c92a00.
Dec 7 09:53:17 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: interface en is coming UP
Dec 7 09:53:23 Mehers-MB-Pro-2 configd[14]: AppleTalk startup complete
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Data
Dec 7 09:53:28 Mehers-MB-Pro-2 diskimages-helper[3365]: terminating disk1 - image is no longer available
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Data
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: rder First]
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: ] [IOType Read] [PBlkNum 722696] [LBlkNum 29801] [FSLogMsgID 1403590549] [FSLogMsgOrder First]
Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher‚Äôs MB Pro/.Spotlight-V100/Store-V1/Stores/BC3DE15F-75AA-4E8E-9111-4C032F3A085F)(Error ) IndexCI in copyFileOrFd:write error (6)
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: HFS resolvelink: can't find iNode463676
Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher‚Äôs MB Pro/.Spotlight-V100/Store-V1/Stores/BC3DE15F-75AA-4E8E-9111-4C032F3A085F)(Error ) IndexCI in copyFileOrFd:write failed - expected:12017024, actual: 1048576
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:28: --- last message repeated 1 time ---
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: [FSLogMsgOrder First]
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:28 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Stopping backupd to allow ejection of backup destination disk!
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: 741] [FSLogMsgOrder First]
Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher‚Äôs MB Pro/.Spotlight-V100/Store-V1/Stores/BC3DE15F-75AA-4E8E-9111-4C032F3A085F)(Error ) IndexCI in recoverIndex:recover canceled (live.0.)
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:28 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 received VQ_NOTRESP event (1)
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:28: --- last message repeated 1 time ---
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Data-1
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Data-1
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Data-1
Dec 7 09:53:28 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: primary reconnect failed 5, trying secondary /Volumes/Data-1
Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher‚Äôs MB Pro/.Spotlight-V100/Store-V1/Stores/B6F40692-02AF-4C0C-8F42-19D3C2E8FFCC)(Error ) IndexCI in ContentIndexUpdateContent:Caught mach exception. Fun Fun Fun.
Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher‚Äôs MB Pro/.Spotlight-V100/Store-V1/Stores/B6F40692-02AF-4C0C-8F42-19D3C2E8FFCC)(Error ) IndexGeneral in bool siwriteBackAndIndex(_SI*, __ContentIndex*, const __CFDictionary*, const __CFDictionary*, db_obj**, const __CFString*, int, bool, bool, bool, __SIUserCtx*, const __CFString*, int32_t, bool):ContentIndexUpdateContent failed
Dec 7 09:53:28 Mehers-MB-Pro-2 mds[38]: (/Volumes/Backup of Meher‚Äôs MB Pro/.Spotlight-V100/Store-V1/Stores/B6F40692-02AF-4C0C-8F42-19D3C2E8FFCC)(Error ) IndexGeneral in void setAttributes(siset_attrctx*, Boolean, long unsigned int):Couldn't update index.
Dec 7 09:53:28 Mehers-MB-Pro-2 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[259]: StatusMonitor::volumesChangedCallBack returned -47
Dec 7 09:53:29 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:29 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:29: --- last message repeated 1 time ---
Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:30: --- last message repeated 1 time ---
Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:30 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Stopping backupd to allow ejection of backup destination disk!
Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:30: --- last message repeated 1 time ---
Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:30 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:30: --- last message repeated 1 time ---
Dec 7 09:53:30 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3359]: Backup failed with error: 26
Dec 7 09:53:30 Mehers-MB-Pro-2 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[259]: StatusMonitor::volumesChangedCallBack returned -47
Dec 7 09:53:30: --- last message repeated 1 time ---
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:31: --- last message repeated 1 time ---
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:31: --- last message repeated 1 time ---
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:31: --- last message repeated 1 time ---
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:31 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:31: --- last message repeated 1 time ---
Dec 7 09:53:31 Mehers-MB-Pro-2 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[259]: StatusMonitor::volumesChangedCallBack returned -47
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:32: --- last message repeated 1 time ---
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:32: --- last message repeated 1 time ---
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:32: --- last message repeated 1 time ---
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:32: --- last message repeated 1 time ---
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: jnl: disk1s2: close: journal 0x4e8ae08, is invalid. aborting outstanding transactions
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:32: --- last message repeated 1 time ---
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]: disk1s2: media is not present.
Dec 7 09:53:32 Mehers-MB-Pro-2 /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[259]: StatusMonitor::volumesChangedCallBack returned -47
Dec 7 09:53:32 Mehers-MB-Pro-2 kernel[0]:
Dec 7 09:53:32: --- last message repeated 1 time ---
Dec 7 09:53:34 Mehers-MB-Pro-2 com.apple.launchd[1] (com.apple.netauth.sysagent[3360]): Stray process with PGID equal to this dead job: PID 3363 PPID 1 check_afp
Dec 7 09:53:40 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Data, flags 0, pid 3414
Dec 7 09:54:36 Mehers-MB-Pro-2 [0x0-0x14014].com.apple.finder[259]: AFPFSMapIDName afpfsMapIDNameFSCTL returned -1, errno: 2
Dec 7 09:54:55: --- last message repeated 7 times ---
Dec 7 09:55:08: --- last message repeated 8 times ---
Dec 7 09:55:12 Mehers-MB-Pro-2 [0x0-0x14014].com.apple.finder[259]: AFPFSMapIDName afpfsMapIDNameFSCTL returned -1, errno: 2
Dec 7 09:55:17: --- last message repeated 7 times ---
Dec 7 09:59:07 Mehers-MB-Pro-2 kernel[0]: Link Up: Ctrl 1140, Adv 0de1-0200, Lpa cde1-2c00 Autoneg capable 1
Dec 7 09:59:12 Mehers-MB-Pro-2 kernel[0]: AirPort: Link Down on en1
Dec 7 09:59:12 Mehers-MB-Pro-2 configd[14]: AppleTalk shutdown
Dec 7 09:59:12 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: interface en is going DOWN
Dec 7 09:59:12 Mehers-MB-Pro-2 configd[14]: AppleTalk shutdown complete
Dec 7 09:59:12 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: interface en is going DOWN
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetDisconnect called for port 0x4fd2300
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: filter detached
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: down
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en1: detached
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: Freeing hub at 0x4bb4800.
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x4fd2300.
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetConnect: returning port 0x4fd2300
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: Allocated hub 0x4bb4800 for hubNum 0.
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:e1:0f:ab
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: Port 0
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: got dev 0x4e3d204
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: up
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: attached
Dec 7 09:59:13 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x4fd2300.
Dec 7 09:59:14 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845766270
Dec 7 09:59:14 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845766270
Dec 7 09:59:14 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845766370
Dec 7 09:59:14 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845766370
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845766520
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845766520
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845766622
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845766622
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845766770
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845766770
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845767020
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845767020
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845767273
Dec 7 09:59:15 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845767273
Dec 7 09:59:16 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845767622
Dec 7 09:59:16 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845767622
Dec 7 09:59:16 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/4 to 224.0.0.251:5353 skt 7 error -1 errno 50 (Network is down) 1845767622
Dec 7 09:59:16 Mehers-MB-Pro-2 mDNSResponder[16]: mDNSPlatformSendUDP sendto failed to send packet on InterfaceID 00824E00 en1/6 to FF02:0000:0000:0000:0000:0000:0000:00FB:5353 skt 8 error -1 errno 50 (Network is down) 1845767622
Dec 7 09:59:16 Mehers-MB-Pro-2 configd[14]: rtmsg: error writing to routing socket
Dec 7 10:00:54 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Backup requested by user
Dec 7 10:00:54 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Starting standard backup
Dec 7 10:00:54 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Data-1
Dec 7 10:00:54 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:00:54 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:00:54 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 1 seconds and then try again
Dec 7 10:00:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:00:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:00:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 2 seconds and then try again
Dec 7 10:00:57 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:00:57 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:00:57 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 4 seconds and then try again
Dec 7 10:01:00 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_Reconnect: posting to KEA EINPROGRESS for /Volumes/Data-1
Dec 7 10:01:00 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 received VQ_NOTRESP event (1)
Dec 7 10:01:00 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 type 'afpfs', mounted on '/Volumes/Data-1', from 'afp_0TSQUm1d9lTB00ntaN0Pyetl-1.2f000012', not responding
Dec 7 10:01:00 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 found 1 filesystem(s) with problem(s)
Dec 7 10:01:00 Mehers-MB-Pro-2 loginwindow[39]: 1 server now unresponsive
Dec 7 10:01:01 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:01:01 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:01:01 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 8 seconds and then try again
Dec 7 10:01:05 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_mount: /Volumes/Data, pid 3441
Dec 7 10:01:05 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 type 'afpfs', mounted on '/Volumes/Data-1', from 'afp_0TSQUm1d9lTB00ntaN0Pyetl-1.2f000012', not responding
Dec 7 10:01:05 Mehers-MB-Pro-2 loginwindow[39]: 1 server now unresponsive
Dec 7 10:01:05 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Network volume mounted at: /Volumes/Data
Dec 7 10:01:09 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:01:09 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:01:09 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
Dec 7 10:01:19 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:01:19 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:01:19 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
Dec 7 10:01:20 Mehers-MB-Pro-2 hdiejectd[3459]: running
Dec 7 10:01:21 Mehers-MB-Pro-2 kernel[0]: jnl: disk1s2: replay_journal: from: 75768832 to: 76011520 (joffset 0x1d0f000)
Dec 7 10:01:22 Mehers-MB-Pro-2 kernel[0]: jnl: disk1s2: journal replay done.
Dec 7 10:01:22 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 type 'afpfs', mounted on '/Volumes/Data-1', from 'afp_0TSQUm1d9lTB00ntaN0Pyetl-1.2f000012', not responding
Dec 7 10:01:22 Mehers-MB-Pro-2 loginwindow[39]: 1 server now unresponsive
Dec 7 10:01:22 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Disk image /Volumes/Data/Meher’s MB Pro_002332b0b0ea.sparsebundle mounted at: /Volumes/Backup of Meher’s MB Pro
Dec 7 10:01:22 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Backing up to: /Volumes/Backup of Meher’s MB Pro/Backups.backupdb
Dec 7 10:01:29 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:01:29 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:01:29 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
Dec 7 10:01:30 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Waiting for index to be ready (906 > 0)
Dec 7 10:01:35: --- last message repeated 1 time ---
Dec 7 10:01:38 Mehers-MB-Pro-2 KernelEventAgent[40]: tid 00000000 unmounting 1 filesystems
Dec 7 10:01:39 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_unmount: /Volumes/Data-1, flags 524288, pid 40
Dec 7 10:01:39 Mehers-MB-Pro-2 loginwindow[39]: No servers unresponsive
Dec 7 10:01:39 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data-1
Dec 7 10:01:39 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect on /Volumes/Data-1 failed 49.
Dec 7 10:01:39 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: sleep for 10 seconds and then try again
Dec 7 10:01:45 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Waiting for index to be ready (905 > 0)
Dec 7 10:02:00: --- last message repeated 1 time ---
Dec 7 10:02:10 Mehers-MB-Pro-2 kernel[0]: Link Down
Dec 7 10:02:10 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: interface en is going DOWN
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetDisconnect called for port 0x9cd4800
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: filter detached
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: down
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: detached
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: Freeing hub at 0x4bb4800.
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x9cd4800.
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetConnect: returning port 0x9cd4800
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: Allocated hub 0x4bb4800 for hubNum 0.
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:f4:e9:4f
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: Port 0
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: got dev 0x5d1be04
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: up
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: attached
Dec 7 10:02:14 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x9cd4800.
Dec 7 10:02:14 Mehers-MB-Pro-2 configd[14]: rtmsg: error writing to routing socket
Dec 7 10:02:20 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Waiting for index to be ready (905 > 0)
Dec 7 10:02:45 Mehers-MB-Pro-2 /System/Library/CoreServices/backupd[3439]: Waiting for index to be ready (905 > 0)
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: Link Up: Ctrl 1140, Adv 0de1-0200, Lpa cde1-2cff Autoneg capable 1
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetDisconnect called for port 0x62aeb00
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: filter detached
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: down
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en2: detached
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: Freeing hub at 0x4bb4800.
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIf_Create: created userIf at 0x62aeb00.
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNetConnect: returning port 0x62aeb00
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0 does not exist, allocating memory.
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: Allocated hub 0x4bb4800 for hubNum 0.
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: VMNETSOBINDTOHUB: port: paddr 00:50:56:f5:10:a0
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: Hub 0
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: Port 0
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: got dev 0x4e3d204
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: up
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: bridge-en0: attached
Dec 7 10:02:46 Mehers-MB-Pro-2 kernel[0]: vmnet: VNetUserIfFree: freeing userIf at 0x62aeb00.
Dec 7 10:02:48 Mehers-MB-Pro-2 mDNSResponder[16]: Note: Frequent transitions for interface en0 (192.168.1.130); network traffic reduction measures in effect
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: doing reconnect on /Volumes/Data
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: connect to the server /Volumes/Data
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Logging in with uam 10 /Volumes/Data
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: Restoring session /Volumes/Data
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfs_DoReconnect: primary reconnect failed 5, trying secondary /Volumes/Data
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfsCheckOpenFiles: File <1d89> can not be reopened due to deny modes or byte range locks (file has exclusive access).
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: AFP_VFS afpfsCheckOpenFiles: File <token> can not be reopened due to deny modes or byte range locks (file has exclusive access).
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: disk1s2: 0x5 (UNDEFINED).
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]:
Dec 7 10:02:55: --- last message repeated 1 time ---
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: disk1s2: 0x5 (UNDEFINED).
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]:
Dec 7 10:02:55: --- last message repeated 1 time ---
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: disk1s2: 0x5 (UNDEFINED).
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]:
Dec 7 10:02:55: --- last message repeated 1 time ---
Dec 7 10:02:55 Mehers-MB-Pro-2 kernel[0]: disk1s2: 0x5 (UNDEFINED).

After changing my wifi password I am having trouble finding my time machine on my network, any help please?

I have just changed my wifi password for added security but cannot find my time machine on my network. In the status bar it says that the time machine is not configured (although it has been) and every time I try to find it using airport utlity it remains hidden. Any help would be appreciated as I have a recent back up on there.

First off, thank you so much to everyone who is trying to help! I really appreciate it!
I opened the "backups.backupdb" folder as you suggested "jeffreyfromtas" and found 2 folders:
dvlynn's iMac and
dvlynn's iMac 2.
The 1st folder seems to contain all the backups from the 1st time it backed up in Sept. 2010 until the last time it backed up without error in January of this year.
The 2nd folder contains one file titled "2014-01-03-175020.inProgress"
I purchased this time machine backup drive in 2010 after the origional drive on my iMac crashed and was replaced. When that happened my system was updated to Snow Leopard where it is now. The only major changes I have made are that I moved a lot of large video files off my main drive onto external hard drives to make more room on the iMac.
Other than that everything has stayed the same.
I'm asking it what size the 2 folders are but it's taking forever to answer and I venture to guess it will be 99.99% in the 1st folder and 0.01% in the second folder.
Let me know if that makes any sense.
And thanks again!

Time machine crashes after Yosemite upgrade

I recently upgraded to Yosemite 10.2.2. on a mid-2010 MacBook, but am having problems backing up using TimeMachine.
I can access my past backups, which is good news, although I need to select one of the disks being backed up in the left column of the finder window (if I just select my username it doesn't seem to work). However, when I attempt a backup the computer crashes during the beginning of the backup process ("Processing backup"). I don't get any particular error message when Time Machine crashes, the computer just restarts and sometimes I will get an error message once the computer has finished restarting indicating that the computer restarted because of a problem.
I back up onto a non-Apple (Seagate) connected to the WiFi network drive, which has been working well for about 6 months under the previous OS.
Anyone have any thoughts on this? I've run the disk utility to repair disk permissions, removed the network disk as backup then re-added.

And here is the Problem Details and System Configuration in case its helpful:
Anonymous UUID: B73BF844-60BD-9880-938A-BEF0C404EA33
Thu Jan 29 23:20:29 2015
*** Panic Report ***
panic(cpu 1 caller 0xffffff8019735d11): "hfs_UNswap_BTNode: invalid backward link (0x00012299 == 0x00012299)\n"@/SourceCache/xnu/xnu-2782.10.72/bsd/hfs/hfs_endian.c:303
Backtrace (CPU 1), Frame : Return Address
0xffffff8085e63030 : 0xffffff801932fe41
0xffffff8085e630b0 : 0xffffff8019735d11
0xffffff8085e63100 : 0xffffff8019726327
0xffffff8085e63130 : 0xffffff801957b5e5
0xffffff8085e63240 : 0xffffff801957aa5a
0xffffff8085e632f0 : 0xffffff8019578ff4
0xffffff8085e63340 : 0xffffff801975e7b1
0xffffff8085e63370 : 0xffffff8019763cd0
0xffffff8085e63430 : 0xffffff80197429ba
0xffffff8085e63550 : 0xffffff8019570cb6
0xffffff8085e635e0 : 0xffffff80197ac9d8
0xffffff8085e63f50 : 0xffffff801984b386
0xffffff8085e63fb0 : 0xffffff8019436e86
BSD process name corresponding to current thread: mds_stores
Mac OS version:
14C109
Kernel version:
Darwin Kernel Version 14.1.0: Mon Dec 22 23:10:38 PST 2014; root:xnu-2782.10.72~2/RELEASE_X86_64
Kernel UUID: DCF5C2D5-16AE-37F5-B2BE-ED127048DFF5
Kernel slide: 0x0000000019000000
Kernel text base: 0xffffff8019200000
__HIB text base: 0xffffff8019100000
System model name: MacBook7,1 (Mac-F22C89C8)
System uptime in nanoseconds: 3182901727712
last loaded kext at 3016699200744: com.apple.filesystems.afpfs 11.0 (addr 0xffffff7f9bfb2000, size 364544)
last unloaded kext at 338817335836: com.apple.filesystems.msdosfs 1.10 (addr 0xffffff7f9bf3a000, size 61440)
loaded kexts:
com.apple.filesystems.afpfs 11.0
com.apple.nke.asp-tcp 8.0.0
com.apple.filesystems.smbfs 3.0.0
com.apple.driver.AppleBluetoothMultitouch 85.3
com.apple.driver.AudioAUUC 1.70
com.apple.driver.AppleHWSensor 1.9.5d0
com.apple.driver.AGPM 100.15.5
com.apple.filesystems.autofs 3.0
com.apple.iokit.IOBluetoothSerialManager 4.3.2f6
com.apple.driver.AppleOSXWatchdog 1
com.apple.driver.AppleMikeyHIDDriver 124
com.apple.driver.AppleMikeyDriver 269.25
com.apple.driver.AppleHDA 269.25
com.apple.driver.AppleUpstreamUserClient 3.6.1
com.apple.driver.AppleLPC 1.7.3
com.apple.iokit.IOUserEthernet 1.0.1
com.apple.GeForceTesla 10.0.0
com.apple.driver.AppleBacklight 170.5.0
com.apple.driver.AppleMCCSControl 1.2.11
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport 4.3.2f6
com.apple.Dont_Steal_Mac_OS_X 7.0.0
com.apple.driver.AppleHWAccess 1
com.apple.driver.AppleHV 1
com.apple.driver.ACPI_SMC_PlatformPlugin 1.0.0
com.apple.driver.SMCMotionSensor 3.0.4d1
com.apple.driver.AppleUSBTCButtons 240.2
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 35
com.apple.driver.AppleUSBTCKeyboard 240.2
com.apple.iokit.SCSITaskUserClient 3.7.3
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage 2.7.0
com.apple.driver.AirPort.Brcm4331 800.20.24
com.apple.nvenet 2.0.22
com.apple.driver.AppleUSBHub 705.4.2
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleAHCIPort 3.1.0
com.apple.driver.AppleUSBEHCI 705.4.14
com.apple.driver.AppleUSBOHCI 656.4.1
com.apple.driver.AppleRTC 2.0
com.apple.driver.AppleHPET 1.8
com.apple.driver.AppleACPIButtons 3.1
com.apple.driver.AppleSMBIOS 2.1
com.apple.driver.AppleACPIEC 3.1
com.apple.driver.AppleAPIC 1.7
com.apple.driver.AppleIntelCPUPowerManagementClient 218.0.0
com.apple.nke.applicationfirewall 161
com.apple.security.quarantine 3
com.apple.security.TMSafetyNet 8
com.apple.driver.AppleIntelCPUPowerManagement 218.0.0
com.apple.security.SecureRemotePassword 1.0
com.apple.driver.AppleMultitouchDriver 262.33.1
com.apple.AppleGraphicsDeviceControl 3.8.6
com.apple.kext.triggers 1.0
com.apple.driver.AppleBluetoothHIDKeyboard 176.2
com.apple.driver.IOBluetoothHIDDriver 4.3.2f6
com.apple.driver.AppleHIDKeyboard 176.2
com.apple.iokit.IOSerialFamily 11
com.apple.driver.DspFuncLib 269.25
com.apple.kext.OSvKernDSPLib 1.15
com.apple.iokit.IOUSBUserClient 705.4.0
com.apple.driver.AppleHDAController 269.25
com.apple.iokit.IOHDAFamily 269.25
com.apple.iokit.IOAudioFamily 203.3
com.apple.vecLib.kext 1.2.0
com.apple.nvidia.classic.NVDANV50HalTesla 10.0.0
com.apple.nvidia.classic.NVDAResmanTesla 10.0.0
com.apple.driver.AppleBacklightExpert 1.1.0
com.apple.driver.AppleSMBusController 1.0.13d1
com.apple.iokit.IOBluetoothHostControllerUSBTransport 4.3.2f6
com.apple.iokit.IOSurface 97
com.apple.iokit.IOBluetoothFamily 4.3.2f6
com.apple.driver.IOPlatformPluginLegacy 1.0.0
com.apple.driver.IOPlatformPluginFamily 5.8.1d38
com.apple.driver.AppleSMBusPCI 1.0.12d1
com.apple.iokit.IONDRVSupport 2.4.1
com.apple.iokit.IOGraphicsFamily 2.4.1
com.apple.driver.AppleSMC 3.1.9
com.apple.iokit.IOSCSIBlockCommandsDevice 3.7.3
com.apple.driver.AppleUSBMultitouch 245.2
com.apple.iokit.IOUSBHIDDriver 705.4.0
com.apple.iokit.IOUSBMassStorageClass 3.7.1
com.apple.iokit.IOSCSIMultimediaCommandsDevice 3.7.3
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily 1.7.1
com.apple.iokit.IOCDStorageFamily 1.7.1
com.apple.driver.AppleUSBMergeNub 705.4.0
com.apple.driver.AppleUSBComposite 705.4.9
com.apple.iokit.IOAHCISerialATAPI 2.6.1
com.apple.iokit.IOSCSIArchitectureModelFamily 3.7.3
com.apple.iokit.IO80211Family 710.55
com.apple.iokit.IONetworkingFamily 3.2
com.apple.iokit.IOAHCIFamily 2.7.5
com.apple.driver.AppleEFINVRAM 2.0
com.apple.driver.AppleEFIRuntime 2.0
com.apple.iokit.IOUSBFamily 710.4.14
com.apple.driver.NVSMU 2.2.9
com.apple.iokit.IOHIDFamily 2.0.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox 300.0
com.apple.kext.AppleMatch 1.0.0d1
com.apple.driver.AppleKeyStore 2
com.apple.driver.AppleMobileFileIntegrity 1.0.5
com.apple.driver.AppleCredentialManager 1.0
com.apple.driver.DiskImages 396
com.apple.iokit.IOStorageFamily 2.0
com.apple.iokit.IOReportFamily 31
com.apple.driver.AppleFDEKeyStore 28.30
com.apple.driver.AppleACPIPlatform 3.1
com.apple.iokit.IOPCIFamily 2.9
com.apple.iokit.IOACPIFamily 1.4
com.apple.kec.corecrypto 1.0
com.apple.kec.Libm 1
com.apple.kec.pthread 1
Model: MacBook7,1, BootROM MB71.0039.B0B, 2 processors, Intel Core 2 Duo, 2.4 GHz, 4 GB, SMC 1.60f6
Graphics: NVIDIA GeForce 320M, NVIDIA GeForce 320M, PCI, 256 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x0198, 0x393930353432382D3032362E4130314C4620
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1067 MHz, 0x0198, 0x393930353432382D3032362E4130314C4620
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.106.98.100.24)
Bluetooth: Version 4.3.2f6 15235, 3 services, 27 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: TOSHIBA MK2555GSXF, 250.06 GB
Serial ATA Device: HL-DT-ST DVDRW GS23N
USB Device: Ext HDD 1021
USB Device: Built-in iSight
USB Device: BRCM2070 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Apple Internal Keyboard / Trackpad
Thunderbolt Bus:

Why does "enter time machine" crash my computer?

The title is pretty descriptive. The "crash" is that I get the spinning beach ball of death and over the course of a few seconds my machine becomes completely non-responsive to input (keystokes stop working, then the wiggling the mouse stops working). I have do hold down the power button to reset the machine after that. Although I'm quite familiar with http://pondini.org/OSX/Home.html I don't see that anything readily addresses "Time Machine crashes my whole OS". Any ideas? Thanks!

Here a log of what happens. I got this same effective log in two different situations: first when I ran an attempted backup, then again basically the same when I changed the computer name and tried again. That second attempt is probably pretty telling since there is no sparsebundle with the new computer name, meaning the error of "diskimagealreadyattached" cannot be true.
Starting standard backup
Attempting to mount network destination URL: afp://[email protected]/timecapsule
Mounted network destination at mountpoint: /Volumes/timecapsule using URL: afp://[email protected]/timecapsule
Disk image already attached: /Volumes/timecapsule/computer_dying.sparsebundle, DIHLDiskImageAttach returned: 35
Running backup verification
Disk image already attached: /Volumes/timecapsule/computer_dying.sparsebundle, DIHLDiskImageAttach returned: 35
Backup verification incomplete!
Disk image already attached: /Volumes/timecapsule/computer_dying.sparsebundle, DIHLDiskImageAttach returned: 35
Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7faf9305d400 {MessageParameters=(
Ejected Time Machine network volume.
Waiting 60 seconds and trying again.
Attempting to mount network destination URL: afp://[email protected]/timecapsule
Mounted network destination at mountpoint: /Volumes/timecapsule using URL: afp://[email protected]/timecapsule
Disk image already attached: /Volumes/timecapsule/computer_dying.sparsebundle, DIHLDiskImageAttach returned: 35
Running backup verification
Disk image already attached: /Volumes/timecapsule/computer_dying.sparsebundle, DIHLDiskImageAttach returned: 35
Backup verification incomplete!
Disk image already attached: /Volumes/timecapsule/computer_dying.sparsebundle, DIHLDiskImageAttach returned: 35
Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7faf93507310 {MessageParameters=(
Ejected Time Machine network volume.
Waiting 60 seconds and trying again.
Attempting to mount network destination URL: afp://[email protected]/timecapsule
Mounted network destination at mountpoint: /Volumes/timecapsule using URL: afp://[email protected]/timecapsule
Disk image already attached: /Volumes/timecapsule/computer_dying.sparsebundle, DIHLDiskImageAttach returned: 35
Running backup verification
Disk image already attached: /Volumes/timecapsule/computer_dying.sparsebundle, DIHLDiskImageAttach returned: 35
Backup verification incomplete!
Disk image already attached: /Volumes/timecapsule/computer_dying.sparsebundle, DIHLDiskImageAttach returned: 35
Failed to mount disk image: Error Domain=com.apple.backupd.ErrorDomain Code=31 "The operation couldn’t be completed. (com.apple.backupd.ErrorDomain error 31.)" UserInfo=0x7faf93060170 {MessageParameters=(

Time machine crashes finder on restore and I see no record of files.

Time machine crashes the finder on restore and I see no files.
Just tried to resort a single file and it crashes the finder as soon as I try to go down in the different folders. several restarts did solve that bit and after several attempts I get down 2 or 3 levels but there are no files at all.
If I mount the sparse image on my server (I backup to a server with external hard disk over my local network) all the files are there and I can access them. So I have restored the corrupted file I wanted too, but still need to solve this problem.
Any tips?

ChangeAgent wrote:
OK. if I go in to the disk that I backup to. I find the disk image of the backup. if I load this I see what is inside.
Again, what do you mean by "load"? If you mean mounting the disk image and using the Finder to copy from the files inside it, that's not "restoring," and isn't recommended, as you will have permissions problems with the copied files.
the folder that refuses to back (all of them on the second level these are tho folders that are the dated folders of the backup) up is the one that is locked, has different permissions as it should have. If I fix the permission of the folders I can see them in the TM backup. however every new backed up folder is locked again and can not be restored till unlocked as described above.
Yes, that's correct. Time Machine tries to keep us mere mortals from shooting ourselves in the foot by messing about with the backups. Once you've manually altered things inside your backups, there's no telling what will (or won't) happen.
Try this: create a new user, and sign on to that account. Make a test folder somewhere inside it's home folder (but not it's desktop) and put some test files in it. Run a backup. Then use the "Star Wars" display to restore that folder to the desktop (an "alternate location.") Does that work? Can you see and change the restored files as that user? Are other users prevented from changing them?
I don't know exactly what's happened, but it appears your backups are badly corrupted. You can try Repairing the sparse bundle (as Mr. Horowitz suggested), per #A5 in the Time Machine - Troubleshooting *User Tip,* also at the top of this forum, but it's doubtful that will really fix them. Your only option may be to delete the sparse bundle and let Time Machine start fresh.

Time machine restore from network drive kernel panic

I had a late 2013 macbook pro 15" retina, I was backing up with time machine to a network drive (western digital my cloud). All of my backups are there and the data looks valid. In April I ended up selling the macbook pro, then recently I bought another one and attempted to restore from the network drive.
I chose the option to restore on boot from network device, it properly detects and lets me browse my previous backups. I choose restore, the restore will run for a few hours and then reboot with a kernel panic.
panic(cpu 0 caller 0xffffff00184c0ac1): "Unable to find driver for this platform: \"ACPI\".\n"0/SourceCache/xnu/xnu-2422.90.20/iokit/Kernel/IOPlatformExpert.cpp: 1541"
I've tried a few different backups, one from April, one from march...both result in the same error. Any ideas why this would happen?

Time Machine full system restores only work if the backup disk doesn't need drivers separate from Mac OS X to mount. To make a long story short, you CAN'T do a full system restore with the disk your backups are on.

Time Machine and a network drive combined

I figured out how to connect Time Machine with a network drive (like LaCie Mini). It works great, the only thing is, everytime I restart the mac I need to re-connect manually to the server in order TM can run.
I wondered why OS X gives not the option to connect to certain servers AUTOMATICALLY when starting up?
thanks for help

Well,
PLEASE can you tell us how you figured out how to backup to a network drive because Apple tech told me you could not do that!
To your question though, on those LaCie drives, you have to log in with a password, right? On the drives I have used with clients, although the password was filled in for me, we had to press OK every single time to actually connect to the drive... I could not bypass the login procedure on the drive, it had nothing to do with OSX. You might serve yourself well to see if LaCie can offer you a way to connect to the drive automatically?
Although I know nothing about scripts, could you just get a script to run automatically at startup to connect you to that drive?
I'm interested in this topic so please feel free to share what you know and your experience with it. Thanks in advance.
I was also frustrated to find out that I couldn't even back up via Time Machine to a drive connected via USB to my Airport Extreme... I mean come on!

Time machine over a network volume

So since Snow Leopard (and I think Leopard), when you use Time machine to back up over a network share (for example, a USB drive attached to a mini server), the OSX creates a sparsebundle image where all time machine files are stored.
In Lion, If I encrypt my hard drive, and I keep on backing up using time machine over this network share.. will the sparsebundle image be encrypted or not?

I don't see much difference between using a sparsebundle image or an encrypted sparsebundle image.
I've sent this feedback to Apple see if they enable this in subsequent updates.

Time Machine over the Network: Terribly Slow

Hello,
I've been using Time Machine for over 3 years now with no issues over the network; the destination being a 2TB external Seagate connected to another iMac connected through gigabit ethernet. Everything has been working flawlessly: Every hour Time Machine would MOUNT the sparseimage it created on the disk, BACKUP the data and UNMOUNT the disk image when finished.
Until I upgraded to Lion. The above process is still working per se, however it is PAINFULLY slow! A 50MB backup can take up to AN HOUR! Searching around on the net, advised that there could be an issue with Spotlight as well, however this is not the case for me, since Spotlight finished a new index in under 30 mins. Followed every tutorial I could find on the issue, to no avail..
I then upgraded to Mountain Lion with the hope that the issue will clear itself. Cleared my old backups, resetted Time Machine by erasing its .plist file, restarted my iMac just to make sure and connected Time Machine to the network share anew, creating a "sharing only" account on the host iMac, i.e. the one that has the external HD connected through USB. Still no luck.
I painfully realize that I still have the same issue. While backing up, network traffic is under 100KB, and activity monitor does not show any backupd or mds or any similar processes taking anything over 3% of CPU time.
What could be wrong?

Hello again,
Tries on the other iMac (also running 10.8.2) and things are exactly the same: Image creation takes almost half an hour, and copying crawls at under 1MB/min. While time machine image is mounted and Time Machine is "backing up", accessing ANY disk on the host Mac is VERY slow. Seems like something hogs up appleshare when Time Machine is in use. Mind you, there is insignificant network traffic as seen by Activity Monitor, as well as insignificant CPU usage while backing up.
Stopping backup and using tmutil to set the Time Machine destination to the mounted image as mounted by Finder, solves the issue again, revving up Time Machine throughput to over 20MB/sec! There is also no issues acessing the other Mac as well, under this scenario.
Up to this point, the only way I have managed to use Time Machine over a networked external HD is through the NAS server. Both configurations where I am using a Mac running 10.8.2 as a server of the external disk have failed with very low throughput while backing up. Something must be wrong in 10.8.2's afp when Time Machine is mounting the image by itself.
I may need to remind you that I have been successfully backing up to the external HD for 4 years now; something broke a few months after the client iMac was upgraded to Lion and at the time when the host iMac was upgraded to Mountain Lion. Will try to locate a Mac running some later OS X version to do some more testing.
Also reminding that I have used two distinctive iMacs and two external HD drives for my tests so far. The client iMac has remained the same, however 10.8.2 has been reinstalled on it a couple of times. Have also used an afp-enabled NAS server which worked fine with Time Machine.

Can't back up MBA on Time Capsule using Time Machine Via Wifi

Hi,
I can't back up MBA on time capsule using Time Machine via wifi. I bought the time capsule new Dec 2014. I was able to backup for the 1st 3 days. In less than a week time, a message came up every time I tried to back up: "Time Machine couldn’t complete the backup to AirPort Time Capsule. The backup disk could not be found. Make sure the backup disk is connected or select a different backup disk". So, there's been no backup at all for almost 3 weeks. Wifi connectivity under Airport Utility is fine. Green light on the time capsule is on etc.
Please kindly advice what is going on with this time capsule wifi backup. Do I have to connect the time capsule with MBA with a physical cable to perform this job?
Many thanks in advance,
On Ki

The warranty entitles you to complimentary phone support for the first 90 days of ownership.

Time machine on a network drive

The situation:
We have a Mac Pro with a Time Machine volume on an external drive that is attached to a networked Mac. I don't think this is a very common scenario, but it works just fine over a gigabit network. We do not automount any drives on the networked machine but mount (or connect to) this remote machine manually whenever the Mac Pro in question is restarted (which is not often).
The question:
Due to some renovation, we'd like to temporarily connect this external drive to the Mac Pro and mount the Time Machine Volume. Will Time Machine find the correct sparse bundle on the external drive, recognize it as an existing Time Machine backup and update that as long as needed. In other words, the external drive will have a different unix path name, but the sparse bundle will have the correct name. And when the renovation is done, we will resume running Time Machine over the network, and I hope that Time Machine will again do the right thing.
I want to avoid having Time Machine's creating a new backup when the unix path changes.
Thanks.

In the past Apple was not holding you hostage by requiring you to use a Time Capsule for network Time Machine backups. Search on Google for Time machine NAS OS X (or something like that) You will find a number of drives that were working with SL.
Now, they did change the file protocol in Lion, so some of the NAS servers won't work with Lion, at the moment. So long as it is a decent company that makes the NAS they should be releasing a firmware update to get their NAS working with Lion.
One of the companies that put out a press release was Western Digital. They said they would be working on an updated firmware so that you could use it as a Time Machine drive.
Just look around the interwebs and I am sure you will find several that will work.

Time Machine Crash along with death screen

Ever since I did the 10.5.2 update Time Machine crashes, ejects my hard drive, and I keep getting the gray death screen to restart. I turned off Time Machine but my HD keeps getting ejected and still having the restart issue.
I'm running a Mirror face G4 and have NEVER had a problem before, so this is very irritating.

Hi there,
Thanks for your posting - I followed the links in order to try and find out why my disk image may not be working properly.
I backup my MacBook to an internal slave drive on my G4 using Time Machine. It was working fine for a month but has suddenly given me Kernel Panic so from these posts I assume that to mean a corrupt image. I tried running Disk Warrior on the image. It found a HUGE number of errors. Pretty much every file in the volume was repaired for "Extended Attribute". However, unfortunately Disk Warrior gave the following message:
DiskWarrior has successfully built a new directory for the disk named "Backup of JowieBook." The new directory cannot replace the original directory due to a Mac OS services failure.
Try rebuilding again. If this problem persists, please restart from the DiskWarrior CD and then try rebuilding again.
Hmmm, that not good. I haven't tried restarting from the CD because I don't see much point - the image isn't on the boot drive, it's on a slave. I checked the volume read/write status as suggested and this is the result (abridged):
image-path : /Volumes/Lemon Jelly/JowieBook_0016cbcc5f19.sparsebundle
image-type : sparse bundle disk image
writeable : TRUE
autodiskmount : TRUE
removable : TRUE
image-encrypted : false
So I'm pretty stumped. Shall I just run it again? Here's the chmod status of the volume:
drwxr-xr-x 6 jowie jowie 510 Feb 20 22:30 Backup of JowieBook
I'm not very good with Unix but that looks okay to me... So I'm a bit stumped. Any thoughts?
Thanks!

Can you use time machine on a networked hard drive

Can you use time machine on a networked hard drive?

See if this helps: Using Time Machine with a networked hard drive

Time Machine crashes using Mac OSX 10.7.5

Past few days, Time Machine crashes when attempting to use the application. This problem just started and had previously worked.

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.
Step 1
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 name of the crashed application or process in the Filter text field. Select the messages from the time of the last crash, if any. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message (command-V).
When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Anonymize before posting.
Step 2
In the Console window, look under User Diagnostic Reports for crash reports related to the crashed process. The report name starts with the name of the process, and ends with ".crash". Select the most recent report and post the entire contents — again, the text, not a screenshot. In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.) Please don’t post other kinds of diagnostic report — they're very long and not helpful.

Time machine crashes Wifi network

Similar Messages

Maybe you are looking for