Time Machine Encryption - Cannot Prepare Disk

When i select my USB hard drive in Time Machine and tell it to use Encryption, I get the following error:
There was an error preparing the Time Machine backup disk "<disk name>". 
Invalid request.
This happened before and after I successfully encrypted my internal drive with FileVault.

The same with a
LaCie Hard Drive USB:
  Capacity:          320.07 GB (320,072,933,376 bytes)
  Removable Media:          Yes
  Detachable Drive:          Yes
  BSD Name:          disk3
  Product ID:          0x0651
  Vendor ID:          0x059f  (LaCie)
  Version:          0.00
  Serial Number:          10000E000CDADC1F
  Speed:          Up to 480 Mb/sec
  Manufacturer:          LaCie
  Location ID:          0xfd100000 / 3
  Current Available (mA):          500
  Current Required (mA):          2
  Partition Map Type:          GPT (GUID Partition Table)
  S.M.A.R.T. status:          Not Supported
  Volumes:
disk3s1:
  Capacity:          209.7 MB (209,715,200 bytes)
  BSD Name:          disk3s1
  Content:          EFI
Backup:
  Capacity:          319.73 GB (319,728,959,488 bytes)
  Available:          319.3 GB (319,303,114,752 bytes)
  Writable:          Yes
  File System:          Journaled HFS+
  BSD Name:          disk3s2
  Mount Point:          /Volumes/Backup
  Content:          Apple_HFS
from logs:
7/26/11 2:43:30.613 PM System Preferences: Disk preparation failed - main error: -69886 Invalid request.; detailed error: 0 No Error
But... i was able to do a Time Machine encrypted backup with a 2,5" Apple HDD @5400 rpm (unmounted from a MBP 15") using a USB/SATA controller.
Any possible correlation/solution?
–Mic

