Time Machine drive constantly being accessed?

After my Mavericks install, I've noticed that my TM drive sounds like it's being accessed (or written to?) constantly. When it goes to sleep (due to settings in Energy Saver), it'll stop, but then it'll wake back up a few minutes later and make sounds again. It's not grinding or anything, and the indicator LED is not flashing. (It only does that when sleeping/waking or when TM is actively backing up.) I looked in Activity Monitor, and could not find anything that would be affecting the drive. It's also excluded from Spotlight. Did I miss something?
The TM drive is a Western Digital MyBook, if that helps.

Well, I didn't actually suspect that it was a corrupt file. If it is a corrupt file, I'm not sure really how to deal with it. Any suggestions on tracking down the culprit?
What I actually suspect is that buildhdindex is an old drive indexing app (been around since 10.3 I believe) that wasn't updated to deal with Time Machine's hard-linking. It also has no options to exclude the Time Machine drive, it wants to index everything. Because TM is basically keeping a huge series of links and not actual copies of files, it's looping endlessly.
Of course, I would expect to have heard more about this issue, so maybe it is something specific to my machine, i.e. a corrupt file.
Possibly related, I get a ton of these messages in the console:
com.apple.RemoteDesktop.agent[1087]: SystemFlippers: didn't consume all data for vers ID 1 (pBase = 0x1e424a20, p = 0x1e424a44, pEnd = 0x1e424a4f)
Message was edited by: Anthony Hecht

Similar Messages

Can I move the time machine drive from being a usb drive

Hello
I am not sure whether this fits best in the time capsule or in the time machine forum. I try here as this a issue thar arises only to time capsule users.
I have a new USB drive that I want to use for time machine backups. Eventually I want it to be attached to the time capsule and make the time machine back up via wifi. However the first backup is 261 Gb and this is too long for the wi-fi. I am doing it right now via the USB and take 12 hours (estimated).
After the USB backup will be finished, can I move the drive to the time capsule and let time machine make the backups via wifi? I mean, is time machine going to find the backup done via USB or once started with USB I am stuck with that?
Thanks for answering and for reading
Roberto
PS
maybe was better on the time machine forum, still don't know.

