Time Machine problems behind network switch?

Just installed a Netgear GS108T gigabit switch and placed my Mac Mini w/backup drives that was being used as a HTPC and Time Machine server behind it, along with the other computers. Neither my Macbook (wireless to router which is also plugged into switch) nor Mac Pro (connected to switch) can backup. I can see & login to the Mini, as well as mount the drives. However, the sparsebundles for the various computers do not mount for very long... they show up then disappear immediately and TM does not complete the backup. Aside from the improved file transfer speeds and lack of TM backups, I haven't noticed any differences after installing the switch so it's been pretty transparent.
Any ideas?

Figured it out. I had to reboot the computer and power cycle the drives that TM used, and found that it fixed things. For some reason I could check them with Disk Utility from all computers (including the host, and no problems found) but not mount them. So a reboot and power cycle of drives fixed it for some weird reason. I thought it was the switch (all devices are plugged into it) as it happened the same night as I installed it, but it was just a coincidence I guess, especially since it was an unmanaged switch. Thanks!

Similar Messages

  • Time Machine Problems - Please Help!

    I am fairly new to the world of Mac's, purchasing my first in late November 2010 and i have recently been investigating Apples own Time Machine software as a means of backing up my Mac. I had an Iomega 1TB Home Media Network drive which i had connected via ethernet to my router and my Mac was on wireless. When Time Machine saw the network drive it refused to back up to it and then occasionally it didn't see it at all. I then decided to use this drive just for the Windows PCs in my household and not for my Mac as i thought it may not be backing up because i have Mac backups and Windows backups on the same drive without partitioning. I have now got a Freecom Classic 3.5" 500GB hard drive connected directly to the USB in my Mac and Time Machine sees it and begins the backup. I get so far and then i receive the error "The backup was not performed because and error occurred while copying files to the backup disk" - i have installed the Time Machine buddy widget from Apple and have looked into it, this is what i get:
    Starting standard backup
    Backing up to: /Volumes/Macbook Pro Backup 1/Backups.backupdb
    Error parsing SystemMigration.log to determine source volume of system migration.
    Backup content size: 58.7 GB excluded items size: 4.9 GB for volume Macintosh HD
    No pre-backup thinning needed: 64.52 GB requested (including padding), 455.32 GB available
    Error: (-36) SrcErr:NO Copying /Applications/AlpineCrawler.app/Contents/Resources/aahh_02.aif to /Volumes/Macbook Pro Backup 1/Backups.backupdb/Macbook Pro/2011-04-12-190436.inProgress/A63BA24E-781B-4368-B837-3A4DCA67834D/Macintosh HD/Applications/AlpineCrawler.app/Contents/Resources
    Stopping backup.
    Error: (-8062) SrcErr:NO Copying /Applications/AlpineCrawler.app/Contents/Resources/aahh_02.aif to /Volumes/Macbook Pro Backup 1/Backups.backupdb/Macbook Pro/2011-04-12-190436.inProgress/A63BA24E-781B-4368-B837-3A4DCA67834D/Macintosh HD/Applications/AlpineCrawler.app/Contents/Resources
    Copied 0 files (387 KB) from volume Macintosh HD.
    Copy stage failed with error:11
    Backup failed with error: 11
    So the Errors are:
    Error parsing SystemMigration.log to determine source volume of system migration.
    Error: (-36) SrcErr:NO Copying /Applications/AlpineCrawler.app/Contents/Resources/aahh_02.aif to /Volumes/Macbook Pro Backup 1/Backups.backupdb/Macbook Pro/2011-04-12-190436.inProgress/A63BA24E-781B-4368-B837-3A4DCA67834D/Macintosh HD/Applications/AlpineCrawler.app/Contents/Resources
    Error: (-8062) SrcErr:NO Copying /Applications/AlpineCrawler.app/Contents/Resources/aahh_02.aif to /Volumes/Macbook Pro Backup 1/Backups.backupdb/Macbook Pro/2011-04-12-190436.inProgress/A63BA24E-781B-4368-B837-3A4DCA67834D/Macintosh HD/Applications/AlpineCrawler.app/Contents/Resources
    Copy stage failed with error:11
    Backup failed with error: 11
    I have tried everything and looked through the forums finding people with similar problems - i have tried Verifying my Internal HD, Repairing my External HD and have tried running Tech Tool Deluxe - all of which cannot find any problems. I have also tried excluding this file but Time Machine just finds the same error with the next file in alphabetical order in the folder - i should also add it is not just the folder Applications. Can someone please tell me if i am doing something wrong as this is always a possibility with my inexperience with Macs.
    Thanks for your help and sorry it's a little long winded.

    Time Machine can back up to some NAS (Network Attached Storage) devices, if they meet Apple's criteria. But there are some downsides; see the pink box in #2 of [Time Machine - Frequently Asked Questions|http://web.me.com/pondini/Time_Machine/FAQ.html] (or use the link in *User Tips* at the top of this forum).
    But yes, even if it supports Time Machine, backing-up both Windoze and OSX to the same partition is unlikely to work.
    You'll have to check with Iomega about that.
    Error parsing SystemMigration.log to determine source volume of system migration.
    That's not really a problem; it just means Time Machine isn't sure whether you "migrated" your data from a different Mac.
    Error: (-36) SrcErr:NO Copying /Applications/AlpineCrawler.app/Contents/Resources/aahh_02.aif to /Volumes/Macbook Pro Backup 1/Backups.backupdb/Macbook Pro/2011-04-12-190436.inProgress/A63BA24E-781B-4368-B837-3A4DCA67834D/Macintosh HD/Applications/AlpineCrawler.app/Contents/Resources
    I have also tried excluding this file but Time Machine just finds the same error with the next file in alphabetical order in the folder - i should also add it is not just the folder Applications.
    That's the kind of thing we see when there's a problem with a file or the destination; often a bad connection. But if it's happening on every file, obviously it's something much more serious.
    Is the external HD formatted properly? See #C1 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum).

  • Help, I am about to pull my hair out, can't get into a locked drive and Time Machine problem

    I've screwed everything up, I think.  I had Time Machine doing backups to an external 500Gig drive and somehow it got locked.  I went into Get Info to try and change the access but it won't allow me.  On top of this problem, my original drive died and I can't get into Time Machine to restore.  When I click "Enter Time Machine", nothing happens.  I created an eDisk and a startup disk to another external drive that I'm using now, but since everything that's been backed up is on the other drive that I can't access.  When I try accessing the drive it gives:  "The folder “G-DRIVE ” can’t be opened because you don’t have permission to see its contents."  I'm not knowledgeable enough to work from the command line, so if I need to do that to access the drive, please walk me though it.  As for the Time Machine problem, I have no idea how to recover anything since it won't even come up, it just sits there.  Outside of blowing my brains out, I don't know what to do.  Any help would be greatly appreciated as I can't afford to take it to Apple to let them try and fix it.

    Hello, not sure how this might affect a TM drive, or not, but...
    Here is what i needed to do for my drive "320GB HD", the last command is just for clean up
    Open Terminal and type these commands carefully with the spaces & change 320GB HD to the name of your drive.
    sudo chflags 0 "/volumes/320GB HD"
    sudo chown root "/volumes/320GB HD"
    sudo chmod 1775 "/volumes/320GB HD"
    sudo -k
    That said, these should be sufficient to do the job:
    sudo chflags 0 "/Volumes/320GB HD"
    sudo chmod a+rx "/Volumes/320GB HD"

  • 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.

  • 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 problems

    My question is this: Is there any way to force Time Machine to make a complete backup of all files, not just the recently changed ones?
    My story so far:
    Installed Leopard yesterday. Detected brand-new (and newly Mac formatted Extended Journaled) Seagate 300GB hard drive and asked if I wanted to use it for Time Machine. Answered yes. Thought I was through with worrying about Time Machine- wrong! First backups went OK- so I thought. First one took several hours and seemed to back up the whole drive. Subsequent ones were shorter, which seemed to make sense. After a couple backups had been performed, decided to see if I could "go back in time". The only window to show up was the original backup (which I never bothered to check to see if it truly was complete). This morning I was greeted with an error that it couldn't do the backup because it couldn't complete the library.
    So I come to this forum and read posts advising me to reformat my drive and name it with no spaces (it was previously "Backup Disk"). I did that, erasing all previous backups. Seemed to help, but...
    Now, unfortunately, Time Machine doesn't realize that the backups are not there anymore and will not do a complete backup with my completely empty external drive. I even tried removing the com.apple.TimeMachine.plist file from its place in the directory to see if that would force the program to build a new library. It didn't.
    Not even sure that making a complete backup again will solve all my Time Machine problems but it's a start!

    I had this same problem when I first started using my Time Machine on my MBP. I had a portable drive (Western Digital 160 gig passport drive).
    I was advised by the tech to do the following before the first use of the drive:
    1. Turn off the time machine
    1. format the drive with your disk utility.
    3. configure the time machine for the drive.
    4. Turn on the time machine. Make sure your not backing up anything but your main hard drive. (Your shouldn't back up any other external hard drives). At least not the first time you run Time machine.
    5. start the backup.
    The first backup is always the longest, but it shouldn't take that long, especially if your doing the Macbook Air.
    Hope this helps.

  • 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

  • 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! 

  • Problems setting up Time Machine using a network drive

    I am having problems setting up TimeMachine on my Mac Mini to work with a WD MyBookLive network drive.  The network drive came with a TimeMachineBackup shared folder preconfigured.  When I first connected the drive to the router and turned on TimeMachine, the TimeMachineBackups appeared as an option when I did "Select Backup Disk" from TimeMachine Preferences.
    I managed to successfully connect to the drive and start a backup running.  However the backup hit a problem and I started getting an error that the "disk was already in use".  I therefore tried to remove the disk to try and start again.  Hoever when I now do go into "Select Backup Disk" from TimeMachine Preferences the shared folder on the drive no longer apperas and I only get the option to serach for an Time Capsule.
    If I go into Finder, the MyBookLive shows up as a connected Device with all its shared folders showing (including the TimeMachineBackup folder)  and my Mac is definitely connected to the drive.  How do I get the Drive & TimeCapsuleBackup shared folder to reappear in TimeMachine Preferences so that I can select it as the destination for my backups?

    Check around the forum, you are one of very very many. It doesn't matter what WD say, do you see a Certified by Apple notice on it?
    Go here, most authoritative site about Time Machine you can find. http://pondini.org/OSX/Home.html
    Specific info on Network Drives are here http://pondini.org/TM/2.html
    Post back here and ask for Pondini if you need more.
    You can also read some tales of woe here

  • Time machine problem. Switching from one external drive to another. Problem started when upgrading to Mavrics, and changing to a WD drive

    I am a long time Mac user, running my business on an apple  platform since 1984. I currently use a 17" MacBook Pro as my primary computer for work. when it is at work it is plugged in via thunderbolt to my monitor and a one tb back up drive. I use time machine to back up the laptop to the one tb drive. When I go home, I take the laptop with me and use another drive at home as a back up. This way I have redundant back ups, in two separate locations. I have been doing this for years, and Time machine has worked flawlessly, automaticity switching from one drive to another.
    I recently switched to Maverics, and got a new drive for home. Now whether I am at home or at work, time machine fails to automatically back up. It will alert me every hour that backups cannot be completed, and I  must go to the time machine control panel and manually select a drive and click, "back up now". I also see an alert that says "waiting to complete first back up" even though each backup has been completed.
    This is quite annoying, and sometimes embarrassing. When giving lectures in large venues, the backup failure alert appears and shuts down my keynote presentation (again, something new since switching to Maverics and the new WD drive.
    I have reformatted the WD drive, and also spent time trying to change parameters in the time machine control panel, but so far no luck.
    Any advice out there?

    Time machine requires a GUID partion scheme, as well as a Mac OS X extended, journaled Volume.
    It needs these to correctly:
    1) copy the files
    2) run a modified spotlight index pass on the files
    Both are required to complete a abckup, and most new drives do not conme this way from the factory.

  • Time Machine backup causes network connections to fail

    We have a simple network with OS X Server (10.6.4) + a 10.6.4 Mac client and a Windows XP client. For some time we have been suffering sporadic drop outs of the network connection from the iMac OS X client to the server: the shared drives just disappear and you can't reconnect.
    I have now narrowed this down to a problem with Time Machine. By logging on as a user on the OS X Server I was able to observe that the user session on the server suffered the same problem sometimes and this ONLY happens when Time Machine is running - I think its always when Time Machine is backing up the server.
    Its an absolutely infuriating problem and very disruptive for our business. I am loath to switch off Time Machine on the server but don't know what else to do. Has anyone else experienced this problem or got any ideas?
    Message was edited by: davidav

    Yep, Rikakiah, seems you are right, I am not alone! There are two other threads here which discuss the same issue:
    http://discussions.apple.com/thread.jspa?messageID=11539266&#11539266
    http://discussions.apple.com/thread.jspa?messageID=11539227
    From my testing it seems that the problem may be related to some interplay between Time Machine and LDAP - I say this because I can sometimes clear the problem and regain access to my shares by going into Workgroup Manager, removing the group assignments (which give access to the shares), saving the change, then adding the group assignments back.
    This made me think that your solution should fix it, but unfortunately although I have excluded /var/db from Time Machine backups, I am still sporadically getting the problem.
    Message was edited by: davidav
    Message was edited by: davidav

  • 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).

Maybe you are looking for