Time Machine drive files after data recovery.....permissions problem?

Client had a hard drive crash, and then turned out her Time Machine drive was bad. We ran a data recovery on the Time Machine drive, which produced about 40GB of disk images...12 in all. There is a very promising image which shows the user folders, and we can click on hers and see her folders. BUT...when we try to open Documents, we get a message that
"Item "Documents" is in use by Mac OS X and cannot be opened"
Would there be an override of permissions or some such available to take a peek inside and hopefully pull files?
Thanks to all in advance.

A general look at backup files......

Similar Messages

Time Machine drive disappears after Sleep

Hey peeps,
I have been trying to put my computer to SLEEP after 1-hour of inactivity as it's a family machine that is used minimally and I want to save energy. It is an early 2009 mac mini running 10.9.
When I wake the computer up, one of my external USB drives comes back, however the external USB hard drive that has my time machine drive seems to unmount itself or disconnect and I have to physically turn the power on and off to get it to come back.
I have checked DISK UTILITY and it's gone from there too.
anyone seeing this too?

Hello r_dizzle,
Thank you for the details of the issue you are experiencing with your external hard drive. I found an article with steps you can take when an external device is not behaving as expected
I recommend following the steps in the section titled "Top troubleshooting tips" in this article:
USB and FireWire Quick Assist
http://support.apple.com/kb/HT1151
Thank you for using Apple Support Communities.
Best,
Sheila M.

Missing index file after data recovery

Hello
I accidently deleted some pages files from my trash. I recovered them using Filesalvage. Now when I try to open them I get the message
"Unable to open xxxxx.pages because the document is invalid. The index.xml file is missing."
So I suppose the recovery program hasn't recovered that part of the file package.
Is there anyway to rebuild or recover the data?
Thanks
Dion

I have the exact same issue, of course this occurred before time machine came along. Have you been able to recover any of your deleted pages documents. I learned later to make sure that the suffix .pages is turned on and that creates a .pdf wrapper that can be recovered if accidently deleted.
Let me know if you have any luck with your situation and I will do the same.
Sincerely,
David

Time Machine drive unavailable after 10.7.2 upgrade

I've just updated my iMac (Oct 2010 27") to Lion 10.7.2. All appeared to complete normally and everything is working OK bar this.
Time Machine runs to an external USB 2Tb hard drive (Samsung). This was working perfectly until the update.
Now, the non-Time Machine files on the external drive are still visible to Lion but the Time Machine volume is not.
Disk Utility cannot repair it and recommends reformatting. However, on that volume is all my TM backups from the last 6 months.. I really don't want to reformat.
Any ideas?
Thanks.

"I open Time Machine in System Preferences, and I see the barber pole is spinning next to "Backing up", but under it, it just says "Looking for backup disk"."
Looks as though it might be a 10.7.2 problem as it was working perfectly before.
I get a tad further than you with the barber pole spinning and "Preparing backup...".
Added later...
Maybe not a problem after all. Mine sat spinning for around 10 minutes and now, it is suddenly backing up.

Can't Access Time Machine Backup Files After Reinstall

I just completed a clean reinstall of Mountain Lion. Obviously I've missed some important step(s). When I enter Time Machine, I can see that there are older back ups by the dates on the right hand side of the screen, but they are greyed out. I'm confident the files are there, the issue is being able to access the files.
I've seen some notes about "reassociating Time Machine" with my "new" computer with some terminal commands, but I get lost with the instructions I've read and it sounds like if I do it wrong there is a pretty good chance I could really cause some damage. For the time being, I've turned off TM, but the dirve is still mounted and available.
For some reason, I was able to access and resotre my Documents folder - I just can't get into all the folders/files. Prior to the reinstall, I did visually confirm that I could see and access all my backup files.
Any help is appreciated.
Thanks.

Time Machine Troubleshooting
Time Machine Troubleshooting Problems
Time Machine FAQ

ITUNES DOES NOT PLAY ALL MUSIC FILES AFTER DATA RECOVERY

My external Iomega Firewire 160gig HD, all of a sudden, changed the drive letter from H to F with unknown format.
I recovered music files ( Using Stellar Phoenix FAT)and files/folders are in iTunes but only 20-30 play (out of over 6,000)
I can play CD and rip new music in iTunes, though.
Any suggestions how to get my music play all library files??
Dell Windows XP Media center

WiseBird,
There might be several causes for that kind of erratic behaviour:
1st use Disk Utility to check your internal disk as well as the external one.
2nd Your Library database might be damaged
- Quit iTunes
- Goto ./Users/YourUserName/Music/iTunes
There will 2 files named something "Library" - move them to your desktop
- Launch iTunes
As you're now starting from scratch, iTunes will offer to search for audio tracks - Don't let it.
- Your iTunes should be "clean"
- in iTunes Preferences - Advanced - General:
Point the Music Folder Location to the appropriate folder on your ext hd
Disable "Copy Files to iTunes music folder....."
- Quit Preferences
- From iTunes Menu - File choose "Add to library..." + select that folder on your ext hd that contains all your tracks.
- All your tracks should be back by now in iTunes Library.
- To get your playlists back: From iTunes Menu - File choose "Import" and open that .xml file that you moved to your desktop (might work but need not).

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