Backup strategy
Backing up a client computer to Time Capsule hardware with Time Machine software via the network provides ample time for contemplation, and rumination as to why the backup is taking so long. An initial 200Gb backup has an estimated time of "3 days" even on a wired network. Incremental backups following the initial backup are also beset with delays, with various message which can be viewed with the programmer's delight, the "Console" app. Otherwise the System Preference Time Machine interface is mute. The glacial pace of the Time Capsule backup process is exhaustively documented on the internet, but with no solutions - at least that I have found any after too many hours searching.
The System Preferences->Time Machine interface is always used to start a backup, monitor, or stop a backup, whether the backup drive is present on the network via Time Capsule, or if the backup drive is directly connected to the client computer.
On the positive side, Time Machine performs quickly and provides hourly backup to external drives directly attached to the client computer. The delay appears in network backups via Time Capsule.
Another positive is that network backups to Time Capsule are reliable when the client computer is stable, always on, and never detached from the network. In this case, the mute interface offered by system preferences->Time Machine is welcome. For example, my Apple Mac Mini web server (always on) is reliably backed up to a Time Capsule.
The negative experience is encountered when backing up a laptop when, as laptops do, the laptop wanders from the network. As stopping a backup can take 15 minutes, backups are necessarily interrupted when dashing off to work with your laptop. In the network where I have experience, there are 5 laptops and 1 stationary (Mac Mini) clients living on an all-Apple network. Failing to complete a backup via network for days on end gives no feeling of security.
Reading from Podini's excellent website
http://pondini.org/TM/Works.html
and extracting a summary, files copied from a client computer using Time Machine are stored on the backup drive in one of two formats: sparse bundle (special file type) when backing up to Time Capsule (or to a drive attached to a Time Capsule), or a folder with the client computer name when the backup drive is Firewire attached to the client. A closer examination of the sparse bundle file on the network with the Finder shows that the same folder appears with the computer name.
So, Time Machine backups always go to a folder with the client computer name, and this folder is either inside a sparse bundle or not depending upon if the backup drive is mounted on the network via TC or directly attached to the client.
An external drive mounted on the network via Time Capsule will create a sparse bundle file for the client or add to it if it already exists. Even if backups are present of the same machine, but not in a sparse bundle, Time Capsule will create a sparse bundle if it does not exist for the current backup client computer, and start a new backup.
An external drive directly connected to the client has a different experience. No Time Capsule is involved. Upon turning on backups via Time Machine, the backups will go to a sparse bundle file with the client computer name, if it exists. If the sparse bundle file does not exist, a folder is created with the computer name.
A strategy of backing up to an external drive moved between various computers and the Time Capsule might resolve some of the many delays. The strategy is simple, if delays are encountered, directly attach the backup drive to the client computer. If a backup is to be manually deleted in order to begin anew, directly attach the backup drive to the client computer before deleting the sparse bundle file.
To begin a new backup with this strategy of "drive+TC", initiate (via TM) the backup on the network (via TC), then stop after 10 minutes (with TM), noting that a sparse bundle of zero size is created. Continue the first backup by directly connecting the external backup drive to the client then pointing Time Machine to the newly connected drive. The backups by way of direct connect will go to the existing sparse bundle. Wait three hours rather than three days for a 200Gb backup to complete. Subsequent backups will go to the sparse bundle file on the backup drive, whether the backup drive is on the network (via TC) or directly connected.
But what of the internal drive on the TC? In this strategy, it is not used for backups unless the client computer is always attached to the network.
With so little documentation from Apple, we are left to speculate as to the cause of TC largo. Normally, slight documentation means little to know for the user, and the user is spared the complex machinations under the hood, but when the operation is flawed the user is left without resources.
A secure backup strategy stores a backup offsite, just in case the house burns down, or buglers make a clean sweep of computers and backup drives. Unfortunately, this means doubling the equipment, including two Time Capsules and two external drives attached to the TCs. The offsite copy is rarely mentioned in the same paragraph as the Time Capsule, likely because of the cost. It's an uncomfortable fact that a sole TC is vulnerable to local hazards, along with the local client computers.
This is the strategy I'm testing now. I'll send an update in a few days.

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.

Reinstall of OSX, will I be able to access my old system via time machine drive.

This is probably a no brainer, but I haven't had to do this yet so I want to verify. I'm running Snow Leopard and my machine is running very slow now and appears corrupted. It's definitely time to reinstall my OS. If I back up all my folders and apps using time machine on an external drive, erase my computer's hard drive, and reinstall snow leopard, will I be able to plug in that time machine drive and dump all my folders, work, and apps back onto my newly reinstalled machine?

Thanks to you all for responding. You guys make some great points and it's been very helpful. I think I am going to manually back up all my main programs which are not native mac apps, and folders, etc. It's going to be a longer process but will allow me to trim the fat and avoid backing up what could be lurking as the problem to some of my corruption issues. The below screen shot is an example, the empty button contains a random letter/number rather than 'empty'. Thanks again for your input!

Trouble with Time Machine (runs constantly). Erase and install?

Trouble with Time Machine (runs constantly). Tried re-installation (equivalent of archive install) of Snow Leopard. Time Machine still unable to complete a back-up. Erase and install recommended at Genius Bar. Have backed up data to external HD using Super Duper. Should be a bootable backup. Last successful backup through Time Machine was 6/1/11. Not sure if I can access this back-up if I erase and re-install.
Computer shipped with Tiger (7/2007). Have original disks. Now running Snow Leopard. So: erase HD, install Tiger, then update to Snow Leopard? Start-up from Tiger disks does not appear to work (starting up holding "C" key). Suggestions? Want very much to transfer data to new iMac, but do not want to carry bugs forward. Very nervous about erasing HD. And have the questions above about reinstalling system software.
Advice desired! Thanks.

