Finder cannot see AirPort Time Machine drives

I'm running OS X 10.9.4 on a MacBook Air (2 GB memory, 64 GB SSD storage).
I'm using an AirPort Time Capsule (with Time Machine) as my router and backup. I have an additional hard drive connected to the USB port on my AirPort Time Capsule.
For over a year the entire configuration has worked well: Backups are done, and I can access both the AirPort Time Capsule internal hard drive and the external hard drive from my MacBook Air, and from any other device on the network.
For the past few weeks, Finder (on my MacBook Air) sometimes cannot see either drive (internal or external) on the AirPort Time Capsule. Backups are still okay, and PCs are still able to access and use both drives on the AirPort Time Capsule. Also, software on my MacBook Air CAN see and use the drives. For example, if I have a photo on one of those drives that I want to post on Facebook, the "finder" window that appears when I click "Upload Photos/Video" (on Facebook) sees the drives, and can upload the photo from the drives. The ONLY time I cannot see the drives is when I try to access them with Finder. (See photos.)
At first, Finder occasionally could not see the drives, or sometimes it took a minute or two to see the drives. Now, Finder generally cannot see the drives, no matter how long I wait. My PCs, and ALL SOFTWARE on the MacBook Air CAN ALWAYS see the drives. Also, Finder can ALWAYS see ALL THE OTHER shared drives on the network (on the PCs, for example), even when it cannot see the drives on the AirPort Time Capsule.
Can anyone tell me what is going on?
Using Finder:
Using Facebook:

With the shared folder open, select
View ▹ Show View Options
from the Finder menu bar. In the dialog that opens, select
Arrange by: None

Similar Messages

Migration Assistant doesn't see USB Time Machine drive

My dad recently got a new MacBook Pro and wants to restore from his Time Machine backup, stored on a USB drive. He didn't use the Setup Assistant at the start - I'm really not sure why, but anyway...
Now we're looking at Migration Assistant, and it can't find the Time Machine drive. On the 'Select your disk' screen, the wheel just spins and spins. The backup drive is plugged in and mounted. We've checked the drive for errors using Disk Util, and it's fine. Moreover, I tested this with my own MBP and it's backup drive and the same problem occurs.
He also tried booting from the install DVD and using the 'restore' option from the Utilities menu, without success.
Is this because he has started to set up the machine using a user (as admin) with the same account name as the Time Machine backups? This website suggested that maybe that's what happening: http://web.me.com/pondini/AppleTips/Setup.html. Before I take him through a reinstall, etc, I'm hoping to confirm that this is really the problem!

Just create a new user account with a different name. Logout of the current account and log into the new one. Be sure the new account has admin status. You can then try migrating and see if it now works. Also see OS X 10.5- Migration Assistant keeps "looking for other computers".
See User Tips for Time Machine for help with TM problems. Also you can select Mac Help from the Finder's Help menu and search for "time machine" to locate articles on how to use TM. See also Mac 101- Time Machine.

Cannot see latest Time Machine backup in Recovery, Setup Assistant, Migration Assistant

I was experiencing really slow HD response, and so chose to boot into the Recovery HD and run Disk First Aid. Disk First Aid said there was an issue and recommended a I backup and reformat the drive and reinstall. So I rebooted into my main drive, made sure Time Machine had done a backup of the latest files. Then rebooted into Recovery HD. Reformated the HD in Disk First Aid. Then went to Restore from Time Machine Backup. Under that heading it would only let me restore a system from 6 months ago. I want restore the latest backup that I verified it had run. So then I decided to Reinstall the OS and hope that Setup Assistant would see the latest update. It didn't even see the drive to recover from. So I skipped it and then hoped Migration Assistant would recognize it. Migration Assistant recognized the backup drive (Time Capsule) but then wouldn't recognize the specific backup for this machine. It only saw the backup of a different computer on my network. So what's going on? Why won't my computer restore from the latest backup? Am I going to have to manually restore? Which would suck considering the number of apps I am going to have to reinstall. Any help on this issue would be much appreciated. I am running 10.8.3 on a 2009 13" MacBook Pro w/ 8 GB RAM and a 500GB HD.

