Time Machine backups fail after initial drive connection, cannot eject drive

I have a Macbook Pro 13" Retina Display, 8GB running OS X Mavericks 10.9.4 and have set Time Machine backups to a 1TB WD My Passport.  When I first connect the drive the backup will run fine, but subsequent backups always fail.  In addition I typically cannot eject the drive.  I've scoured online forums and have completely reformatted the drive, and have even deleted some backup settings files from the hard drive, none of these has resolved my issue.

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
The title of the Console window should be All Messages. If it isn't, select
          SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
          View ▹ Show Log List
from the menu bar at the top of the screen.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter the word "Starting" (without the quotes.) You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard."
Each message in the log begins with the date and time when it was entered. Note the timestamp of the last "Starting" message that corresponds to the beginning of an an abnormal backup. Now
CLEAR THE WORD "Starting" FROM THE TEXT FIELD
so that all messages are showing, and scroll back in the log to the time you noted. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
☞ If all you see are messages that contain the word "Starting," you didn't clear the text field.
☞ The log contains a vast amount of information, almost all of which is irrelevant to solving any particular problem. When posting a log extract, be selective. Don't post more than is requested.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
☞ Some private information, such as your name, may appear in the log. Anonymize before posting.

Similar Messages

  • Time Machine backups fail after initial backup in Yosemite

    After upgrading from Mavericks to Yosemite, I was able to run one backup to my trusty USB drive.  Subsequent backups all start with "Preparing backup", and will write roughly 900KB to disk (or so it says) and then fails.  I created a Time Machine-compatible network drive on my Drobo 5n, and again, the initial backup is successful, and subsequent ones fail.  This is concerning and infuriating.  I'm hoping someone out there has encountered this problem as well.
    Please note: this is regarding backups only.  I see a handful of discussions about not being able to perform restores in Yosemite, but that is not my issue.

    Same here.
    From Time Machine Buddy app:
    Starting manual backup
    Total content size: 424.3 GB excluded items size: 21.01 GB for volume Macintosh HD
    Found 2439814 files (403.3 GB) needing backup
    424.87 GB required (including padding), 250.63 GB available
    Deleted backup /Volumes/Backupmac/Backups.backupdb/.df. (3)/2014-10-23-120445.inProgress/F8CFC567-7E6E-49B0-B366-88DF31DAF49B containing 4 KB; 250.63 GB now available, 424.87 GB required
    Removed 1 expired backups so far, more space is needed - deleting oldest backups to make room
    Deleted 1 backups containing 4 KB total; 250.63 GB now available, 424.87 GB required
    Backup date range was shortened: oldest backup is now Oct 23, 2014
    Backup failed with error 7: Not enough available disk space on the target volume.
    It wants to do a full backup. Fine... so why doesn't it just delete more of the old backups to do so? I don't want to wipe the backup drive and start over now, but that seems like the only way to go.

  • Time machine backup fails; error creating folder. Western Digital drive requires password which is perhaps/likely the issue. I can't eliminate the password/encryption.

    Time Machine backup fails on new WD external drive (My Passport Studio); error creating folder (after several hours of Time Machine apparently working).
    Background: I purchased a Western Digital drive from an Apple Store to use for Time Machine backup.  I followed the Western Digital instructions that came with the drive for Mac. I didn't get the Time Machine prompt which the instructions indicated I would receive--namely to select whether I want to encrypt my Time Macine backups. (I already have a Time Machine backup I use at another location, which is perhaps why I didn't receive a prompt.)
    I decided to install the Western Digital utilities and security software that comes on the disk--with a view to potentially encrypting the disk (since I still wanted to have an encrypted backup since I was mobile). I forgot that (from experience 2-years previous) that I shouldn't install Western Digital software because it just makes life really complicated.
    I tried several times to do a Time Machine backup with failures each time (error creating the backup folder). I tried to get help from WD but I don't think the technicians were following what my issue was. Potentially I was not helpful in explaining it. I deleted the WD applications from my system after the first contact with WD. However the problem persisted--I still had an encrypted hard drive. After three phone sessions with three different WD techs I still could not get a solution. (By the second call I was not at all interested in having an encrypted drive--I just wanted to format and restore the drive to an unencrypted state so that I could have SOME kind of Time Machine backup.)
    I still don't have a solution--either to get Time Machine working with the WD encryption/password on the drive, or to remove the encryption so I can backup. Right now my options are to return the drive to the Apple Store -- or get a return authorization from WD. Seems crazy since the drive is fine and I have the working password.

    Never install "helpful software" provided by WD and Seagate (or any HD mfg.)
    All such stuff is fluff and nonsense that interferes with normal HD operation.
    Always when you buy a new HD, format it for Mac and then use it to TM backup or clone a HD, or archive data.
    Less is more on HD new out of box.  A "blank brick", no fluff and cotton candy software

  • Time Machine Backup fails after Restore

    Had my 500GB HD on my iMac fail. After being replaced by Apple, I performed a restore from 1TB time machine backup. After this was done, I set time machine back up to back up to this 1TB drive. I want it to append to the previous backups. However, the backup fails due to "backup is too large for the backup volume". It doesn't seem to want to append to previous backups but thinks this is an entirely new backup, which I guess is mostly true. I suspect this has to do with UUIDs of the new and old drives, but I'm not sure how to correct it (I'd prefer not to just wipe the backup disk and start over). I migrated backups before from one extenal HD to another but can't remember what I did... If anyone has steps to fix this, let me know em. Thanks.
    Here's the time machine log:
    Starting standard backup
    Backing up to: /Volumes/MyBook-Mac/Backups.backupdb
    Event store UUIDs don't match for volume: Macintosh HD
    Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|
    Starting pre-backup thinning: 506.55 GB requested (including padding), 502.31 GB available
    No expired backups exist - deleting oldest backups to make room
    Error: backup disk is full - all 0 possible backups were removed, but space is still needed.
    Backup Failed: unable to free 506.55 GB needed space
    Backup failed with error: Not enough available disk space on the target volume.
    Message was edited by: Delmonte3161

    Delmonte3161 wrote:
    Had my 500GB HD on my iMac fail. After being replaced by Apple, I performed a restore from 1TB time machine backup. After this was done, I set time machine back up to back up to this 1TB drive. I want it to append to the previous backups. However, the backup fails due to "backup is too large for the backup volume". It doesn't seem to want to append to previous backups but thinks this is an entirely new backup, which I guess is mostly true. I suspect this has to do with UUIDs of the new and old drives,
    yes, that's correct. TM will make a full backup after a full system restore on a new hard drive because the UUIDs of the new drive is different from the old one.
    you may try the following hack to get around it
    http://www.macosxhints.com/article.php?story=20090213071015789
    But I make no promises about how well it works.
    but I'm not sure how to correct it (I'd prefer not to just wipe the backup disk and start over). I migrated backups before from one extenal HD to another but can't remember what I did... If anyone has steps to fix this, let me know em. Thanks.
    Here's the time machine log:
    Starting standard backup
    Backing up to: /Volumes/MyBook-Mac/Backups.backupdb
    Event store UUIDs don't match for volume: Macintosh HD
    Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|
    Starting pre-backup thinning: 506.55 GB requested (including padding), 502.31 GB available
    No expired backups exist - deleting oldest backups to make room
    Error: backup disk is full - all 0 possible backups were removed, but space is still needed.
    Backup Failed: unable to free 506.55 GB needed space
    Backup failed with error: Not enough available disk space on the target volume.
    Message was edited by: Delmonte3161

  • Time machine backup fails in my seagate 3tb external drive

    Time machine backup fails in my seagate 3tb external drive

    Without any specifics it's impossible to assist you, however the best tool for debugging TM failures is using Pondini's Time Machine Troubleshooting guide.
    Good luck.

  • Time Machine backup fails in extended network

    Dear all,
    I've recently setup an extended network using 2 additional AirPort Express units connected to the main Airport Extreme modem (all working well). I'm using the Extreme for Time Machine Backups, which used to work just fine as well.
    However, when connected to the Expresses, the Time Machine Backups fail with the message that the backup file is already in use. I'm guessing the Express modem tries to connect to the backup file, while the Extreme is keeping the file stand-by or something.
    Does anybody know a fix to this problem?
    Kind regards,
    Dennis

    It took a Snow Leopard a while but after 2 days it started working again. I've checked whether the connection was directly to the Extreme, but the connection actually went through one of the bridged Expresses.
    I guys one just has to hope for the best ;-)
    I've upgraded to Lion last week and backup works fine with the new operating system as well.

  • Is possible to have a time machine backup on an external hd connected to either a primary or secondary router and not have "back to my mac" using 10.7.3?

    Is possible to have a time machine backup on an external hd connected to either a primary or secondary router and not have "back to my mac" using 10.7.3?

    The bottom line is that Apple does not support Time Machine backups at the USB port of the AirPort Extreme. If they don't support their own router, they certainly don't support other routers from other manufacturers.
    Connect the drive directly to the Mac using either USB or FireWire.....or....use a Time Capsule.  Either of these setups will be supported.
    If you want to try the unsupported method(s), you can certainly do so. But, I would suggest that you have a secondary backup plan in place if this is important data that you will be backing up.

  • Time Machine backup fails because "volume could not be found".

    I just had my logic board replaced in my Macbook Pro and went to do a backup (yeah, I didn't do this right before it crashed) and now Time Machine backup fails with the message "volume could not be found"  Under Time Machine/Choose Disk, it appears that the drive is the one selected.  The computer "sees" the drive and I can read files on it.  The only other thing that has happened in the meantime is that a friend helped pull a file off the hard drive that I needed for a project.  No apparent issues there.  Any suggestions?

    You might try going to /Library/Preferences, then drag the file com.apple.TimeMachine.plist to the Desktop.  Reboot your Mac, then try declaring the backup disk for Time Machine.  It might help if you mount the backup disk first.
    Are you using Time Machine to write its backups to the disk of a Time Capsule?  If not, since this discussion section is for Apple's Time Capsule AirPort base station, a discussion involving Time Machine should be held on the discussion section for whatever version of OSX that you're using.

  • Time Machine Backup Failed even though I still have 1.9TB of a 2TB Time Capsule. I am using Yosemite.

    Time Machine Backup Failed even though I still have 1.9TB of a 2TB Time Capsule. I am using Yosemite 10.10.3 on an iMac (mid 2010)

    The recent update in Yosemite (10.10.3) is causing some issues for some users.
    Try a complete network power cycle as follows:
    Power off each and every device on your network......modem, Time Capsule, computers, printers, etc......in any order that you want
    Wait a minute
    Power up the modem and let it run 2-3 minutes
    Then, power up the next device that is connected to the modem an let it run a full minute
    Then, continue to power up devices one at a time about a minute apart until everything is back up
    Check the network
    Wait for a backup to occur and report on your results

  • Time Machine: backups failing because "connection failed"

    I have a 500GB external HD connected to my Airport Extreme base station base station via USB, and I use it for wireless Time Machine backups for my iMac and my MBA.
    (Yes, I know this setup isn't officially supported. But, it's been working well for a couple years now.)
    But over the last few months, backups keep failing because the HD keeps getting disconnected. If I go to find the drive in the finder, it appears, but when I click it, it says "connection failed".
    I've found that if I reset the AEX (via airport utility) that allows it to connect, but, never long enough for a full backup to happen.
    And, several times recently I've gotten some message about how the backup needs to be verified or something like that- the bottom line is always that the old backups are lost and I need to start all over with the initial backup that takes days. But of course I can never finish it, because it always drops the connection.
    At first I thought the problem was only with the iMac backups, which would lead me to believe the drive/router/etc isn't the problem and that it's something on the iMac, but then I had the problem with the MBA too, so I'm guessing it has to be something with the AEX base station (firmware maybe?), or the HD itself...
    Is my HD dying?  I've run disk utility on it and it checks out OK. Not sure how else to troubleshoot that.
    I used to have tons of problems with my internet dropping out when backups were running, but an airport firmware update eventually solved that, and things had been running fine...
    I'm running Lion and all the latest software/firmware updates.
    Ive found tons of threads about this problem, but they're all at least a year old, and none had a solution...
    Does anyone have any thoughts??
    Thanks!!

    Alexroet wrote:
    And, several times recently I've gotten some message about how the backup needs to be verified or something like that- the bottom line is always that the old backups are lost and I need to start all over with the initial backup that takes days.
    That's not one of Apple's clearest messages -- it means the backups are corrupted beyond OSX's ability to repair them.  See #C13 in Time Machine - Troubleshooting.
    Is my HD dying?
    Possibly. 
    But more likely is the usual cause -- network or power problems that the Airport can't deal with well enough to prevent corruption. 
    Part of the reason you're seeing problems now may be more networks, cordless phones, microwaves, etc., in your area causing more network problems.  Another part may be that it's only in the last 18 months or so that Time Machine started running the periodic checks to find the problem.  You may have had trouble earlier but didn't know it.
    Bottom line, you need to find a reliable way to back up.
    In your case, it's actually easy:  Delete the sparse bundle containing the iMac's backups, and start backing-up to it directly.  Then back the MBA up to the same drive (preferably to a separate partition) via your network.  See Time Machine - Frequently Asked Question #22 for setup instructions.  Also see #33 there.

  • Time Machine backup on MBA 13" drop connection after a while

    Nov 2010 MBA 13", OS X 10.6.7 (latest)
    2008 Time Capsule, Firmware 7.5.2 (latest)
    Since a while ago, possibly 10.6.7 patch, my MBA has had problems maintaining a wireless connection both to my TC and to an Airport Express that I have, especially when left unattended for 10' or so. My Iphone 4 and a Vista PC on the same network never had a similar problem.
    Genius Bar folks ran hardware tests which showed nothing, then suggested a clean install and app migration (without network settings) which I did. For a day or so my MBA then starting to behave well.
    Since yesterday, when I reinstalled 10.6.7, my MBA doesn't drop the connection, but has another problem. It won't finish its wireless Time Machine backup (3.6GB). Sometimes it can't find the TC disk, others it can. Then it goes ok for a while, even sometimes 2/3 of the way and then drops the internet connection and the connection to TC, but the Airport binding to the TC still shows as active on the MBA menubar. If I turn the Airport interface off and back on again on the MBA, eventually after a while it might find the wireless network again.
    The only other internet-related app running in the background is Skype 5.1.0.914 (latest). Also, TC network channel is not shared with any other wireless close by.
    I strongly believe this is a problem with the latest OS X patch (10.6.7) and MBA/TC combination. Even while it backups ok, it seems that the backup speed is low, which points to some conflict.
    Do other people have the same or a similar issue?  Can Apple Support chime in, since Genius Bar suggestion didn't do much for me?
    Thanks in advance.

    Update:
    Stopping Skype allows backups to run faster and complete normally. In fact Time Machine has never been that fast for me..
    Seems the problem is gone, hopefully this might also help others.

  • Time Machine Backup Fails - backup disk is unmounted during backup

    I've been having trouble on and off with Time Mahcine backups.  I have an iMac running Lion, an external USB HD which is my Time Machine disk.  It will run fine for a day or so and then fail with the "Unable to complete backup.  An error occurred while creating the backup folder".  If I run the Time Machine Buddy utility it shows the follwing error log:
    Starting standard backup
    Backing up to: /Volumes/Media/Backups.backupdb
    Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/Media/Backups.backupdb/Kitchen size:37
    Backup failed with error: 2
    Stopping backup to allow backup destination disk to be unmounted or ejected.
    Backup failed because the destination disk was ejected or disconnected unexpectedly!
    Any idea why the backup disk would be unmounted during the backup?

    I have had a related problem.
    Over the last three-four years of using TimeMachine I have had FOUR (4) disk drives fail on me. In the first instance, the power supply failed twice. Switching from connection via Firewire to USB seemed to solve that problem.
    Then in May 2011 I bought TWO x Freecom HD 1 TB portable drives, I indicated to the Apple retailer, YooBee, expressly for use as TimeMachine backups.
    They have both FAILED for me, as per the description below, which I have filed on the Freecom support site.
    So FOUR disk drives failing over 3 to 4 years is beyond bad luck, beyond coincidence, but 'conspiracy' as Churhill might have put it. The common factor is that all four disks failed 'on watch' as being my TimeMachine drives. I am VERY ALARMED at his rate of failure, and wonder if there is a fault with TimeMachine in burning out the disks through some feature of excess use?
    I note the detailed advice here is pertinent ... but I've only just found it!
    Backup, restoring, formatting info: Apple Support Communities. (n.d.). Retrieved January 16, 2012, from https://discussions.apple.com/message/16276201#16276201 
    Message to Freecom Support Forum 2012-1-14, and YooBee.
    I was absolutely assured by my Apple Mac (YooBee, 123 Broadway, Newmarket) store that these drives would be perfect for TimeMachine backup. But to have TWO fail within 8 months of purchase is very, very, very alarming. One failing is bad luck. Two failing is more than coincidence....
    There was an alarming clicking noise from the disks.
    Disks were disconncted from USB.
    Message from Mac saying USB drive disconnected incorrctly. I DID NOTHING: Timemachine was just in the middle of doing a backup, perhaps. I was just working away when I noticed the tiny noise, above.
    I turned of Timemachine in preferences. Physically powered down and disconnected Freecom drive. Waited. Reconnected. Unable to remount. Used Disk Utility to mount, and initiated Repair.
    Message Apple disk utility
    Verify and Repair volume "MELLALIEU-01-FREECOM-HDD-1TB"
    Checking file system
    Volume repair complete
    Updating boot support partitions for the volume as required
    Error: disk Utility cant repair this disk. Back up as many files as possible, reformat the disk, and restore your backed up files"
    Another message
    Mac OS X can't repair the disk
    MELLALIEU-01-FREECOM-HDD-1TB
    You can still open or copy files on the disk, but you can't save changes to files on the disk. Back up the disk and reformat it as soon as you can.
    Well: the Freecom is not able to be remounted, even after plugging, and replugging the USB.
    This happened with TWO drives.
    And despite the suggestion to backup the files NONE are accessible.
    This is NOT what I expect to have happen with drives expressly purchased for use as TimeMachine backups.
    I managed to reformat the one that first failed, about two months after purchase. I have not attempted to reformat the latest failure-- and loose my complete Timemachine backup. Naturally, I don't use the reformatted disk for Timemachine, but a Vault for Aperture.
    Equipment specification and serial numbers:
    Freecom HD Mobile Drive xxs 1 Tb x 2
    model SSYAAA P/N 35154
    Purchased May 2011, YOOBEE, Newmarket.
    S/N 351540442100051.
    S/N 351540442100021.

  • Second Time Machine backup wiped after Yosemite install

    Following on from my initial thread a few weeks ago (https://discussions.apple.com/activity?streamSource=connections&streamID=1989606) regarding the disappearance of my Time Machine backups from my iMac after installing Yosemite (7 people reporting a similar experience) and having noticed that the data seems to be 'hidden' on the backup drive, my partner upgraded her macbookpro and wow... lo and behold, the exact same damned 'glitch'.
    Having not connected the external to the laptop for a few weeks after upgrading (yeah, yeah, I know) the reminder said something like "Time Machine has not completed a backup since 5th January" so we attached the external only to be given the error that the external didn't have enough room to backup the data and that the last successful backup was sometime in September 2014.
    LogViewer for Time Machine states:
    5:35:09 pm - Starting manual backup
    5:35:09 pm - Backing up to /dev/disk2s2: /Volumes/Extreme Brain for Backup/Backups.backupdb
    5:35:10 pm - Event store UUIDs don't match for volume: HD
    5:35:10 pm - Deep event scan at path:/ reason:must scan subdirs|new event db|
    5:35:10 pm - Running event scan
    5:38:12 pm - Finished scan
    5:38:14 pm - Saved event cache at /Volumes/Extreme Brain for Backup/Backups.backupdb/Melanie’s MacBook Pro/2015-02-01-173510.inProgress/217DA034-93A7-423F-9E1B-AFD794855456/.087C6F9B -067A-3B9C-B8C3-EA26A092B101.eventdb
    5:38:14 pm - Not using file event preflight for HD
    5:41:23 pm - Found 527595 files (98.94 GB) needing backup
    5:41:23 pm - 118.74 GB required (including padding), 12.28 GB available
    5:41:23 pm - No expired backups exist - deleting oldest backups to make room
    5:42:47 pm - Deleted backup /Volumes/Extreme Brain for Backup/Backups.backupdb/Melanie’s MacBook Pro/2014-08-17-151644 containing 6.42 GB; 18.72 GB now available, 118.74 GB required
    5:42:47 pm - Removed 1 expired backups so far, more space is needed - deleting oldest backups to make room
    5:42:47 pm - Deleted 1 backups containing 6.42 GB total; 18.72 GB now available, 118.74 GB required
    5:42:47 pm - Backup date range was shortened: oldest backup is now Feb 1, 2015
    5:42:47 pm - Backup failed with error 7: Not enough available disk space on the target volume.
    6:32:00 pm - Starting automatic backup
    6:32:00 pm - Backing up to /dev/disk2s2: /Volumes/Extreme Brain for Backup/Backups.backupdb
    6:32:01 pm - Forcing deep traversal on source: "HD" (device: /dev/disk1 mount: '/' fsUUID: 087C6F9B-067A-3B9C-B8C3-EA26A092B101 eventDBUUID: 83559EC0-09D1-410C-BDEF-BBF54FE7A56C)
    6:33:30 pm - Total content size: 198.52 GB excluded items size: 77.96 GB for volume HD
    6:33:30 pm - Found 617219 files (120.56 GB) needing backup
    6:33:30 pm - 142.04 GB required (including padding), 18.72 GB available
    6:33:30 pm - No expired backups exist - deleting oldest backups to make room
    6:33:31 pm - Backup failed with error 7: Not enough available disk space on the target volume.
    6:32:00 pm - Starting automatic backup
    6:32:00 pm - Backing up to /dev/disk2s2: /Volumes/Extreme Brain for Backup/Backups.backupdb
    6:32:01 pm - Forcing deep traversal on source: "HD" (device: /dev/disk1 mount: '/' fsUUID: 087C6F9B-067A-3B9C-B8C3-EA26A092B101 eventDBUUID: 83559EC0-09D1-410C-BDEF-BBF54FE7A56C)
    6:33:30 pm - Total content size: 198.52 GB excluded items size: 77.96 GB for volume HD
    6:33:30 pm - Found 617219 files (120.56 GB) needing backup
    6:33:30 pm - 142.04 GB required (including padding), 18.72 GB available
    6:33:30 pm - No expired backups exist - deleting oldest backups to make room
    6:33:31 pm - Backup failed with error 7: Not enough available disk space on the target volume.
    This is disappointing. Like seriously (insert swearword here) disappointing. No one has any idea what the glitch might be? Two different machines experience the exact same issue with Time Machine after upgrading is more than a coincidence in all my years of Apple fanboy-ism.
    I am annoyed. Just letting folks know that

    Not exactly the same error message, but start with C4 in the 1st linked article.
    Time Machine Troubleshooting
    Time Machine Troubleshooting Problems

  • Time machine backup freezes on initial backup attempt - any ideas?

    I just purchased a Seagate 3 TB USB 2.0/3.0 external drive to use as my time machine backup drive.  I have a MacBook Pro that was purchased about 3-4 years ago.  The MacBook Pro has a 120 GB hard drive and is currently running MAC OSx 10.6.8.  I also have another WD 1 TB FireWire external drive that I use to store all of my media files. 
    After I followed the instructions for installing the new Seagate drive for use with the MAC OSx, I initiated a time machine backup.  It very quickly determined that it needed to back up almost 900,000 files totaling just about 400 GB.  It started the backup process at a rate of about 1 GB per minute.  In a little less than an hour it reach 53 GB and remained there for an additional two hours before I decided to stop the backup. 
    Once I got the backup stopped, I deleted the backup and decided to look at my energy saving settings.  I noticed that the "Put drives to sleep whenever possible" check box was checked, so I unchecked that option and restarted the MAC.  I then initiated the time machine backup again.  Like the first time it quickly determined that it needed to backup the same amount of data as before and started the backup process at a rate of about 1 GB per minute.  Before going to bed at around 11 PM last night it was at about 60 GB so I thought I was out of the woods (having gotten further than the 53 GB earlier).  When I woke up this morning at 5:30 AM it was sitting at 69 GB.
    I am really frustrated at this point and don't know why the time machine back up would be failing on a brand new hard drive.  Does anyone have any ideas?
    PS - I was previously using a Seagate 1.5 TB USB drive as my time machine backup and never had any issues with it.  I decided to use the 1.5 TB drive for a different purpose, which is why I have the new 3 TB drive to use as a backup.  And I still have the full backup on the 1.5 TB drive just in case anything were to go awry.

    Your best bet is probably to deal with the kernel panics first;  whatever's causing that may be part or all of the cause of the other problem.
    They are usually caused by hardware problems, but can be software, especially kernel extensions.
    Start by running this: Intel-based Macs: Using Apple Hardware Test.  Run the Extended tests(that may take an hour or so, depending on how much RAM you have).  Write down any error code(s) it shows.
    If that doesn't show a problem, see this Apple article: If “You need to restart your computer” appears
    If that doesn't help, post a new thread about the kernel panics, with as much detail about what's running (or not running) at the time, etc. 

  • Restore Lion 10.7.3 from Time Machine Backup Fails

    Follwoing a hard disk failure and installing a new disk, I connected to my Time Capsule to restore my Mackbook Pro running Lion.
    Choosing the latest backup resulted in it restoring about 36% of the drive and failing with a subsequesnt reboot from which the system was unable to root to the hard disk.
    After repeating the restoration process, I kept choosing backups from Time Capsule, going back choosing an older one each time following a restoration failure as described above.
    Once I chose the latest 10.7.2 backup, restoration completed.
    I have since attempted to choose and restore several of the 10.7.3 and 10.7.2 backups in the sequence on the Time Capsule, and ONLY the 10.7.2 backups are fully recoverable.
    I believe there is a bug in 10.7.3 which prevents backups from restoring off of a Time Machine Backup that is not in 10.7.2.
    Can anyone else confirm this?

    No.  It will not fix my issue, per say...
    I have essentially had to restore from backup of a 10.7.2 dated version, and update everything back to where it was before it failed with 10.7.3, and then put all the latest updates on to include the TM update...  Now hopefully I can rely on my backups...  again...  not that I knew I couldn't... 
    I really do not feel good about this...    So, ALL data & settings are going into Dropbox and onto External RAID media, as well as I am presently making an image of my disk...  which by the way is SSD now.
    Fortunatley the 10.7.2 backup worked and it only required a few hours to get the system updated back to where it was b4 the crash, but had that not happened, I would have been looking at a couple of days...

Maybe you are looking for