Time Machine drive continually gets compromised
More that one external Time Machine drive loses the ability to create folder due to what appears to be a drive issue. Disk Utility reports the following:
Incorrect number of extended attributes
(It should be 936186 instead of 936185)
Incorrect number of Access Control Lists
(It should be 936184 instead of 936183)
Time Machine works for a while after restart or disk repair. Have used different Time Machine drives, different boot drives, reset Time Machine, reformatted Time Machine drives.Time Machine drives formatted GUID OS Extended (Journaled). All the Time Machine drives work fine on my older 2ghz Mac Mini running. OS 10.5.8. What am I missing?
Hi, and welcome to the forums.
Something is corrupting the file system. Are you careful to eject it before disconnecting? Any power failures while it's connected?
Make sure all connections are snug and secure; try different port(s) and cables, and combinations -- a plug that works fine in one port may not quite make a good connection in another.
Some drives that worked with Leopard need driver or firmware updates to work with Snow Leopard. Check with the maker to see if they have updates for yours (especially if they're all the same make).
Verify the internal HD, just to be sure something there isn't corrupted.
If nothing else helps, it could be a problem with your installation of OSX. I'd suggest downloading and installing the 10.6.4 "combo" update. That's the cleverly-named combination of all the updates to Snow Leopard since it was first released, so installing it should fix anything that's gone wrong since then, such as with one of the normal "point" updates. Info and download available at: http://support.apple.com/kb/DL1048 Be sure to do a +Repair Permissions+ via Disk Utility (in your Applications/Utilities folder) afterwards. Don't delete the download yet, though.
If that doesn't help, reinstall OSX from your Snow Leopard Install disc (that won't affect anything else), then apply the "combo" again.
Similar Messages
-
I am using a WD My Passport Studio external hard drive as a Time Machine. I get the error that a back up folder could not be created when my iMac has been asleep, any advice. The hard drive is set set not to go to sleep.
Were you not plugged in via USB to begin with?
I would recommend performing some resets just to be on the safe side. Unplug the external HD, and try these steps:
http://support.apple.com/kb/HT3964
http://support.apple.com/kb/HT1379 -
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 -
how can I get all of my music off of my laptop and onto an external hard drive? I bought a new hard drive for it but it got turned into a Time Machine drive... I want to have all of my music on the external hard drive, and NOT on my macbook pro. Thanks everyone
Hello lramospsych,
To move your iTunes media library to a different location, take a look at the article below to walk you through that process. Make sure that you have everything organized before you move everything over.
iTunes for Mac: Moving your iTunes Media folder
http://support.apple.com/kb/ht1449
Regards,
-Norm G. -
I am tring to installe OS X Mavericks. When I get to the select disk page it says that the HD is uesd as time machine drive. How can I remove time machine backup from my Mac.
Open up your Finder and click on Go on the top menu bar. Select Computer and then double click Macintosh HD. In here delete the backup folder. Might be called backups.backupdb.
-
Getting new external drive, can I switch back up time machine drives?
I don't want to loose the info time machine has already captured on my external hard drive called B1, if I install a new hard drive B2, can I just copy B1 to B2 and then point time machine to B2?
Not sure what the process would be, but I want to get rid of B1 as a time machine drive and add b2 and not loose any info already captured.
Suggestions?Related question:
I partitioned my 500GB external drive, 30GB in G-1 for a bootable system (currently 10.4.10) and the remaining space in G-2 for Time Machine.
I now want to resize the partitions on the fly in Terminal, to free up 20GB more for TM, but I plan to use Carbon Copy Cloner to first make a backup of both G-1 and G-2, just in case.
If I lose data resizing the partitions and then have to restore the TM backup files from the clone, will Time Machine recognize its earlier files and pick up where it left off, or will it start over?
Aside: Disk Utility in Leopard indicates it will resize partitions on the fly without losing data, but I have read in other threads that data has been lost anyway.
Ken -
Time machine backups continue to fail. I keep getting the message Sparse bundle in use
My time machine backups continue to fail. I keep getting the message: sparse bundle occupied. Any suggestions?
Half off all problems seem to be solved by simply powering off a device, waiting a few minutes, and then powering it back up again.
What happens when you do this for the Time Capsule? -
Time machine wont continue backing up after restore
hey all,
i had to do a restore after boot camp crashed on me and i lost my 10 Gig of space which i chose to partition. more to the point, i migrated from a time Machine backup to get my mac running the same way it was before i restored only one problem remains... when time machine tries to backup it does not carry on backing up from before i restored, instead it chooses to try and backup everything that is currently on my macs hard-drive (300 Gig) i just want it to backup changed files... just like before.
Other wise everything else is fine, time machine even works and i can go into the time machine interface and restore old files which i have deleted. This is such a nuisance can anyone help?
Thanks.I'm interpreting what you are saying as a reinstall of the system software followed by a migration of your user data from the Time Machine backup. The better procedure is to restore the whole system from the Time Machine backup (done by accessing the restore option from the menu on the install disk). I believe then you wouldn't have had this issue. The essence of the problem is that Time Machine thinks you have migrated user data to a new system and so is backing up the whole new system. I don't know what you can do about that. It is possible that the fact the system looks physically different (ie you don't have the partitioned hard drive you used to have) is a deal breaker for Time Machine.
But it's certainly worth checking the computer name. You find that by opening System Preferences and clicking the Sharing icon. At the top of the page is a box labelled Computer Name. That needs to be the same as the name when the backups were made. You can confirm the name when the backups were made by going into the backup volume via Finder. There will be a folder called Backups.backupd. Double click that and there is a folder with the Computer Name at the time of the backups. As I say, these have got to be the same for Time Machine to continue to use the same backup directory. -
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?
--BobWell 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 -
How do I make a hard drive "forget" that it was once a (no longer used) Time Machine drive?
I'm starting a new thread on this question in the hope that someone new will notice it.
I've started using a larger hard drive for my TM backups. I want to be able to use the previous drive for other things BUT I also want to keep the oldest TM backup, just in case. In order to do that I want to move all but one day's backup to the trash but of course get the "The operation can’t be completed because backup items can’t be modified." message. I also, of course, can't change the name of the backups.backupdb folder for the same reason. In older OSs it was possible to use a Terminal command to bypass all this but it would seem that it's no longer possible to do this in Mt. Lion.
Note that the old drive is NOT being used in Time Machine, so that's not the problem.
Does anyone know how to make Time Machine realize that the drive is now just a drive, not a Time Machine drive? Obviously I know I can just reformat it but then I'll lose ALL the files. I want to keep one day's worth, so reformatting is not the solution. I do know that I can copy everything over to another drive but I don't have another drive large enough to do that, so need to unflag the one set of files as TM backups and trash the others.
Any help gratefully accepted.I think I understand your question, but I'm puzzled at what you are trying to accomplish.
Let's say you've been using TM for a year, now you start a new backup set on a different device.
What you seem to want to do is delete all the backups in the old backup set on the old except for the very first backup - ie. the oldest.
That would mean that you would retain the oldest backup from 1 year ago, and all the new backups from the start of the new set forward. Deleting all the past year's backups except for the very first plus the new backups going forward on the new device. Is that what you want?
The only way I know of doing this would be to manually delete in TM all the undesired backups -slow and tedious for sure,
On the other hand, you want to keep the last backup of on the old device then....
Assuming that you started the new back up set shortly after the last backup on the old device, then the first backup on the new and the last on the old are almost identical for all practical purposes.
If that's what you want I'm not sure it accomplishes anything useful.
Can you clarify what you want to achieve/do, so we can help you better. -
External time machine drive no longer being automatically recognized
Recently my RMBP has stopped recognizing my external time machine drive. When ever I connect my 1 TB WD drive to my mac, it shows up on my desktop as usually but will not get recognized by time machine. I used to be able to connect the drive, have it show up on my desk with the orange USB logo, and then it would be auto recognized and the time machine logo would appear on it and it would start backing up. Now, I connect it and it just stays at the orange USB logo. I have to go to the time machine menu bar icon and open time machine's preferences and manually select the drive to get it to back up. This happens both on battery power and while I'm charging. I have already verified the disk in disk utility and have repaired as well. I don't recall when this started happening. I was running the 10.9.4 beta before its public release, but it hadn't been working before I upgraded to that either.
This simple procedure will clear your Time Machine settings, including exclusions. The backups won't be affected. If you have a long exclusion list that can't be recreated easily, you may prefer a more complicated procedure that preserves the exclusion list. In that case, ask for instructions. Otherwise, do as follows.
Triple-click anywhere in the line below on this page to select it:
/Library/Preferences/com.apple.TimeMachine.plist
Right-click or control-click the highlighted line and select
Services ▹ Reveal in Finder (or just Reveal)
from the contextual menu.* A Finder window should open with a file selected. Copy the file to the Desktop. Then move it (the original, not the copy) to the Trash. You'll be prompted for your administrator password. Restart the computer and recreate your settings in the Time Machine preference pane. It will show that you have no backups. Don't worry; your backups haven't been touched. Run a backup to test. The backup may take much longer than usual. If TM now performs as expected, delete the file you copied to the Desktop.
*If you don't see the contextual menu item, copy the selected text to the Clipboard by pressing the key combinationcommand-C. In the Finder, select
Go ▹ Go to Folder...
from the menu bar and paste into the box that opens by pressing command-V. You won't see what you pasted because a line break is included. Press return. -
Encrypted Time Machine Drive not visible
Hi,
I have a Mac Mini (2.53 GHz Intel Core 2 Duo with 4GB 1067 MHz DDR3 Ram) running OS 10.8.4 and all other OS/application updates have been run. I have a Drobo (2nd Generation, the one with four drive bays & Firewire) with 3.69TB used and 1.72TB free. The Drobo has the most up-to-date firmware 1.4.2 as well as the latest Drobo Dashboard software (2.5.2).
I was using a different NAS to backup my data from the Mini but the housing failed and I'm waiting for Other World Computing to send a new one. In the mean time, I decided to backup the Mini to the Drobo and Encrypt it. I believe it went through one complete backup of the Mini (440GBs) overnight. I also use the Drobo as my main drive for my photos and iTunes library. I have about 2TBs of music/movies and about 1TBs of photos already stored on the Drobo. During the day yesterday, during a regularly scheduled Time Machine backup (I believe it backs up every hour), I was in the process of deleting photos off the Drobo and got the dreaded spinning beach ball. I waited for 1/2 hour but still after no changes, I turned off the Mini and after rebooting the Time Machine drive will not show on the desktop.
The Drobo is visable in the Drobo Dashboard app and of course it says there are no issues.
The Drobo shows up in Disk Utility as a Virtual Whole Disk (in red type) and when running Verify or Repair Disk, it states that "Error: This disk needs to be repaired. Click Repair Disk." I can do this till the cows come home but nothing changes. The only other info that shows up in red is "Invalid Disk Label @ 17591825289216: invalid field value. It repeats it four times, I'm assuming once for each drive. The last piece of info is "disk3s2 is not a CoreStorage volume.
I saw on another thread to run a Terminal command "diskutil cs list" and it came up with the below listed info.
Last login: Thu Jul 18 12:51:04 on console
skurkis:~ administrator$ diskutil cs list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group 6E1361BB-CAF7-468D-9CD5-5A77ED37C763
=========================================================
Name: -none-
Status: Initializing
Size: 0 B (0 B)
Free Space: -none-
|
+-< Physical Volume 161162B5-ABCE-4540-BA90-A3EA9E2E956B
Index: 18446744073709551615
Disk: disk3s2
Status: Failed
Size: -none-
skurkis:~ administrator$
Any help to get my nearly 4TBs of music, movies, photos back would be awesome!
Thanks,
JeffAre there any utilities that can help "uncorrupt" the volume so I can rescue my data?
The only thing you can do is destroy the Core Storage logical volume, which will remove all data. If there is anything other than backup data on it, you're in a recovery situation, which is a job for professionals.
You should immediately start a new backup on another storage device. Don't do anything else with the computer until that's done. -
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 -
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......
-
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?
Maybe you are looking for
-
How do you create a new Game center account for IOS 8.1?
I really want to know how to create a Game center account on IOS 8.1. Can u please help me?
-
Video out, dvi, apple vga? , help me
i ahve a pb g4 12" 867mhz, i want to buy a video out cable, but i notice that my port is different from several friends who have the 1.0ghz model g4 12", can someone link me to a website with what i need? or am i even able to buy the older cable? tha
-
Iterating an ArrayList HashMap with JSTL in a JSP? Can it be done?
I made up the following code to iterate an ArrayList of HashMaps using JSTL Core in a JSP, but it doesn't work. However I've seen examples of similar code that works, so I'm not sure what's wrong with mine. Any help would be greatly appreciated. <%
-
Person or Group colum in the SharePoint list retrieves empty value for Mobile phone property
Person or Group colum in the SharePoint list retrieves empty Mobile phone for some users although thoses users have Mobile Phone values in the User Proifles. This happens only for some users. For some users it shows Mobile phone for some days and af
-
How to use member variable to all my pakages
i want to use some member variables to all my packages in my project how to declare it.