Well if you can hold option and boot off the Superdupes clone and it works fine then you should be set to do what you need to do to the original boot drive.
Disconnect all drives and c boot off the Snow Leopard install disk, use Disk Utility to Erase > format HFS+ journaled your internal boot drive.
Quit and reinstall OS X Snow Leopard, setup (do not use Setup/Migration Assitant!) and update to 10.6.8
When you setup the new install, use the same hard drive name and user name as you did before.
Now the free iLife that came on the Tiger disks you won't get naturally, but you can pick them off the disk with the shareware program called Pacifist.
install your programs from fresh sources, this way you don't get the "crap" from the older setup.
Once your machine is up and going. Hook up the clone and transfer your user folders over manually. With iTunes just replace the whole folder. Because you kept the same user and boot drive name as before, the playlists should be fine.
Once your all peachy, take the opportunity to clone this new setup to a external drive, label and disconnect.
Make another clone for day to day, or week to week clone updates and your just a hold option boot away for recovery.
You know Superdupes and Carbon Copy Cloner both have auto-scedualing/updating ability, so you can leave them plugged in and it will perform a update so your clone stays fresh and recent.
But you should keep a clone timed back about a couple of weeks back just in case you install something bad and don't learn about it right away.

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

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.

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

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

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

Using iCloud Drive as a Time Machine drive?

Hi,
do you know if there is a way to use iCloud drive as a Time Machine drive. I mean, we can have more than one time machine drive, using iCloud Drive would be a nice option for off site backup no?
I Currently use Crashplan for that, but using iCloud drive would be better, as I'd have access to my stuff more easily than with crashplan's UI.
MAybe a third party services offers that?
What do you think guys?

Manusnake wrote:
Well I thought the same, but actually I did a new Time Machine backup a month ago via wifi (starting from scratch). About 700 GB of data. It was slower than Ethernet of course, but it worked without any issue.
You must have top-of-the-line WiFi hardware. How long did it take? I don't even remember how long it took for the initial Ethernet backup before my Time Capsule died. It was at least a day.
However I see your point for online backup. That'd require TM to be more gentle. To do one backup per day for example could be a solution (instead of one every hour).
Time Machine works best in small increments. I always advise against hacking the backup frequency. People who complain about Time Machine tend to have hacked it up. People who don't tend to have left it alone. Just sayin'.

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.

Time capsule set up fine but time machine hangs up when accessed

hi,
i just bought my mac book pro this year. then, purchased 1TB Time capsule. i had set up the time cap after 2 days with the time machine. it worked well but i cannot print when the printer cable is attached to the time cap. then, i missed several scheduled back ups due to electricity interruptions and even resorted to deleting the sparsebundle to start anew. when i enter time machine, i can see the outerspace background but the finder window and everything else could not be accessed. it just freezes. i brought my time cap to istore (reseller store here in the phil) and fortunately, they facilitated to replace my time cap with a new one.
with the new time cap, i rushed to set it up. initial back up has been done. my problems are:
1. i can enter time machine, but i could not access anything. the time line freezes and so with the finder window. i even resorted to ctrl option esc to get out of time machine; and
2. i still could not print via time capsule.
please help me. the discussion portion of apple website is the only direct line of help available as i am located far from the apple reseller. i don't have the landline telephone so i could not directly call apple support.
help me please....
just_je

I had this problem with my Time Machine drive very recently. I wasn't using a Time Capsule but it sounds exactly like my problem.
Time Machine would backup to my external drive with no problems but every time I wanted to go into the program, it would freeze. It would be fine in the current time, (when you first enter Time Machine) but if I tried to go back in time, the animation would happen, but I wouldn't be able to click on anything in the finder Window. The only way to get out of it was, as you said, to press Apple, Option and Escape.
The way I solved this was to use Disk Utility on my external drive. I had tried before but when I clicked on verify or repair disk it just sat there for ages doing nothing. What you need to do is select the Time Capsule drive in Disk Utility and then do a repair on it.
Warning though, it will take about an hour to complete. It took probably about 20 minutes for mine to even start repairing. But it does work, I did it on mine and now Time Machine is fully working again.
Hope this helps
Chris