Time Machine Recovery (after data recovery)

Several months ago, Disk2 and Disk3 in my 2007 MacPro 1,1 (OSX 10.7.5) became unreadable by the computer. To make matters worse, the Time Machine external backup became equally as unreadable. All at the same time! Drive 1, with the operating system, seems to be unaffected. The two unreadable drives showed up as "media" in disk utility, but didn't show up in Disk Warrior or any other similar programs (partition repairing) using the "terminal." I sent the Time Machine drive (WD Mybook Essential 3Tb) to DataRecovery.com and they found no phyical issues with the drive. There was, however,"Data Corruption in the file tables and data area" (according to the evaluation report). This was corrected and the TM drive was supposedly completely recovered.
Upon receiving the external drive (now replaced by a newer 3Tb Mybook), I replaced disk2 and disk3 with new 1TB drives (formatted with a single partition) and tried to perform a restore for these two drives. No such luck.....The drive was readable by the computer but would not actually enter into "Time Machine." I examined the actual drive and found an inordinate amount of Unix executable files, especially when going into the individual backups. The drive does show that they recovered 870Gb of information, but nothing seems to be readable much less recoverable.
I'm wondering if there is a workaround for any of this or whether I should contact the data recovery people to resolve this. I appreciate any help on this as it's become expensive and a bit deflating.......I still hold out some hope, though. Thanks. The drives were most likely corrupted by a generator that kicks on once a week (automatic maintenance) and temporarily cuts power long enough to turn the computer off...I've since gotten a UPS.

A general look at backup files......

HT4527 My old mac book was backed up to a Time Machine drive. That Macbook is dead. I have a new Mac Mini. How do I get the iTunes library (not just the music files but all other data...playlists, ratings, etc) on the new Mac from my Time Machine?

My old Mac died. I had it backed up to a Time Machine external drive (fortunately). I have a new Mac. I want to get my entire iTunes library from the Time Machine drive to the new Mac. I want not only the music files but all the "library" metadata, playlists, song rankings, unique genre designations. How do I do this?

No backup is a huge mistake.
You can redownload some itunes purchases in some countries:
Downloading past purchases from the App Store ... - Apple - Support

Unable to empty trash with data from Time Machine Drive