Thank you for your response!
Thinking out loud:
Both external LaCie's were were subject to a veriy and repairt process with no errors were found.
They both mount on the iMac desktop with no problems.
TM bu's to the LaCie's appear to operate correctly.
I can easliy and quickely move content to and from them at will.
Evidence seems to suggest that when entering Migration Assistant(MA), the automatic process of closing all applications save MA, seems to break the iMac<> LaCie connection. Could this be a good lead?
PONDINI
"You posted that TM was set to back up only to the LaCies but the sample you posted below shows a sparsebundle on the TC. Please clarify."
LMISES
My error: That is an old MacBook TM backup(bu)
PONDINI
"What were you running before?"
LMISES
10.8.3.
PONDINI
"Are you sure? Many folks see what they think is their internal HD, but it's really their backups. What confuses them is, it shows the Computer and disk name that were backed-up, not the name of the drive the backups are on."
LMISES
Please see the screen shot below of what Migration Assistant(MA) presents:
PONDINI
"Ordinarily, it's done by excluding the System folder via TM Preferences > Options. That puts up a prompt, and if confirmed sets an indicator in the .plist that controls backups. We do have a very few reports of it getting set some other way, mostly on Mountain Lion, but have no idea how."
LMISES
Thank you. In my view this is very significant as this behavior, it now appears for me, leaves MA as the only option. Not to value MA vs Recovery objectivly, rather, there are benefits exclusive to each process. As I sit now however, MA fails to recongnise not only the TM bu's residing on both LaCie's; MA fails to recongnise the LaCie's as hardware.
PONDINI
"What's in the sparse bundle on your Time Capsule (in the "Data" folder)? Double-click the sparsebundle to mount it; then the "Time Machine Backups" disk image should appear in your Finder sidebar. Double-click that to open it. Inside it should be aBackups.backupdb folder just like the ones on your LaCie drives, with similar contents."
LMISES
The following screen shots are of the "Data" folder.

Imovie not seeing partitioned time machine drive. I partitioned my TM 2GB and formatted Mac OS Extended (Journalled). These drives in iMovie have a Yellow exclamation mark and I cant access events. Can access in Finder?

Any assistance would be greatly appreciated

Thank you for your response. I was able to successfully format the drives Extended journaled when they were out of the raid configuration. I was not able to format as Extended (not journaled) in the Raid configuration.

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

Moved Time Machine drive - can't see backup.

I was having trouble with my Time Machine drive, which was connected by USB to my Airport Extreme. I moved the drive to a USB connector on my MacBook Pro to improve the speed, and after formatting the drive, made a complete, new backup with Time Machine, which took about 8 hours.
Then I moved the drive back to the AirPort and told Time Machine to use it for backup. Time Machine doesn't see the earlier backup (I can verify that it's there using the Finder) and is now doing another complete backup of my MBP.
What's wrong here? How can I tell Time Machine to use the backup it made yesterday instead of starting over?
Walt

Actually, Tech Support told me that they support only Apple Time Capsules connected to the Air Port Extreme. They most certainly do NOT support using Seagate drives such the ones I have been using successfully for over three years, on two MBPs.
I firmly believe (but Apple does not want to hear this) that my problem originated with the erratic WIFI connections since I upgraded to Lion, which has been discussed at length in the forums. Time Machine reported backups failing when the WIFI connection could nto be restored after waking from sleep.
My wife's MBP, running Snow Leopard, is working just fine on the same hardware.
Walt
EDIT: I tried "Inheriting" the backup that was made via the direct USB connection, but it still doesn't show up in the TM history. The tmutil program is interesting - it does distinguish between the "machine_directory" - the backups.backupdb folder that was made by the direct USB backup, and the sparse_bundle file that was created by the AirPort backup.

How to see all back ups on Airport Time Machine?

I have lots of backups on an external HD.
Looking for a folder/file is easy because I can see all backuped folders and files in the folder set up I have decided upon.
I would like to see all my folders and files as these have backed up on Airport Time Machine. I just want to see these folders and files like this is the case on my external HD.
They must be placed somewhere on Time Machine.
How can I see these?
I am not really interested in going into Time Machine Backups on a date related basis, but on a folder related basis.

I am not really interested in going into Time Machine Backups on a date related basis, but on a folder related basis.
Unfortunately, Time Machine is not really interested in working this way. Apple takes the word "Time" in Time Machine seriously.
The best that you will be able to do is navigate to find a folder that you want on your Mac
Then, open Time Machine and use the timeline to see different versions of that folder

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

Finder Lags Until Time Machine Drive RPM Increase

Example.
In a FInder window I click on Today and the list of files modified today will not appear until the time machine drive gets up to speed. I can hear the drive start to spin when I click on Today, and when the drive gets up to a certiain speed, the list of files appear and the spinnig wheel is gone.
Is this normal?
Mtn Lion 10.8.3
WD 2TB Drive using Firewire

It's normal if you have been using files from the external drive. Note that external drives may take some seconds to load data. The same happens when you are using Time Machine on an external drive and you want to restore a file: the Time Machine window is frozen until the external drive loads all backups saved in it