Time Machine Drive Ejecting Itself--Spotlight culprit?

Hi,
I have to backup my MBP ASAP so that I can take it to Apple for repairs. When I first got the computer, I thought both my external drives were ejecting randomly so I never thought that Time Machine was the issue. The other hard drive proved to have a faulty wire and solved that problem, but I still can't seem to determine why my Time Machine drive keeps randomly ejecting. I searched this and various other forums for an answer and narrowed down my problems to my antivirus and spotlight indexing. At first, the harddrive would last anywhere from 0mins-45mins before being ejected. I began checking the console logs and notices some instances where my antivirus was running at the same moment. I disabled scanning of the TM backup and saw the biggest improvement in how long the drive was able to stay connected and make backups before ejecting. It stayed on for close to 6-7 hours.
Then, it ejected randomly again and I checked the console messages and saw spotlight returned some indexing errors. This time the ejection made the drive unreadable and I had to reformat. I backed up again and it kept ejecting itself early on in the backup process with the same spotlight errors. I added the entire drive to Spotlight's privacy list, and it managed to complete the entire backup. The drive then stayed connected without ejecting for another 7-9 hours the next day without any random ejects before the spotlight errors struck again. The drive is still listed in the privacy and it is still excluded from antivirus scanning. I have repaired the disk several times and gotten the "Appears to be OK" message. I even reformatted the drive and did another complete backup hoping that would take care of any corrupt Spotlight indexing. I have also rebuilt the entire index for both Spotlight on the internal and external drive. At this point, I need to run the backup as I am getting my hard drive swapped. What I am most concerned about is, even if I get another backup successfully on the drive, will I run into any problem using Setup/Migration assistant (random ejects, freezes, corrupt data) when its time to transfer my info back to the new install of OS X and be left without my data altogether? I also just need to this work... as what is the point of a backup solution, if you can't rely on it to make it through a day without crashing..
Below is the latest log file from Console. Any help will be greatly appreciated as I have went through the same steps that proved successful for others who had the same issue before me.
Console Log:
Oct 25 19:35:58 CSKMBP1086 com.apple.backupd[12396]: Starting standard backup
Oct 25 19:35:58 CSKMBP1086 com.apple.backupd[12396]: Backing up to: /Volumes/Time Machine /Backups.backupdb
Oct 25 19:36:04 CSKMBP1086 com.apple.backupd[12396]: No pre-backup thinning needed: 202.8 MB requested (including padding), 35.59 GB available
Oct 25 19:37:15 CSKMBP1086 kernel[0]:
Oct 25 19:37:15 CSKMBP1086 com.apple.backupd[12396]: Error: (-36) SrcErr:NO Copying /Library/Logs to /Volumes/Time Machine /Backups.backupdb/CSKMBP1086/2010-10-25-193558.inProgress/69A3D5EC-1F5B-495A-AE B6-CFE539F99764/Macintosh HD/Library
Oct 25 19:37:15 CSKMBP1086 kernel[0]:
Oct 25 19:37:15: --- last message repeated 4 times ---
Oct 25 19:37:15 CSKMBP1086 mds[41]: (/Volumes/Time Machine/.Spotlight-V100/Store-V1/Stores/3ACBCEAD-A6E0-485B-9EC8-6ABCAB507777)(E rror) IndexStore in SIStoreDirytySDBChunks:Error storing dirty sdb pages: 22
Oct 25 19:37:15 CSKMBP1086 kernel[0]:
Oct 25 19:37:15: --- last message repeated 1 time ---
Oct 25 19:37:15 CSKMBP1086 mds[41]: (/Volumes/Time Machine /.Spotlight-V100/Store-V1/Stores/3ACBCEAD-A6E0-485B-9EC8-6ABCAB507777)(Error) IndexCI in _ContentIndexSyncIndexBulk:preSync error:22 22
Oct 25 19:37:16 CSKMBP1086 com.apple.launchd[1] (com.apple.backupd[12396]): Job appears to have crashed: Segmentation fault
Oct 25 19:37:16 CSKMBP1086 Finder[7405]: * CFMessagePort: dropping corrupt reply Mach message (0b100101)
Oct 25 19:37:16 CSKMBP1086 com.apple.Finder[7405]: Failed to send message to backup server: error = -5
Oct 25 19:37:16 CSKMBP1086 SystemUIServer[7404]: * CFMessagePort: dropping corrupt reply Mach message (0b100101)
Oct 25 19:37:16 CSKMBP1086 com.apple.SystemUIServer.agent[7404]: Failed to send message to backup server: error = -5
Oct 25 19:37:16 CSKMBP1086 com.apple.ReportCrash.Root[12410]: 2010-10-25 19:37:16.532 ReportCrash[12410:1407] Saved crash report for backupd[12396] version ??? (???) to /Library/Logs/DiagnosticReports/backupd2010-10-25-193716localhost.crash

