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

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

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

Similar Messages

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

I have an external hard disk attached to my iMac, which it uses for Time Machine backups. Can I configure Time Machine on my Macbook to use that same drive, and to connect to it over my network? Thanks.

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

My MacBook pro won't recognize hard drive I put in it. It boots only to a white screen unless I boot to my recovery USB. If I do that then I can select my USB and my external time machine drive in the disk utility, so no problems there. But what do you

My MacBook pro won't recognize hard drive I put in it. It boots only to a white screen unless I boot to my recovery USB. If I do that then I can select my USB and my external time machine drive in the disk utility, so no problems there. But what do you think it is? It won't recognize any hard drive I put in the machine, so might it be the sata cable?

Boot the Recvoery USB, use Disk Utility to select the internal drive makers namea and size on the left.
Now select erase and select the midde option and click erase, it will take a bit to complete but it's best for the drive.
Now select Partiton tab, click the big box and Options: GUID and then Format: OS X Extended journaled and click apply.
Quit and you should be able to install OS X now with your Apple ID and password.
see
http://osxdaily.com/2011/08/08/lion-recovery-disk-assistant-tool-makes-external- lion-boot-recovery-drives/

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.

Lion can't find my external Time Machine Drive

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

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

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.

What do I do when I suspect a virus? Is it safe to do a back up on my external time machine?

What do I do when I suspect a virus? Is it safe to do a backup on my external time machine?

It is not a virus.
Please explain exactly what makes you think you might have a virus.
Yes. It is safe to backup to an external Time Capsule using Time Machine as the software to do that on your Mac.

HT201250 Can I back up multiple volumes using Time Machine on Snow Leopard?

I have a fault with my time machine software where it is no longer able to perform incremental back ups of the volumes (partitions) I have created on my internal hard drive - every attempt results in a full back up. However incremental back up of the Mac HD is working. I have had it working perfectly in the past. I'm backing up to a dedicated external hard drive.
I have just been told by an apple support manager that Time machine on OS 10.6.8 is not designed to back up multiple volumes (partitions) on my internal hard drive, only the current Mac HD drive - is this correct? He said it shouldn't be backing up the other volumes and the reason it is doing so and has done so in the past is because of bug!
Surely this is not the case?

I would read and try this. Pondini is very knowledgeable about Time Machine:
http://pondini.org/TM/32.html
Ciao.

Restore from back up does not recognize time machine drive

My wife's hard drive in her 2010 MB Pro decided to give up the ghost a few days ago, so I purchased a new hard drive for her, booted from the Snow Leopard Install disc that came with the computer. However, after the installation is complete, when it gives the option to "Restore from backup", it will not locate the drive with the Time Machine Backups. The drive with the time machine backups is a dedicated 500 Gig Seagate External, that is set up on the network through our Airport Extreme. When I plug the drive directly into the computer, the drive doesn't even show up on the list. When I plug it back into the router it will recognize it as the Time Machine Disk, but will say "Connection Failed" when I try to connect with it. I have watched several youtube videos and read several blogs, and it looks so easy, simply click on "Restore From Backup" and bang! You're in business, but my drive and its backups won't even show up!
After going through with the intitial set up, I can click on the Time Machine Icon, and choose to view other Time Machine disks, and it shows up there, and I can see about two (2) years worth of back ups; however, each time I boot from the install disks, it still doesn't show up in the "Restore from Backup" mode. Migration assistant shows the files, but when I migrated them, it says that I do not have permission to view the files. Also, when I enter the Time Machine it only shows a blue folder with "Macintosh HD" on it, and when I try to simply "Restore" that folder, it will start transfering files for about an hour (Maybe get up to 10-15 Gigs, and then it will say that it cannot replace or over right "Systems", and then stop the transfer.
Thinking that some of the drives were from when we upgraded to Lion, I redownloaded Lion, and it is more of the same.
I am in a really tight spot here, because I have been faithfully using Time Machine Backups, and was told that if a situation like this ever occurred I would be good to go with a new hard drive, or even a new computer. We have about 80 Gigs (not kidding) of family photos on the computer, and those are precious to my wife, so if nothing else I would just like to get those off of the drive.
If anyone could provide me with any tips as to
1) How to make Restore from Backup recognize the drive; or
2) Migrate the files, but actually have permission to view them; or
3) Any other way to Restore from Time Machine that I may be overlooking,
I would greatly appreciate it.