After Kernal Panic can't see Time Machine Drive

I have a usb iSub speaker.
Apparently it is NOT compatible with Leopard but I have been following certain threads with interest as I hate to sell it just yet.
Yesterday there was a post that said if you go into Audio MIDI Setup and change some settings, then change them back- your iSub will work!
Well when I was in the Audio MIDI Setup utility I experienced a kernal panic (first since using Leopard)
After that I was not able to boot past the Grey Apple Screen.
I even left it overnight and it would not start.
I finally reverted to my old Tiger backup external drive- I booted to that, then started my Tiger DVD,
I ran Disk Utility, then Repaired permissions and I am back up and running.
My Time Machine hard drive is not showing on my desktop though! (I have 2 external drives- one is my old Tiger cloned back up with SuperDuper- the other is my TimeMacine backup)
I tried looking for it with DiskUtility but it is not seeing it either.
Any advice would be helpful at this point.
One other thing...it seems to be writing....the case the hard drive is in has lights on it and it is blinking..and I can hear it slightly.

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

Lion can't find my external Time Machine Drive

Anyone having a problem with Lion identifying the external Time Machine drive? When I go to Time Machine set up all I get is "Set Up other Time Capsule". Connections seem OK and drive is on and worked fine previous to the upgrade.
Any ideas?

Is the drive a USB or FireWire external HD, or a network drive (NAS)?
If it's a NAS, it needs an update. See #C16 in Time Machine - Troubleshooting.
If it's an external HD, try repairing it, per #A5 in that same link.

Migration assistant - doesn't see Time Machine drive

I'm using a netatalk based Time machine drive which works perfectly from my old 2006 MBP.
I'm trying to use Migration Assistant to restore the data to my new 2010 MBP. Time machine on both macs sees the netatalk drive, however, Migration Assistant does not - there is just an empty window with a spinning progress wheel.
Any ideas?

This seemed to be a problem with mounting the Time Machine sparsebundle from the old MBP.
I solved it by:
1. Launching Disk Utility,
2. Drag sparsebundle into the drive list on the left (takes ages, ignore spinning wheel)
3. select the sparsebundle
4. Click Repair
took a few hours, but now I can mount the image and once mounted manually, Migration Assistant sees it.
Although it makes sense, it's not obvious that you need to mount the disk image manually for Migration Assistant to see it when Time machine sees it as a destination without doing that step.

Where to find video files in Time Machine?

I'm still not figuring all of this out apparently. Hours later I have backed up my computer onto an external HD via Time Machine. I wanted to check & be sure my videos are on there before I delete some from my hard drive & when I use finder to open Time Machine (the external HD), I cannot find anywhere in there that there are video files or even all of my (1000+) photos from Iphoto... where would these be listed? I don't see titles of the programs or folders called video or photo or pictures or anything along those lines. I even did a search of the drive for .mov and got nothing....
Help!

You should never, NEVER use Finder to view or manage files on a Time Machine back-up.
With the Time Machine drive mounted, click the Time Machine icon at the top menu bar. Amongst the choices that come up is, "Enter Time Machine". A "Finder-like" set of windows hovering in outer space will open with your back-ups layered by date of the backup (shown below). Once you navigate to (using the big silver arrows), find the date you want, click on the folder icon in the window that will navigate your way to the file(s) you want to see, or restore.
At that point you can "see" whether the files you wanted to check on are there. You can also restore any files you wish to do so, by highlighting (clicking a file or folder), then hit the "Restore" button at the bottom right of the window.

How do we regain control over our Time Machine drive revisited

+I posted this question as two posts over in the+ *Intel-based iMac* +forum but I think I may have put it in the wrong place. Please forgive me if you've already read this over there. If someone tells me how to delete a post I will or perhaps a Moderator can/will do it for me.+
+O M Oz+
Recently our 2.66 Intel Core 2 Duo started into a cycle of rebooting itself during the startup sequence. Eventually we decided to Restore the disk from the Time Machine Backup which is kept on an external 1TB La Cie drive.
After the Restore was complete; Time Machine attempted to do a backup run but we got an error message saying the drive could not be accessed to write the backup. Only the very last backup could be seen from the Star Wars screen. The icon had changed to the generic usb drive icon with a padlock.
I attempted a Full Reset of Time Machine by deleting the Preferences as described in the Troubleshooting thread. Since then we have not been able to access the Time Machine drive at all with either Time Machine or Finder.
A check of Sharing and Permissions shows that all users are listed having custom access which seems to mean you cannot read or write the drive. Disk Utility reports the drive as seeming to be okay when run in either Verify or Repair modes.
I have also attempted to run the sudo command from Terminal with no success. I'm running out of ideas. I don't want to do a low level reformat of this drive yet because it IS a backup drive and I'm not clear on the status of the restored drive.
*Next Day after sleeping on it, I posted...*
I've been thinking it over carefully and think I might have done the damage myself.
Before things went pear shaped I needed to back up the 80GB Hard Drive for a laptop but was just a little short of space on the 1TB drive. In Finder I went into the backup.backup folder and deleted the oldest backup under Finder.
From what I NOW know of the data structures of Time Machine I suspect this would have also removed the backups of whatever it is that logs the various permissions. Am I right?
If I am right can I recover from this and still save the the older backups?
Old Mac Oz

