Partition and rename existing Time machine drive?

I use a 1 TB external hard drive for Time Machine backups and as extra storage for miscellaneous files - a total of 130 gigs is used (100 gigs of Time Machine backups plus 30 gigs other files).   I am using Mountain Lion 10.8.5. That external drive is named "Seagate Drive"... I want to partition that drive in two 500 gig volumes and rename the first 500 gig to "Time Machine" for backups, and rename the other volume to "Extra Storage".
I understand that the existing backups should remain intact on the first volume after I partition the drive, but when I rename that first volume to "Time Machine" will the Time Machine app continue backing up to it or will Time Machine become confused because of the name change and no longer auto backup to the drive, thus requiring me to re-start a completely new full backup?  ...Also after I rename the Time Machine drive volume will the Time Machine app still recognize the older backups that were recorded when the external drive had its older name?
...will any of this cause me trouble?
Thanks
I don't want to create any headaches for myself.
Thanks!

You can always inherit the backup if you have problems.
Inherit a Backup
Inherit a Backup (2)

Similar Messages

  • 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/

  • Ejecting an encrypted Time Machine drive always prompts "Eject All"

    Whenever I eject my encrypted Time Machine drive, Finder reports that the drive has more than one partition and asks if I want to eject just the Time Machine partition or all. So I have to hit "Eject All" in this dialog every time I want to disconnect my MacBook from my Time Machine drive.
    Thing is, there is only one partition. I've even gone so far as reformatting the drive to one partition and restarting my Time Machine backups fresh twice, but I still get the Eject All prompt every time.
    Anybody else have this issue and/or know of a solution?

    I wouldn't use RAID for TM, but...
    http://pondini.org/TM/2.html
    https://discussions.apple.com/thread/4062015?start=0&tstart=0

  • Can I back up macbook to external time machine drive attached to my Samba?

    I'm already backing up my macbook with a WD MAc Formatted drive. I want to connect it to a NAS (Samba Server).
    I know that time machine will not work with NAS. Will my existing time machine drive work if I connect it wirelessly to a Samba based NAS device?

    yes. mount the drive remotely on the macbook and choose it as the designated TM drive in TM system preferences.

  • Lost the ability to Spotlight Index my Time Machine drive

    I have an external, Firewire Time Machine drive which has been working without problems up to now. This evening I had a backup which hung up in the "preparing" stage (no file transfers begun yet). When I went to look in the console, there was a device error apparently related to trying to detect the powered-on state of my Time Machine drive. Apparently Time Machine did not handle this gracefully. In the course of trying to clear that I got into a state where I had to force shutdown of the system (holding the power button). (I accidentally clicked on the Time Machine icon which got hung up trying to display the histories, and left me with no access to the Desktop....)
    Things appeared to check out fine when I brought the machine back up (including Verify Disk of both the main and Time Machine drives and Repair Permissions of the main drive), and I finally did a Back Up Now in Time Machine. Due to the forced shut down, this became a "Deep Traversal" "preparing"stage. We'll I've seen those before, so no worries. However it lasted quite a bit longer than it should, at which point I noticed that Spotlight was indexing the Time Machine drive.
    So at this point I dragged the Time Machine into the Spotlight Privacy list. Rather than going away completely as I expected, the indexing of the Time Machine drive apparently went into some sort of clean-up phase that said it was still indexing for another 5 minutes (where it had, just prior, said it was going to be indexing for another 2 hours). The progress bar advanced normally as if it really did do 5 minutes more of indexing of the Time Machine drive. I've not seen this before
    When that finished, the backup which had been "preparing" during all of this also finished "preparing", transferred the several MB of files I expected, and finished normally. There were no errors in the console related to any of this.
    I rebooted, and once again did a pair of Disk Verifies and a Repair Permissions without problems. Opened up the console to track things, and poked around in the Time Machine. All was normal as far as I can tell. I also explored the Time Machine drive via the Finder. No problems.
    So I now went into Spotlight Privacy and removed the Time Machine drive from the privacy list expecting it to do the re-indexing I had stopped above. Spotlight started indexing the drive and a couple seconds later it stopped. I tried again -- into and out of privacy -- same result, a couple seconds of indexing and then it stopped.
    At this point I noticed the console was saying I had some bus errors in the I/O system, and that's what was terminating the md worker process and stopping the indexing.
    So I shut down, unplugged the Time Machine drive, and went through my maintenance ritual.
    I reset the PMU (this is a powerbook), reset PRAM, booted once in Safe Mode, booted normally, and ran Disk Utility again to Verify and Repair Permissions on the main hard drive. All of that went without a hitch. No failures, faults or funnies.
    I ran through the list of Applications I use, keeping an eye on the console. Again no problems.
    So I shut down, plugged the Time Machine drive back in and booted back up. I put the drive into Spotlight Privacy and turned off Time Machine backups. I then did a Verify Disk on that drive. No problems. I went into the Time Machine history display. No problems. And no problems looking at it in the Finder either. In particular, no bus errors or anything else funny in the console.
    I rebooted and did a new Back Up Now. It completed without problems. It was another Deep Traversal backup due to the Safe Mode Boot, but it went without a hitch. I rebooted and did another Back Up Now and got a normal speed incremental backup again without a hitch. The bottom line is that as far as I can see that Time Machine drive is working just fine.
    So I went into Spotlight Privacy and removed it from the list. Once again it started to index and stopped in a couple seconds. But this time there were NO Console error messages.
    I moved my main hard drive into Spotlight Privacy and removed it and it re-indexed from scratch just fine. Tried again with the Time Machine drive -- indexing stopped in a couple of seconds with no message in the Console. Spotlight searches find all the right stuff in the main drive. Spotlight and finder searches find only the top level Time Machine folders in the Time Machine drive.
    I also tried removing the Spotlight plist from my account's Library / Preferences. Spotlight created a new plist as expected but it still won't index that darned Time Machine drive.
    Apparently there is something left over from when I originally aborted the Spotlight indexing of that drive which is causing Spotlight to think it has no work to do. I'm not seeing any I/O errors of any sort any more (I think my maintenance pass took care of that) and Time Machine backups and history access continue to work just fine. And again, the Time Machine disk Verifies just fine.
    So I've run out of things to try.
    Is there a hidden file that I need to remove from that drive so that Spotlight no longer thinks it already has it indexed?
    --Bob

    Well unfortunately the command
    sudo mdutil -E /Volumes/MyDiskName
    didn't help.
    The command itself echoed the name of the volume and then said "Indexing Enabled", which looked good. But the Spotlight indexing stopped after a couple seconds. The Console reported the Terminal sudo command and nothing else.
    I tried moving the Time Machine drive in and out of Spotlight privacy and once again the indexing started and stopped a couple seconds later with no Console messages.
    I then tried another trick I've learned to make Spotlight indexing happen which is to do a Finder search for, say, all folders (limited to the one drive) via Command-f and while Including both System Files and files both Visible and Invisible. And indeed Spotlight indexing started but again stopped a few seconds later.
    However, this time there were console messages and a crash report.
    The Console shows (with personal information x'ed out):
    12/31/07 1:30:38 PM mds[28] (/)(Error) IndexCI in openindex_filelazy:open file error: 2, 0.indexGroups
    12/31/07 1:30:41 PM ReportCrash[146] Formulating crash report for process mds[28]
    12/31/07 1:30:42 PM com.apple.launchd[1] (com.apple.metadata.mds[28]) Exited abnormally: Bus error
    12/31/07 1:30:42 PM com.apple.launchd[1] (0x10ba40.mdworker[96]) Exited: Terminated
    12/31/07 1:30:42 PM com.apple.launchd[1] (0x1004a0.mdworker[108]) Exited: Terminated
    12/31/07 1:30:42 PM mds[147] (/Volumes/Xxxxxx Time Machine/.Spotlight-V100/Store-V1/Stores/80F3EC85-D77A-49FE-8BDC-BB7C3B3EC1CF)(E rror) IndexCI in ContentIndexOpenBulk:Unclean shutdown of /Volumes/Xxxxxx Time Machine/.Spotlight-V100/Store-V1/Stores/80F3EC85-D77A-49FE-8BDC-BB7C3B3EC1CF/0. ; needs recovery
    12/31/07 1:30:43 PM ReportCrash[146] Saved crashreport to /Library/Logs/CrashReporter/mds2007-12-31-133038Xxxxxx-Xxxxxx-Computer.crash using uid: 0 gid: 0, euid: 0 egid: 0
    The Crash Report reads as follows (again with personal information x'ed out):
    Process: mds [28]
    Path: /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Support/mds
    Identifier: mds
    Version: ??? (???)
    Code Type: PPC (Native)
    Parent Process: launchd [1]
    Date/Time: 2007-12-31 13:30:38.746 -0500
    OS Version: Mac OS X 10.5.1 (9B18)
    Report Version: 6
    Exception Type: EXCBADACCESS (SIGBUS)
    Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000030
    Crashed Thread: 15
    Thread 0:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0000cfa0 0x1000 + 49056
    5 mds 0x00005580 0x1000 + 17792
    Thread 1:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0005987c 0x1000 + 362620
    5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
    6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 2:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0005987c 0x1000 + 362620
    5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
    6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 3:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0005987c 0x1000 + 362620
    5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
    6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 4:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0005987c 0x1000 + 362620
    5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
    6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 5:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0005987c 0x1000 + 362620
    5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
    6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 6:
    0 libSystem.B.dylib 0x92eda3ec _semwaitsignal + 12
    1 libSystem.B.dylib 0x92f16fa0 pthread_condwait + 1580
    2 mds 0x00009648 0x1000 + 34376
    3 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 7:
    0 libSystem.B.dylib 0x92ee0ea0 read$UNIX2003 + 12
    1 mds 0x000091b4 0x1000 + 33204
    Thread 8:
    0 libSystem.B.dylib 0x92f15438 kevent + 12
    1 mds 0x0007e584 0x1000 + 513412
    Thread 9:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0005987c 0x1000 + 362620
    5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
    6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 10:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0005987c 0x1000 + 362620
    5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
    6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 11:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0005987c 0x1000 + 362620
    5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
    6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 12:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0005987c 0x1000 + 362620
    5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
    6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 13:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.spotlight.index 0x00207f0c _handleExceptions + 208
    3 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 14:
    0 libSystem.B.dylib 0x92ed39d8 machmsgtrap + 8
    1 libSystem.B.dylib 0x92eda8fc mach_msg + 56
    2 com.apple.CoreFoundation 0x90214664 CFRunLoopRunSpecific + 1828
    3 mds 0x00059ab8 0x1000 + 363192
    4 mds 0x0005987c 0x1000 + 362620
    5 com.apple.Foundation 0x969c5d9c _NSThread__main_ + 1004
    6 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 15 Crashed:
    0 com.apple.spotlight.index 0x002046cc ContentIndexContainsContentByDocId + 204
    1 com.apple.spotlight.index 0x00164358 QueryFunctionCallbackContext::findContent(db_obj*, __CFString const*, char*, int) + 244
    2 com.apple.spotlight.index 0x001634d0 qpContentIndexMatch(datastoreinfo*, dblazyobj*, query_piece*, void*, int) + 328
    3 com.apple.spotlight.index 0x0015587c comparefile_againsttree + 828
    4 com.apple.spotlight.index 0x00155d30 comparefile_againsttree + 2032
    5 com.apple.spotlight.index 0x00155d5c comparefile_againsttree + 2076
    6 com.apple.spotlight.index 0x001e307c -[SISearchCtx isObjectInQuery:withQuery:shortcut:] + 144
    7 com.apple.spotlight.index 0x001fa268 -[SISearchCtx_FSWalk performSearch:] + 996
    8 com.apple.spotlight.index 0x001e2cbc -[SISearchCtx executeSearchContextCracked_2:jobNum:] + 136
    9 com.apple.spotlight.index 0x00177e80 siwork_queueprocess + 752
    10 com.apple.spotlight.index 0x0017811c sischeduleronce + 356
    11 com.apple.spotlight.index 0x0017816c sischeduleronce + 436
    12 com.apple.spotlight.index 0x001784f8 sischeduler_run_waitingtimeout + 640
    13 com.apple.spotlight.index 0x0016529c runLoop + 72
    14 com.apple.spotlight.index 0x00165308 query_runLoop + 32
    15 libSystem.B.dylib 0x92f15bf8 pthreadstart + 316
    Thread 15 crashed with PPC Thread State 32:
    srr0: 0x002046cc srr1: 0x0200f030 dar: 0x00000030 dsisr: 0x40000000
    r0: 0x002046a4 r1: 0xf09a4380 r2: 0x00000000 r3: 0x00000000
    r4: 0xf09a43c0 r5: 0x00000000 r6: 0x000074d1 r7: 0x00000000
    r8: 0x003fc080 r9: 0x00000000 r10: 0x00000000 r11: 0x44000444
    r12: 0x92ede094 r13: 0x00000000 r14: 0x00000000 r15: 0x00373410
    r16: 0x00000000 r17: 0x00239e98 r18: 0x00000001 r19: 0x00227b9c
    r20: 0x00000000 r21: 0x00245554 r22: 0x00000001 r23: 0x00000001
    r24: 0x00000000 r25: 0x00000005 r26: 0x00000000 r27: 0x00000000
    r28: 0x00000000 r29: 0x00000005 r30: 0xf09a43c0 r31: 0x00204610
    cr: 0x24000444 xer: 0x20000004 lr: 0x002046a4 ctr: 0x92ede094
    vrsave: 0x00000000
    Binary Images:
    0x1000 - 0xc1ffb mds ??? (???) <af9cc958b4b030835101ff024186c7d3> /System/Library/Frameworks/CoreServices.framework/Frameworks/Metadata.framework /Support/mds
    0xde000 - 0xe0ffd com.apple.MDSChannel 1.0 (1.0) /System/Library/PrivateFrameworks/MDSChannel.framework/Versions/A/MDSChannel
    0x139000 - 0x23fffb com.apple.spotlight.index 10.5.0 (398.1) <5843125c709dd85f22f9bd42744beea5> /System/Library/PrivateFrameworks/SpotlightIndex.framework/Versions/A/Spotlight Index
    0x1ca9000 - 0x1caaffc liblangid.dylib ??? (???) <5f078ac1f623f5ce432ea53fc29338c0> /usr/lib/liblangid.dylib
    0x2198000 - 0x22bdffb libmecab.1.0.0.dylib ??? (???) <cd875e74974e4ec3a0b13eeeb236fa53> /usr/lib/libmecab.1.0.0.dylib
    0x8fe00000 - 0x8fe309d3 dyld 95.3 (???) <a7be977c203ec5c76b2f25a7aef66554> /usr/lib/dyld
    0x90123000 - 0x9016effb com.apple.Metadata 10.5.0 (398) <b6bb1fd5a7a9135f546b2d8cbd65eafc> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
    0x901ab000 - 0x902d0ff3 com.apple.CoreFoundation 6.5 (476) <9073c2bfdf6842562c8b7f0308109c02> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x9060a000 - 0x90612fff libbsm.dylib ??? (???) <c1fca3cbe3b1c21e9b31bc89b920f34c> /usr/lib/libbsm.dylib
    0x90683000 - 0x90688ff6 libmathCommon.A.dylib ??? (???) /usr/lib/system/libmathCommon.A.dylib
    0x90757000 - 0x907d2fff com.apple.SearchKit 1.2.0 (1.2.0) <1b448fbae02460eae76ee1c6883f45d6> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
    0x9088a000 - 0x9090ffff libsqlite3.0.dylib ??? (???) <7b379cb4220346e99c32c427d4539496> /usr/lib/libsqlite3.0.dylib
    0x90aa7000 - 0x90ab5fff libz.1.dylib ??? (???) <1a70dd3594a8c5ad39d785af5da23237> /usr/lib/libz.1.dylib
    0x90b50000 - 0x90be2fff com.apple.framework.IOKit 1.5.1 (???) <591b8b0cc4261db98a6e72e38eef5f9a> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x91105000 - 0x9116cffb libstdc++.6.dylib ??? (???) <a4e9b10268b3ffac26d0296499b24e8e> /usr/lib/libstdc++.6.dylib
    0x9116d000 - 0x912b5ff3 libicucore.A.dylib ??? (???) <250daed2fb2e6bf114480e2e4da0728b> /usr/lib/libicucore.A.dylib
    0x91c3c000 - 0x91d32ffc libiconv.2.dylib ??? (???) <05ae1fcc97404173b2f9caef8f8be797> /usr/lib/libiconv.2.dylib
    0x91d3a000 - 0x91db4ffd com.apple.CFNetwork 220 (221) <00b882d3d3325526b78ded74880759fe> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
    0x9236a000 - 0x92382ffb com.apple.DictionaryServices 1.0.0 (1.0.0) <fe37191e732eeb66189185cd000a210b> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Diction aryServices.framework/Versions/A/DictionaryServices
    0x92383000 - 0x9238effb libgcc_s.1.dylib ??? (???) <ea47fd375407f162c76d14d64ba246cd> /usr/lib/libgcc_s.1.dylib
    0x92742000 - 0x92769fff libxslt.1.dylib ??? (???) <3700d04090629deddb436aa2d516c56d> /usr/lib/libxslt.1.dylib
    0x92777000 - 0x92860fff libxml2.2.dylib ??? (???) <6f383df1e1e775be0158ba947784ae13> /usr/lib/libxml2.2.dylib
    0x928aa000 - 0x928b9fff com.apple.DSObjCWrappers.Framework 1.2 (1.2) <2411674c821a8907449ac741ce6a40c3> /System/Library/PrivateFrameworks/DSObjCWrappers.framework/Versions/A/DSObjCWra ppers
    0x92a17000 - 0x92afafeb libobjc.A.dylib ??? (???) <4a90e315bd1718c3f5ae09ee6c23e36c> /usr/lib/libobjc.A.dylib
    0x92afb000 - 0x92bc9ff7 com.apple.CoreServices.OSServices 210.2 (210.2) <bad4943629f870d305f2bc7c6dfffe2d> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
    0x92bde000 - 0x92dbfffb com.apple.security 5.0.1 (32736) <15632bf9bbdb223194b3d79a2e48e02d> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x92e9a000 - 0x92ec5ff7 libauto.dylib ??? (???) <c1f2bd227817ad7c7bf29ec74729ac7c> /usr/lib/libauto.dylib
    0x92ed2000 - 0x9306bfe3 libSystem.B.dylib ??? (???) <8a6cd873dfa7ada786efac188f95ed1b> /usr/lib/libSystem.B.dylib
    0x931a7000 - 0x934a7ff3 com.apple.CoreServices.CarbonCore 783 (783) <fd2acaf23e95472f78b8a077fa039986> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
    0x946f2000 - 0x9472afff com.apple.SystemConfiguration 1.9.0 (1.9.0) <d925dde7699e6231c88a41b0254a7591> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
    0x94933000 - 0x9494eff3 com.apple.DirectoryService.Framework 3.5 (3.5) <3246a5d1c6a3d678798a90e8c5cd3677> /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
    0x9494f000 - 0x9494fffa com.apple.CoreServices 32 (32) <42b6dda539f7411606187335d9eae0c5> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x94c68000 - 0x94c9dfff com.apple.AE 402 (402) <a4b92c8ac89cc774b85fb44c48b9d882> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.fram ework/Versions/A/AE
    0x96831000 - 0x9683afff com.apple.DiskArbitration 2.2 (2.2) <9c8f8ade43fa25b32109ef9dcc0cb5d5> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x9683b000 - 0x968d1ff7 com.apple.LaunchServices 286 (286) <a3a0b2af862e9a8945072f8cb523678f> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchS ervices.framework/Versions/A/LaunchServices
    0x969bc000 - 0x96c00ffb com.apple.Foundation 6.5.1 (677.1) <4152239382fb0f48abbcbf35bd04afa6> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0xfffec000 - 0xfffeffff libobjc.A.dylib ??? (???) /usr/lib/libobjc.A.dylib
    0xffff8000 - 0xffff9703 libSystem.B.dylib ??? (???) /usr/lib/libSystem.B.dylib
    Apparently the mdutil command didn't actually delete the Spotlight index file which is causing the problem, or at least didn't leave the indexing files in a consistent, empty state to start indexing over again. I may have to Erase this Time Machine disk and start over.
    I should point out that except for Spotlight indexing this disk is otherwise working just fine. It passes Verify Disk with no errors and both new Time Machine backups and viewing and restoring via Time Machine and Finder work without problem.
    Any suggestions before I just Erase the disk and start over with a new backup?
    --Bob

  • Fix for owners of Desktops and Laptops for Time Machine Wirelessly

    Hey guys,
    I have a fix for you to use which works well for me. Thus far I have had zero problems with it, was even able to allow a full 50 GB backup over wireless (took forever, but its the principle of it) as well as incremental backups. It requires NO terminal or any other stuff, just clicking around in the interface. Here's the steps I went through:
    1.) Connect the Time Machine External Hard Drive to your desktop mac (any method, firewire preferred).
    2.) Connect and establish the time machine drive as a time machine backup drive on your desktop. Allow the desktop to sync and begin its backup to the drive.
    3.) Open your laptop
    4.) Open finder
    5.) Go to the "Shared" Section on the sidebar
    6.) Find your desktop mac, connect to it as a full user (not a guest)
    7.) Save the password, and make sure you have full access
    8.) Find the external Time Machine Drive on your desktop's "Shared" Menu (Should be the bottom folder, will have a "Web Globe" On it
    9.) Click the folder
    10.) An eject symbol should appear next to the Time Machine External Drive Folder on the desktop section (If you are in column view in Finder)
    11.) The drive should appear in your "Devices" Tab on the sidebar
    12.) Open Time Machine Preferences
    13.) Turn on Time Machine
    14.) Select your drive from the list (should just be one)
    15.) Allow the initial download to commence (upwards of 5 hours)
    After the initial backup, incremental backups aren't noticeable. In fact, clicking on the Time Machine icon in the dock will "search" for the backup drive even if you don't have it mounted from the beginning. Just make sure your desktop stays on when your laptop is on so that it can backup. I haven't noticed any lag in my internet either. Good luck, let me know if there are problems or if this works for you too.
    My specs:
    iMac G5 (iSight) 20" 10.5
    Macbook (White) 10.5
    External Hard Drive: Western Digital MyBook, 500GB Firewire 400/800/USB

    Edit: these are steps for making TM work with EHD attached to AEBS- not what I am saying we should do. BUT the step concerning "supported" drives might help alleviate unrecognized drives.
    Quoting this from Mac-Forums (which quoted from Apple forums I guess):
    "Another post:
    From user A@ron posted in MacRumors:
    TM working with airport disk in GM
    Well thank me later I got it working fellas. It was there in front of our faces with the exception of doing a chown and chmod.
    Someone else please confirm I will post steps.
    1) disconnect airport disk and plug into computer as a USB drive directly.
    2) Set up time machine to use this volume.
    3) In terminal cd to volume "cd /Volume/HDD"
    4) In terminal "touch .com.apple.timemachine.supported" this will create an invisible file.
    5) In terminal "sudo chown root:admin .com.apple.timemachine.supported"
    6) In terminal "sudo chmod 1775 .com.apple.timemachine.supported"
    7) In terminal "ls -l -a" the .com.apple.timemachine.supported file should be -rwxrwxr-t
    8) eject disk, unplug from mac, plug into Airport.
    9) mount at mac using connect to server in finder (command k) and afp://airportname.local./HDname
    10) see if time machine now sees the drive and tries to use it.
    Best, Fernando"
    Might work if you can't get TM to recoginize your drive. Could try the:
    " In terminal "ls -l -a" the .com.apple.timemachine.supported file should be -rwxrwxr-t"
    command. I dunno though. Patience is a virtue.
    Message was edited by: Varick

  • I am having sporadic issues after new hard drive install and recovery using Time Machine. The same sluggish response, start up screen pixelating...If I reinstall Lion will it wipe out other applications? My HD was formatted and partitioned correctly, I ha

    I am having sporadic issues after new hard drive install and recovery using Time Machine. The same sluggish response, start up screen pixelating...If I reinstall Lion will it wipe out other applications? My HD was formatted and partitioned correctly, I have a late 2009 iMac.

    Use the trackpad to scroll, thats what it was designed for. The scroll bars automatically disappear when not being used and will appear if you scroll up or down using the trackpad.
    This is a user-to-user forum and most people will post on here if they have problems. You very rarely get people posting to say there update went smooth. The fact is the vast majority of Mountain Lion users will not be experiencing any major problems with the OS, or maybe with apps which are not compatible, but thats hardly Apple's fault if developers don't update their apps.

  • Why does Macbook Pro rename my Time Machine and other external hard drives?

    Why does my Macbook Pro rename my Time Machine to "Time Machine I" and then back again periodically.  Last night it was one name, this morning it is another. It also does it on other external hard drives - usually by adding a I after the name. It is frustrating for me because I store a large runtime folder on an external hard drive and end up losing a lot of time with my computer not being able to find files because of the renaming.
    And even though it still looks like Time Machine under "Get info: - when I open a folder window or Disk Utility it has a new name, and there is no way to change it.  I've seen other questions that mention Macs renaming themselves, so it seems like a similar issue. I did try deleting the preferences plist file, but that did not work.
    Is this a glitch with this particular model or operating system?
    Specs: Macbook Pro A1297 - 2009 model.
    Snow Leopard 10.6.8
    2.8GHz Intel Core 2 Duo
    8GB ram
    Many thanks for any advice.

    nachdenki wrote:
    strange, my external HDs were added to the exception list automatically. maybe because they wouldn't fit on the time machine volume.
    It seems to depend on when the drives were connected. When you first turn Time Machine on, it only excludes the TM drive itself, and any drives not formatted HFS+.
    If you connect a drive later on, that drive will be excluded automatically.

  • How can i put music drive AND a time machine drive on wireless network?

    Right now I have a MacBook with ONE external drive with my music and movies… and ANOTHERexternal drive for my backups.
    I would LOVE to figure out how to hook both the music drive and the time machine drive to a wireless router so the only plug I have for my laptop is the power plug.
    I already have a NetGear wireless router… but it only has ethernet ports out, no usb.
    What would be the best/easiest way to network these two external hard drives?
    tx!

    Another option, where you can still utilize your existing drives, is to consider a dedicated NAS device that supports both Time Machine and iTunes functions. One such NAS device is the Synology DS415+. It would be far superior than what you have now. Albeit at an additional cost.

  • HT3275 EMERGENCY!!!!!!!!  NEED TO RETREIVE AN ACCIDENTALLY DELETED BACKUP! BACK UP FROM MY TIME MACHINE DRIVE????  In other words, I emptied out a folder on my main MAC to make space and the next subsequent backup backed up the EMPTY FOLDER and then delet

    EMERGENCY!!!!!!!!
    IS THERE ANY WAY TO RETREIVE AN ACCIDENTALLY DELETED BACK UP FROM MY TIME MACHINE DRIVE????
    In other words, I emptied out a folder on my main MAC to make space and the next subsequent backup backed up the EMPTY FOLDER and then deleted the "old backup" that actually contained the contents of the very important folder.
    Now only the emptied folder exists on my MAC and in the two backups on my Time machine backup drive.
    This was clearly a big mistake on my part not realizing that the "old backup" being deleted by Time Machine would include backed up files that I had no intention of getting rid of....
    What can I do now?
    Is DATA RETREIVAL even an option?
    I am sure that the Folder of files that I need are on the most recently deleted "OLD BACKUP" but how do I get to this, if even possible?????
    Super desperate situation here...
    M

    inna-help-me wrote:
    Is DATA RETREIVAL even an option?
    It may be possible to recover some of the data, if it hasn't been overwritten, but it won't be cheap or easy. 
    You've posted in the Time Capsule forum, but you mention a "backup drive."  If your backups are on a Time Capsule's internal HD, instead of an external HD, it's even worse.
    See Data Recovery.
    Good luck.

  • WD World Edition 1TB as a Time Machine drive with Mac and XP?

    I plan on buying a WD World Edition 1TB to use as my Time Machine drive over wireless netowrk at home for my 320GB MBP.
    My wife has a Windows XP PC so I would like to partition the 1TB into maybe 600MB for me and 400MB for her.
    First of all, will this type of partition work with TM and also, what format should the WD Drive be? I have installed MacFuse and NTFS-3G on my MBP.
    Any info from someone who does something simalr would be greatly appreciated.
    Dave

    That sounds fine.
    So in theory, the WD comes with no partitions so I could set the whole thing up on the XP machine and set the partition sizes, then go the Mac, connect to the partition I've set aside for myself and select it, at which point the Mac will format it to HFS and start backing up?
    You say the Mac is oblivious to partitions so what would stop it formatting the entire drive to HFS?
    Ideally I'd like to get the WD software to backup the XP machine to the XP partition and TM to backup the Mac to the HFS partition. Do you know if this is likely to work? Hopefuilly someone with this drive will be able to answer as well.
    Thanks for your help so far

  • How to keep using existing Time Machine backup after replacing main hard drive

    The hard drive in my iMac (Lion) is failing. I cloned it to a new drive and installed it in the iMac. Now the system wants to start fresh with a whole new Time Machine backup.
    It seems obvious that there must be a way to keep using the existing Time Machine backup set, but I can't figure out how to do it. Help, please.

    If you had done a full system restore from Time Machine, it would have been done automatically.  But 3rd-party cloning apps don't leave a "trail" so Time Machine can figure out that the new drive has all the old stuff on it.
    Effective with Lion, there is a way to "associate" the new drive with the backups of the old one, but it requires the use of Terminal.  See #B6 in Time Machine - Troubleshooting.  As noted though, this only works on directly-connected backup drives, not backups made over a network.

  • Can i use time capsule for external h drive and also for time machine?

    Can i use time capsule for external h drive and also for time machine?

    Hello, vascocaco.
    If I understand correctly, you're wondering if you can use your Time Capsule's internal hard disk both for Time Machine backups and as an ordinary drive. Is this your question?
    You can, but Time Machine backups may take longer.
    To do it, you should partition your Time Capsule's hard disk to create one volume for the backups and one for other files.

  • Can't see time machine drive and can't boot

    Last week the internal hd on my Mac mini (mid-2010) began failing. I took it in and AppleCare replaced the drive. The genius told me they loaded 10.7.3 and I should be able to use Time Machine (TM) to bring it all back. So I go home, plug in my TM drive and the Mac can't see the drive the TM is on. And yet I know it recognizes the drive because if I turned it off it would give me the nasty warning about disconnecting before unmounting. So not knowing what to do I went and popped in the installation disc that came with my Mac mini (10.6), and booted with the cd. I told it to restore from TM, and this time it sees my drive and transfers the data. When it restarts I get the gray screen with a null (not permitted) sign. So I can't make heads or tails of it an decide that maybe I have to make a clean install and then upgrade to 10.7.4 and then try time machine (I'm grasping at straws now). Only when I attempt to to restart after installing 10.6 it go from a gray screen to a blue screen (of death) and just sits. I'm baffled and don't know what to do. Could my time machine disk, which was backing up a failing internal HD, have been bad?  What do I do?

    Hello:
    If I were you (and I am not), I would bundle up the repaired computer and your Time Machine drive and take it in and ask the Apple person to bring it back to life.  IMHO, that should have been done the first time.
    Barry

  • I just installed a larger hard drive, and used my Time Machine Backup to transfer my info back to the new hard drive. When I open Iphoto, my thumnails are there, but they aren't linked back to the actual photos.I see the photos in my HD. What should I do

    I just installed a larger hard drive, and used my Time Machine Backup to transfer my files back to the new hard drive. When I open Iphoto, my thumbnails are there, but they aren't linked back to the actual photos. I see the original photo files in my HD. Is there a way to link the Iphoto thumbnails back to the original files?

    Use the Firewire cable and t boot the old Mac's hard drive to the new Mac's desktop and transfer your entire iPhoto folder.
    Use Disk Utiliy to erase'format HFS+ Journaled your TimeMachine drive and use the free Carbon Copy Cloner and clone your new boot drive to the external, it's hold option bootable.

Maybe you are looking for