Time Machine / Disk Space / iPhoto(?)

Ok, I'm not techy so please bare with me!!
I have Time Machine & backup to an external hard drive.  I've always had 30+ days worth of backups on there.
Today Time Machine says there is not enough space on my hard drive to do a backup.  I thought I'd just delete a couple of really old backups, only to find that Time Machine has already done this & there is actually only one backup on there, which is from Friday!!
I'm not sure if it's connected, but on Friday I installed the newest version of iPhoto & it copied all my photos over from my previous version.
I don't see how I was previously fitting 30 days worth of stuff on the disk, and now I can't even fit 2..??
Time Machine says it needs 125GB of space for the backup - I don't know if this sounds "normal" - I'm a graphic designer with Adobe Creative suite, lots of InDesign files & millions of photos of my kids! 
I can't even check back & see what size my backups were prior to Friday, as they've been deleted :-(
So, could the two be connected?  Any advice about the situation at all would be appreciated as it's making me dizzy thinking about what on earth has gone on..!!

Time Machine automatically deletes old snapshots to make room for new ones, but it won't delete the last previous snapshot of any disk.
Are you storing any other data on the backup volume, or have you ever backed up another disk or computer to it that you no longer have? If the answer to both these questions in "no," then there isn't enough space on the volume for all the data you want to back up.
If you are storing other data, or if you have backups of a volume you no longer need, you should move or delete that data to make room for more. Alternatively, put the device aside and start a new backup on another storage device. When you're sure you'll no longer need the data on the first device, erase it and start over.

Similar Messages

  • Time Machine Disk Space Problem

    I have approximately 1TB of data (as confirmed by Time Machine) and I purchased a 1.5TB external backup disk to dedicate exclusively to Time Machine backups.  However, Time Machine will not backup because according to Time Machine there is not enough space (not even for an initial backup).  I have read discussions that suggest Time Machine uses 20% more space than the backup data (https://discussions.apple.com/message/17944550#17944550).  If that is true, I should have more than enough space.  Does anyone have any idea what the problem is?  Why is 50% of extra space not enough?  Thanks for your help.

    Did you partition and format the drive before using it?
    Drive Partition and Format
    1. Open Disk Utility in your Utilities folder.
    2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
    3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Apply button and wait until the process has completed.
    4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
    5. Set the format type to Mac OS Extended (Journaled.) Click on the Security button, check the button for Zero Data and click on OK to return to the Erase window.
    6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.

  • Time Machine disk space management?

    My 2009 MacBook Pro (500 MB which has 160 GB of space used) hard drive has a Time Capsule (2 TB, USB which has 323 GB of space used) and seems to work fine. 
    I'm getting suspicious because whenever I check backupd with Console, Console reports back Time Capsule always has 1.52 TB of free space.   It says this after I've added movies, music, and photos.  It seems like it should be using more of the Time Capsule as I add more files.
    Time Machine indicates it has daily backups for a month and then switches to weekly backups until Time began.  I can retreive deleted files through Time Machine with no problem. 
    Do I worry too much or have a problem?

    You're probably ok, but it wouldn't hurt to "spot check" via the "Star Wars" display to be sure your recent movies, etc., are really there.
    And/or, use one of the apps in #A2 of Time Machine - Troubleshooting to see exactly what's getting backed-up each time.
    If everything is there, what you may be seeing is the rather odd behavior of the sparse bundle disk image that Time Machine puts your backups in when they're made over a network.  It will grow as you add things, but doesn't shrink automatically when you remove them. 
    So what may have happened is, some large things that weren't on your system for a long time were deleted, and after 24 hours or a month, Time Machine deleted the backup copies of those items.  But that didn't recover any space.  Instead, all your new backups are using that vacated space.  Once it's filled-up, the sparse bundle will start to grow again.

  • Freeing up Time Machine Disk Space

    I've used Time Machine for 2 yrs now and my 1TB drive is about full. How do I go about cleaning up some of Time machine. I really only want a year's worth of storage.
    Dan

    dkardell wrote:
    Thanks I figured that was the case. I wish there was a setting to say just store back to a year and not fill up the drive. Yes I do use the drive for other things, however it was interesting that yesterday it told me there was not enough space on the drive anymore as it dropped to just 5mb free. Not sure what happened there.
    Yeah, that can happen unexpectedly. There are times when extra-large backups are required, such as after an OSX update, or converting to iPhoto 09. And of course you'll get a full backup after certain hardware repairs, a full restore, etc.
    Anyway I went in and deleted and excluded the Applications folder as I have CD's for all of my software. I also am running Fusion for my Windows session that I need to get into every now and then. Deleting the Applications and Virtual folders gave me back 290G.
    I hope you have a record of any purchase codes for 3rd-party apps and/or plugins. (I'd not recommend omitting Apps, as you might guess.)

  • Managing Time Machine Disk Space

    I have a NAS server that I use to back up all my computers (3 PCs, and 2 Macs).  For various reasons that I won't bore you with, I cannot partition that storage into multiple partitions.  Is there a way to control how much disk Time Machine uses before it starts dropping old backups?  I do not want it to use up unecessary space to keep backup longer than needed.  I there a way to control the amount of disk space available to TM or control how long to keep backups?
    Thanks.

    Thanks for the reply but this link did not give me anything new that I did not know.  Good overview of Time Machine but did not answer the question.

  • Time Machine disk space concerns

    I've had a 17" MacBook Pro for several months now and never really got around to actually using Time Machine to back up its 750GB hard drive without irritating messages of "not enough disk space".
    I use a 1TB external My Passport USB 3.0 hard disk and just turned on TM to back it up; it's about 70% full (that is, about 500GB) and, therefore, 1GB should be more than enough for the task.
    It starts off OK, backs the full content and then proceeds to the hourly rounds. In a couple of hours it begins complaining that it doesn't have enough disk space. I believe that's due to my constant use of two VMWare virtual machines (total of roughly 280GB-320GB counting both).
    Can someone confirm/deny my suspicion? Also, what's the "best practice" say about size of external drive to back up a 750GB HDD? Any other hat tricks I can use to have a reliable backup?
    Thanks in advance!
    Fernando

    Apple recommends that a Time Machine backup drive should be twice as large as the drive it's backing up.

  • Time Machine Disk Space error

    I've been using Time Machine for a will now without a problem but on my latest backup I get An Error message saying that there is not enough disk space even though I still have 69Gb left in Ex hard Drive.
    I haven't added more than a few hundred Mb since my last backup. I have a 160Gb internal Drive with 67Gb left on it and a 160Gb External for Time Machine with 69Gb left.
    Any ideas

    PapaFunk wrote:
    Hi Mate,
    Thanks for the response, I was under the impression that Time Machine did the one initial backup and then only what is new. So Does it keep several full copies of what is on the hard drive?
    No, as Roger says, in most cases there's only one copy of each version of each file on your internal HD, but if you change something often, the copies of all the versions can add up.
    Starting pre-backup thinning: 93.80 GB requested (including padding), 69.64 GB available
    No expired backups exist - deleting oldest backups to make room
    It was trying to back up about 78 GB (it adds 20% for workspace, so needs 93.8). Apparently a full backup of your internal HD is about 93 GB, so this is quite large indeed.
    Are there any other disks connected to your Mac, that aren't excluded? See what the estimated size of a full backup (slightly different wording) is under the exclusion box in TM Preferences > Options.
    Are you running any of the things (or similar to those) mentioned in #D4 of the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.

  • Time machine disk space use

    My time machine backups are working great.
    I have just noticed that my Mac HD has used 105GB of space but my external drive, using time machine, has used 168GB. Why the difference? Is this normal? Thanks.

    runningman5 wrote:
    My time machine backups are working great.
    I have just noticed that my Mac HD has used 105GB of space but my external drive, using time machine, has used 168GB. Why the difference? Is this normal? Thanks.
    That is perfectly normal. TM does not just have your current HD data, but also everything you have erased and/or changed over the time you have been running it. You can recover a file that you deleted months ago because it's still on the TM drive; hence the larger file volume.

  • Time Machine disk space

    I use Time Machine to back up my Macbook to a Time Capsule.  This works fine but I have recently started trying to back up a second Mac to the same Time Capsule.  I get a message saying that there is insufficient space for a full back up, 60GB required, 9GB available.  Both figures are about right, I think.  I unerstand tht time Machine should delete old back ups when insufficient space is available, but will it do that if the back ups are for a different computer?  If that is the case, how can I create enough space to back up the second computer?  There is nothing on the time Capsule apart from the back ups.

    will it do that if the back ups are for a different computer?
    No.
    how can I create enough space to back up the second computer?
    You could manually delete some of the oldest snapshots of the first computer, but I wouldn't recommend that. A better solution would be to back up the second computer to a different drive, which could be a USB hard drive connected to the Time Capsule.

  • Time Machine Disk out of space

    Every time Time machine does a backup I get a message saying that the disk is full and it will delete the oldest backup.  In fact, the disk has tons of free space.  When I do Get Info on the disk it says that 214 gigabytes are available.  My internal hard drive which it is backing up only has 22 gigabytes on it.
    As things stand now I can only store about 6 days of backups and things will certainly get worse.
    I am running Mac OS X 10.7.2.  I have VMWare Fusion installed and Windows 7 as a virtual machine under Fusion.

    here it is:
    Filesystem                          Size   Used  Avail Capacity  Mounted on
    /dev/disk0s2                       698Gi   46Gi  651Gi     7%    /
    localhost:/x4-2qwsQFDj-Rw5mjpzuUI  698Gi  698Gi    0Bi   100%    /Volumes/MobileBackups
    /dev/disk1s3                       371Gi  342Gi   28Gi    93%    /Volumes/Time Machine Disk
    unknownb88d12299a84:~ sganarelle$
    and here is the screenshot:

  • What is the equation for Time Machine required space?

    Once again Time Machine says it has run out of room to do my backup. I guess I just don't understand the equation for figuring this out.
    These are my specs:
    Disks being backed up - 2 drives
              Internal Drive - 640gb, 482gb in use
              External Drive - 500gb, 105gb in use
         587gb total data in use
    Time Machine disk - 1TB, 715gb in use, 284gb available, asking for 303gb
    TM wants space that is more than half of my total data in use. I have one (old) 2gb file, all others are 99mb and smaller, mostly much smaller.
    Why isn't TM removing older backup files to make room for the latest? Why does it think it needs a block of 303gb when the new files it needs to back up are all in the sub 10mb range?
    On the surface it seems like TM is using disk sizes to do it's caluclations instead of file size.
    What is the equation it uses to figure this out? I am puzzled...

    jlmcvay wrote:
    Starting pre-backup thinning: 286.19 GB requested (including padding), 265.05 GB available
    That's your main problem; wanting to back up about 238 GB (plus 20%).  Curiously, that's a bit less than the previous messages.
    See what's shown for Estimated size of full backup under the exclusions box in Time Machine Preferences > Options.  According to the figures in your first post, it should be about 587 GB.  If it's considerably larger, then there are two possibilities:
    Something else is connected, and Time Machine is trying to back it up.
    There's a directory problem on one of the disks being backed-up, so Time Machine thinks it's much larger.  If so, try verifying your internal HD, and repairing the external, per #A4 in Time Machine - Troubleshooting.
    But if the estimate is reasonably close, then something very large has changed.  See #D4 in Time Machine - Troubleshooting for some of the common culprits.  Unfortunately, there's no way to tell in advance what it is;  you can only see that after a backup completes.
    If nothing there helps, try excluding the external HD and trying again (per #10 in Time Machine - Frequently Asked Questions) -- that should tell us whether the problem is on the internal or the external.  Then we can try to narrow it down.
    Seems like there is a problem with the Event store UUIDs for my internal drive.
    Not a major one.  That message means that Time Machine isn't sure that the previous backup was completed normally (which it obviously didn't).  When that happens, Time Machine can't use the Event store, but has to do a "deep traversal" to compare everything on the drive to the backups to figure out what's changed and needs to be backed-up.  That takes a while, of course, and means your backup will take considerably longer than usual. 
    I commonly have iPhoto open all the time. If TM cannot back up iPhoto while it open that would explain why it needs to backup a lot of data.
    That's a possible explanation, but 238 GB is a lot of photos.  How large is your entire iPhoto Library? 
    Time Machine can sometimes back the iPhoto Library up when iPhoto is open -- it seems to depend on just what you've been doing.  So it's fairly unusual for it to be missed for very long.  (It ought to send a message after a certain time, but it doesn't.)
    If excluding the external HD doesn't turn up a clue, try excluding your Pictures folder.

  • How to Move a Shared Time Machine disk to another Mac?

    Hi,
    I have a network with three macs. Initially, I had a Time Machine disk connected via USB to Mac A. Mac A and Mac B used that disk for TM backups.
    Now I have coupled the Time Machine disk (via Firewire if that matters) to Mac C.
    Mac B can't find the Time Machine disk anymore (as well as Mac A I guess), although the TM disk itself has still the same name. When I explicitly open the TM disk on Mac C in the Finder on Mac B, Mac B does not recognise it as its original TM disk.
    After I clicked Change Disk in the Time Machine preferences on Mac B, I was able to reselect the TM disk. However, it doesn't see that there is already a long history present from Mac B and Time Machine plans to back up from scratch.
    How can I tell Mac A and Mac B that the TM disk that is now connected to Mac C is still the same disk?
    Thanks a lot for your help.

    I want to do the same thing but i have a BW database (SAP) and i want to move the datafile form one mount poitn to another due to space constraint, but i want to use BR*TOOLS utility to do this, so can anyone help me out on this on how to do this, what are the precaution need to be undertaken.
    Jafar

  • Time machine disk permissions changed to read only

    Somehow, my Time Machine disk permissions have now changed tand my backups are failing;
    The permissions are:
    Me - read/write, Staff  - read/write, Everyone - read only. I clicked on the lock and entered my system password, but I cannot change anything.
    Then I ran Disk Utilities to repair and verify. Still nothing. I rebooted, logged out, logged back in, etc.
    There is plenty of space left on the 2 GB drive. It is a Seagate GoFlex drive.This seems to be a new problems that has not surfaced before. My backups always ran flawlessly.
    What to do?

    10/22/13 7:44:57.820 AM com.apple.backupd[49208]: Backup failed with error: The target volume is read-only.
    10/22/13 7:44:57.851 AM coreservicesd[66]: Application App:"UserNotificationCenter" [ 0x0/0xdd9dd9]  @ 0x0x7fb372e4b9c0 tried to be brought forward, but isn't in fPermittedFrontASNs ( ( ASN:0x0-0xdc8dc8:, ASN:0x0-0xa50a5:) ), so denying.
    10/22/13 7:44:57.851 AM WindowServer[1075]: [cps/setfront] Failed setting the front application to UserNotificationCenter, psn 0x0-0xdd9dd9, securitySessionID=0x186af, err=-13066
    10/22/13 7:55:27.048 AM CalendarAgent[25590]: [com.apple.calendar.store.log.caldav.queue] [Account refresh failed with error: Error Domain=CoreDAVHTTPStatusErrorDomain Code=401 "The operation couldn’t be completed. (CoreDAVHTTPStatusErrorDomain error 401.)" UserInfo=0x7ffba30190c0 {AccountName=Gmail, CalDAVErrFromRefresh=YES, CoreDAVHTTPHeaders=<CFBasicHash 0x7ffba247e7c0 [0x7fff7fa61110]>{type = immutable dict, count = 11,
    entries =>
        0 : Case Insensitive Key: X-Content-Type-Options = <CFString 0x7ffba24c02e0 [0x7fff7fa61110]>{contents = "nosniff"}
        1 : Case Insensitive Key: Content-Type = <CFString 0x7ffba2469b10 [0x7fff7fa61110]>{contents = "application/vnd.google.gdata.error+xml; charset=UTF-8"}
        2 : Case Insensitive Key: Server = <CFString 0x7ffba24e5590 [0x7fff7fa61110]>{contents = "GSE"}
        3 : Case Insensitive Key: Transfer-Encoding = <CFString 0x7fff7f24e928 [0x7fff7fa61110]>{contents = "Identity"}
        6 : Case Insensitive Key: Date = <CFString 0x7ffba2483320 [0x7fff7fa61110]>{contents = "Tue, 22 Oct 2013 11:55:26 GMT"}
        7 : Case Insensitive Key: X-Frame-Options = <CFString 0x7ffba249b8c0 [0x7fff7fa61110]>{contents = "SAMEORIGIN"}
        8 : Case Insensitive Key: X-XSS-Protection = <CFString 0x7ffba24f24d0 [0x7fff7fa61110]>{contents = "1; mode=block"}
        9 : Case Insensitive Key: Www-Authenticate = <CFString 0x7ffba24b3d40 [0x7fff7fa61110]>{contents = "GoogleLogin realm="https://www.google.com/accounts/ClientLogin", service="cl""}
        10 : Case Insensitive Key: Alternate-Protocol = <CFString 0x7ffba24e68f0 [0x7fff7fa61110]>{contents = "443:quic"}
        11 : Case Insensitive Key: Cache-Control = <CFString 0x7ffba24e0ee0 [0x7fff7fa61110]>{contents = "private, max-age=0"}
        12 : Case Insensitive Key: Expires = <CFString 0x7ffba24c1290 [0x7fff7fa61110]>{contents = "Tue, 22 Oct 2013 11:55:26 GMT"}
    10/22/13 8:01:07.101 AM WindowServer[1075]: handle_will_sleep_auth_and_shield_windows: no lock state data
    10/22/13 8:01:07.102 AM loginwindow[1074]: ERROR | -[LWScreenLock(Private) screenIsLockedTimeExpired:] | No lock state found, use built in check
    10/22/13 8:01:07.103 AM WindowServer[1075]: Created shield window 0x809 for display 0x003f003d
    10/22/13 8:01:07.103 AM WindowServer[1075]: handle_will_sleep_auth_and_shield_windows: no lock state data
    10/22/13 8:01:07.103 AM WindowServer[1075]: Created shield window 0x80a for display 0x003f003e
    10/22/13 8:01:07.103 AM WindowServer[1075]: handle_will_sleep_auth_and_shield_windows: no lock state data
    10/22/13 8:01:07.108 AM WindowServer[1075]: MPAccessSurfaceForDisplayDevice: Set up page flip mode on display 0x04241110 device: 0x103b5d110  isBackBuffered: 1 numComp: 3 numDisp: 3
    10/22/13 8:01:07.232 AM loginwindow[1074]: resume called when there was already a timer
    10/22/13 8:01:29.746 AM coreaudiod[202]: Disabled automatic stack shots because audio IO is active
    10/22/13 8:01:30.373 AM coreaudiod[202]: Enabled automatic stack shots because audio IO is inactive
    10/22/13 8:01:33.595 AM com.apple.iCloudHelper[52460]: AOSKit ERROR: Setup request failed, [email protected], url=https://setup.icloud.com/setup/get_account_settings, requestHeaders=
        "Accept-Language" = "en-us";
        Authorization = "Basic ...";
        "X-APNS-Token" = f399cac3645458297dd7be50afbcef111e82ed4220706386f776a845c51135c9;
        "X-Aos-Accept-Tos" = false;
        "X-Mme-Client-Info" = "<MacPro5,1> <Mac OS X;10.8.5;12F45> <com.apple.AOSKit/152.4 (com.apple.systempreferences/12.0)>";
        "X-Mme-Country" = US;
        "X-Mme-Timezone" = EDT;
    error=Error Domain=AOSErrorDomain Code=5002 "The operation couldn’t be completed. (AOSErrorDomain error 5002.)" UserInfo=0x7fcb08435310 {HttpStatusCode=401, DialogInfo={
        AlternateButtonLabel = "";
        AlternateButtonLink = "";
        Body = UNAUTHORIZED;
        DefaultButtonLabel = "mme.setupservice.SetupServiceJS.OK";
        DefaultButtonLink = "";
        DialogType = PasswordDialog;
        ErrorID = UNAUTHORIZED;
        Header = "";
        HelpLink = "";
        description = "These account credentials are unauthorized.";
        localizedError = UNAUTHORIZED;
        protocolVersion = 2;
    }}, httpStatusCode=401, responseBody=
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
        <dict>
            <key>protocolVersion</key>
            <string>2</string>
            <key>DefaultButtonLabel</key>
            <string>mme.setupservice.SetupServiceJS.OK</string>
            <key>Body</key>
            <string>UNAUTHORIZED</string>
            <key>ErrorID</key>
            <string>UNAUTHORIZED</string>
            <key>DialogType</key>
            <string>CustomDialog</string>
            <key>AlternateButtonLink</key>
            <string></string>
            <key>AlternateButtonLabel</key>
            <string></string>
            <key>localizedError</key>
            <string>UNAUTHORIZED</string>
            <key>DefaultButtonLink</key>
            <string></string>
            <key>Header</key>
            <string></string>
            <key>HelpLink</key>
            <string></string>
            <key>description</key>
            <string>These account credentials are unauthorized.</string>
        </dict>
    </plist>
    10/22/13 8:01:35.293 AM System Preferences[52480]: Unknown serviceID: com.apple.Dataclass.SharedStreams
    10/22/13 8:01:35.423 AM System Preferences[52480]: Unknown serviceID: com.apple.Dataclass.SharedStreams
    10/22/13 8:01:35.423 AM System Preferences[52480]: Unknown serviceID: com.apple.Dataclass.SharedStreams
    10/22/13 8:01:35.900 AM com.apple.iCloudHelper[52460]: AOSKit ERROR: Quota usage request failed, [email protected], url=https://p20-quota.icloud.com:443/quotaservice/external/osx/1170343864/getQuotaIn fo, requestHeaders=
        "Accept-Language" = "en-us";
        Authorization = "Basic ...";
        "X-Mme-Client-Info" = "<MacPro5,1> <Mac OS X;10.8.5;12F45> <com.apple.AOSKit/152.4 (com.apple.systempreferences/12.0)>";
        "X-Mme-Country" = US;
        "X-Mme-Timezone" = EDT;
    error=Error Domain=AOSErrorDomain Code=1000 "The operation couldn’t be completed. (AOSErrorDomain error 1000.)" UserInfo=0x7fcb0984dc00 {HttpStatusCode=401, DialogInfo={
        DialogType = Unknown;
    }}, httpStatusCode=401
    10/22/13 8:01:36.357 AM System Preferences[52480]: Unknown serviceID: com.apple.Dataclass.SharedStreams
    10/22/13 8:01:36.358 AM System Preferences[52480]: Unknown serviceID: com.apple.Dataclass.SharedStreams
    10/22/13 8:01:36.502 AM System Preferences[52480]: Unknown serviceID: com.apple.Dataclass.SharedStreams
    10/22/13 8:01:36.503 AM System Preferences[52480]: Unknown serviceID: com.apple.Dataclass.SharedStreams
    10/22/13 8:01:36.535 AM System Preferences[52480]: handleOpenParameter called activateIgnoringOtherApps
    10/22/13 8:01:36.583 AM System Preferences[52480]: Unknown serviceID: com.apple.Dataclass.SharedStreams
    10/22/13 8:01:36.941 AM com.apple.time[1108]: Interval maximum value is 946100000 seconds (specified value: 9223372036854775807).
    10/22/13 8:01:37.161 AM aosnotifyd[52497]: bootstrap_look_up failed (44e)
    10/22/13 8:01:38.098 AM fseventsd[48]: Logging disabled completely for device:1: /Volumes/Recovery HD
    10/22/13 8:01:38.153 AM fseventsd[48]: disk logger: failed to open output file /Volumes/JRL1/.fseventsd/00000000043da126 (No such file or directory). mount point /Volumes/JRL1/.fseventsd
    10/22/13 8:01:38.241 AM fseventsd[48]: disk logger: failed to open output file /Volumes/JRL1/.fseventsd/00000000043da126 (No such file or directory). mount point /Volumes/JRL1/.fseventsd
    10/22/13 8:01:38.771 AM locationd[52500]: NOTICE,Location icon should now be in state 0
    10/22/13 8:01:39.397 AM System Preferences[52480]: INFO: FMM: containsRecoveryPartition: YES, version: 12E55
    10/22/13 8:01:39.438 AM System Preferences[52480]: INFO: FMM: containsRecoveryPartition: YES, version: 12E55
    10/22/13 8:01:39.672 AM System Preferences[52480]: INFO: FMM: recoveryPartitionNeedsUpdate: NO
    10/22/13 8:01:39.672 AM System Preferences[52480]: INFO: FMM: containsRecoveryPartition: YES, version: 12E55
    10/22/13 8:01:39.672 AM System Preferences[52480]: INFO: FMM: recoveryPartitionNeedsUpdate: NO
    10/22/13 8:01:39.673 AM System Preferences[52480]: INFO: FMM: can enable: YES
    10/22/13 8:01:39.678 AM System Preferences[52480]: Unknown serviceID: com.apple.Dataclass.SharedStreams
    10/22/13 8:01:39.758 AM System Preferences[52480]: INFO: FMM: containsRecoveryPartition: YES, version: 12E55
    10/22/13 8:01:39.758 AM System Preferences[52480]: INFO: FMM: recoveryPartitionNeedsUpdate: NO
    10/22/13 8:01:39.758 AM System Preferences[52480]: INFO: FMM: containsRecoveryPartition: YES, version: 12E55
    10/22/13 8:01:39.759 AM System Preferences[52480]: INFO: FMM: recoveryPartitionNeedsUpdate: NO
    10/22/13 8:01:39.759 AM System Preferences[52480]: INFO: FMM: can enable: YES
    10/22/13 8:01:39.759 AM System Preferences[52480]: INFO: FMM: containsRecoveryPartition: YES, version: 12E55
    10/22/13 8:01:39.759 AM System Preferences[52480]: INFO: FMM: recoveryPartitionNeedsUpdate: NO
    10/22/13 8:01:39.760 AM System Preferences[52480]: INFO: FMM: containsRecoveryPartition: YES, version: 12E55
    10/22/13 8:01:39.760 AM System Preferences[52480]: INFO: FMM: recoveryPartitionNeedsUpdate: NO
    10/22/13 8:01:39.760 AM System Preferences[52480]: INFO: FMM: can enable: YES
    10/22/13 8:01:40.022 AM System Preferences[52480]: INFO: FMM: containsRecoveryPartition: YES, version: 12E55
    10/22/13 8:01:40.022 AM System Preferences[52480]: INFO: FMM: recoveryPartitionNeedsUpdate: NO
    10/22/13 8:01:40.023 AM System Preferences[52480]: INFO: FMM: containsRecoveryPartition: YES, version: 12E55
    10/22/13 8:01:40.023 AM System Preferences[52480]: INFO: FMM: recoveryPartitionNeedsUpdate: NO
    10/22/13 8:01:40.023 AM System Preferences[52480]: INFO: FMM: can enable: YES
    10/22/13 8:01:40.151 AM System Preferences[52480]: Unknown serviceID: com.apple.Dataclass.SharedStreams
    10/22/13 8:01:40.340 AM com.apple.iCloudHelper[52460]: AOSKit ERROR: Quota usage request failed, [email protected], url=https://p20-quota.icloud.com:443/quotaservice/external/osx/1170343864/getQuotaIn fo, requestHeaders=
        "Accept-Language" = "en-us";
        Authorization = "Basic ...";
        "X-Mme-Client-Info" = "<MacPro5,1> <Mac OS X;10.8.5;12F45> <com.apple.AOSKit/152.4 (com.apple.systempreferences/12.0)>";
        "X-Mme-Country" = US;
        "X-Mme-Timezone" = EDT;
    error=Error Domain=AOSErrorDomain Code=1000 "The operation couldn’t be completed. (AOSErrorDomain error 1000.)" UserInfo=0x7fcb08412810 {HttpStatusCode=401, DialogInfo={
        DialogType = Unknown;
    }}, httpStatusCode=401
    10/22/13 8:01:47.781 AM System Preferences[52480]: Unknown serviceID: com.apple.Dataclass.SharedStreams
    10/22/13 8:01:53.583 AM App Store[52489]: No alternate URLs found for packageId com.apple.pkg.MakeQueuesScript
    10/22/13 8:04:35.496 AM Mail[52536]: Using V2 Layout
    10/22/13 8:04:35.675 AM librariand[52538]: MMe quota status changed: under quota
    10/22/13 8:04:39.533 AM com.apple.SecurityServer[15]: Session 100508 created
    10/22/13 8:04:42.421 AM com.apple.iCloudHelper[52460]: AOSKit ERROR: Setup request failed, [email protected], url=https://setup.icloud.com/setup/get_account_settings, requestHeaders=
        "Accept-Language" = "en-us";
        Authorization = "Basic ...";
        "X-APNS-Token" = f399cac3645458297dd7be50afbcef111e82ed4220706386f776a845c51135c9;
        "X-Aos-Accept-Tos" = false;
        "X-Mme-Client-Info" = "<MacPro5,1> <Mac OS X;10.8.5;12F45> <com.apple.AOSKit/152.4 (com.apple.syncdefaultsd/0.0)>";
        "X-Mme-Country" = US;
        "X-Mme-Timezone" = EDT;
    error=Error Domain=AOSErrorDomain Code=5002 "The operation couldn’t be completed. (AOSErrorDomain error 5002.)" UserInfo=0x7fcb09b00080 {HttpStatusCode=401, DialogInfo={
        AlternateButtonLabel = "";
        AlternateButtonLink = "";
        Body = UNAUTHORIZED;
        DefaultButtonLabel = "mme.setupservice.SetupServiceJS.OK";
        DefaultButtonLink = "";
        DialogType = PasswordDialog;
        ErrorID = UNAUTHORIZED;
        Header = "";
        HelpLink = "";
        description = "These account credentials are unauthorized.";
        localizedError = UNAUTHORIZED;
        protocolVersion = 2;
    }}, httpStatusCode=401, responseBody=
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
        <dict>
            <key>protocolVersion</key>
            <string>2</string>
            <key>DefaultButtonLabel</key>
            <string>mme.setupservice.SetupServiceJS.OK</string>
            <key>Body</key>
            <string>UNAUTHORIZED</string>
            <key>ErrorID</key>
            <string>UNAUTHORIZED</string>
            <key>DialogType</key>
            <string>CustomDialog</string>
            <key>AlternateButtonLink</key>
            <string></string>
            <key>AlternateButtonLabel</key>
            <string></string>
            <key>localizedError</key>
            <string>UNAUTHORIZED</string>
            <key>DefaultButtonLink</key>
            <string></string>
            <key>Header</key>
            <string></string>
            <key>HelpLink</key>
            <string></string>
            <key>description</key>
            <string>These account credentials are unauthorized.</string>
        </dict>
    </plist>
    10/22/13 8:04:42.834 AM WindowServer[1075]: CGXSetWindowBackgroundBlurRadius: Invalid window 0xffffffff
    10/22/13 8:04:45.323 AM System Preferences[52480]: Unknown serviceID: com.apple.Dataclass.SharedStreams
    10/22/13 8:04:45.342 AM xpcd[25595]: AOSAlertManager[52545]: registration request failed: (0x12, 0xd) process failed sandbox check
    10/22/13 8:04:45.369 AM System Preferences[52480]: INFO: FMM: containsRecoveryPartition: YES, version: 12E55
    10/22/13 8:04:45.369 AM System Preferences[52480]: INFO: FMM: recoveryPartitionNeedsUpdate: NO
    10/22/13 8:04:45.370 AM System Preferences[52480]: INFO: FMM: containsRecoveryPartition: YES, version: 12E55
    10/22/13 8:04:45.370 AM System Preferences[52480]: INFO: FMM: recoveryPartitionNeedsUpdate: NO
    10/22/13 8:04:45.370 AM System Preferences[52480]: INFO: FMM: can enable: YES
    10/22/13 8:04:53.708 AM System Preferences[52480]: Unknown serviceID: com.apple.Dataclass.SharedStreams
    10/22/13 8:04:53.796 AM AppleIDAuthAgent[48807]: SERVER AppleIDAuth: Already existing account "jo...ne@?????.???" re-added; succeeded.[ NULL ]  (__AppleIDDoAddAppleID()/AppleIDAuthenticationImpl.cpp #169) com.apple.coreservices.appleid.authentication.peer.0x7fa3eb600e.xpcq

  • Time Machine disk not recognised

    My G5 PowerMac has been away for repair; it's needed a new logic board. It was away for nearly two weeks. Now Time Machine doesn't recognise the external drive which contains the Time Machine backups from last November. It wants to do a backup from scratch and says there isn't enough space on the disk.
    Is there any way of getting the Time Machine to recognise the previous backups and start adding to them?
    I'll be very grateful for any advice.

    To TM, it is a different computer. The logic board includes your Ethernet "Mac Address", which is a unique number that TM uses to be sure it knows which Mac is which.
    There is a fairly elaborate way to attempt to persuade TM that the existing backups really are for your "new" Mac: http://www.macosxhints.com/article.php?story=20080128003716101
    It is very easy for the inexperienced user of Terminal (and the not-so-inexperienced as well) to make an error with Terminal, get no error message, and have it not work, so try it at your own risk.
    But there is an alternative: hold down the Option key while selecting the TM icon in your Menubar. The +Enter Time Machine+ option changes to +Browse Other Time Machine Disks.+ That's a bit misleading, but it will take you into the normal TM interface where you can see and restore from the old set of backups.
    Even if you're successful with the Terminal work, your first backup with the new logic board may be a full one -- every file and folder on your system. If TM decides to do that, you cannot prevent it.
    So if your TM disk/partition isn't at least 2.5 times the size of the data it's backing-up, your best bet may be to just erase it with Disk Utility and let TM start over.

  • Time Machine, Disk Utility, and clearing out corrupted snapshots

    Hi, all. I've been having some troubling issues with Time Machine and could use your collective insight.
    I have a 500GiB external USB2 disk that I've been using for Time Machine since December (the oldest snapshot in Backups.backupdb is named 2007-12-13-222250). Everything worked fine until sometime in late January, when Time Machine decided to ax 2/3 of my Applications directory. Time Machine's logging is terse, so I wasn't able to determine what caused the corruption. The fact that this error wasn't caught and flagged by Time Machine bothers me.
    Especially because I discovered this in the process of needing to recover from a crash on my laptop's hard drive -- I had to roll back to a previous, complete snapshot to get all my applications back.
    After that I had to engage in some jiggery-pokery to get Time Machine to re-snapshot everything, but things proceeded normally until I received my new copy of DiskWarrior 4.1 last night (although DiskWarrior is an innocent bystander here). I tried to use DiskWarrior to rebuild the directory on the Time Machine disk, but it failed before trying to write anything.
    (For those who care: after some back and forth with Alsoft tech support, we determined this was likely because my Time Machine volume has 6.2GB of catalog data, and DiskWarrior works by rebuilding the directory in memory, so it has to be able to fit the whole catalog into virtual memory.)
    I was a little paranoid that something might be wrong with the disk after that, so I fired up Disk Utility and told it to repair the disk. It churned for about 6 hours and repaired an extraordinarily large number of hardlink reference count errors, but completed by claiming that the disk had been repaired.
    When I next told Time Machine to run, instead of copying over a couple GB of data like it usually does, it started copying 38GB! ***? I took a look at the previous Time Machine snapshots, and discovered that Disk Utility had totally corrupted every snapshot I'd made since last month's fandango. Most of the root-level directories in the snapshots now look like this:
    $ ls -al /Volumes/Time\ Machine\ Backups/Backups.backupdb/xxx.net/2008-03-13-025640/Euphrosyne/
    total 128
    drwxrwxr-t@ 16 root admin 1020 Feb 15 00:17 ./
    drwxr-xr-x@ 3 root ogd 204 Mar 13 02:56 ../
    -r--r--r--@ 9151 root 20051003 0 Feb 11 23:13 .DRM_Data
    -r--r--r--@ 50574 root 20051004 0 Feb 11 23:13 .DS_Store
    -r--r--r--@ 9154 root 20051006 0 Feb 11 23:13 .SymAVQSFile
    -r--r--r--@ 9155 root 20051007 0 Feb 11 23:13 .VolumeIcon.icns.candybarbackup
    drwxr-xr-x@ 2 ogd admin 68 Feb 29 2004 .buildinstaller1.tmp/
    -r--r--r--@ 9149 root 20051001 0 Feb 11 23:13 .com.apple.timemachine.supported
    -r--r--r--@ 9150 root 20051002 0 Feb 11 23:13 .com.apple.timemachine.supported (from old Mac)
    -r--r--r--@ 9153 root 20051005 0 Feb 11 23:13 .redethist
    -r--r--r--@ 58730 root 20051009 0 Feb 11 23:13 Applications
    -r--r--r--@ 37526 root 20051012 0 Feb 11 23:13 Desktop Folder
    -r--r--r--@ 13328 root 20051013 0 Feb 11 23:13 Developer
    -r--r--r--@ 64211 root wheel 0 Feb 11 23:13 Library
    -r--r--r--@ 49886 root 20051080 0 Feb 11 23:13 Network
    -r--r--r--@ 5643 root 20051120 0 Feb 11 23:13 System
    lrwxr-xr-x 1 root ogd 60 Mar 13 02:56 User Guides And Information@ -> /Library/Documentation/User Guides and Information.localized
    drwxr-xr-x@ 5 root admin 204 Dec 6 02:07 Users/
    -r--r--r--@ 2554 root wheel 0 Feb 11 23:13 Volumes
    -r--r--r--@ 37448 root 20051010 0 Feb 11 23:13 bin
    -r--r--r--@ 37525 root 20051011 0 Feb 11 23:13 cores
    lrwxr-xr-x@ 1 root ogd 11 Mar 13 02:56 etc@ -> private/etc
    -r--r--r--@ 26309 root 20051078 0 Feb 11 23:13 mach_kernel
    -r--r--r--@ 26310 root 20051079 0 Feb 11 23:13 mach_kernel.ctfsys
    lrwxr-xr-x 1 root ogd 12 Mar 13 02:56 opt@ -> /private/opt
    drwxr-xr-x@ 8 root wheel 272 Dec 6 02:31 private/
    -r--r--r--@ 52664 root 20051119 0 Feb 11 23:13 sbin
    lrwxr-xr-x@ 1 root ogd 11 Mar 13 02:56 tmp@ -> private/tmp
    -r--r--r--@ 41668 root 20052660 0 Feb 11 23:13 usr
    lrwxr-xr-x@ 1 root ogd 11 Mar 13 02:56 var@ -> private/var
    That is clearly, completely wrong, and it alarms me that Disk Utility could cause so much damage to a Time Machine volume.
    Since I also use SuperDuper! to regularly clone this disk, it's not as big a nightmare as it could be, but this means that I'm going to have to clear out every snapshot for the last month by hand, both because I obviously can't trust them anymore, and because I keep getting messages like this in the logs:
    2008/03/13 7:25:35 PM /System/Library/CoreServices/backupd[1229] Error: (-36) copying /.com.apple.timemachine.supported to /Volumes/Time Machine Backups/Backups.backupdb/xxx.net/2008-03-13-192246.inProgress/70254508-90E3-4FF A-AE46-9E8210095DAE/Euphrosyne
    2008/03/13 7:25:35 PM /System/Library/CoreServices/backupd[1229] Error: (-36) copying /.com.apple.timemachine.supported (from old Mac) to /Volumes/Time Machine Backups/Backups.backupdb/xxx.net/2008-03-13-192246.inProgress/70254508-90E3-4FF A-AE46-9E8210095DAE/Euphrosyne
    2008/03/13 7:25:35 PM /System/Library/CoreServices/backupd[1229] Error: (-36) copying /.DRM_Data to /Volumes/Time Machine Backups/Backups.backupdb/xxx.net/2008-03-13-192246.inProgress/70254508-90E3-4FF A-AE46-9E8210095DAE/Euphrosyne
    2008/03/13 7:25:35 PM /System/Library/CoreServices/backupd[1229] Error: (-36) copying /.DS_Store to /Volumes/Time Machine Backups/Backups.backupdb/xxx.net/2008-03-13-192246.inProgress/70254508-90E3-4FF A-AE46-9E8210095DAE/Euphrosyne
    2008/03/13 7:25:35 PM /System/Library/CoreServices/backupd[1229] Error: (-36) copying /.redethist to /Volumes/Time Machine Backups/Backups.backupdb/xxx.net/2008-03-13-192246.inProgress/70254508-90E3-4FF A-AE46-9E8210095DAE/Euphrosyne
    2008/03/13 7:25:35 PM /System/Library/CoreServices/backupd[1229] Error: (-36) copying /.SymAVQSFile to /Volumes/Time Machine Backups/Backups.backupdb/xxx.net/2008-03-13-192246.inProgress/70254508-90E3-4FF A-AE46-9E8210095DAE/Euphrosyne
    2008/03/13 7:25:35 PM /System/Library/CoreServices/backupd[1229] Error: (-36) copying /.VolumeIcon.icns.candybarbackup to /Volumes/Time Machine Backups/Backups.backupdb/xxx.net/2008-03-13-192246.inProgress/70254508-90E3-4FF A-AE46-9E8210095DAE/Euphrosyne
    I'd like to keep the old snapshots if I can. What's likely to happen if I just go and clear out the b0rked backup sessions by hand?
    (Hmm... it appears yes, because I just deleted them all and the disk didn't recover the freed space.)
    Here's the important question: has anyone else had issues using Disk Utility on a Time Machine volume, and does anyone at Apple have any plans to add integrity checking to Time Machine? As it stands, I don't really feel like I can trust it in its present form, as convenient as it is...

    I have trouble with disk utility on my new (1 TB Lacie) as well as on my old (500 GB WD) drive. After doing a backup, du tells me a never ending list of errors like
    HasFolderCount flag needs to be set (id = 599567)
    (it should be 0x10 instead of 0)
    Everything was O.K. before doing the backup; so is the disk to be backupped, according to du.
    Up to now, no other problem occurred, but I´d like to clear this issue before my trust in time machine is restored.

Maybe you are looking for