Time machine backup error failing
I have been using time machine for nearly a year now and has proved very usefull in restoring my data when i had 2 hard disk crashes,and replaced and 1 motherboard failure before apple replaced the computer. It really gives great peace of mind insurance.
Anyway yesterday th backup failed with simple error message. i tried a couple of times again, same failure at same point. I tried a complete new backup to different disk but this also failed.
This is a transcript from console at time of failure
what do i need to do to fix
thanks
Paul
Oct 26 10:09:40 paul-cathcarts-macbook-pro /System/Library/CoreServices/backupd[313]: Error: (-36) SrcErr:YES Copying /Users/paulcathcart/Documents/Microsoft User Data/Office 2004 Identities/Main Identity/Database to (null)
Oct 26 10:09:40 paul-cathcarts-macbook-pro /System/Library/CoreServices/backupd[313]: Error: (-36) SrcErr:NO Copying /Users/paulcathcart/Documents/Microsoft User Data/Office 2004 Identities/Main Identity/Database to /Volumes/Time/Backups.backupdb/Paul Cathcart’s Computer/2008-10-25-145059.inProgress/EA7D8166-5CBC-49A6-9E35-DE608F36D194/Maci ntosh HD/Users/paulcathcart/Documents/Microsoft User Data/Office 2004 Identities/Main Identity
Oct 26 10:09:40 paul-cathcarts-macbook-pro /System/Library/CoreServices/backupd[313]: Stopping backup.
Oct 26 10:09:40 paul-cathcarts-macbook-pro /System/Library/CoreServices/backupd[313]: Error: (-8062) SrcErr:NO Copying /Users/paulcathcart/Documents/Microsoft User Data/Office 2004 Identities/Main Identity/Database to /Volumes/Time/Backups.backupdb/Paul Cathcart’s Computer/2008-10-25-145059.inProgress/EA7D8166-5CBC-49A6-9E35-DE608F36D194/Maci ntosh HD/Users/paulcathcart/Documents/Microsoft User Data/Office 2004 Identities/Main Identity
Oct 26 10:09:40 paul-cathcarts-macbook-pro /System/Library/CoreServices/backupd[313]: Copied 1406 files (679.3 MB) from volume Macintosh HD.
Oct 26 10:09:40 paul-cathcarts-macbook-pro /System/Library/CoreServices/backupd[313]: Copy stage failed with error:11
Oct 26 10:09:45 paul-cathcarts-macbook-pro /System/Library/CoreServices/backupd[313]: Backup failed with error: 11
Oct 26 10:11:53 paul-cathcarts-macbook-pro SyncServer[325]: SyncServer: Truth vacuumed. Next vacuum dat
Hello,
I have the same problem with Time Machine failing on the same database file. I believe it's more linked to the size of the file rather that on a corruption of it. I ran the repair tool of Microsoft (ou just need to depress the option key while starting the application) and the file is fine.
On my mac the file is 5 GB and I strongly believe that backinp up such a large file on a network filesystem like my Time capsule it's a challenge.
Any comment on that ? What is the maximum file size that the backupd procee can handle safely ?
Regards
Eric
Similar Messages
-
Since upgrading my Macbook to Lion, the time machine backups are failing - error message: "The backup disk image “/Volumes/Jackie Scanlon's Time Caps/Jacqueline Drabczynska’s MacBook.sparsebundle” could not be accessed (error -1)." I have rebooted the TIme Capsule and it worked OK, but don't want to do that every time. Any suggestions? Thanks
Any new info on this?
I had the exact same problem and went crazy and spent a hecka lot of time trying to deal with my brand new 2TB Time Capsule and almost brand new MacBook Pro. Then I thought I fixed it...and I tried SO MANY things, I don't really know what did it...except taking out any apostrophe's in names of stuff that Apple puts in there...BUT...now it's back.
Grrr... -
Upgraded to Mavericks and time machine backups keep failing.
I upgraded to Mavericks a few days ago and now I find my time machine backups keep failing. I first tried turning off the power to the time machine then turning it on again and I managed to get one complete backup but that took over 20 hours to complete.
The time machine backup mode never seems to get beyond " preparing backup" then showing the message "backing up failed, disc already in use"
The time machine backup worked fine before I upgraded, is there a way round this problem or will I have to go through reloading the time machine as if it were a new piece of equipment?
My wife's iMac is still on mountain lion 10.8.5 and the backups on the same Time Machine work fine.
Any help would be gratefully received
GregHi,
I have exactly the same problem.
MBP 2011 running 10.9 named "ebook"
MacMini running 10.8.5 server with TM share
everything works fine UNTIL for some reason the MBP is interrupted during a TM backup ...
After that I get the disk already in use error !
Rebooting the MBP wont help, but I narrowed the problem down ...
Looking on the Mini server I noticed :
- the TM backup user stays connected over AFP, even after several hours of inactivity and a couple of reboots of the MBP. Killing the AFP connection works, But problem stil continues !
- looking on the MBP with "lsof | grep ebook" showed me that the SparseBundles were still in use by the AFP process ... Using the Server control panel and restarting AFP solved that ...
After restarting the AFP process the remote TM Backup started to work again !
A couple of days later, the same problem occurred again, fixed it by this work around ...
I hope there will be a more permanent solotiun for this ! -
My Time Machine backup keeps failing. I get a message the "Volume has the wrong case sensitivity for a backup". Please advise.
Thanks, HowardYou can change the case sensitivity of the sparsebundle.. but I really doubt the error is real.
See A8 here.
http://pondini.org/TM/Troubleshooting.html
The sparsebundle should have case sensitivity turned on.
I cannot even fathom how it could have changed.
Let me recommend before you start fooling around with the sparsebundle.
Do a full network start.
Power everything off.. start up modem.. wait 2min.. power up the TC.. wait 2min.. power up any other network gear like switches.. wait..
Now power up the computer and try it.
If the error is the same.. I would do a factory reset of the TC.. give it all short names, no spaces and pure alphanumeric. Then reset TM .. see A4 in the same reference as above.. and do a verify of the backups.. A5 above and try the backup again..
No luck..
Then erase the TC and start over.. it is sometimes necessary as TM does get itself in a knot. -
I am getting a Time Machine backup error "The backup disk image “/Volumes/Data/Extreme.sparsebundle” could not be accessed (error -1)."
Then a Finder window pops up with the backup directory in it. When I open it I see all the backups that were completed successfully and then the one there is simply always shows the data and .inProgress. I thought that maybe if I could delete the one that is perpetually in progress it would start a new one and run fine, but I won't let me delete it.Reboot the TC.. or go to the 5.6 utility.. and disconnect all users.. to force it to reconnect.
C17 in troubleshooting.. to give more specifics to Kappy's comment.
http://pondini.org/TM/Troubleshooting.html -
Forgive my clumsiness ---
My Time Machine backup keeps failing...how do I find out why?? MacBook Pro 5,1 OS 10.5.8, 6GB ram backing up to new OWC Mercury Elite-AL Pro 2TBHave you formatted the disk to Mac OS Extended (Journaled)?
Caio. -
My time machine backup keeps failing
My Time Machine Backup keeps failing . Does anyone know what I should do
Launch your console program (located in the utilities folder) and click on all messages in then left column then type "backupd" in the filter box in the upper right. Read the messages, it may give you a clue as to what's causing the problem.
-
Can't restore from Time Machine backup error message
My hard drive on my Macbook failed a few days ago. Just makes a clanking noise and won't boot up etc... I installed a new drive, formatted it, and selected restore from Time Machine backup from the installer screen. It started restoring from my backup I had on an external drive and everything was fine untill it got about 6% done then get a message that says "An error occured when restoring from the backup" It is pretty non descriptive. It also says please restart your system and try again or something to that effect. I tried again, same problem. When I try to copy files over manually I eventually gets some error that says there is a problem with a file and it will quit. Any ideas on how to get my data? I can see all my files on there, but can't get them. My backup disc is just used for backup on this one machine nothing else, so it shouldn't have a problem. Help!
Good to hear MA is doing something!
>I have never had much luck with Time Machine...
Same here, not one good backup or restore, can't tell which.
You can set any of these to Clone/Update as often as you wish...
Carbon copy cloner...
http://www.bombich.com/software/ccc.html
Or SuperDuper...
http://www.shirt-pocket.com/SuperDuper/
Or the most expensive one & my favorite, Tri-Backup...
http://www.tri-edre.com/english/products/tribackup.html -
I just bought a new 2gb Time Capsule to replace my 3 year old 1gb model. I have 4 Macs that back up to the Time Capsule (3 laptops wirelessly, 1 iMac wired). It is the exact same setup I had with the old Time Capsule. I set up the new Time Capsule without transferring over prior backups.
On my Retina MacBook Pro, I am receiving the error "The identity of the backup disk “MyName” has changed since the previous backup." Some add'l details:
1) The new and old TCs were named the same and no other external drives are plugged into any computers
2) The other 3 computers are properly using the Time Capsule
3) The issue seems to pop up over night, in other words when I have not been using the MBP for a while, but I am not sure that has any bearing on this, just a data point
4) I have deleted the sparsebundle and plist file for the MBP, essentially trying to clear out all remnants
5) I am on Mavericks with all software up to date
6) I have selected and unselected the backup disk several times in System Preferences/Time Machine/Select Disk
I have looked at /volumes/ on both the MBP and my iMac and watched as I run a Time Machine backup. As the TM backup runs, additional volumes appear and then disappear once the process completes:
On the iMac: Volumes named "MyName Time Capsule" and "Time Machine Backups" appear while the process is running, then both disappear once finished.
On the offending MBP: Volumes named "MyName Time Capsule" and "Time Machine Backups" appear while the process is running, then both disappear once finished. However, there is another volume called "MobileBackups" that does NOT go away once finished. I've tried to manually dismount that volume, and when I re-run the Time Machine process it reappears and does not automatically disappear.
Any advice would be greatly appreciated.
Thank you in advance, JohnWell, I am virtually convinced that this is an issue around when the rMBP goes into sleep mode and loses connectivity to my network. I was away from the machine for a couple of hours today, and upon return noticed an exclamation point in the Time Machine icon. The menu indicated "Backup Delayed".
1) When I tried to manually start a backup, after several minutes I received a notice "Time Machine couldn't complete the backup to "myname". The backup disk is not available. Make sure the backup disk is connected or select a different backup disk."
2) When trying to select the disk in Airport Utility and trying to manually run a backup, after several minutes I received the error "There was a problem connecting to server "myname". Check the server IP address, and then try again. If you continue to have problems, contact your system administrator."
3) I also tried to open the drive via Finder but was unable to connect to the drive.
4) Based on a suggestion from someone, I ran the following Terminal command (see results below):
sudo tail -f /var/log/system.log | grep -i backup
5) Meanwhile, I checked both my iMac as well as my wife's MBA and both had been running Time Machine properly throughout, no errors in the past and no errors today. I manually ran a backup on both the iMac and the MBA and both ran perfectly.
6) I restarted the Time Capsule via the Airport Utility. Upon restart, I was able to successfully manually run a TM backup form my rMBP. I was also able to access the Time Capsule via Finder.
Add'l Notes:
a) I am not losing my network connection in general. I am still able to browse, etc. I am just losing my TC connection apparently.
b) I was using an old Time Capsule with this same laptop for about a month before buying this new Time Capsule. I never once had this issue with the old Time Capsule.
It seems clear to me that upon non-use I am somehow losing connectivity to the Time Capsule. While the issue hasn't happened in over the past 2 nights, it did happen today while I was out running errands. My hypothesis on why it didn't happen the past 2 nights is that there may have been some network activity (ie: receiving an email, receiving an iMessage, etc.) that allowed the rMBP to maintain connectivity.
Any additional ideas with the new info? I will call Apple ASAP, but cannot tonight.
Thanks in advance.
Results of Terminal command while trying to run a TM backup:
Jan 4 16:02:56 Aaa-Bbbs-MacBook-Pro.local com.apple.backupd[3845]: NAConnectToServerSync failed with error: 89 for url: afp://aaa%20bbb;AUTH=SRP@Bbb._afpovertcp._tcp.local/Bbb%20Time%20Capsule
Jan 4 16:02:56 Aaa-DAgostinos-MacBook-Pro.local com.apple.backupd[3845]: Attempting to mount network destination using URL: afp://Aaa%20Bbb;[email protected]/Bbb%20Time%20Capsule
Jan 4 16:05:27 Aaa-DAgostinos-MacBook-Pro.local com.apple.backupd[3845]: NAConnectToServerSync failed with error: 89 for url: afp://Aaa%20Bbb;[email protected]/Bbb%20Time%20Capsule
Jan 4 16:05:27 Aaa-DAgostinos-MacBook-Pro.local com.apple.backupd[3845]: Backup failed with error 19: The backup disk could not be resolved, or there was a problem mounting it. -
Time machine backup error in Mavericks
I"m getting backup errors in Mavericks when it tries to back up to the Backups.backupdb folder in my 3TB external backup drive. This happens even when I turn Time Machine off!
This is the error I'm getting (taken from the console) when I manually start a time machine backup:
10/26/13 9:56:39.268 AM com.apple.backupd[18160]: Starting manual backup
10/26/13 9:56:40.826 AM com.apple.backupd[18160]: Backing up to /dev/disk2s2: /Volumes/Macbook Pro Backup 3TB/Backups.backupdb
10/26/13 9:56:46.069 AM com.apple.backupd[18160]: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/Macbook Pro Backup 3TB/Backups.backupdb/Macbook Pro 25 size:37
10/26/13 9:56:46.070 AM com.apple.backupd[18160]: Backup failed with error 2: 2
Has anyone seen this? At this point, I haven't been able to back up anything after upgrading to Mavericks, and I really don't want to delete the backup folder and start over.
I thought it might be a permissions problem, so I tried to use the disk utility to verify this. I wasn't able to select verify or repair disk permissions. When I tried to verify the disk, I got a 'Live file system repair is not supported' error. I've never seen this before.
Any thoughts on all of this?I fixed this by hard booting, then repairing the disk. A restart didn't work.
-
Time Machine backup error message
I am making a second backup with a new HD. It made the first Time Machine backup, but ever since, I get the error message "unable to complete backup".
The Time Machine buddy gives me this message:
Starting standard backup
Backing up to: /Volumes/DIANE EXT HD 02/Backups.backupdb
Error: (22) setxattr for key:com.apple.backupd.ModelID path:/Volumes/DIANE EXT HD 02/Backups.backupdb/Diane Tolomeo’s iMac size:7
Error: (-50) Creating directory 2011-11-03-142638.inProgress
Failed to make snapshot container.
Error: (22) setxattr for key:com.apple.backupd.ModelID path:/Volumes/DIANE EXT HD 02/Backups.backupdb/Diane Tolomeo’s iMac size:7
Backup failed with error: 2
Can this be fixed? If so, how?Take a look here
https://discussions.apple.com/thread/2142747?threadID=2142747&messageID=10782279 #10782279 -
I had my hard drive replaced and since my Time Machine backups say failed
I had my hard drive replace and since my Time Capsule backups are failing. The exact message is:
The backup was not performed because an error occurred while copying files to the backup disk.
The problem may be temporary. Try again later to back up. If the problem persists, use disk utility to repair your backup disk.No, replacing your hard drive has nothing to do with it. There is a problem with your backup drive. As far as Time Machine is concerned replacing a drive is no different than buying a new computer. Time Machine will need to make a brand new backup from scratch.
If you have a large enough backup drive this may not be a problem. Otherwise, you may not have sufficient space to maintain a new backup and keep the old one. So, I would suggest under the circumstances that you erase your backup drive, then start a new Time Machine backup from scratch.
Drive Erase
1. Open Disk Utility in your Utilities folder.
2. After Disk Utility loads select the volume you wish to format from the left side list. Click on the Erase tab in the Disk Utility main window.
3. Set the format type to Mac OS Extended (Journaled.) Click on the Erase button and wait until the process has completed.
For additional help with Time Machine: Visit Pondini's Time Machine FAQ for help with all things Time Machine. -
Restore from Time Machine backup is failing
The internal drive on my daughter's iMac has failed for the second time in less than two years. I'm not able to restore from the Time Machine backup. The Time Machine restore process failed last time as well. Not surprisingly I'm now questioning whether Time Machine is an appropriate backup solution.
First question: *Is Time Machine a reliable backup and restore solution?*
- I get no errors whatsoever during backup from Time Machine
- Have yet to successfully be able to restore system (TM is 0 for 2 for us)
Second question: *Is it an issue with my setup?*
Based on the Macs and other items I already had, the setup that the local Apple store recommended to me for backup is what I followed. Here's a summary:
- 4 Macs on a network with Airport Extreme for router/wireless access
- Mac mini with 10TB of external storage has one 2 TB drive setup as a centralized Time Machine drive, which all the Macs on the network connect to
Backups all work with no error messages. Restoring individual files here and there through Time Machine has worked fine. Never really needed, but I tested it a few times from each Mac just to ensure everything was working fine.
Unfortunately, when my daughter's iMac internal drive failed I discovered that the restore not work. First issue was that restoring the system during OS X install was not an option because I was not able to get it to use the network drive. I was told to go ahead and install OS-X and then use the migration assistant, which unfortunately didn't work. Summary of what happened:
- My account on the iMac was successfully restored
- The main account with all the critical data (my daughter's) was created, but none of her data (iTunes music, school work, photos, etc) were restored
- No error message at the end of the restore
I know the Time Machine backup for her account was working as I had specifically checked to make sure that her iTunes music and photos were included in the backup just a week ago. Since the backup was being done to a drive connected to another Mac on the network, her iMac's backup was stored as a sparsebundle. In speaking with Apple support this morning, they had me try to mount the backup by double-clicking on the sparsebundle, which results in an error message indicating that it is corrupt. ARG!
After two failed restores, I'm convinced I need to change the setup either moving to drives directly connected to each Mac (seems like a waste) using Time Machine or switch to another backup tool.
What are your recommendations?It may be helpful for others for me to post the approach I've decided to take, which seems to be working well.
Background:
I've confirmed with an Apple genius and with support, that the likely issue with both of the failed TM restores is that the TM backup was corrupted by the drive failures. Files get corrupted and are backed up to the drive. That is why in both cases it is the specific account that was running (also the highest priority for restore) is the one that is corrupted.
In nearly 3 decades of computing, I've yet to ever need to restore a single file or folder that I accidentally deleted. It's just not a scenario I care about. TM seems to fit this requirement well and has a very cool user experience to do it. Unfortunately, it also seems to have a tendency (0 for 2 in my case) to fail at restoring after drive failure.
Decision: no TM in my back up approach.
My primary need is for backup in case of drive failure. I also have some files that are extremely important that I want redundant backup for.
Decision:
1. ChronoSync for bootable backup clone of drives scheduled monthly and done over the home network. Can easily be triggered manually if there is a big change (SL install, etc) that I want to make sure is included
2. ChronoSync based sync of just critical files to a shared network drive that syncs daily. This is actually a large amount of data and includes family photos (Lightroom catalog and all photos), iTunes libraries, PLEX media library and other user created files.
Pluses:
1. Allows me to keep drives centrally located, which is definitely preferable for me
2. Easy rotation of drives with critical files for offsite storage
3. Over the network sync is fully supported by ChronoSync
4. Easy yet highly configurable UI. Unlike with TM I'm finding I can get the software to do precisely what I want, when I want.
Cons:
1. $40 cost for ChronoSync
I also looked at SuperDuper and Carbon Copy Cloner.
I tried implementing the above first with SuperDuper, but found the setup confusing and the overall execution and sync was not what I expected. For example, SuperDuper encountered some file errors and just halted the sync as a result.
I tried Carbon Copy Cloner next. The setup was more intuitive than SuperDuper; even though the UI is not as polished. I kept the offending files on the drive to see how CCC handled them. It did much better in that it identified the file issues, but completed the sync for the rest to the files on the system. Clear error message at the end with summary information and the ability to look at the details in the log.
Since I wasn't thrilled with either SD or CCC, I decided to check out ChronoSync. For me, it does a very good job of presenting a simple UI with the ability as need arrises to get in to adjust and fine tune the specifics (options, configuration, schedule, etc) to precisely what I want. Scheduling, including sequencing, is very well done. Performance was the best of the three. Full cloning and incremental sync/backups with ChronoSync were the fastest. Not really an issue for me, but still a plus. A big plus for ChronoSync was that it did by far the best job of maintaining file permissions. SuperDuper did the worst. For some reason after all three uses of SuperDuper with the backup approach above many of the original files had user and file permission changes. For example, user name was "Rachel" with Read/Write access. After sync/clone, user became "_unknown" with read/write access. CCC did a better job; though I did have a number of issues when using cloned drive to boot (these were resolved) and with restore some file permissions were not maintained.
I really think Apple (at least retail and genius employees) should be clearer about the limitations and issues with TM. After my first failed restore, I was told it was an unusual and very rare case. I was assured that the approach (including using a network drive was fine). With a second failed restore from TM, it became crystal clear in my opinion that this is not a very rare occurrence; and that there are fundamental aspects of TM that make it susceptible to backup corruption when a drive fails.
TM is a sexy solution for incremental file backup and restore when you accidentally delete a file or folder. If that's what you need, go for it. As part of a backup solution for drive failure? I just don't see the value UNLESS you want to have incremental hourly, daily, weekly, monthly backups that you can use for accidental deletions. The accumulation of all those snapshots ends up taking up a fair bit of space. I was surprised at my actual backup storage needs in my switch to the above approach.
Your needs are likely unique to you, so your mileage may vary. This is just my perspective after a fair bit of pain and a lot of discussion, reading and testing. -
Time Machine backup error (see logs)
I got this error twice today on a Time Machine backup. Disk Util shows the backup disk ("Drifting") to be ok.
Logs:
1/18/08 1:57:16 PM /System/Library/CoreServices/backupd[67912] Backup requested by automatic scheduler
1/18/08 1:57:16 PM /System/Library/CoreServices/backupd[67912] Starting standard backup
1/18/08 1:57:16 PM /System/Library/CoreServices/backupd[67912] Backing up to: /Volumes/Drifting/Backups.backupdb
1/18/08 1:57:20 PM /System/Library/CoreServices/backupd[67912] No pre-backup thinning needed: 573.7 MB requested (including padding), 177.37 GB available
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/.DS_Store to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/.localized to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Address Book Plug-Ins to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Enhancers to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/.DS_Store to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/.pqgyczlrc to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/Adobe to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/Apple to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/BOINC Data to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/BorisFX to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/Canon to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/CG_01demo to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/Digidesign to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/DivX to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/Final Cut Express Support to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/GarageBand to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/GraphicConverter to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/hp to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/HWPrefs to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/iDVD to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/IK Multimedia to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/iMovie to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/iPhoto to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/iSlayer to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/iWork '06 to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/LiveType to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/Logitech to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/Macromedia to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/MindVision to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/Mozilla to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/NetServices to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/Omni Group to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/Path Finder to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/plasq to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/ProApps to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/Shark to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:21 PM /System/Library/CoreServices/backupd[67912] Error: (-43) copying /Library/Application Support/SketchUp 5 to /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Aldebaran/Library/Application Support
1/18/08 1:57:24 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:24 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:25 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:25 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:25 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:26 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:26 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:26 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:27 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:27 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:34 PM com.apple.launchd[1] (com.apple.dyld) Throttling respawn: Will start in 60 seconds
1/18/08 1:57:44 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:44 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:45 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:45 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:45 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:46 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:46 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:46 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:47 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:47 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:47 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:48 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:48 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:48 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:49 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:49 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:50 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:50 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:50 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:51 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:51 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:51 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:52 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:52 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:52 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:52 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:53 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:53 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:53 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:54 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:54 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:54 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:55 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:55 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:55 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:56 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:56 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:56 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:56 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:57 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:57 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:57:57 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:58:12 PM /System/Library/CoreServices/backupd[67912] Bulk set MDS attrs failed.
1/18/08 1:58:12 PM /System/Library/CoreServices/backupd[67912] Copied 6122 files (26.5 MB) from volume Aldebaran.
1/18/08 1:58:12 PM mds[61] ((null))(Error) IndexCI in openindex_filelazy:open file error: 24, 0.indexGroups
1/18/08 1:58:12 PM mds[61] ((null))(Error) IndexGeneral in notify_lowspace:low space for device 234881035 (/Volumes/Drifting/.Spotlight-V100/Store-V1/Stores/16239C4E-774B-42DE-8444-7189 88D09AB8)
1/18/08 1:58:12 PM /System/Library/CoreServices/backupd[67912] MDBackupBegin() returned result (915) > 0, waiting
1/18/08 1:58:12 PM mds[61] (Error) Volume: LOW DISK SPACE device:234881035
1/18/08 1:58:12 PM mds[61] ((null))(Error) IndexCI in openindex_filelazy:open file error: 24, 0.indexGroups
1/18/08 1:58:12 PM mds[61] ((null))(Error) IndexCI in bt_openTrie:open 1.indexCompactDirectory err: 24
1/18/08 1:58:12 PM mds[61] ((null))(Error) IndexCI in bt_openTrie:open 1.indexArrays err: 24
1/18/08 1:58:12 PM mds[61] (/Volumes/Drifting/.Spotlight-V100/Store-V1/Stores/16239C4E-774B-42DE-8444-7189 88D09AB8)(Error) IndexCI in ContentIndexOpenBulk:could not open /Volumes/Drifting/.Spotlight-V100/Store-V1/Stores/16239C4E-774B-42DE-8444-71898 8D09AB8/1.
1/18/08 1:58:13 PM mds[61] ((null))(Error) IndexCI in bt_openTrie:open 0.indexDirectory err: 24
1/18/08 1:58:13 PM mds[61] (/Volumes/Drifting/.Spotlight-V100/Store-V1/Stores/16239C4E-774B-42DE-8444-7189 88D09AB8)(Error) IndexCI in ContentIndexOpenBulk:Failed creating /Volumes/Drifting/.Spotlight-V100/Store-V1/Stores/16239C4E-774B-42DE-8444-71898 8D09AB8/0.
1/18/08 1:58:13 PM mds[61] (/Volumes/Drifting/.Spotlight-V100/Store-V1/Stores/16239C4E-774B-42DE-8444-7189 88D09AB8)(Error) IndexGeneral in SICreateNewIndex:Could not create new content index
1/18/08 1:58:36 PM com.apple.launchd[1] (com.apple.dyld) Throttling respawn: Will start in 58 seconds
1/18/08 1:58:42 PM /System/Library/CoreServices/backupd[67912] MDBackupBegin() returned result (909) > 0, waiting
1/18/08 1:58:42 PM mds[61] ((null))(Error) IndexCI in bt_openTrie:open 0.indexDirectory err: 24
1/18/08 1:58:42 PM mds[61] (/Volumes/Drifting/.Spotlight-V100/Store-V1/Stores/16239C4E-774B-42DE-8444-7189 88D09AB8)(Error) IndexCI in ContentIndexOpenBulk:Failed creating /Volumes/Drifting/.Spotlight-V100/Store-V1/Stores/16239C4E-774B-42DE-8444-71898 8D09AB8/0.
1/18/08 1:58:42 PM mds[61] (/Volumes/Drifting/.Spotlight-V100/Store-V1/Stores/16239C4E-774B-42DE-8444-7189 88D09AB8)(Error) IndexGeneral in SICreateNewIndex:Could not create new content index
1/18/08 1:59:12 PM /System/Library/CoreServices/backupd[67912] MDBackupBegin() returned result (909) > 0, waiting
1/18/08 1:59:12 PM mds[61] ((null))(Error) IndexCI in bt_openTrie:open 0.indexDirectory err: 24
1/18/08 1:59:12 PM mds[61] (/Volumes/Drifting/.Spotlight-V100/Store-V1/Stores/16239C4E-774B-42DE-8444-7189 88D09AB8)(Error) IndexCI in ContentIndexOpenBulk:Failed creating /Volumes/Drifting/.Spotlight-V100/Store-V1/Stores/16239C4E-774B-42DE-8444-71898 8D09AB8/0.
1/18/08 1:59:12 PM mds[61] (/Volumes/Drifting/.Spotlight-V100/Store-V1/Stores/16239C4E-774B-42DE-8444-7189 88D09AB8)(Error) IndexGeneral in SICreateNewIndex:Could not create new content index
1/18/08 1:59:35 PM com.apple.launchd[1] (com.apple.dyld) Throttling respawn: Will start in 60 seconds
1/18/08 1:59:42 PM /System/Library/CoreServices/backupd[67912] MDBackupBegin() returned result (909) > 0, waiting
1/18/08 1:59:42 PM mds[61] ((null))(Error) IndexCI in bt_openTrie:open 0.indexDirectory err: 24
1/18/08 1:59:42 PM mds[61] (/Volumes/Drifting/.Spotlight-V100/Store-V1/Stores/16239C4E-774B-42DE-8444-7189 88D09AB8)(Error) IndexCI in ContentIndexOpenBulk:Failed creating /Volumes/Drifting/.Spotlight-V100/Store-V1/Stores/16239C4E-774B-42DE-8444-71898 8D09AB8/0.
1/18/08 1:59:42 PM mds[61] (/Volumes/Drifting/.Spotlight-V100/Store-V1/Stores/16239C4E-774B-42DE-8444-7189 88D09AB8)(Error) IndexGeneral in SICreateNewIndex:Could not create new content index
1/18/08 1:59:46 PM mds[61] ((null))(Error) IndexCI in openPayload:open err: 24, live.0.indexPostings
1/18/08 1:59:46 PM mds[61] (/.Spotlight-V100/Store-V1/Stores/80E5874D-D344-45BD-B3AE-4269FC662C35)(Error) IndexGeneral in notify_lowspace:low space for device 234881029 (/.Spotlight-V100/Store-V1/Stores/80E5874D-D344-45BD-B3AE-4269FC662C35)
1/18/08 1:59:46 PM mds[61] (Error) Volume: LOW DISK SPACE device:234881029
1/18/08 1:59:46 PM mds[61] ((null))(Error) IndexCI in bt_openTrie:open live.0.indexDirectory err: 24
1/18/08 1:59:46 PM mds[61] ((null))(Error) IndexCI in openPayload:open err: 24, live.2.indexPositions
1/18/08 2:00:12 PM /System/Library/CoreServices/backupd[67912] MDBackupBegin() returned result (909) > 0, waiting
1/18/08 2:00:35 PM com.apple.launchd[1] (com.apple.dyld) Throttling respawn: Will start in 60 seconds
1/18/08 2:00:36 PM mds[61] ((null))(Error) IndexCI in openindex_filelazy:open file error: 24, 0.indexIds
1/18/08 2:00:36 PM mds[61] (/Volumes/Fairytale/.Spotlight-V100/Store-V1/Stores/5D5CBF7A-E4D1-489C-AFF1-624 6F0102A77)(Error) IndexGeneral in notify_lowspace:low space for device 234881026 (/Volumes/Fairytale/.Spotlight-V100/Store-V1/Stores/5D5CBF7A-E4D1-489C-AFF1-624 6F0102A77)
1/18/08 2:00:36 PM mds[61] (Error) Volume: LOW DISK SPACE device:234881026
1/18/08 2:00:36 PM mds[61] ((null))(Error) IndexCI in openindex_filelazy:open file error: 24, live.0.indexIds
1/18/08 2:00:36 PM mds[61] ((null))(Error) IndexCI in openPayload:open err: 24, live.1.indexPostings
1/18/08 2:00:43 PM /System/Library/CoreServices/backupd[67912] MDBackupIndexFile returned -1135 for: /Volumes/Fairytale/Data/iPhoto Library, /Volumes/Drifting/Backups.backupdb/enya/2008-01-18-135716.inProgress/CE1C5E2A-9 DDD-49FA-B42E-BBFA35C1BDF0/Fairytale/Data/iPhoto Library
1/18/08 2:00:43 PM /System/Library/CoreServices/backupd[67912] Aborting backup because MDBackupIndexFile failed
1/18/08 2:00:43 PM /System/Library/CoreServices/backupd[67912] Canceling backup.
1/18/08 2:00:43 PM /System/Library/CoreServices/backupd[67912] Copied 6122 files (68.9 MB) from volume Fairytale.
1/18/08 2:00:43 PM /System/Library/CoreServices/backupd[67912] Copy stage failed with error:11
1/18/08 2:00:43 PM mds[61] (/Volumes/Drifting/.Spotlight-V100/Store-V1/Stores/16239C4E-774B-42DE-8444-7189 88D09AB8)(Error) IndexCI in ContentIndexOpenBulk:No index
1/18/08 2:00:43 PM /System/Library/CoreServices/backupd[67912] Backup failed with error: 11
...can anyone make anything of this? Has been working fine for months.
? Tnx.
blakespotThe subdirectory nesting could be part of the underlying problem. Is there anything on your hard drive nested over 100 levels deep?
Spotlight (any of the stuff in the log starting with "md) is having problems with the files as well as Time Machine. You can force Spotlight to reindex by dragging the drive to the Privacy pane in Spotlight's preferences and then dragging it out again. However, I would be highly doubtful that would solve the problem given Disk Utility's complaint about folders being too deeply nested. If no one comes up with a solution here try asking about this in the Using Mac OS X Leopard forum. -
Time Machine Backup Error. Time machine could not delete the backup disk image .sparsebundle
Time Machine is giving an error message. Time Machine couldnt complete the backup. I am using the Seagate GoFlex Home. Error message states Time Machine could not delete the backup disk image "/volumes/Go Flex Home Backup/iMAc.sparsebundle". Does anybody have any ideas?
I have deleted all files in the Time Machine backup via Windows, Finder, and GoFlex UI.
I think this is your problem.. you need to follow the exact setup from seagate to get TM running again.. please read the manual... I do not have one but I do have another brand of NAS and setting up TM involves a fairly complex set of instructions.. because it is not a native Apple device.. your computer does not recognise it as TM capable.. you need to use the work around the manual will explain.
Maybe you are looking for
-
Temporary table within a package
I'm not sure this is the best way to achieve it, but I'm trying to use a temporary table within my package, but I failed! In my package, my procedure do receive 5 different phone numbers (vTel1 to vTel5) and I need to order them, using data from a ta
-
Advanced certification in ABAP
Hi All I am a ABAP programmer with 3 yrs of ABAP experience and currently working on EDI / IDOC technologies. I wanted to go for ABAP certification but I was advised by many not to do it as exam has got very simple ABAP questions, mainly on Basic ABA
-
when i am updating to 10.7.5, the internet was disconnected, it was partially 83%completed, when I repudiated again, it always fails.what should i do now please?
-
Setting In/Out In Event Viewer
with a clip highlighted in my event viewer and double clicking on the timer to get to a specific point in the clip, Im not getting the right time like say I want to go to 4 seconds I hit 4 0 0 to advance to the seconds and what Im getting is 2:29 ins
-
Keyboard gone crazy - writes 'pl' when stroking 'l' etc - on IdeaPad S10e
Suddenly the keyboard is acting very strange - many of the keys is writing something different than what it should. Even dobbelt (and different) characters appears when stroking the key once. Anyone who have a suggestion how to fix?