BrinXx wrote:
narrowed down my problems to my antivirus
Unless you're running Windoze on your Mac, you may not need any anti-virus software at all. See Thomas Reed's [Mac Virus Guide|http://www.reedcorner.net/thomas/guides/macvirus]. But yes, keep your TM drive excluded.
The drive then stayed connected without ejecting for another 7-9 hours the next day without any random ejects before the spotlight errors struck again.
Excluding your TM drive from Spotlight doesn't stop all indexing of it: http://docs.info.apple.com/article.html?path=Mac/10.6/en/8991.html
What I am most concerned about is, even if I get another backup successfully on the drive, will I run into any problem using Setup/Migration assistant (random ejects, freezes, corrupt data) when its time to transfer my info back to the new install of OS X and be left without my data altogether?
The backups will probably be ok, but if your internal HD is corrupted, as it seems to be, that corruption may be transferred to them.
Oct 25 19:37:15 CSKMBP1086 com.apple.backupd[12396]: Error: (-36) SrcErr:NO Copying /Library/Logs to /Volumes/Time Machine /Backups.backupdb/CSKMBP1086/2010-10-25-193558.inProgress/69A3D5EC-1F5B-495A-AE B6-CFE539F99764/Macintosh HD/Library
Now that's quite odd, indeed: the /Library/Logs folder is supposed to be +*excluded automatically+* from backups! That's controlled by a special plist deep inside OSX, so it's been altered, corrupted, or ignored, which is not a good sign.
Ordinarily, I'd suggest downloading and installing the 10.6.4 "combo" update, but that may not be enough -- you may need to reinstall OSX, too, and depending on what's wrong with your system, you may not have time, and if your system is misbehaving, it may not work anyway. If you want to, the info and download are available at: http://support.apple.com/kb/DL1048 Be sure to do a +Repair Permissions+ via Disk Utility (in your Applications/Utilities folder) afterwards.
Oct 25 19:37:15 CSKMBP1086 mds[41]: (/Volumes/Time Machine/.Spotlight-V100/Store-V1/Stores/3ACBCEAD-A6E0-485B-9EC8-6ABCAB507777)(E rror) IndexStore in SIStoreDirytySDBChunks:Error storing dirty sdb pages: 22
That's from the mds process, used by both Spotlight and Time Machine.
Oct 25 19:37:16 CSKMBP1086 com.apple.launchd[1] (com.apple.backupd[12396]): Job appears to have crashed: Segmentation fault
Another indication of possible corruption in your installation of OSX.
|
It's always a good idea to keep secondary backups, since all hardware fails, sooner or later, and no backup app is perfect. Given the apparent corruption of your installation of OSX, I'd recommend that even more strongly. See #27 in [Time Machine - Frequently Asked Questions|http://web.me.com/pondini/Time_Machine/FAQ.html] (or use the link in *User Tips* at the top of this forum) for some suggestions.
Sorry not to have better news or more concrete suggestions.
Let us know what Apple finds, and/or if you need help restoring.

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.

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

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

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

Time Machine drive constantly being accessed?

Similar Messages

Maybe you are looking for