Well the first thing you should do is have a local professional image the TimeMachine drive to another drive, then you can install Data Rescue on your computer and use that to read the 1's and 0's of the imaged drive directly and recover any files out of the morrase that is TimeMachine.
TimeMachine is a freaking eyecandy abortion, when it screws up, it screws up royally. However it's easy and better than nothing for computer newbies who tend to delete stuff by accident.
Computer professionals prefer "imaging" or "cloning" which makes a exact duplicate of a drive in every detail and accessability. Carbon Copy Cloner is the choice software for that.
If you not comptuer savvy or want to take a risk, then I'd advise you to get a local PC/Mac data recovery expert to recover your files, they are still on the drive and somewhat accessible, but if you fool around too much TM can delete them as it "copies" your present new boot drive. Then data recovery could cost thousands for platter dissection if the TM drive is overwritten/updated by TM software.
So to be safe, get profesisonal data recovery help, and not the clueless types at the Genius bar.
FYI, once a TM drive has been infected with Lion, you can't use it with SL.
So it's best to stop and get a image, then decide to play with the image or allow the pro's to recover your files before they are really gone forever.

Can't stop OS X indexing the Time Machine drive

I have a dedicated drive for time machine connected via FW800.
I've gone to spotlight preferences and made sure it is excluded from the spotlight search.
But the drive spends hours each day thrashing, even when TimeMachine is not actually backing anything up. Seems wasteful, and (as it is a noisy drive) a bit of a distraction.
So I looked in Activity Monitor, and saw that there is a process running called buildhdindex when the thrashing is occuring, and it is using loads of processor power. Here is a clip from my Activity Monitor display:
1108 buildhdindex root 40.5 1 529.96 MB 1.20 GB
Should I be concerned?
Is there any way to stop this?
Any advice / help / suggestions most welcome.

I think it is a leftover from Panther days... If you find that preference in /Library/Preferences/com.apple.ARDAgent.plist you can trash it and restart.
-mj
Message was edited by: macjack

10.9.3 won't recognize my Seagate external Time Machine drive...

I've already used Disk Utility. The hard drive shows up, but the volume itself is greyed out. When I repair the hard drive, this is the message I get:
Verifying and repairing partition map for “Seagate FA GoFlex Desk Media”
Checking prerequisites
Checking the partition list
Adjusting partition map to fit whole disk as required
Checking for an EFI system partition
Checking the EFI system partition’s size
Checking the EFI system partition’s file system
Checking all HFS data partition loader spaces
Checking booter partitionsReviewing boot support loaders
Checking Core Storage Physical Volume partitions
Updating Windows boot.ini files as required
The partition map appears to be OK
When I repair the volume ("Armand"), this is the response:
Verifying volume “Armand”
Checking file system
Error: This disk needs to be repaired. Click Repair Disk.
Verify and Repair volume “Armand”
Checking file systemVolume repair complete.Updating boot support partitions for the volume as required.
Error: Disk Utility can’t repair this disk. Back up as many of your files as possible, reformat the disk, and restore your backed-up files.
So...help? The hard drive hasn't been dropped, jostled, or anything like that. I'm using a MacBook Pro, Retina, 13-inch, Early 2013. This is really annoying, as I'd normally have just migrated my information from the last backup, done this morning!

The issue with WD drives started with Mavericks. WD does have a fix. You need to remove the WD software and update.
WD Drive Manager needs to be updated on Mac OSX 10.9.X (Mavericks)
Dear WD Registered Customer,
On October 30th, 2013 Western Digital informed registered customers of affected products via E-mail regarding reports of Western Digital and other external HDD products experiencing data loss when updating to OS X Mavericks (10.9). Our investigation to date has found that for a small percentage of customers that have the WD Drive Manager, WD Raid Manager and/or WD SmartWare software applications installed on their Mac, there can be cases of a repartition and reformat of their Direct Attached Storage (DAS) devices without customer acknowledgement which can result in data loss.
WD has been tracking this issue closely through our WD Forum and through our Technical Support hotline and the occurrence rate of this event has been very low. A specific set of conditions and timing sequences between the OS and the WD software utilities has to occur to cause this issue. SHOULD THIS EVENT OCCUR, THE DATA ON THE PRODUCT CAN LIKELY BE RECOVERED WITH A THIRD PARTY SOFTWARE UTILITY IF THE CUSTOMER STOPS USING THE DEVICE IMMEDIATELY AFTER THE OS X MAVERICKS (10.9) UPGRADE. WD will be issuing updated versions of these software applications that resolve this issue.
WD strongly urges our customers to uninstall these software applications before updating to OS X Mavericks (10.9), or delay upgrading until we provide an update to the applications. If you have already upgraded to Mavericks, WD recommends that you remove these applications and restart your computer. If you have already upgraded to Mavericks and are experiencing difficulty in accessing your external hard drive, please do not save anything to the drive, disconnect the drive from your computer, and contact Western Digital Customer Service at http://support.wd.com/country/ .