Hi there,
Cause of the current issue:
I am hoping the experts can help me with this one. I have an external hard drive which is used for my Time Machine Backups. Recently there has been an error on the backup to this drive on occasion. This error only occurs when the system does the back up, and appears only periodically, never when I do the back up manually. One of the threads I read to solve this issue is to delete some older backup files from your time machine drive, and all is good. This worked for awhile.... but now a new problem:
New Problem:
I have been able to empty all of the trash save one particular set of folders. So the trash always appears with content.
The structure of the trash content appears as such...
Macintosh HD
+-Users
+--<username>
+---Library
+----FK6T0KGc9y4KBB <-- This changes each time I try to empty the trash.
The library folder always has the time/date of the last time I tried to empty the trash.
What I have tried:
1. I have tried to empty the trash Securely. No good.
2. I have tried the terminal command : sudo rm -rf ~/.Trash with no success
3. I have tried this terminal command : sudo rm -rf ~/.Trash/* with no success
4. I have tried just plain old Empty Trash. But I get the message "This operation cannot be completed because the item 'FK6T0KGc9y4KBB' is in use.
Any thoughts, recommendations?

Hey thanks for the help anyway VK.
I tried that command and no go either.
Last login: Fri Jul 25 08:13:39 on console
iMac:~ tmlohnes$ sudo rm -rf /Volumes/Time\ Machine\ Backups/.Trashes/501/*
Password:
rm: /Volumes/Time Machine Backups/.Trashes/501/2008-03-28-160634/Macintosh HD/Users/tmlohnes/Library/8xMlmPGUHzilET: Directory not empty
rm: /Volumes/Time Machine Backups/.Trashes/501/2008-03-28-160634/Macintosh HD/Users/tmlohnes/Library: Directory not empty
rm: /Volumes/Time Machine Backups/.Trashes/501/2008-03-28-160634/Macintosh HD/Users/tmlohnes: Directory not empty
rm: /Volumes/Time Machine Backups/.Trashes/501/2008-03-28-160634/Macintosh HD/Users: Directory not empty
rm: /Volumes/Time Machine Backups/.Trashes/501/2008-03-28-160634/Macintosh HD: Directory not empty
rm: /Volumes/Time Machine Backups/.Trashes/501/2008-03-28-160634: Directory not empty
iMac:~ tmlohnes$
I am wondering, would it make sense to try this same command if I were to do a safe boot?
What about formatting the external hard drive and starting fresh?

Can I use a TIme Machine drive of my Macbook to transfer data to a new IMac

Hi everyone
I currently have a 2.6GHz Intel Core 2 Duo Macbook Pro as my main machine, using System 10.6.4.
I'm keen add a second computer which will allow me to run both systems at the same time.
My day job is a music producer, so I have plenty of audio programmes and plug ins, that are all intel spec and up to date, so I'm aware of tranferring new password codes etc to a new hard drive however I wondered if there were any potential issues transferring the data from my Macbook Pro and or it's Time Machine Drive to a new iMac ? I'm guessing not as they are both Intel Machines and will be running the same operating system, but any guidance to re-assure me would be greatfully received.
Many thanks in advance to any replies.
Robert

I wouldn't use Migration Assistant for anything but to transfer your Home folder assuming you wanted to operate out of the same account on both machines. That's certainly the easiest approach. It's what i do between my Mac Pro and my MBP.
But Migration Assistant is not a tool for maintaining synchronization between two computers. For that you can either have the two computers on the same local network and sync them over the network with third-party software. Or you can maintain an external "common" backup that is used to keep the two computers up to date using third-party software.
My choice is the common backup on an external hard drive. I use a notebook sized drive because it's easy to take with me when I travel. I backup the most recently changed computer to the external drive. Then connect it to the other computer and do an incremental update. This keeps both computers in sync. You just need to remember which was the most recently changed computer.
If you have a local network, then when both computers are connected to the network you can enable File Sharing on one of the computers, then sync the two with third-party software.
Backup Software Recommendations
1. Retrospect Desktop (Commercial)
2. Synchronize! Pro X (Commercial)
3. Synk (Backup, Standard, or Pro)
4. Deja Vu (Shareware)
5. Carbon Copy Cloner (Donationware)
6. SuperDuper! (Commercial)
7. Intego Personal Backup (Commercial)
8. Data Backup (Commercial)
9. SilverKeeper 2.0 (Freeware)
10. MimMac (Commercial)
11. Tri-Backup (Commercial)
Others may be found at VersionTracker or MacUpdate.
Visit The XLab FAQs and read the FAQ on backup and restore. Also read How to Back Up and Restore Your Files.

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

HT3275 TIme Machine deleting files I deleted from my home drive

This seems like a very basic problem but I cant find an answer and am no longer able to use Apple Support. I am trying to erase files from my very crowded home drive. I bought an external drive and backed up all fikles there. However, now when I delete files from my home drive and plug in the external drive, Time Machine delets the files I deleted from my home drive on the external drive which defeats my purpose. Can anyone help a hopelsessly tech savvyless stranger.
Thanks So much

Copy the files to the external drive in the Finder instead of going through Time Machine. If you want that drive to have a bootable OS, you'll need to use software such as Carbon Copy Cloner or SuperDuper.
Time Machine backups are designed for recovery of accidentally or inadvertently deleted files. They aren't meant for primary storage of files you don't want on any other drive. In any case, drives eventually fail; anything you want to keep shouldn't be on only one drive.
(70364)

Brand new iMac 23.GHz Intel Core i5. Mounts external drive for time machine, then dismounts after backup is complete.

brand new iMac 23.GHz Intel Core i5. Mounts external drive for time machine, then dismounts after backup is complete.

The warranty entitles you to complimentary phone support for the first 90 days of ownership.
If you bought the product in the U.S. directly from Apple (not from a reseller), you have 14 days from the date of delivery in which to exchange or return it for a refund. In other countries, the return policy may be different. If you bought from a reseller, its return policy applies.

I have a time machine backup file on a USB hard drive. I bought a time capsule / airport extreme, flat 3TB. I wish to transfer the backup file from the usb hard drive to the time capsule hard drive. 10.6.8

I have a time machine backup file on a USB hard drive. I bought a time capsule / airport extreme, flat 3TB. I wish to transfer the backup file from the usb hard drive to the time capsule hard drive. 10.6.8

Unfortunately, Time Machine backups that are stored on a drive that has been connected directly to a Mac are completely different than Time Machine backups that are stored on a Time Capsule.
Frankly, it is not worth the effort and trouble to try to transfer the old backups to the new Time Capsule.....my opinion....having done this in the past.
It is possible though, but I would not recommend it due to the complexity and downsides involved with this. To give you an idea of how to do this, check out this support article.
http://pondini.org/TM/18.html
Even if you transfer the "old" backups over to the Time Capsule successfully, Time Machine will not simply "add on" to the old backups.
Time Machine will make a new complete backup of your Mac and then add incremental backups from that point.
My advice.....start a new backup on the Time Capsule and move forward. Keep the USB hard drive around for a month, maybe 2 or 3 in case you need to go back to an old backup for some reason. At that time, you will not likely need the old backups at all since you will have a current 2-3 month history of new backups. At that point, you can erase the USB drive and use it for another purpose.

Time Machine drive files after data recovery.....permissions problem?

Similar Messages

Maybe you are looking for