Time Machine Weirdness

I was sitting at my computer listening to Leo Laportes twit netcast. One hour and twenty some odd minutes. I did nothing with the computer in that time. But in that time Time Machine ran twice. The second time it backed up over 570megabytes. The only thing the computer did in that time was play a netcast. What the heck did Time Machine need to back up, what could have changed from one backup to the next???
Rachael

I looked in the time machine directory to see what it had backed up. And what I found was that it had backed up my entire itunes drive. I have one drive that I have an itunes folder with my music and another folder that I copy purchased music to until i can burn them off. Time machine backed up everything on both folders. So now I am wondering if time machine only backs up changed files or if it backs up entire folders that may contain one file, the netcast, that was changed. Anyhow thanks for the reply.
Rachael

Similar Messages

  • Time Machine Weirdness - HELP!

    Using a mid 2010 MacBook Pro with 10.9.4 installed, all updates present. Attached a WD 750GB My Passport to the Macbook Pro, reformatted the passport to MAC OSX Extended Journaled. Check both MacBook Pro and Passport with Techtool Pro 7 latest version plus Disk Warrier 4.4... Everything seems to check out on both notebook and External HD.
    Opened Time Machine in preferences, chose the WD / HD and began an initial back up on Sunday morning. It's now 12 noon on Monday and I only have 117 GB backed up so far...
    This is when it gets weird. I've turned off the screensaver, put everything to the max in terms of power, clicked the "put the hard disk to sleep" to off etc.etc. and just dimmed the screen thinking the hard disk would stay awake.
    However, every few minutes  Time Machine hangs and stops backing up files... If I walk over and click the arrow on the system preferences box, which is open to the Time Machine box showing progress, then magically, it will start backing up again. I click the box itself not any buttons. Few minutes later, I go back, it's hung, I click on the box, it starts again. This is just not the way it was intended to work... BTW, Don't think it's the My Passport... I use my passports on my iMac (2 of them backing up in tandem) my other brand new MacBook Pro retina and my daughter's macbook.
    My worst nightmare is to have this initial back up go on till Wednesday and then it gives me an error message,
    Anyone seen this before, anyone got any ideas? I'm stumped!

    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.

  • Time Machine OS X server weirdness

    Is this anything to worry about?
    My external Time Machine drive is connected to a 2014 MBP through OS X sever software and shows file size "zero bytes" for this MBP's sparsebundle when I open the drive in a finder window, yet from within the server program Time Machine Backups it shows the backup size as I'd expect.The other MBP and the iMac show sparse bundle sizes in the finder window that are appropriate.
    Details: I just installed OS X server on my 2010 MacPro to use an external 3TB Seagate drive for three other macs (2 MBP, 1 iMac). I "think" Time Machine is working because entering TM seems to work on all three macs. BUT, opening the backup drive in finder is weird. The 2009 MBP shows "Bob MBP 2009.sparsebundle" with 44 GB size, the iMac shows "iMac 2007" with no ".sparsebundle" after it and a file size of 175GB, and the "MBP 2014" shows "zero bytes" also with no ".sparsebundle" following. I've deleted this zero bytes sparse bundle and re-backedup, but get the same results.
    All three initial backups were made with direct connection to the MacPro. The older  machines used FW800, and the 2014 MBP used a Thunderbolt to FW800 adapter. Subsequent backups are done wirelessly.
    All machines have current software versions.

    In my experience Time Machine will only work on the same VLAN, unless you have IP helpers on your routers pointing to your TM server. You could always put the sharepoint as an auto mount upon login. Either force it on the local machine, or if your using Leo server with OD, just do it via group control.

  • Time Machine and Hard Drive Weirdness -- start again?

    I bought a LaCie 500 Gig slick Porsche metallic drive to go with my slick metallic iMac last year. Set up Time Machine, was in awe, life was good. In recent weeks, I've noticed the drive running hot and a little louder than normal. Since it's not crucial for me to have TM always on, I just turn the drive off.
    Recently, I noticed TM machine wouldn't mount. It was doing a lot of work, running real warm, but not mounting. In disc utility, the drive was blinking in and out of being accessible. Finally I was able to access it, and I verify/repaired it twice.
    The next time it booted up, the drive icon wasn't in 'go' green but 'wait a bit' yellow. In preferences, I could see it preparing and preparing. It seemed like it would never end, and finally needing to go to sleep, I turned it off on yellow. This morning, it mounts GREEN and is working normal. Not hot, not noisy.
    Here's the big question: now what I do?
    You see, I've got some warranty left on this drive, and I can't figure out if it's about to break, or Time Machine is breaking the drive.
    My gut tells me to trash my backups.backupdb file and start all over again. After all, I'm at a nice place where I don't need anything from a while ago. I figure if I try to do this and it outright fails to backup, this is an indication of a weary drive.
    Also, if I were to backup all over again, it would be about 160 gigs of info. My backup drive currently has 130 available. There's maybe another 60 gigs or so of stuff on this drive tops, and so it seems Time Machine has nearly doubled in size of what it's backing up.
    So, would y'all recommend purging the backup and starting again?
    Sorry for longwindedness, but just trying to provide all info I can,
    Me
    Also, I see that I've got about 130 Gigs open on the 500 gig drive. I'm using half of my iMac's 300 gig drive, and so by my best guestimation I'd say Time Machine has already double

    Jerome,
    First, make sure Spotight is not set to Index the LaCie drive. That could have been the cause of the excessive use.
    Next, if Time Machine hasn't been backing up for a while ("wouldn't mount"), then the next time it successfully mounts it will do a long "Preparing..." (I believe it's called a "Deep Traversal") session to compare what has changed since the last time it connected. This is normal and will show the drive as busy (Yellow light). Let it do its' thing in that case - perhaps leaving it on over night.
    Your Drive is most likely fine.

  • HELP: Time Machine super weirdness, ext drives just disappear...

    Hi all and Merry Christmas!
    I bought 2 brand new Maxtor One Touch 1TB Ext FW800 drives, intended one for Time Machine and the other possibly for backing up purposes or SuperDuper (http://www.maxtorsolutions.com/en/catalog/OTIII_Turbo/index.html)
    *Both drives have the same result:*
    I mounted the drive each for the first time, and use Disk Utility to erase (format) again, simple format, no raid no nothing.
    Then I set up Time Machine to do the 1st initial back up, but after a while, into a few GB of data back up, the ext drive *just suddenly unmount and disappear from the Desktop*. Twice for both drives. Now when I *turn the drives back on, I can't get them to mount... HELP!!*
    Did I miss something, did something wrong or I should have format it as a RAID drive as it should be?
    *But right now I need to "rescue" the drives back, how do I do it?* OR that the drives are DOA and somehow faulty?
    Thanks again and Happy Holidays, hope someone is reading this... cheers!

    Hi. I did a Erase like any other internal or external Mac disk - Journaled, not FAT, etc. One simple partition, no GUID etc.
    Anyway, I am very happy to report that the Time Machine drive is now working fine, here was what I did before that failed:
    1. The 2 1TB Ext FW800 drives were connected to a Belkin FW800 Hub, the hub is then connected to the sole FW800 port behind the iMac
    2. I gave the designated Time Machine drive a custom icon, using Get Info/Copy & Paste the icon graphic.
    So I remove the hub, connected the 1st drive to the FW800 port, and the 2nd one daisy chain to the first drive. This actually remounted the 2 drives and I re-format and re-erase them again.
    This time my designated Time Machine drive I left it alone as it is, no icon pasting whatsoever.
    Did the initial backup, the FW disk icon immediately changed to the Green Time Machine icon drive, the process took quite a while but has completed and successful.
    So I am not sure whether it's the combination of the above points 1 & 2, maybe the hub was faulty (it's new), or because I change the icon. Anyway, something learnt.
    Cheers

  • WEIRD "Time Machine could not complete Backup" error

    So this started back in Leopard 10.5.
    I used Time machine once and didn't like it so I turned it off and unhooked the external drive.
    Ever since that time, I get a Time Machine could not complete Backup error window that pops up every  2 hours or so it seems.
    I updated to Snow Leopard and still got this problem all the way up to 10.6.8.
    I have now updated to Lion and I STILL get this stupid annoying error.
    My TM is OFF and there are no drives selected anywhere.
    What should I do ?

    Very true, I didn't even tink about that... but.....
    I did have TimeMachineEditor but it was already set to OFF.
    I also had another program (Time Machine Scheduler) that was also set to off.
    ****, I would have loved it to be that !!!

  • Weird external drive behavior with Time Machine....

    I have a 500 GB WD My Essentials USB hard drive.  I've been using on Lion for 6+ months.  I have the drive in 2 partitions, 400 GB for Time Machine and 100 GB for storage.  Everything has been working fine for 6+ months.  As of yeterday when I plug in my WD drive, the storage partition will mount on the desktop but the 400 GB Time Machine partition will not.  The TM partion does show in the disk utility but cannot be repaired.  I'm wondering why the problem is only with the Time Machine partition.
    Any ideas?

    Oh, the drive will not "eject" properly either.  When I try to eject it the storage partion turns light in color but it still shows on the desktop and is still listed in the Finder side menu (but you can't access or see the actual drive).

  • Time Machine Error with weird math

    Not sure what's the cause of this, but suddenly TM is not backing up. I get this error:
    "Time Machine Error
    This backup is too large for the backup volume. The backup requires 442.3 MB but only 23.6 GB are available."
    How can this be? Only 442 mb needed for the backup, yet I have 50 times that much space available on the TM volume? The only new things on my computer are iTunes 8 and its Front Row update from a couple of days ago. This TM error started sometime last night.
    TIA.

    Tony,
    This is what I have been able to discover about this particular error message.
    Sometimes, this error is legitimate. The user may not realize that they need to exclude additional hard disks that TM may be seeing. This is done in the “Options…” window of the Time Machine Preferences.
    Nevertheless, many times this error just doesn’t make sense, stating that not enough free space exists for a backup that is clearly smaller. (“The backup requires 45.9 GB but only 182.6 GB are available”)
    The answer and fix may have been discovered by a poster in the macosxhints forums: (http://forums.macosxhints.com/archive/index.php/t-84284.html)
    Essentially, while Time Machine DOES delete old backups from the sparsebundle, it DOES NOT free up the space occupied by those old backups. Eventually, "all previous backups were deleted and no space was gained. . . . What appears to be going on here is that the sparsebundle isn't self-shrinking - unused bands aren't being automagically discarded."
    The solution is to compact the TM backup sparsebundle in Terminal using:
    hdiutil compact yoursparsebundlefilename.
    He concludes, "I gained 30+gb of space on the backup volume by compacting that sparsebundle. And now TM runs just fine, since it has plenty of space."
    Obviously, this is a bug in TM. It does not appear to effect everyone, and only seems to appear under certain curcumstances.
    Let us know if this works for you.

  • Time Machine Buddy: weird message after backup

    Hello Pondini and all,
    Note the last line in the Time Machine Buddy log messages.
    The drive was not ejected. Any idea what this was about?
    Starting post-backup thinning
    No post-back up thinning needed: no expired backups exist
    Backup completed successfully.
    Stopping backupd to allow ejection of backup destination disk!
    Thanks,
    harv47

    Hello Pondini and all,
    Note the last line in the Time Machine Buddy log messages.
    The drive was not ejected. Any idea what this was about?
    Starting post-backup thinning
    No post-back up thinning needed: no expired backups exist
    Backup completed successfully.
    Stopping backupd to allow ejection of backup destination disk!
    Thanks,
    harv47

  • Weird interaction with time machine

    Whenever time machine starts doing a backup, iMovie goes beserk. If it's playing a movie, it suddenly stops. Then when I hit the space bar to start it again, it jumps to a different project. In particular, I've been watching a clip in an event. But after the time-machine hiccup, the next I hit the space bar, it jumps to a project I was working on yesterday and starts playing that! Anyone seen this?

    I'm having a difficult time following, I understand English isn't your native language. You may have good luck with Google Translate.
    Also please read Pondini's Time Machine FAQs & Time Machine Troubleshooting.

  • Time Machine behaving weird

    I'm having trouble with time machine. I have a 500 gb drive in my MBP (late 2009) and an external drive also on 500 gb which I use as a Time Machine backup drive.
    For some time now it has not been backing up because because it said it was lacking space on the external drive. I thought it was supposed to delete old backups in case that happened?
    Then I manually deleted all backup data on my external drive and set Time Machine to backup from scratch. And now it tells me that the drive is not big enough??? Apparently it needs to backup 590 gb from the internal drive (which has a capacity of 500 gb) to my external drive.
    What's going on?
    TIA

    Phero2 wrote:
    First I erased the data by just dragging it to the bin then later I read that it should be erased from disk utility. Unfortunately that didn't help.
    But i wasn't aware that it needed 20% extra so thank you for telling me - it was a quick answer too!
    I have excluded my download folder and now it backs up again.
    Incremental backup would be great, but in reality all I need is one backup of everything in case the internal drive decides to make a head crash or something.
    then you might want to use a different backup program instead of TM. there are plenty good ones around
    see this post by Kappy for options
    http://discussions.apple.com/thread.jspa?messageID=7495315#7495315
    You are my hero of the day - thanks again!
    //Summer

  • Mavericks Time Machine stops halfway and weird mds errors

    Ever since I upgraded to Mavericks I have not been able to do backups using Time Machine. Most of the time it stops during the "Preparing Backup..." phase but by deleting prefs and incomplete backups I have been able to get about 50% into writing the backup to my external drive. The backup doesn't crash, but all disk writes and reads stop and the process uses no CPU (it also makes no progress, I've waited there for about an hour after the bar stopped moving).
    In addition to this (and possibly related, although I don't know how) I get this message in the console every 30s when my external hard drive is plugged in:
    mds[37]: (Error) Server: mdsync launch failed: (ipc/send) invalid destination port
    and mdutil -as gives me:
        Indexing and searching disabled.
    /.MobileBackups:
    2013-12-23 16:30:43.345 mdutil[555:507] Metadata.framework [Error]: mdsCopyStoreAttributes failed: (8) (os/kern) no access
        No index.
    /Volumes/Hitachi:
        Indexing and searching disabled.
    /Volumes/Hitachi/Backups.backupdb:
        Indexing enabled.
    I have indexing turned off for all my drives, so I imagine the indexing is on for the backups folder as a default necessity (I cannot seem to be able to turn it off using the mdutil command).
    Does anyone know how these two things are connected and what could possibly be going wrong?

    Linc Davis wrote:
    I have indexing turned off for all my drives
    I suggest you turn it back on, at least on the ones you want to back up.
    Is this necessary? It seems to do half the backup without it. If I remember correctly I have indexing turned off not only because I don't use it but also because it was hanging up/using a lot of CPU... If I absolutely must I will turn the indexing back on and wait for it to do its dirty business, but I'm a bit reticent in trading my problem for one that I don't really have an interest in solving.

  • Time Machine on Snow Leopard just doesn't work.

    So I've had huge nightmares over the past few days over Time Machine.
    So I've always been a big proponent of Time Machine. I always tell everyone that you NEED a backup solution, and while Time Machine may not be the be all and end all, it's a great starter solution for those that don't want any fuss.
    But perhaps not anymore.
    It just works, right? Well apparently not.
    So a little while ago I performed a Time Machine-assisted hard drive swap for a MacBook (not mine). That is, I install a new drive, boot from SL DVD, perform a HD wipe, then restore from Time Machine. It seemed to go well.
    Fast forward to more recently, I went on a trip overseas (Taiwan). While there, I obviously took a lot of photos, and it became that time again - purchase a new hard drive with more capacity for my MacBook Pro! HD were a little cheaper where I visited, so I not only bought a new drive for my MBP, but also a new drive for my wife's MB, as well as new external drives to upgrade our Time Machine drives.
    While I was there, I decided to update my own Time Machine first - following the instructions from Apple's own knowledge base on the matter:
    http://support.apple.com/kb/HT1427
    I transferred my existing backups to the new drive to continue my Time Machine. I didn't notice any problem at the time.
    Then I returned to my home country (New Zealand). First thing I did when I got back was to perform the Time Machine-assisted HD swap after making sure the OS were up-to-date as were their respective backups, on both my own MBP and my wife's MacBook.
    That's when the troubles started.
    First off, I noticed that a few images from my Aperture Library were missing. The album data and everything were there, but the actual files were not. They also did not exist anywhere on the Time Machine drive and as such never made it over to the new HD. Weird, I thought. They were there, clear as day on my original drive. They simply weren't backed up.
    Now I'm aware of a few TM niggles, such as the false backups after verifying a disk, but I hadn't done that.
    The second issue was much more major. My Wife's MB would be endlessly stuck on the white boot screen with the grey Apple logo. As it turns out, it's exactly this issue here:
    https://discussions.apple.com/thread/2738620?threadID=2738620&tstart=74
    In short, the fresh Time Machine backups I made before transferring to the new HD showed no sign of updating the /System/Library/Framework/Security.framework/Versions/A/Security package, which is REQUIRED for the Mac to boot into 10.6.7 (it had an old one from before).
    Great, I thought, but maybe I can fix that by installing a fresh 10.6.7 combo update on the MB via target disk mode.
    No dice. On trying, it goes all the way to the end, and then fails installation. I had to resort to copying over the correct, more recent security package just to get it to boot.
    After booting, what to do? Who knows what other files Time Machine failed to update, and what consequences they would have. After putting back the original security package, I tried updating 10.6.7 again. Nope, no dmgs would open - i HAD to use the new Security package for anything to open. Fair enough, but even with that, the installation would inevitably fail.
    Problem with the package? Nope. Tried a fresh download, and checked the SHA and everything.
    Time to do some blitzing. I pulled out my trusty Snow Leopard DVD and did a reinstall on top. That's gotta get my problem, right? Well, nope. After resetting to 10.6.0, the 10.6.7 combo updater STILL failed on installation. Furthermore, the updater no longer worked on MY MBP either.
    What gives?
    As it turns out, it was related to this:
    https://discussions.apple.com/message/11317470?messageID=11317470
    In short, some files had the user immutable flag switched on, preventing changes from being made to those files (manifests as a little lock icon on the file icon). They included (and I'm sure not limited to) the Acknowledgement.rtfs in /Library/Documentation/, as well as a majority of the fonts in /Library/Fonts.
    Checking back in the backup drives, it was clear that Time Machine was the culprit - instances of those files in the backups were also locked. When did that happen? Looking back, it looks like it happened when I transferred the backups from one Time Machine drive to another. But it wasn't all at once - in the first backup on one drive, one of the Acknowledgement.rtf files was locked, and the other one wasn't, but in the second onwards, both were. It was clear that Time Machine seemed to be doing it to those files. Which files and why? I have no idea.
    So removing the uchg flag with "sudo chflags -R nouchg /" in terminal finally allowed me to apply the 10.6.7 combo update without failure.
    So were the troubles over then?
    Nope.
    While checking if everything was fine, I noticed iPhoto on the MB had all the thumbs missing - after rebuilding, they weren't back, and only a .plist trashing fixed it (I consider this pretty normal - probably looking for the files on the old UUID drive or something).
    But what gives? ALL the photos taken on the trip were gone! Not just the thumbs - the actual files were missing from the iPhoto Library! The data in the albums existed, just the actual files, just like my instance in Aperture on my own MBP.
    Checked the Time Machine - again, it was clear Time Machine had completely stuffed up - the files were nowhere to be found on the Time Machine drive.
    So currently, I've returned the original internal drive to the MacBook, performing a FRESH on new reformatted disk Time MAchine, and will use THAT to restore.
    Nightmares, indeed. It's several days of work doing all the restores, considering I have limited drives to work with. And yes, rest-assured, I was doing enough permission repairs, and PRAM resets to ensure they weren't issues.
    It occurs to me there are several faults with the most recent version of Time Machine (maybe 10.6.6 or something as that's when people had some of the issues above):
    1) At some point in time, Time Machine may not update a necessary Security package (and probably other files too - I believe the files around it were also not updated), meaning that if you use that Time Machine to restore, the outdated package will cause your computer to fail to boot.
    2) Transferring your backups to a new destination Time Machine drive may cause certain files to become user immutable or 'locked', with one consequence being you cannot update the OS.
    3) Time Machine may fail to backup image files with the Aperture or iPhoto Library. Trying to remember back, I *think* this may be related to the fact that we changed time zones, as the unupdated image files were after the zones were changed. Strangely, every other file within the Library packages were updated, as album data was updated - just not the actual image files and folders.
    Conclusion? I no longer trust Time Machine. The basic foundation of a backup service is that you trust it to do what it's supposed to do. After all this, how can I?
    You might think they are isolated incidents, but they were occurring on two Macs that I have, and they same errors can be found in others.I think I have detailed some root causes, but who really knows.
    At any rate you should keep an eye on at least these files I have detailed. Would love to hear Pondini on the matter, as I know he knows a lot about Time Machine.

    Someone has suggested just installing Snow Leopard on the machine. Will that work?
    If you can find a copy of the workstation version of Snow Leopard shipped with the same model of Mac mini, yes. Apple has not, to my knowledge, shipped a retail version of Snow Leopard new enough to boot your mini.
    I've also heard there is a way to install SL while connected to my old Powerbook in order to suck the entire old drive onto the new machine in an operable manner. Is this accurate, and can this be done if my old machine is the Powerbook on the old apple chip when the new machine is intel based
    No, it's not accurate. The OS on your PowerBook will not boot your mini.
    what are the differences between the single pack and the family pack?
    If you mean single and family pack of Mac OS X, the single pack is licensed for installation on one computer only, while the family pack is licensed for installation on up to five Macs.
    Regards.
    Message was edited by: Dave Sawyer

  • Time Machine no longer backs up after archive & install

    I have just had something mysterious happen to my Macbook - it spontaneously shut down, then wouldn't restart past a gray screen with Apple logo. After trying every troubleshooting page I could find, I ended up doing an archive and (re)install of Leopard on my hard drive. (btw, I ran the Disk Utility hard drive diagnostic, and it said the HD is fine, though I'm skeptical because it's making new noises I've never heard before.)
    I finished that install, restarted, everything seemed fine, and I re-connected the external hard drive that had been used for my Time Machine backups before. Now, every time it attempts to back up, it's stuck on "preparing" for 30 minutes, then starts copying SLOWLY and the progress bar says "6 KB of 10 GB." Well, I have a lot more than 10 GB to back up. Then the process halts and I get an error message: "Unable to complete backup. An error occurred while copying files to the backup volume." And I can't get any more specific information about the error - can't find a log file or anything.
    I know that there's a troubleshooting article about Time Machine issues with only backing up 10 GB, but mine doesn't even get that far, and besides, this is not my first Time Machine backup - I have no other external drive big enough to transfer my older data to while I reformat this drive as the support article suggests.
    I was thinking that perhaps a system setting got messed up somehow and that maybe I should just forget this archive & install thing I did and instead do a fresh erase & install on my Macbook hard drive and then restore from Time Machine's old backup (a day or so before my Macbook started acting weird). But 1. would that make a difference? And 2. if Leopard gives me an error while backing up in Time Machine, what if I do the erase & install and I get an error trying to restore from Time Machine? That would be a nightmare.
    My Macbook has always been so reliable - I'm very confused about what's going on! Any help would be appreciated.

    Hmm; the external drive had no errors, according to Disk Utility.
    Here are the time machine logs from Console:
    1/13/08 12:14:47 AM com.apple.launchd[1] (com.apple.backupd[301]) Exited abnormally: Bus error
    1/13/08 1:10:28 AM com.apple.launchd[1] (com.apple.backupd[430]) Exited abnormally: Bus error
    1/13/08 2:21:23 AM com.apple.launchd[1] (com.apple.backupd[519]) Exited abnormally: Bus error
    1/13/08 4:12:57 AM com.apple.launchd[1] (com.apple.backupd[612]) Exited abnormally: Bus error
    1/13/08 5:22:59 AM com.apple.launchd[1] (com.apple.backupd[818]) Exited abnormally: Bus error
    1/13/08 6:24:00 AM com.apple.launchd[1] (com.apple.backupd[915]) Exited abnormally: Bus error
    1/13/08 7:24:52 AM com.apple.launchd[1] (com.apple.backupd[1012]) Exited abnormally: Bus error
    Also, I tried to repair permissions on my internal drive and I got the following error messages:
    Warning: SUID file "usr/libexec/load_hdi" has been modified and will not be repaired.
    Warning: SUID file "System/Library/PrivateFrameworks/DiskManagement.framework/Versions/A/Resources /DiskManagementTool" has been modified and will not be repaired.
    Warning: SUID file "System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Reso urces/Locum" has been modified and will not be repaired.
    Warning: SUID file "System/Library/PrivateFrameworks/Install.framework/Versions/A/Resources/runner " has been modified and will not be repaired.
    Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/readconf ig" has been modified and will not be repaired.
    Warning: SUID file "System/Library/PrivateFrameworks/Admin.framework/Versions/A/Resources/writecon fig" has been modified and will not be repaired.
    Warning: SUID file "usr/libexec/authopen" has been modified and will not be repaired.
    Warning: SUID file "System/Library/CoreServices/Finder.app/Contents/Resources/OwnerGroupTool" has been modified and will not be repaired.
    Warning: SUID file "System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/MacOS/ARDAg ent" has been modified and will not be repaired.

  • SPECS FOR NEW MBP HARD DRIVE AND HOW TO INSTALL NEW OS AND USE TIME MACHINE

    I need to replace the hard drive in my early-2006 1.83 MacBook Pro (15-inch), because the Genius at the Apple Store told me that I'm getting weird behavior on it due to the drive slowing down and that it won't last much longer.
    I have 2 questions:
    First, I want to order the drive online and have it installed locally. I will probably get a 320 to 500GB drive. What are the exact other specs I will need to find the right one?
    Second, I am currently running 10.5.8 and backing up with Time Machine. I would like to install 10. 6 on the new drive, but don't know how to go about using the Time Machine backup to get all my apps and files running. Can someone describe this procedure for me?
    Many thanks!

    Hi Annie,
    You need a 2.5" 9.5mm high SATA HD, either 5400 or 7200RPM. Check out macsales, newegg, amazon to name a few places.
    How to restore from a TM backup: http://support.apple.com/kb/ht1427
    Prepare your HD by formatting and partitioning it:
    1. Boot from install disc (press power button, immediately insert install disc and hold down c key).
    2. Select your language.
    3. Open Disk Utility from Utilities menu.
    4. Select the HD in the left pane (the manufacturer’s name and the HD model number).
    5. Click on the Erase tab.
    6. Choose the Format: Mac OS Extended (Journaled).
    NOTE: if you want to zero the HD (which I always think is a good idea, but does take time), click on Security Options, click the button for Zero Out Data, click OK. The larger the HD, the longer this will take, in some cases several hours.
    7. Click on Erase and wait for the entire process to finish.
    8. Click the Partition tab.
    9. Click on Volume Scheme: and choose the number of partitions (normally just one unless you have other plans).
    10. Click on the Options button (located underneath the Volume Scheme pane) and select GUID.
    11. Click Apply.
    12. Quit Disk Utility and continue with the installation process to install OSX or run Restore from a TM backup; when finished, repair permissions, run updates, repair permissions.
    Message was edited by: tjk

Maybe you are looking for