Can I backup two macs onto one external time machine?

Can I backup two macs onto one external time machine drive? I am trying to do this over Wi-Fi.

Yes, the external drive has to be formatted correctly to HFS+ and shared to the network.
It doesn't matter how the second machine logs into the network but wireless back will be extremely slow as it will involve double hop wireless, I presume to a wifi router somewhere. For incremental backups this is no biggie but do the initial backup with the drive plugged into that particular computer or over ethernet.. gigabit for preference.
Pondini has some instructions as he has for most things.
http://pondini.org/TM/4.html
Also look at Q33 where he lists using a shared drive on another Mac.
If you are planning using something other than wifi router give clear information about the network layout you have and hope to use.

How to downgrade from Mountain Lion back to snow leopard with Time Machine

The final straw was the horrible mouse sideways page wiggle while trying to scroll down and read safari pages. Even after turning the feature off, tech support said it will still wiggle a little. That and the HORRIBLE grey icons everywhere was enough to send me back to my beloved iMac I loved when I bought it. I'll give up the iMessage and the few new items ML gave me. But as many others said, what I got new was far less than what was taken away.
So what tech support had me do was this. Even though the apple engineers said it would not work, apple tech support had me try it and it worked for me so good luck. Engineers said that after you install mountain Lion, it messes with ALL your time machine back ups and won't revert back to snow leopard even if you select a snow leopard date back in time. That didn't happen to me. I have a 2010 27 inch iMac
This worked for me but PROCEED AT YOU OWN RISK
Export individually any email folders or photos or data you will lose between now and the date you are reverting back to.
1. Insert Snow Leopard DVD that came with computer. The install disk not the applications. Make sure time machine external drive IS connected.
2. Restart computer and when you hear The Mac chime, hold down the C key and then it will take several minutes to boot up from the DVD.
3. Select the little blue triangle to continue in English.
4. When it gets to the screen that says "continue" stop. There might be a screen or two before this one I can't remember but either way stop at the word continue.
5. Go up to the top left and find the UTILITIES pull down menu and select disk utility.
6. In the window that opens up, Select the Apple drive which should be the very top one in the window.
7. Select erase.. it should be Mac OS extended journaled
8 select erase and maybe a password. It only takes a few seconds
9 go back up to UTILITIES in upper left and then select restore from time machine or backup or whatever it says. It's the last choice.
10. Select the external time machine drive and navigate to the date you last had Snow Leopard running and that will be the date it restores to. You will lose any data between now and then but you can export your mail, export photos, and other items separately. I only stayed on ML For a few days before hating it enough to go back so I had no loss of data except a few emails.
11. Hit RESTORE. And then it will take several hours. When you restart it, it should come right back to that day you selected as if ML was just a bad thought on someone's drawing board.   If for some reason it still comes up ML, Then they said to erase HD Again (steps 1-8) and then manually drags back USER folder or individual folders with Mail, photos etc.   if this way doesn't work, have another plan printed out so that you are not stuck by this one.
Good luck. Proceed at your own risk..

The ultimate solution:
You need an USB of at least 5 GB and the Snow Leopard Install DVD.
1. make a bootable USB with Disk Utility in it:
     a. download the Mountain Lion Installer from the App Store
     b. quit the installer after download
     c. find the installer in the Applications folder
     d. option+click in it and select "Show Pakage Contents"
     e. go to Contents>SharedSupport to find there the InstallESD.dmg file and mount it by double-clicking it
     f. with the Disk Utility, restore its contents into your USB
2. boot from the USB:
     a. restart the computer and hold-down the option key while booting
     b. select the USB and boot
3. run the Disk Utility and format in ONE partition the HD of your computer
REMEMBER: BACKUP YOUR HARD DISK BEFORE DOING ALL THESE, YOUR DISK WILL BE EREASED AND DATA BECOME UNRECOVERABLE OTHERWISE
4. insert the Snow Leopard DVD and reboot from it
5. follow the on-screen instructions to install OS X 10.6
After this, you can, if you will, upgrade to Lion or stay in Snow... Good Luck!!

Lost the ability to Spotlight Index my Time Machine drive

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

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

Time Machine 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.

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

Similar Messages

Maybe you are looking for