Similar Messages

  • Lost all photos on my iPhoto and get the ERROR WRITING TO DISK when trying to reload from Time Machine. iPhoto cannot import your photos because there was a problem writing to the volume containing your iPHOTO LIBRARY  . Looking for solution.

    Lost all photos on my iPhoto and get the ERROR WRITING TO DISK when trying to reload from Time Machine. iPhoto cannot import your photos because there was a problem writing to the volume containing your iPHOTO LIBRARY  . Looking for solution.

    Problems such as yours are sometimes caused by files that should belong to you but are locked or have wrong permissions. This procedure will check for such files. It makes no changes and therefore will not, in itself, solve your problem.
    First, empty the Trash, if possible.
    Triple-click anywhere in the line below on this page to select it, then copy the selected text to the Clipboard by pressing the key combination command-C:
    find ~ $TMPDIR.. \( -flags +sappnd,schg,uappnd,uchg -o ! -user $UID -o ! -perm -600 \) 2>&- | wc -l | pbcopy
    Launch the built-in Terminal 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 Terminal in the icon grid.
    Paste into the Terminal window (command-V). The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign ($) to appear.
    The output of the command will be a number. It's automatically copied to the Clipboard. Please paste it into a reply.
    The Terminal window doesn't show the output. Please don't copy anything from there.

  • HT1178 I have set up Time Capsule to use with Time Machine.  When I open Time Machine it 'cannot find' the Time Capsule and I have the Select the Disk each time.  In the Next Backup tab it always says "When disk is connected" even though the disk is alrea

    I have set up Time Capsule to use with Time Machine but when I open Time Machine it 'cannot find' the Time Capsule and I have to 'Select the Disk' each time. In the Next Backup tab it always says "When disk is connected" even though the disk is already connected.

    Your pro doesn't matter.. I presume it is happily working.
    Your imac setup has got messed up because you changed from a local (my book being USB type I presume) to network drive. Did you do a clean install of Lion?
    Did you use the backup from the Pro on the imac? Otherwise I don't see how the Pro shows up in use previous disk. Where is Pondini when you need him??
    You cannot download Time Machine as an App and replace the current version. It is built into the OS.. the only way to do it is a clean install. Unfortunately that might be the only way around the issue.
    There is a number of issues that Pondini has covered in the setup issues of troubleshooting.
    This is the most relevant I think. http://pondini.org/TM/B6.html
    But look at the whole section B setup problems.
    http://pondini.org/TM/Troubleshooting.html
    If it was me, I would store all the info you need.. not using TM but using a straight copy of files.
    Then clean install Lion. I doubt any of these issues would exist if you had not installed Lion over existing setup or used a different backup.
    See if you can get Pondini to respond.. !!

  • Time Machine stuck in Preparing Data Mode

    In the past two days my time Machine has not made a successful back up. It seems to be stuck in "preparing data" and will stay like this all day. Even when I click the time machine preferences and stop it, it never changes. Does anyone have any solutions to this or has experienced it.Any suggestions would be greatly appreciated.
    Thanks!!

    Judith,
    The following might contain an explanation for what you are experiencing.
    *_Time Machine May Report "Preparing..." For a Long Time_*
    First, it’s good to determine WHY Time Machine is "Preparing..." for an extended period of time. Examining the Console logs during this event can reveal what is actually going on behind the scenes. It may be “Preparing…” for a genuinely good reason. How long is 'too long' to wait for Time Machine to finish "Preparing..."? Some times, "Preparing..." is required to perform the normal housekeeping that Time Machine does periodically. Other times, it really is "stuck" and never proceeds after more than 24 hours.
    *”Deep Traversal” (Recent Crash / Forced Restart / System Update / Extended Period Between Backups)*
    According to the following KB article it can sometimes take quite a long time if Time Machine begins a “deep traversal” and has to compare data inventories. This may apply to your situation, particularly if many Gigs of data are involved. [http://support.apple.com/kb/TS1516]
    You see, Time Machine *+does not+* ordinarily perform file-by-file comparisons to determine what has changed and thus determine what needs to be backed up. Rather, Time Machine relies on FSEvents notifications. This is a log that the system uses to keep track of changes to directories. Rather than scan tens of thousands of files for changes each time, Time Machine simply looks at this log and narrows its’ scan to only the directories that have experienced changes since the last backup. Otherwise, Time Machine would have to be running constantly just to catch every change on its own and thus eat up precious CPU.
    Every event that FSEvents records has its’ own ID which includes a time stamp. At the end of every backup, Time Machine stores the last event ID that it processes. When the next backup is initiated, Time Machine looks at this stored ID and determines that it only needs to backup events that have occurred after the time stamp on this last event ID.
    If, due to a system crash, power failure, forced restart, or some other major system event, Time Machine cannot find this last event ID in the system logs then it will consider the FSEvents log “untrustable” and it will go into what’s called “deep traversal”. The Console logs may report +“Event store UUIDs don't match”.+ In this event, Time Machine will by-pass the system log entirely and perform its’ own file-by-file comparison to determine what has changed since its’ last backup. Obviously, if tens or hundreds of Gigs are involved, then this process can take quite some time and should be allowed to proceed.
    Additionally, it appears that if Time Machine has to go back too far to find the last event ID, then it will give up and simply go into “deep traversal” and do the file-by-file scan on its’ own. This can occur if Time Machine has not been able to perform its’ hourly backups for some time, as is the case for users who only backup once a week or so. This is also the case with major Mac OS system updates that change thousands of files at one time. There are simply too many events logged by the system for Time Machine to bother looking for the last known event ID.
    *Consolidation / “Thinning”*
    At the beginning, when Time Machine is first used, incremental backups are relatively quick events. But as time goes on, and backup files grow, Time Machine requires time to perform house-keeping on the backed up data. This maintenance is referred to in the Console logs as "thinning". The larger the backup files become, the more time Time Machine requires.
    To prevent the backup drive from filling up too fast, Time Machine will periodically consolidate, or 'thin', backups to free up space for new data. After a certain period of time, each hourly backup becomes "expired". This occurs about 24-48 hours after the hourly backup took place. At that point Time Machine begins consolidating, or "thinning", all the hourly backups of a given day into one daily backup. Then, after about a month all daily backups for a given week “expire” and are consolidated into a single weekly backup.
    Obviously, since the Time Machine process (backupd) does not run continuously, it has to do this "thinning" during routine backups. That is where "Preparing Backup..." and "Finishing Backup..." come in. It is during these initial and closing phases of a backup that "thinning" occurs. As a result, while not every backup will be accompanied by extended periods of "Preparing..." and "Finishing...", periodically Time Machine will require extra time to perform these space-saving consolidations.
    *Anti-Virus Software*
    Running anti-virus software can interfere with the backup process. Either disable it altogether, or try the suggestion outlined here, “If you use third-party anti-virus scanning software and have issues, make sure your Time Machine back up folder (Backups.backupdb on the Time Machine disk) is excluded from virus scanning.” (http://support.apple.com/kb/TS1516)
    *Software Updates* #
    Installing new software, upgrading existing software, or updating Mac OS X system software can create major changes in the structure of your Macs directories. Time Machine will backup every file that has changed since the installation.
    After an OS update (like 10.5.5) Time Machine realizes the system no longer matches what it looked like during the previous backup. So it has determined that it's earlier catalogue of what-should-be-where is “untrustable”. So it is going to go item-by-item comparing the before and after of your system.
    *Spotlight Keeps Indexing Backup Drive* #
    It may be that Time Machine can’t proceed or complete a backup due to Spotlight indexing. During this period, take a look at the Spotlight icon in the upper right corner of your screen. Is there a tiny dot pulsating in the center of the spyglass? Click on the icon. Is there a progress bar displayed? Generally, Spotlight indexing is a good thing. If it has only been a couple of hours then, stop the backup, turn Time Machine OFF, and let the indexing continue.
    However, at times Spotlight may hang and never progress after many hours, preventing further backups from taking place.
    Go to System Preferences --> Time Machine.
    Using the slider on the left, turn OFF Time Machine backups for now.
    Next, click “Show All” in the toolbar.
    Select the Spotlight Preferences.
    Click the Privacy Tab.
    First, drag your Macs’ internal hard disk from the desktop to the Privacy list.
    Wait 10 seconds, then highlight the Macs’ hard disk in the list and click the tiny “-” button at the bottom to remove it from the list.
    Spotlight will initiate a reindex of the hard disk. If you click on the Spotlight menu icon you may see the message:
    +“Spotlight helps you quickly find things on your computer. Spotlight will be available as soon as the contents of your computer have been indexed.”+
    ...and a progress bar will indicate the time remaining.
    Once completed, drag your Time Machine backup disk into the Privacy list of the Spotlight Preferences.
    Wait 10 seconds, then highlight the Time Machine backup disk in the list and click the tiny “-” button at the bottom to remove it from the list.
    Spotlight will now initiate a reindex of the hard disk.
    Once completed, if you have any other hard disks attached to your Mac that are also being backed using Time Machine, then force a reindex as well using the procedure outlined above.
    Then turn Time Machine back ON and initiate a backup.
    *Run Away System Process*
    It’s possible that Time Machine is stuck “Preparing…” because another process is monopolizing your Macs’ CPU. Launch Activity Monitor and sort the items by “CPU”. Is there a process that is at or near 100% that might be preventing the backupd process from moving forward?
    One poster stated, “I took it to my local Genius Bar and they found a Syslogd daemon running, taking up 100% of my CPU….This resulted in the "Preparing..." mode running forever.” [http://discussions.apple.com/thread.jspa?threadID=1755600&tstart=15]
    You may be able use Activity Monitor to “kill” the offending process. Or you may be able to resolve it simply by rebooting your Mac. Then try backing up again.
    *Verify/Repair Mac Hard Disk & Permissions*
    It may be that your Macs’ internal hard disk has so many file/directory issues that Time Machine simply has trouble making sense of it. Some users have had success using Disk Utility on their Macs’ hard drive.
    Launch Disk Utility and click “Repair Disk Permissions”.
    Once complete, attempt a backup.
    If Time Machine appears to hang at “Preparing…” again, then do the following:
    Insert your Macs’ original install DVD and reboot holding down the “C” key.
    At the Welcome screen go up to the “Utilities” menu and select Disk Utility.
    Select your Macs’ hard disk on the left and click “Verify Disk” on the right.
    If problems are found click “Repair Disk”.
    Reboot to your normal desktop and try backing up again.
    *For Time Capsule Users* #
    If, though, none of the options above have helped and it has been 12 hours or more of “Preparing…”, then the Time Capsule may need to be restarted.
    Stop the backup from the Time Machine menu. (Give if a few minutes while it says “Stopping backup…”)
    When the Time Machine icon stops spinning, unplug the TC from the wall outlet.
    Wait 10-15 seconds.
    Re-plug it in again.
    After it has restarted (30-60 seconds), attempt another backup.
    Time Machine will report “Preparing…” again, but it shouldn’t be lasting more than a couple of hours.
    Let us know if any of the above was helpful in resolving your issue.
    Cheers!

  • Time Machine stuck in "preparing" endlessly.

    I have been able to successfully back up my MacBook Pro twice in the past two months using Time Machine, but both times I had to monkey with it, and I'm not even sure what exactly I did to make it work.
    Today I've tried several times to back up my machine, but it seems to get stuck "preparing" for hours.
    I don't keep Time Machine plugged into my laptop because I need that USB for my printer. Rather, I periodically plug my Sea Gate FreeAgent external drive in and attempt to manually back up. But it never just works without a lot of clicking around.
    What am I doing wrong??? How can I get it to work??
    Thanks so much!

    xtine,
    Your situation is explained in the first section of the info below:
    *_Time Machine May Report "Preparing..." For a Long Time_*
    Consider these factors regarding an extended period of "Preparing...". Consider each topic separately and do not attempt to act on all of them at once.
    *Recent Crash or Other Major System Event* (Deep Traversal)
    The reasons for this process are described in an article by George Schreyer. “During the preparation step it checks the FSEvents log for consistency. If it determines that something isn't quite right it has to rescan the whole disk. This can take quite awhile. A full rescan is always triggered by a crash, an unplanned shut down event or by booting from some other bootable disk between backups…. After a crash, Time Machine must scan the whole disk to determine what it has to do because it cannot trust the information that it left behind. Connected via an Ethernet connection, this phase would typically take 20 minutes on an older PowerBook. Being connected wirelessly stretches this phase out to over 3 hours.” [http://www.girr.org/mac_stuff/backups.html]
    According to the following KB article it can sometimes take a very long time if Time Machine begins this “deep traversal” and has to compare data inventories. This may apply to your situation, particularly if many Gigs of data are involved. (http://support.apple.com/kb/TS1516) Additionally, if Time Machine has not been able to perform its’ hourly backups for 24 hours or more, then it will perform a “deep traversal” once backups are renewed. This is the case for users who only backup once a week or so.
    *Anti-Virus Software*
    Running anti-virus software can interfere with the backup process. Either disable it altogether, or try the suggestion outlined here, “If you use third-party anti-virus scanning software and have issues, make sure your Time Machine back up folder (Backups.backupdb on the Time Machine disk) is excluded from virus scanning.” (http://support.apple.com/kb/TS1516)
    *Software Updates* #
    Installing new software, upgrading existing software, or updating Mac OS X system software can create major changes in the structure of your Macs directories. Time Machine will backup every file that has changed since the installation.
    If you take a look at the Console logs Time Machine may be reporting that your backups need "deep traversal". That's fine. Time Machine knows what is wrong and how to fix it. If you have a great deal of data, it may take quite awhile.
    After an OS update (like 10.5.5) Time Machine realizes the system no longer matches what it looked like during the previous backup. So it has determined that it's earlier catalogue of what-should-be-where is 'untrustable'. So it is going to go item-by-item comparing the before and after of your system. If you have just performed an OS Update then Time Machine knows what it's doing - let it do it!
    *Spotlight Keeps Indexing Backup Drive* #
    It may be that Time Machine can’t proceed or complete a backup due to a Spotlight indexing error. During this period, take a look at the Spotlight icon in the upper right corner of your screen. Is there a tiny dot pulsating in the center of the spyglass? Click on the icon. Is there a progress bar displayed? Generally, Spotlight indexing is a good thing. If it has only been a couple of hours then let the process contiune.
    However, at times it may hang and never progress after many hours, preventing further backups from taking place.
    Go to System Prefs --> Spotlight --> Privacy Tab.
    Drag your Time Machine disk into the window. It should now be among the items to exclude from indexing.
    Now quit System Prefs.
    Reboot your Mac.
    Reopen System Prefs and remove ("-") the Time Machine disk from the window.
    Now initiate a backup.
    This should clear out Spotlights cache. Naturally, Spotlight should begin indexing again (maybe even for a few hours depending on how much data there is), but it should eventually stop.
    *Reboot Time Capsule* #
    If, though, none of the options above have helped and it has been 12 hours or more of “Preparing…”, then the Time Capsule may need to be restarted.
    Stop the backup from the Time Machine menu. (Give if a few minutes while it says “Stopping backup…”)
    When the Time Machine icon stops spinning, unplug the TC from the wall outlet.
    Wait 10-15 seconds.
    Re-plug it in again.
    After it has restarted (30-60 seconds), attempt another backup.
    Time Machine will report “Preparing…” again, but it shouldn’t be lasting more than a couple of hours.
    Let us know if any of the suggestions above helped in your case.
    Cheers!

  • Time Machine encryption - after restart, drive won't mount

    Hi all.
    I enabled Time Machine on my Drobo drive, enabling encryption. All was good, Time Machine started encrypting away.
    I restarted my Mac, and now my Drobo won't mount.
    In Disk Utility, it looks like this:
    I'm unable to verify, repair or mount the disk.
    I wasn't prompted for the Time Machine encryption key, I assume that this is stored in my Keychain and unlocked on the fly?
    But regardless - I'm unsure of what to do next! I've got quite a bit of data on the drobo, and didn't expect it to render the drive completley useless. I'll be gutted if I lose my files on my Drobo besides the Time Machine backup I had.
    Any help, suggestions, advice would be much appreciated.
    Update: Output from Disk Utility when trying to verify the drive:
    Verifying partition map for “Drobo”
    Checking prerequisites
    Checking the partition list
    Checking for an EFI system partition
    Checking the EFI system partition’s size
    Checking the EFI system partition’s file system
    Checking all HFS data partition loader spaces
    Checking Core Storage Physical Volume partitions
    Checking storage system
    Checking volume.
    disk1s2: Scan for Volume Headers
    Invalid Volume Header @ 8795614850560: unsupported format
    disk1s2: Scan for Disk Labels
    Invalid Disk Label @ 8795598069760: cksum mismatch
    Invalid Disk Label @ 8795602264064: cksum mismatch
    Invalid Disk Label @ 8795606458368: cksum mismatch
    Invalid Disk Label @ 8795610652672: cksum mismatch
    /dev/disk1s2 is not a CoreStorage volume
    Problems were found with the partition map which might prevent booting
    Error: Storage system verify or repair failed.

    Here is the output of `diskutil coreStorage list`:
    >: diskutil coreStorage list
    CoreStorage logical volume groups (1 found)
    |
    +-- Logical Volume Group 493EC175-1234-465E-B6F5-324615AD2B94
        =========================================================
        Name:         -none-
        Sequence:     0
        Free Space:   0 B (0 B)
        |
        +-< Physical Volume 92E1ADAF-4567-40C6-BA94-4DB39023E3F3
            Index:    0
            Disk:     disk1s2
            Status:   Failed
            Size:     -none-
    Not looking good? But I badly need to recover the data on this drive. How can I ever trust Time Machine to backup my files in the future if it corrupts things like this?

  • Time Machine says "The Backup Disk is Not Available"

    Line 0:  I have a 400 GB external Western Digital drive that I leave plugged into an Airport Extreme.  Previously, this worked mostly without a problem.  It took some massaging to get it to work at first (I had to create the backup with the drive directly connected to the computer, and then I moved the drive over to the Airport Extreme and it was fine after that), but after that, it worked forever.  This was in the previous version of the OS that I was running (snow leopard?).  I very recently upgraded to Lion and it seemed to be OK, but then suddenly it gave me an error that said it had not been able to do a backup for 10 days.  I thought "wow, that means it hasn't backed up since I upgraded to Lion." 
    So I told it to do a backup right away.  It failed with the error "The backup disk is not available."
    I unplugged the drive and plugged it back in.  No go.
    I tried to reselect the drive from within Time Machine preferences.  It would not appear and in fact it kept forcing me to go to the Airport Extreme software.  I did this and there was no obvious way to set anything up from within that software.  I left everything as it was ("Enable file sharing" checked, "Secure shared disks" was at "with device password," and it was remembering the password in my keychain). 
    Go back to Time Machine preferences and the disk still doesn't show up.  Force a reboot on the router, it still doesn't show up.
    I brought the drive over to the computer and plugged it in directly, and everything was fine.  It did a backup on the spot, it read the backup that was there, the drive showed up, etc.  I formatted it just for the heck of it and started over completely and it was happy.  I did a disk check and everything was fine.  After leaving it on all night to complete a new backup, I unmounted the disk, brought it over to the Airport Extreme, plugged it back in, and now we go back to line 0 and rinse repeat.
    Can someone please tell me how to get my drive to start working with Time Machine again?

    It should not have worked in the first place.. when you moved it from the PC to the airport extreme.. that is not correct.. I don't know how SL managed to work around it.. but Lion obviously cannot.
    You will need to start all over again..
    Also note.. the flakey nature of this setup.. according to well respected people here AEBS with USB drive does not give reliable TM backups.. I would pay close attention to what they are saying. Time Capsule is more than a AEBS with a hard drive inside.. although exactly the difference I don't know.
    But you can expect the current setup to not work, because it never should have.

  • Time machines encryption seen as 2 hard drives?

    Hello,
    i've two different hard drive where i do the time machine backup with encryption. I let time machine handle
    the entire disk and the encryption process. But everytime i unmount the drive, osx tell me that it is unmounting
    two partition and ask me to confirm it. Sometimes this doesn't work and i've to wait for minutes before unplugging
    the usb cable and it sais to me that the drive was unsecurely removed. The fact is that in both disk i just
    see one partition only, there is no trace of any other partition even from disk utility.
    This happens on both drives and a third drive did the same too. Any other with this boring problem?
    Thanks!

    I've found out that the problem occurs only after i do a backup. If i connect one of the drive but i unmount it before time machine start to backup, the problem doesn't occur. I've tried to do a timemachine backup while in safe mode but seems it never start, now i will try again. This is the result of the command via terminal on another disk, before and after the backup. Seems something is different at the beginning:
    BEFORE:
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *500.1 GB   disk0
       1:                        EFI                         209.7 MB   disk0s1
       2:                  Apple_HFS Macintosh HD            499.2 GB   disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *500.1 GB   disk1
       1:                        EFI                         209.7 MB   disk1s1
       2:          Apple_CoreStorage                         499.7 GB   disk1s2
       3:                 Apple_Boot Boot OS X               134.2 MB   disk1s3
    /dev/disk2
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:     Apple_partition_scheme                        *17.3 MB    disk2
       1:        Apple_partition_map                         32.3 KB    disk2s1
       2:                  Apple_HFS Flash Player            17.3 MB    disk2s2
    /dev/disk3
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                 Apple_HFSX MyPassport TM          *499.4 GB   disk3
    CoreStorage logical volume groups (1 found)
    |
    +-- Logical Volume Group 5BDE6D8D-43A4-4761-AE49-68EBBD712BD6
        =========================================================
        Name:         Backup
        Size:         499730309120 B (499.7 GB)
        Free Space:   0 B (0 B)
        |
        +-< Physical Volume 25D95AEC-E36A-416E-AE62-EFB7ED4D263A
        |   ----------------------------------------------------
        |   Index:    0
        |   Disk:     disk1s2
        |   Status:   Online
        |   Size:     499730309120 B (499.7 GB)
        |
        +-> Logical Volume Family 244B3518-FE91-4F56-91B8-BB02C58C6C0A
            Encryption Status:       Unlocked
            Encryption Type:         AES-XTS
            Conversion Status:       Complete
            Conversion Direction:    -none-
            Has Encrypted Extents:   Yes
            Fully Secure:            Yes
            Passphrase Required:     Yes
            |
            +-> Logical Volume 6B226218-53A0-4FEF-B5AE-F7EE6A9AFD43
                Disk:               disk3
                Status:             Online
                Size (Total):       499411537920 B (499.4 GB)
                Size (Converted):   -none-
                Revertible:         Yes (unlock and decryption required)
                LV Name:            MyPassport TM
                Volume Name:        MyPassport TM
                Content Hint:       Apple_HFSX
    AFTER:
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *500.1 GB   disk0
       1:                        EFI                         209.7 MB   disk0s1
       2:                  Apple_HFS Macintosh HD            499.2 GB   disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *500.1 GB   disk1
       1:                        EFI                         209.7 MB   disk1s1
       2:          Apple_CoreStorage                         499.7 GB   disk1s2
       3:                 Apple_Boot Boot OS X               134.2 MB   disk1s3
    /dev/disk2
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:                 Apple_HFSX MyPassport TM          *499.4 GB   disk2
    CoreStorage logical volume groups (1 found)
    |
    +-- Logical Volume Group 5BDE6D8D-43A4-4761-AE49-68EBBD712BD6
        =========================================================
        Name:         Backup
        Size:         499730309120 B (499.7 GB)
        Free Space:   0 B (0 B)
        |
        +-< Physical Volume 25D95AEC-E36A-416E-AE62-EFB7ED4D263A
        |   ----------------------------------------------------
        |   Index:    0
        |   Disk:     disk1s2
        |   Status:   Online
        |   Size:     499730309120 B (499.7 GB)
        |
        +-> Logical Volume Family 244B3518-FE91-4F56-91B8-BB02C58C6C0A
            Encryption Status:       Unlocked
            Encryption Type:         AES-XTS
            Conversion Status:       Complete
            Conversion Direction:    -none-
            Has Encrypted Extents:   Yes
            Fully Secure:            Yes
            Passphrase Required:     Yes
            |
            +-> Logical Volume 6B226218-53A0-4FEF-B5AE-F7EE6A9AFD43
                Disk:               disk2
                Status:             Online
                Size (Total):       499411537920 B (499.4 GB)
                Size (Converted):   -none-
                Revertible:         Yes (unlock and decryption required)
                LV Name:            MyPassport TM
                Volume Name:        MyPassport TM
                Content Hint:       Apple_HFSX

  • Time machine error: The backup disk image could not be mounted

    Time Machine worked OK for several months. Now I get this error every 10 minutes or so.
    I unplugged Time Machine capsule and "Change Disk" in Time Machine options.
    Nothing helps, I continue to get this error.
    I cannot Enter Time Machine either. "Connecting to Server, Connecting to backup" does not work.
    Help please because I will probably have to archive and reinstall Leopard. I need the backups,
    Christine

    Christ1ne,
    Before you reformat the disk, consider these causes of this error.
    *_"The Backup Disk Image Could Not Be Mounted" (Console - “Failed to mount disk image”)_*
    First, it is important to distinguish this error message from another, similar Time Machine error that states “The backup volume could not be mounted”. This is important as the causes and cures for these two errors can be very different.
    Consider each topic below separately. When one option does not resolve your issue, then move on the next one.
    *Unmount the Backup Disk Image* (TC)
    If, for some reason, you have manually mounted the Time Machine backup disk image (sparsebundle), or Time Machine failed to eject it after the previous backup, subsequent backups may fail. (Console - “Failed to mount disk image”… “Backup failed with error: 21”)
    Eject the backup disk image (white drive icon) by either clicking the little Eject icon to the right of the disk image in the Finders’ Sidebar, or Ctrl-Click the drive icon on the desktop and select “Eject” from the contextual menu. Now try backing up again or launching Time Machine to view previous backups.
    *“Disconnect All Users…”:*
    If your Time Machine backup drive (“Backup of Users Computer”) is mounted on your desktop or in the Sidebar of the Finder window. then Time Machine may think the drive is already in use. Alternatively, if the Time Capsule hard disk has been recently accessed by a Windows machine, it may not have fully relinquished control. Do the following:
    Open Airport Utility and select the Time Capsule on the left.
    Click “Manual Setup”.
    Select “Disks” at top of window.
    Click “Disconnect All Users…” at bottom of window.
    Close the Airport Utility.
    Now try Backing up again.
    One poster reported: “I got it resolved. Apparently it had to do with one of the files being open on the disk from the drive. I had browsed the disk with one of my windows boxes here and it must have left one of the folders "open". Anyway, I rebooted the TC and we are good to go now.”
    *Proper Computer Name* #
    Make sure your computer has a proper name. Go to System Preferences --> Sharing. Time Machine needs to differentiate your computer from others on your network (i.e. "Bills MacBook" or "Office iMac"). If the "Computer Name" field is blank, create a name. Realize that if this step is necessary, you will likely have to start the Time Machine backup process over again and do another full initial backup.
    According to this article, [http://support.apple.com/kb/TS1760], Time Machine may experience problems if your computer name includes certain characters. Make sure the computer name only includes ASCII characters from the following set.
    (0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ)
    Once a change in the computer name occurs, you should stop and restart Sharing on the affected computer. Uncheck and then recheck Sharing in the Services list on the left.
    # Try removing the apostrophe from the disk images name (sparsebundle).
    *A Stalled .inProgress Files:* #
    It may be that the previous backup attempt was ungracefully interrupted leaving remains that Time Machine can’t deal with.
    Stop any current backup attempt. Choose “Stop Backing Up” from the Time Machine menu.
    Open the Time Machine Preferences and turn “OFF” Time Machine.
    Open your Time Machine drive.
    Open the folder labeled “Backups,backupdb”.
    Now open the folder containing backups of the computer in question.
    Are there any “.inProgress” files there. Delete them by dragging the file to the Trash. Or Ctrl-Click the file and select "Move to Trash" from the contextual menu. (Give this time as deleting a large file on an external disk can take a while.)
    Turn Time Machine back “ON”. Now try backing up again.
    NOTE: If the above procedure becomes impossible to perform, try accessing the disk image from another Mac. Some have discovered that attempting a repair from another computer succeeds where the original computer failed.
    Let us know if any of the suggestions above helped to resolve your issue.
    Cheers!

  • Can Time Machine write to a Disk Image on a Time Capsule?

    I just inherited a Gen 1 Time Machine (500gb).  I have three Macs on my network.  In my current set up I have an external 500gb drive split into three equal partitions, one for each Mac. 
    I know I cannot partition the TC HD, but I also know I can create one or more Disk Images.
    Question:  Can Time Machine write to a Disk Image on a Time Capsule?
    Thanks.
    MotionMan

    I know the backups will not mix.
    One of the Macs is a MacBook that only hooks up to the network every couple weeks.  Before I partitioned my existing TM backup disk, the TM backups of the other two Macs were filling the disk.  When the MacBook then tried to make a backup, the oldest backups of the MacBook would drop off.
    So, the other two Macs had backps for months, but the MacBook ended up with much less.  That is what lead me to the 3 partitions, so each Mac had an equal space for their backups.
    Odd that there there is no good solution for this.
    MotionMan

  • I have just upgraded to Mavericks and have been using Time Machine on an external disk with Snow Leopard.  Can I continue to backup with Time Machine on the same external disk or do I need a new disk since the operating system has changed?

    I have just upgraded to Mavericks and have been using Time Machine on an external disk with Snow Leopard.  Can I continue to backup with Time Machine on the same external disk or do I need a new disk since the operating system has changed?

    Hi there,
    I found that Time Machine in Mavericks will sort it all out for you. You shouldn't need to buy another backup drive, unless you have insufficient space left and can't afford to delete whats on there. It should just work fine.

  • HT3275 Time Machine Error: The backup disk image "Volumes/Data/My Macbook Pro.sparsebundle" is already in use. (How do I correct this issue?)

    Time Machine did not back up:
    Time Machine Error; ("The backup disk image "/Volumes/Data/My MacBook Pro.sparsebundle" is already in use.")
    How do I correct this issue?
    Thanks!

    You need to be careful Bob.. people might take this literally.
    Bob Timmons wrote:
    How do I correct this issue?
    Call the exterminator to get rid of the bugs in Lion and Mountain Lion.
    https://discussions.apple.com/thread/5222487?tstart=0

  • How do I remove Time Machine from an external disk

    After trying it once, I decided that I do not want to use Time Machine. I only want to backup user directories, and use the disk to hold other things. Problem is that I can't reformat the disk and remove the Time Machine stuff. Right clicking only gives me limited options. Is there any way to remove the Time Machine stuff from this disk?

    TM data is just that, data.
    First, be sure you disconnect the TM engine from the drive in the TM preferences by turning the switch to Off.
    There is no right-clicking involved.
    Run the disk utility, select the drive and erase/format/partition or whatever. Nothing to it.

  • My MacBook pro won't recognize hard drive I put in it. It boots only to a white screen unless I boot to my recovery USB. If I do that then I can select my USB and my external time machine drive in the disk utility, so no problems there. But what do you

    My MacBook pro won't recognize hard drive I put in it. It boots only to a white screen unless I boot to my recovery USB. If I do that then I can select my USB and my external time machine drive in the disk utility, so no problems there. But what do you think it is? It won't recognize any hard drive I put in the machine, so might it be the sata cable?

    Boot the Recvoery USB, use Disk Utility to select the internal drive makers namea and size on the left.
    Now select erase and select the midde option and click erase, it will take a bit to complete but it's best for the drive.
    Now select Partiton tab, click the big box and Options: GUID and then Format: OS X Extended journaled and click apply.
    Quit and you should be able to install OS X now with your Apple ID and password.
    see
    http://osxdaily.com/2011/08/08/lion-recovery-disk-assistant-tool-makes-external- lion-boot-recovery-drives/

  • I keep getting this error when trying to backup time capsule with time machine. The backup disk image "/Volumes/Data-1/Dan's iMac.sparsebundle" is already in use.

    I keep getting this error when trying to backup time capsule with time machine. The backup disk image “/Volumes/Data-1/Dan’s iMac.sparsebundle” is already in use.

    Make sure that no other Macs are backing up at the time.
    Pull the power cable from the back of the Time Capsule
    Count to ten
    Plug the power cable back into the back of the Tme Capsule
    Wait a few minutes, then try a backup again.

Maybe you are looking for

  • LabVIEW Applicatio​n Builder Download?

    Were can i download the Application Builder? Best regards Torsten Lochner

  • Drag and drop - like the builder?

    Hi team, It's nice to have drag-and-drop repositioning in the builder. It would be even nicer to be able to offer it to my users. Is there any sort of guidance available on how to replicate the functionality of P5150 of the builder? Thanks jd

  • Itouch cannot be restored message

    when attempting to update software on itouch on my PC when itunes crashed.  Then it told me that i need to restore the itouch to factory settings.  I attempted to do that and it made it all the way to the end of the restore and then said it cannot be

  • Big reports!!

    Hi all, I want to publish one report that generates lots of rows (it has about 15 columns). And I also want it to be exported to Excel. The problem is when the report has a lot of rows, it doesn't work: - Is there any configuration file to limit the

  • I am haven problem sending pics within text messages?

    I know there has to be a quick fix