I half expected you would be the first to reply, Pondini
Pondini wrote:
Old Mac Oz wrote:
. . . The icon had changed to the generic usb drive icon with a padlock . . .
. . . *we are not able to access* the Time Machine drive at all *with either Time Machine or Finder*. > >. . .From what I NOW know of the data structures of Time Machine I suspect this would have also removed the backups of whatever it is that logs the various permissions. Am I right?
Not exactly, but yes, that can damage your backups.
Try to repair them, per #A5 in the Troubleshooting Tip. If that succeeds, your backups are probably ok. If not, It's possible that +Disk Warrior+ can. It's expensive (about $100), and probably a good investment for the future, but there's no guarantee.
I have already tried that but Disk Utility reports that there is nothing wrong with the disk; clearly that is wrong. I cannot reset the permissions to let me (as the Administrator) even read the disk
If that succeeds, and the 80 GB backup from another Mac is still there, you can delete it via Time Machine. See #12 in the Frequently Asked Questions *User Tip,* also at the top of this forum.
The 80GB backup was a simple Finder copy from the extracted Hard Disk onto my Time Machine disk, just simply regaining Finder access will allow me to rescue that
Also, everything you restored to your internal HD is considered as new, so it must be backed-up again. That will, of course, take a lot of space. It's possible that Time Machine deleted a large number of your old backups to make room. If it didn't, because it couldn't do the backup, it will when it can.
I understand that is what should happen.
So . . . try the repair. If that works, see if the old backups are still there, and also see how much space is available on your TM drive. If there's not enough room for a new full backup of your internal HD, plus 20% for workspace, TM will have to delete some old backups. If the disk isn't well over twice the size of the data it's backing-up, your best bet may be to erase the drive and let Time Machine start fresh.
I am coming to that conclusion. The drive is plenty big enough, it's a Terabyte backing up a 300GB disk. Activity Monitor and Finder using +Get Info+ both tell me the drive has 931.39GB available with about 907GB used, we just cannot access any of the data this usage represents due to the locked permissions.
Since I last posted I have also tried resetting PRAM and running sudo from Terminal as per #C5 in the Troubleshooting Tip to reset the permissions to no avail.
The Restore has not been a success so I am probably going to have to wipe the whole computer and rebuild the system, something I am understandably unwilling to do.
I asked here because the problem seems to be related to a recent Time Machine run and the drive I used. Am I asking my question in the correct forum?
Thanks for your input so far.
Old Man Oz

I have an external Time Machine drive that I want to reformat. I can't remember the password. How can I do this. Disk Utility won't let me. Thanks.

I have an iMac that had drive problems last winter. Took the iMac to the Apple Store and they reinstalled everything and now it works again. Only thing is that my external Time Machine drive is screwed up now. Its 1.5 TB.
I had the Time Machine drive partioned into two parts. One partion was for an emergency bootup using carbon copy cloner. That partion I can open and mounts on my desktop. The other partion was Time Machine. It once upon a time opened and mounted without a password.
It requests a password to unlock even though I never had it password protected before the iMac drive problems. And so now it won't mount the drive.
I can go to Disk Utilities and I can see Time Machine with both partions. The Carbon Copy partion is mounted. The Time Machine partion is not mounted. For this reason I can't select it and erase it.
What the heck am I supposed ot do now to erase it and start over. Any help would be appreciated. I really don't want to go and buy another drive.
Kevin

Triple-click anywhere in the line below to select it:
{ diskutil list; echo; diskutil cs list; } | open -f -a TextEdit
Copy the selected text to the Clipboard (command-C).
Launch the 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).
A TextEdit window will open with the output of the command. Post the contents of that window, if any — the text, please, not a screenshot. The title of the window doesn't matter, and you don't need to post that.
If any personal information appears in the output, anonymize before posting, but don’t remove the context.

Finder cannot see AirPort Time Machine drives

Similar Messages

Maybe you are looking for