Time Machine backup failure on case-sensitive disk?

Hello,
I just started getting a Time Machine backup failure error that says "A disk you are backing up is case-sensitive, but the backup disk is not."
None of my external disks have changed and I've not added any new ones.
The error seems to be stemming from the fact that I'm logged in as multiple users on my system, all with MobileMe accounts. When I "get info" on all mounted disks, the only ones that are reporting "Mac OS Extended (Case-sensitive, Journaled)" are the mounted iDisks from the other use accounts that I'm currently logged in as.
Does this mean I cannot use Time Machine while logged in as multiple users, all with the iDisks mounted? That would be a major annoyance to either have to log out/log in to each user as I need them or to disable iDisk syncing in my MobileMe prefs.
Regards,
Terry

That seems odd to me; my iDisk shows WebDAV as the format and doesn't interfere with backups, but I don't have any other users' iDisks, either.
Another possibility would be to reformat your TM drive as case-sensitive. That would, of course, erase all your backups so TM would start over from scratch, and some possible troubles when restoring (see the pink box in #5 of the Frequently Asked Questions *User Tip,* also at the top of this forum, for details); but you'd no longer have the backup problem.

Similar Messages

  • I am trying to do a full Time Machine Backup to a new external disk. The backup starts, and it says "Time remaining about 4 days." That seems like a very long time, but the real problem is that the computer "logs off" after a few hours, and the b.u. stops

    I am trying to do a full Time Machine Backup to a new external disk. The backup starts, and it says "Time remaining about 4 days." That seems like a very long time, but the real problem is that the computer "logs off" after a few hours, and the backup stops. The system preferences are set to "Never" for Computer sleep and Display sleep. The computer does not ordinarily log off automatically, but it has done this twice since I started the Time Machine backup.

    If you have more than one user account, these instructions must be carried out as an 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.
    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
    View ▹ Show Log List
    from the menu bar.
    Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message. Clear the text field and scroll back in the log to that time. 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 (command-C) to the Clipboard. Paste (command-V) into a reply to this message.
    If all you see are messages that contain the word "Starting," you didn't clear the search box.
    If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
    When posting a log extract, be selective. Don't post more than is requested.
    Please do not indiscriminately dump thousands of lines from the log into this discussion.
    Some personal information, such as the names of your files, may be included — anonymize before posting.

  • Time machine backup too big for empty disk??

    So I restart my MacBook Pro a few minutes after completing a full Time Machine backup.  When it restarts it goes through the grey startup screen, then gets stuck on the blue screen just  before the desktop normally appears. This happens whenever I startup. I am still able to hit the power button and get the Restart/Shut Down dialog, so I restart using my Snow Leopard boot disk, run Disk Utility, repair permissions, and repair disk, but the problem still remains. I decide to Restore from Time Machine Backup, so I erase my disk (80 GB, had only 200 MB free), go to the Restore screen and connect my backup disk. Now the weird part -- it says my latest backup is too big for the disk, even though i just erased everything, and 74.2 GB show as free. All my previous backups seem to fit fine, but apparently the last time Time Machine backed up more from my disk than can fit on my disk! It seems having a hard disk close to full is enough to render a backup effectively useless.  Guess I'll have to restore from a previous backup, then manually copy the newer files. Just wanted to alert others to this insane problem, so it doesn't happen to them.

    dgordon412 wrote:
    (80 GB, had only 200 MB free)
    That's likely corrupted your system. You should have a minimum of 10% - 15% free at all times. That's almost certainly why it wouldn't restart.
    even though i just erased everything, and 74.2 GB show as free.
    There must be something else on the drive; if you erase it, it should have just under 80 GB free. Is there another partition?
    Did you erase with a Leopard Install disc or a Snow Leopard disc? If you used a Leopard disc, that might explain showing only 74.2 GB free (it counts differently).
    If so, use your +Snow Leopard+ install disc to do a complete reformat, and try to restore the backup. A Leopard disc cannot restore a Snow Leopard backup. Even the Snow Leopard disc may not work, as it's just too full and/or your system was damaged by getting too full.
    All my previous backups seem to fit fine, but apparently the last time Time Machine backed up more from my disk than can fit on my disk! It seems having a hard disk close to full is enough to render a backup effectively useless.
    Having an OSX drive that full will make your Mac extremely sluggish, cause data corruption and/or loss, apps to crash, etc.
     Guess I'll have to restore from a previous backup, then manually copy the newer files. Just wanted to alert others to this insane problem, so it doesn't happen to them.
    If you can get your Mac running, you need to make several GBs of space immediately.
    If all else fails, reformat the internal HD and install OSX from your Snow Leopard Install disc, then use +Setup Assistant+ after the Welcome video to transfer +*most, but not all+* of your stuff from the backup. Omit the contents of one or more large sub-folders in a home folder (such as Photos, Music, or Movies).
    See #19 in [Time Machine - Frequently Asked Questions|http://web.me.com/pondini/Time_Machine/FAQ.html] (or use the link in *User Tips* at the top of this forum), for details.

  • HT1379 I had to restart by resetting the NVRAM/PRAM.  Now I have a window showing OS X Utilities.  My options are restore from Time Machine Backup (which I could do), Disk Utility to repair or erase, get help online or reinstall OS X.  What should I do?

    I had to restart by resetting the NVRAM/PRAM.  Now I have a window showing OS X Utilities.  My options are restore from Time Machine Backup (which I could do), Disk Utility to repair or erase, get help online or reinstall OS X.  What should I do?  The problem began when I tried to restart my computer and the only thing I saw was the grey screen, Apple logo, and the timer; the computer wouldn't restart from there.

    I searched through trouble shooting options on the Apple Support page and was able to make it this far.

  • How do I encrypt my Time Machine Backup on the External Hard disk

    I have taken a backup of my data onto an external Hard Disk. I have used the Time Machine application to take the back up.
    I want to encrypt this time machine backup on the External Hard disk. Any suggestions???

    jcorroon wrote:
    The Encrypt Backup Disk is greyed out for me. Any suggestions?
    Many thanks!
    Have you selected the disk?
    You can only encrypt disks that are directly-connected (ie, not on a network), with the GUID partition map scheme.
    Put your mouse pointer on the dimmed checkbox, and after a moment an explanation should appear.

  • Time Machine Backup failured (Issue 1426)

    Hello at all,
    well i have got a big problem with my macbook.
    I reinstalled it today (incl. formatting the HD). Now i tried to backup my data (I did all updates) 10.5.8 and it failured.
    Its horrible. I need all my data.
    I hope there´s somebody who can help me, because i have to learn for my Bachelor.
    Here some more data:
    Mac OS X, 10.5.8
    4 GB 667 MHz DDR2
    The time Machine:
    WD Ext HDD 1021 Media
    1 TB
    Mac OS x Extended journaled
    And i have to say it was the first time ever i had to reinstall the system since february 2008 i bought my MacBook.
    Please help me...
    Christin

    mickleroy wrote:
    We setup time machine backups in an office environment which is managed by a mac OS X Lion server.
    I'm not familiar with the server product, but the actual backup process should be the same as on the client version.
    On some occasions, a device requests an admin username and password whilst time machine is backing up.
    Does it say Admin password, or could it be a password for the backup device?  
    Feb  1 10:01:16 pc-205 diskarbitrationd[15]: SystemUIServer [206]:24835 not responding.
    Feb  1 10:01:33 pc-205 diskarbitrationd[15]: SystemUIServer [206]:24067 not responding.
    Not related to Time Machine.
    Feb  1 10:06:15 pc-205 sandboxd[513] ([61]): mds(61) deny file-write-data /dev/dtracehelperThat's not coming from Time Machine.  Looks to be related to Spotlght (mds) trying to index something. 
    Feb  1 10:07:16 pc-205 mds[61]: (Error) Volume: Could not find requested backup type:2 for volume
    We see that occasionally.  It seems to be spurious, or at least not a significant problem.
    Feb  1 10:07:37 pc-205 com.apple.backupd[436]: Backup completed successfully.
    Feb  1 10:07:39 pc-205 com.apple.backupd[436]: Ejected Time Machine disk image.
    Feb  1 10:07:40 pc-205 com.apple.backupd[436]: Ejected Time Machine network volume.
    Yes, that's the "bottom line." 
    Could this be fixed by running a full backup as admin so that time machine doesn't have to backup these inaccessible files (to normal users) anymore?
    No.  However a backup runs, it runs as the root user, so has access to everything.

  • Encryption of Time Machine backup on an external hard disk

    I use an external hard disk (not Time Capsule) for my Time Machine backup. How can I encrypt this external hard disk. I didn't find such a function in the Mac OS. Thanks a lot for any hint.

    Click here and follow the instructions. The image's contents can't be accessed without the password, but the image file can still be deleted.
    (56647)

  • Can you restore a Time Machine backup to a newly formatted disk.

    I am planning on reformatting my MacBook's hard drive, and then restoring my files to it, because of a problem I am having with Boot Camp telling me to reformat my disk and try partitioning again. Can I do this with Time Machine (i.e. wipe everything off my hard drive and then restore it with a Time Machine backup)? Would I just boot up from my Snow Leopard disk and then click on "+Restore Time Machine Backup+"? I am new to Time Machine, and haven't even performed my first backup, so please forgive me if this is a stupid question.
    Also, if I can do this, would it leave it exactly as it was before I reformatted or would I have to download all the updates again (e.g. my computer has Mac OS X v.10.6.2 installed. Would it restore to that or would it restore to v.10.6.0, the version that is on my Snow Leopard disk)?
    Thank you.
    James.

    yes, you can do it with TM but it would be safer to do using a bootable clone. to do it with TM boot from the SL install DVD, reformat the internal drive using disk utility in the utilities menu. quit disk utility and select 'restore system from backup" from utilities menu. follow the instructions.
    but as I said, it's better to use a bootable clone. make a clone to an external drive using CCCloner or Superduper. then boot from the external, reformat the internal using disk utility and clone the clone back to the internal.
    either method will give you your current system back so you won't have to reinstall anything afterward.
    Message was edited by: V.K.

  • How can I resolve repeated Time Machine backup failures?

    Time Machine stopped backing up from my wife's iMac 2 GHz Intel to a designated Iomega FireWire drive on August 6th. I have since erased, reformatted, and reselected the external drive. The profile for the external drive is as follows:
    Manufacturer: Iomega
    Model: 0x1
    GUID: 0xD0B80E5B000BE6
    Maximum Speed: Up to 400 Mb/sec
    Connection Speed: Up to 400 Mb/sec
    Sub-units:
    HDD USB 2.0/1394A Unit:
    Unit Software Version: 0x10483
    Unit Spec ID: 0x609E
    Firmware Revision: 0x12804
    Product Revision Level:
    Sub-units:
    HDD USB 2.0/1394A SBP-LUN:
    Capacity: 149.05 GB
    Removable Media: Yes
    BSD Name: disk2
    Mac OS 9 Drivers: No
    Partition Map Type: GPT (GUID Partition Table)
    S.M.A.R.T. status: Not Supported
    Volumes:
    Iomega Time Backup HD:
    Capacity: 148.73 GB
    Available: 148.31 GB
    Writable: Yes
    File System: Journaled HFS+
    BSD Name: disk2s2
    Mount Point: /Volumes/Iomega Time Backup HD
    I have also performed Tech Tool Pro 4.6.2 Advanced Tests on all related hardware to repair any damaged volumes and files but the Time Machine backup stops after at 97.5 MB of approximately 60+ GB of data.
    I have been unable to detect a cause for the failure in the Console logs but I note that the following entry has been repeated every few seconds in the system log since about August 23rd:
    Aug 26 10:55:30 Dee-Coopers-iMac mds[37]: (Error) Import: importer:0x844400 Importer start failed for 501 (kr:268435459 (ipc/send) invalid destination port)
    Aug 26 10:56:00: --- last message repeated 7 times ---

    I had experienced the similar problem when I first upgraded to Leopard. The problem was caused by spotlight indexing my hard drive and at the same time Time Machine was trying to backup the spotlight index file. The solution was to temporary exclude most of the documents (I have a lot of pdf files) from spotlight and let it runs through the indexing process before starting Time Machine.
    I don't know if my experience help you or not but it might be something worth looking into.
    Good luck.

  • Moutain Lion Time Machine Backup To WHS 2011 Via Disk Utility Image On Windows Share?

    I read that with Lion you could do a Time Machine backup to a network share on Windows Home Server 2011.  I read you could create a image file via Disk Utility that would be placed on the network share, but mounted as a regular disk in Mac.   I think I read this method no longer works on Moutain Lion though.  Has anyone tried it?   I'm setting up a new Mac Mini and would like to do time machine backups to my WHS 2011 drivepool.    If it is possible great, any way to use the backup for bare metal restores as well? (ether across the network, or putting that image file on a usb drive first etc)    I use bootcamp to go back and forth on my Mac Mini, but I'd like to keep things backed up on the Mac side via standard time machine.

    I re-googled and found something I read about a few days ago that shows how it was done in Lion:
    http://basilsalad.com/how-to/create-time-machine-backup-network-drive-lion/
    I think maybe I found someone that tells how to do it:
    http://www.jamesbadger.ca/2012/09/12/mountain-lion-time-machine-over-afp-auto-mo unt-edition/
    The question is, how do I use this backup for a baremetal restore then?   I'm assuming I would do a generic Mountain Lion restore, and then just restore over the network after I manually re-mount the image again first.
    Does this sound like a real option/solution?  Looks like maybe I answered my own question, but I'd like to hear anyone else confirm it works and is worth trying.
    So my goal is to do a time machine backup over the network to a windows machine.
    If it's not possible, I guess I'll have to break down and plug in an external USB drive, but I'd still like to know if it's possible for another friend as well.

  • "Time Machine Backups" could not be unmounted (Disk Utilities)

    Hi there,
    I am having an error message when trying to back up time machine.  Therefore I went to disk utilities and verified disk.. said it needs to be prepared.  When I try to repair time machine, i then get the following message "The disk “Time Machine Backups” could not be unmounted".  I tried again and then it says its been repaired.  so when i tried a backup of time machine i get "time machine error.  unable to complete backup. an error occurred while copying files to the backup volume"
    I have installed "Time machine buddy" and I am getting"error reading system logs"
    I have a mac osx 10.5.8. No antivirus or spotlight running that i know of.
    Any ideas?

    One way to test is to Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, Test for problem in Safe Mode, see if external Drive can be repaired...
    PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive
    Reboot, test again.
    Open Console in Utilities & see if there are any clues or repeating messages when this happens.

  • Time Machine backup not working from startup disk

    So, in an attempt to make BootCamp work, I erased my hard drive (as instructed) after first backing up with Time Machine. Now trying to restore from the Time Machine drive, after starting up from install disk, and nothing happens. Disk Utility works when I open that from Utilities, but when I try to open "Restore System from backup..." nothing happens.
    Any clues?

    SDRussell wrote:
    So, in an attempt to make BootCamp work, I erased my hard drive (as instructed) after first backing up with Time Machine. Now trying to restore from the Time Machine drive, after starting up from install disk, and nothing happens. Disk Utility works when I open that from Utilities, but when I try to open "Restore System from backup..." nothing happens.
    nothing at all? that can only mean you have a problem with your install DVD. nothing can be done about that. what kind of DVD is it? is it the install disk that came with your computer? if so you can try asking apple for a replacement dvd. another option would be to do a fresh install of leopard and them use migration assistant during the original computer setup (you'll be given that option) to import your data and applications from the TM backup.
    Any clues?

  • Time Machine Backup Failure

    Well....
    More and more frequently, I'm getting a backup failed message from Time Machine. I don't see anything particularly incriminating from the console log...but, generally, it's the same problem (below):
    Jun 30 22:45:13 BigMacintosh-2 /System/Library/CoreServices/backupd[313]: Backup requested by user
    Jun 30 22:45:13 BigMacintosh-2 /System/Library/CoreServices/backupd[313]: Starting standard backup
    Jun 30 22:45:14 BigMacintosh-2 /System/Library/CoreServices/backupd[313]: Backing up to: /Volumes/Big TimeMachine/Backups.backupdb
    Jun 30 22:45:14 BigMacintosh-2 /System/Library/CoreServices/backupd[313]: Failed to create progress log file at path:/Volumes/Big TimeMachine/Backups.backupdb/Bob's Big Mac/2008-06-30-194423.inProgress/.Backup.236587514.320138.log.
    Jun 30 22:45:14 BigMacintosh-2 /System/Library/CoreServices/backupd[313]: Error: (-50) Creating directory F0BA6CF7-9087-4EB4-A54B-E3561374FBA2
    Jun 30 22:45:14 BigMacintosh-2 /System/Library/CoreServices/backupd[313]: Failed to make snapshot.
    Jun 30 22:45:20 BigMacintosh-2 /System/Library/CoreServices/backupd[313]: Backup failed with error: 2
    I'm wondering if 10.5.3 was the culprit, since I had no problems prior to it. Guess I'll see if 10.5.4 fixes this oddity... Until then, a restart generally gets the next backup going...
    Thoughts? Solutions?
    Bob

    Nope...a third auto backup failed...
    Jul 2 10:12:29 BigMacintosh-2 /System/Library/CoreServices/backupd[412]: Starting standard backup
    Jul 2 10:12:29 BigMacintosh-2 /System/Library/CoreServices/backupd[412]: Backing up to: /Volumes/Big TimeMachine/Backups.backupdb
    Jul 2 10:12:30 BigMacintosh-2 /System/Library/CoreServices/backupd[412]: No pre-backup thinning needed: 269.3 MB requested (including padding), 219.33 GB available
    Jul 2 10:12:37 BigMacintosh-2 /System/Library/CoreServices/backupd[412]: Copied 495 files (7.2 MB) from volume Macintosh HD.
    Jul 2 10:12:38 BigMacintosh-2 /System/Library/CoreServices/backupd[412]: Starting post-backup thinning
    Jul 2 10:12:38 BigMacintosh-2 /System/Library/CoreServices/backupd[412]: No post-back up thinning needed: no expired backups exist
    Jul 2 10:12:38 BigMacintosh-2 /System/Library/CoreServices/backupd[412]: Backup completed successfully.
    Jul 2 10:19:54 BigMacintosh-2 /System/Library/CoreServices/backupd[427]: Backup requested by user
    Jul 2 10:19:54 BigMacintosh-2 /System/Library/CoreServices/backupd[427]: Starting standard backup
    Jul 2 10:19:54 BigMacintosh-2 /System/Library/CoreServices/backupd[427]: Backing up to: /Volumes/Big TimeMachine/Backups.backupdb
    Jul 2 10:19:55 BigMacintosh-2 /System/Library/CoreServices/backupd[427]: No pre-backup thinning needed: 260.7 MB requested (including padding), 219.32 GB available
    Jul 2 10:20:01 BigMacintosh-2 /System/Library/CoreServices/backupd[427]: Copied 441 files (9 KB) from volume Macintosh HD.
    Jul 2 10:20:01 BigMacintosh-2 /System/Library/CoreServices/backupd[427]: Starting post-backup thinning
    Jul 2 10:20:01 BigMacintosh-2 /System/Library/CoreServices/backupd[427]: No post-back up thinning needed: no expired backups exist
    Jul 2 10:20:01 BigMacintosh-2 /System/Library/CoreServices/backupd[427]: Backup completed successfully.
    Jul 2 10:27:56 BigMacintosh-2 fseventsd[41]: callback_client: ERROR: d2fcallbackrpc() => (ipc/send) invalid destination port (268435459) for pid 431
    Jul 2 10:29:03 BigMacintosh-2 [0x0-0x31031].org.mozilla.thunderbird[447]: Warning: unrecognized command line flag -psn0200753
    Jul 2 10:40:48 BigMacintosh-2 fseventsd[41]: callback_client: ERROR: d2fcallbackrpc() => (ipc/send) invalid destination port (268435459) for pid 467
    Jul 2 11:11:39 BigMacintosh-2 kernel[0]: SetCryptoKey R: len 32, idx 1
    Jul 2 11:12:28 BigMacintosh-2 /System/Library/CoreServices/backupd[505]: Starting standard backup
    Jul 2 11:12:28 BigMacintosh-2 /System/Library/CoreServices/backupd[505]: Backing up to: /Volumes/Big TimeMachine/Backups.backupdb
    Jul 2 11:12:31 BigMacintosh-2 /System/Library/CoreServices/backupd[505]: No pre-backup thinning needed: 309.8 MB requested (including padding), 219.32 GB available
    Jul 2 11:12:49 BigMacintosh-2 /System/Library/CoreServices/backupd[505]: Copied 804 files (40.9 MB) from volume Macintosh HD.
    Jul 2 11:12:49 BigMacintosh-2 /System/Library/CoreServices/backupd[505]: No pre-backup thinning needed: 260.7 MB requested (including padding), 219.28 GB available
    Jul 2 11:12:57 BigMacintosh-2 /System/Library/CoreServices/backupd[505]: Copied 460 files (0 bytes) from volume Macintosh HD.
    Jul 2 11:12:59 BigMacintosh-2 /System/Library/CoreServices/backupd[505]: Starting post-backup thinning
    Jul 2 11:12:59 BigMacintosh-2 /System/Library/CoreServices/backupd[505]: No post-back up thinning needed: no expired backups exist
    Jul 2 11:12:59 BigMacintosh-2 /System/Library/CoreServices/backupd[505]: Backup completed successfully.
    Jul 2 11:36:38 BigMacintosh-2 kernel[0]: disk1s3: I/O error.
    Jul 2 11:36:38 BigMacintosh-2 kernel[0]:
    Jul 2 11:36:38: --- last message repeated 1 time ---
    Jul 2 11:36:38 BigMacintosh-2 kernel[0]: jnl: disk1s3: dojnlio: strategy err 0x5
    Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/C9675DCF-6359-43B8-8696-866D96AD91E 1)(Error) IndexCI in storestream_flush:store_streamflush write err:22
    Jul 2 11:36:38 BigMacintosh-2 kernel[0]: jnl: disk1s3: end_transaction: only wrote 0 of 57856 bytes to the journal!
    Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/C9675DCF-6359-43B8-8696-866D96AD91E 1)(Error) IndexCI in _ContentIndexSyncIndexBulk:Sync error live.0.
    Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/C9675DCF-6359-43B8-8696-866D96AD91E 1)(Error) IndexGeneral in notify_lowspace:low space for device 234881029 (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/C9675DCF-6359-43B8-8696-866D96AD91E 1)
    Jul 2 11:36:38 BigMacintosh-2 mds[35]: (Error) Volume: LOW DISK SPACE device:234881029
    Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4)(Error) IndexCI in ci_ftruncate:ftruncate(57 /Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4/live.0.indexPostings, 4194304) error:22
    Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4)(Error) IndexCI in initPayload:ftruncate err: 22
    Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4)(Error) IndexCI in ci_ftruncate:ftruncate(18 /Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4/live.0.indexIds, 262144) error:22
    Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4)(Error) IndexCI in openindexfile:ftruncate error: 22, size: 262144, live.0.indexIds
    Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4)(Error) IndexCI in ContentIndexOpenBulk:Could not open /Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4/live.0.; needs recovery
    Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4)(Error) IndexCI in copyFileOrFd:error (22) opening 0.indexGroups
    Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4)(Error) IndexCI in recoverIndex:Unrecoverable error: could not recover groups file (0.)
    Jul 2 11:36:38 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB943 4)(Error) IndexCI in CIMetaInfoCreate:Tried to create index when index already existed eMachine/.Spotlight-V100/Store-V1/Stores/84D06902-55F2-49F0-BF13-736335BB9434
    Jul 2 11:36:39 BigMacintosh-2 mds[35]: (/Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/C9675DCF-6359-43B8-8696-866D96AD91E 1)(Error) IndexCI in ContentIndexOpenBulk:Unclean shutdown of /Volumes/Big TimeMachine/.Spotlight-V100/Store-V1/Stores/C9675DCF-6359-43B8-8696-866D96AD91E 1/live.0.; needs recovery
    Jul 2 11:36:39 BigMacintosh-2 mds[35]: (Error) Server: registerForDeadNameNotification failed ((os/kern) invalid argument)
    Jul 2 11:36:39 BigMacintosh-2 kernel[0]: disk1s3: I/O error.
    Jul 2 12:12:28 BigMacintosh-2 /System/Library/CoreServices/backupd[593]: Starting standard backup
    Jul 2 12:12:28 BigMacintosh-2 /System/Library/CoreServices/backupd[593]: Backing up to: /Volumes/Big TimeMachine/Backups.backupdb
    Jul 2 12:12:28 BigMacintosh-2 /System/Library/CoreServices/backupd[593]: Error: (-50) Creating directory 2008-07-02-121228.inProgress
    Jul 2 12:12:28 BigMacintosh-2 /System/Library/CoreServices/backupd[593]: Failed to make snapshot container.
    Jul 2 12:12:33 BigMacintosh-2 /System/Library/CoreServices/backupd[593]: Backup failed with error: 2

  • Time Machine backup failure on 60Gb iPhoto Library on second partition

    I had 1 partition on my Macbook Pro (2010). I have several users on the mac and I use fast switching for them. All users use same iPhoto Library and iTunes Media - they are situation in a separate folder in my partition root. My Time Capsule was setup to backup everything and it actually did it well.
    Sometime ago I started to find a solution to avoid file permission problem - when different users add files/photos, they have permission to delete/change for them only. This caused some unwanted behavior. I read a lot of forums and basically the most appropriate solution is to create a separate partition on the same HDD and remove checkbox on it to support "Owner".
    So I did it - created new partition. Then I moved iTunes and iPhoto to new partition and then I started backup again. Unfortunately, it failed. It took me 2 days to understand that it actually fails on iPhoto Library - all other staff works ok. But as soon as I allow to backup iPhoto Library, it starts backing up and shows some progress, but when 1-2 Gb (or sometimes 100-500 MB) complete it shows that "Backup failed - ... this might be temporary problem..".
    I did not manage to resolve this - so I removed partition and reverted everything back by copying iTunes library and iPhoto library to external drive and then back after removing second partition. When I enabled backing up, everything worked great again - no problem.
    So here is the question - why backup failed on iPhoto library when it was on second partition? Are the any ideas?

    Move/backup/move back/backup did not fix the problem. TM still didn't backup the missing directories.
    I was finally able to convince TM to do the right thing by following the procedure described here:
    http://www.nzmac.com/quick-tips/time-machine/how-do-i-reset-time-machine.html
    This isn't a solution because I still don't know what caused TM to think that it backed up something that it didn't back up. But the article was suggested by a friend of mine in IT who also owns a few Macs. After following the procedure and running TM again I can see all of the previously missing files backed up on the ext drive. I also used BackupLoupe (http://www.soma-zone.com/BackupLoupe/) to browse the files that were actually copied by the last backup. I see that TM copied the directories that I knew were missing and two other directories that I did not know were missing.
    At this point I think my TM backup is complete. But now I'm on the lookout for a better backup solution. Until I find it I'll need to periodically compare backup sizes to make sure that TM keeps doing its job.

  • Can I restore a time machine backup to a new hard disk

    I've just had the HDD replced in my iMac 24 under Applecare Warranty. The data had been backed up on an external HDD using Time Machine.
    The only way I can see to restore the data is reinstal the OS and do a migration. This seems unwieldy, to say the least.
    Can I restore the backup direct to the iMac somehow?
    The backup was done when the iMac ran 10.6. It has come back with 10.5 installed.

    Take a look at Pondini's excellent TM articles, particularly this one -
    http://pondini.org/TM/14.html
    You should be able to restore your system in full if you backed up system folders as well as your data and applications.
    Otherwise, Use the retail Snow Leopard DVD to install Snow over Leopard (no erasing required), then use Setup Assistant from the new installation to migrate from TM.

Maybe you are looking for

  • I just can't seem to get Home Sharing to work...

    I'd really appreciate your advice please... The setup - One PC running Itunes, one Apple TV on a wired connection and an Iphone and Ipad connected over wi-fi.  All are running the latest and greatest software versions. I now want to be able to stream

  • RAW Images won't open in elements

    I recently loaded Photoshop Elements onto my MAC and attempted to use it to review and edit some images I took with my 7D Mark ii. Received the following message: Could not complete your request because the file appears to be from a camera model whic

  • Migration from Jdeveloper 11g r1 to 11g r2 problem

    Hi all I have a project initially created in Jdeveloper 11g r1 after migrating it to Jdeveloper 11g r2 i tried to replace lookup ejb invocation to dependency injection. So i used @EJB annotation in my managed bean. I'm shure there could be no mistake

  • ADF : Groovy Expression

    Hi Is it possible to reference the current entity object name using groovy? I would like to get the entity name in a validator to customize the error message. I currently have a validator and an error message with two placeholders, Attribute {0} is n

  • Authentification from java class

    Hello I have a use case in which I must get the authentification informations in a class(with a servlet) and after that to send them to the jdev Application. Can you help me with a solution? Thank you Angel