Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Time Machine Backup To Time Capsule

M

moonchilddave

macrumors regular
Original poster
Sep 21, 2009
109
0
Just started having problems with my backups. Time Machine mounts the backup volume and starts backing up. After 3 or 4G it fails with a message that the backup drive is not available. Then, no matter what I do, I keep getting an invalid password whenever I try to backup, even after entering the correct password. It's set to connect via the device password.

Time Capsule is running the latest firmware. I'm on OS X 10.6.7. The Time Capsule is set to join a wireless network (a Cradlepoint MBR1000 router).

I don't think the disk itself is the issue as it's a brand new Samsung 2TB drive - and I have done the fan mod on the Time Capsule. Also, it doesn't appear to be dropping off the network as I can still ping it.

This is driving me nuts!
 
moonchilddave said:
Just started having problems with my backups. Time Machine mounts the backup volume and starts backing up. After 3 or 4G it fails with a message that the backup drive is not available. Then, no matter what I do, I keep getting an invalid password whenever I try to backup, even after entering the correct password. It's set to connect via the device password.

Time Capsule is running the latest firmware. I'm on OS X 10.6.7. The Time Capsule is set to join a wireless network (a Cradlepoint MBR1000 router).

I don't think the disk itself is the issue as it's a brand new Samsung 2TB drive - and I have done the fan mod on the Time Capsule. Also, it doesn't appear to be dropping off the network as I can still ping it.

This is driving me nuts!
Click to expand...

It's the Time Capsule. I've also had problems backing up wirelessly to a TC. I suggest you... (You're not going to like this) ...delete the "sparsebundle" file on the 2TB drive and start over from scratch. You will be doing without a backup until the new one gets finished. Guess what? Chances are you are already doing without a backup because once the destination volume "sparsebundle" gets corrupted, it would take a stroke of luck for you to get everything back if your primary drive crashed. The backups will run just fine until the next time it screws up. Sadly Time Machine backup to Time Capsule is a crap shoot.
 
I don't think it's the "sparsebundle" - as I ran Disk Utility on it and it reported no problems. I did notice that if I rebooted the router, it would work fine again - first time, and then the problem reoccurred. So, I found on another site some information about disabling "Multicast Streams" on the router. So I gave that a shot. Now, I'm not having the password or volume not available problem anymore.

However, it's still only doing a partial backup. It'll only do a few gig and then stops. No errors, but it says the last backup was a few days ago still. If I force it to "Backup Now" the process repeats. So, it's chipping away a few gigs at a time??? Any clues?
 
Here's what I'm seeing in the console log, any ideas? Note, before running this session, I ran a "Repair Permissions" on the main hard drive.

May 16 14:26:51 Daves-MacBook com.apple.backupd[25743]: Starting standard backup
May 16 14:26:51 Daves-MacBook com.apple.backupd[25743]: Attempting to mount network destination using URL: afp://Dave@TimeCapsule.local/data
May 16 14:27:01 Daves-MacBook com.apple.backupd[25743]: Mounted network destination using URL: afp://Dave@TimeCapsule.local/data
May 16 14:27:06 Daves-MacBook com.apple.backupd[25743]: QUICKCHECK ONLY; FILESYSTEM CLEAN
May 16 14:29:08 Daves-MacBook fseventsd[49]: event logs in /Volumes/Time Machine Backups 5/.fseventsd out of sync with volume. destroying old logs. (582 120 1437)
May 16 14:29:09 Daves-MacBook fseventsd[49]: log dir: /Volumes/Time Machine Backups 5/.fseventsd getting new uuid: DC45B3F5-3A90-4E55-A4C7-D923BF53FF11
May 16 14:29:09 Daves-MacBook com.apple.backupd[25743]: Disk image /Volumes/data/Daves-MacBook.sparsebundle mounted at: /Volumes/Time Machine Backups 5
May 16 14:29:09 Daves-MacBook com.apple.backupd[25743]: Backing up to: /Volumes/Time Machine Backups 5/Backups.backupdb
May 16 14:30:20 Daves-MacBook com.apple.backupd[25743]: Event store UUIDs don't match for volume: Macintosh HD
May 16 14:30:20 Daves-MacBook com.apple.backupd[25743]: Waiting for index to be ready (101)
May 16 14:31:36 Daves-MacBook com.apple.backupd[25743]: Node requires deep traversal:/ reason:must scan subdirs|new event db|
May 16 14:38:08 Daves-MacBook com.apple.backupd[25743]: No pre-backup thinning needed: 40.93 GB requested (including padding), 1.33 TB available
May 16 14:46:00 Daves-MacBook com.apple.backupd[25743]: Bulk setting Spotlight attributes failed.
May 16 14:49:08 Daves-MacBook com.apple.backupd[25743]: Stopping backupd to allow ejection of backup destination disk!
May 16 14:49:08 Daves-MacBook mds[43]: (/Volumes/Time Machine Backups 5/.Spotlight-V100/Store-V1/Stores/9F7FABF5-1F59-4031-965C-B83BC26F0975)(Error) IndexGeneral in fd_pwrite:pwrite(/Volumes/Time Machine Backups 5/.Spotlight-V100/Store-V1/Stores/9F7FABF5-1F59-4031-965C-B83BC26F0975/live.2.indexUpdates, o:0, s:89856) err:28
May 16 14:49:08 Daves-MacBook mds[43]: (/Volumes/Time Machine Backups 5/.Spotlight-V100/Store-V1/Stores/9F7FABF5-1F59-4031-965C-B83BC26F0975)(Error) IndexCI in store_stream_flush:store_stream_flush write err:28
May 16 14:49:08 Daves-MacBook mds[43]: (/Volumes/Time Machine Backups 5/.Spotlight-V100/Store-V1/Stores/9F7FABF5-1F59-4031-965C-B83BC26F0975)(Error) IndexCI in indexPrepareForSyncBulk:indexPrepareForSync error: 28, live.2.
May 16 14:49:08 Daves-MacBook mds[43]: (/Volumes/Time Machine Backups 5/.Spotlight-V100/Store-V1/Stores/9F7FABF5-1F59-4031-965C-B83BC26F0975)(Error) IndexCI in _ContentIndexSyncIndexBulk:indexPrepareForSyncBulk error:28
May 16 14:49:08 Daves-MacBook mds[43]: (Error) DiskStore: permission cache (/Volumes/Time Machine Backups 5/.Spotlight-V100/Store-V1/Stores/9F7FABF5-1F59-4031-965C-B83BC26F0975/permStore) write error: 28
May 16 14:49:08 Daves-MacBook fseventsd[49]: gzflush(/Volumes/Time Machine Backups 5/.fseventsd/00000000002ec116) returned -1
May 16 14:49:08 Daves-MacBook fseventsd[49]: disk logger: gzclose() failed (-1/28) removing all old log files in /Volumes/Time Machine Backups 5/.fseventsd
May 16 14:49:08 Daves-MacBook fseventsd[49]: failed to store the uuid in /Volumes/Time Machine Backups 5/.fseventsd/fseventsd-uuid. unlinking it.
May 16 14:49:08 Daves-MacBook KernelEventAgent[45]: tid 00000000 type 'hfs', mounted on '/Volumes/Time Machine Backups 5', from '/dev/disk4s2', low disk, very low disk
May 16 14:49:09 Daves-MacBook com.apple.backupd[25743]: Stopping backup.
May 16 14:49:09 Daves-MacBook com.apple.backupd[25743]: Error: (-34) SrcErr:NO Copying /Users/dave/Documents/Parallels/Windows XP.pvm/harddisk0.hdd/harddisk0.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds to /Volumes/Time Machine Backups 5/Backups.backupdb/Daves-MacBook/2011-05-10-232604.inProgress/A7102112-8AFA-4D39-BF0F-199D9EFFF01B/Macintosh HD/Users/dave/Documents/Parallels/Windows XP.pvm/harddisk0.hdd
May 16 14:49:09 Daves-MacBook com.apple.backupd[25743]: Copied 870 files (3.9 GB) from volume Macintosh HD.
May 16 14:49:09 Daves-MacBook com.apple.backupd[25743]: Copy stage failed with error:28
May 16 14:49:19 Daves-MacBook [0x0-0x81b81b].com.apple.systempreferences[25492]: Failed to send message to backup server: error = -5
 
moonchilddave said:
Here's what I'm seeing in the console log, any ideas? Note, before running this session, I ran a "Repair Permissions" on the main hard drive.

LOG SNIPPED
Click to expand...
Looks like, based on the log file you posted, that there is file system corruption on the TC drive, that is not being detected by the initial diagnostic. This could be easily fixed with a reformat of the TC drive, or by verfying/repairing the TC disk, if only there was an easy way to do that (that I am not aware of).
 
Where are you getting that from (file system corruption)? To me it was looking like a problem with Spotlight or my Parallels virtual machine - but what I do not know.

Although you could be right - I did find and fix problems with the main hard drive after the initial TM backup. I so just don't want to start over.
 
Is the destination disk full? Even if it is full, you should get a message about "deleting old backups" rather than simply failing like this with "low disk" showing up in the console...

Code: 
May 16 14:49:08 Daves-MacBook fseventsd[49]: failed to store the uuid in /Volumes/Time Machine Backups 5/.fseventsd/fseventsd-uuid. unlinking it.
May 16 14:49:08 Daves-MacBook KernelEventAgent[45]: tid 00000000 type 'hfs', mounted on '/Volumes/Time Machine Backups 5', from '/dev/disk4s2', low disk, very low disk
May 16 14:49:09 Daves-MacBook com.apple.backupd[25743]: Stopping backup.

Then I noticed you are backing up windows (Parallels) stuff?

Code: 
May 16 14:49:09 Daves-MacBook com.apple.backupd[25743]: Error: (-34) SrcErr:NO Copying /Users/dave/Documents/Parallels/Windows XP.pvm/harddisk0.hdd/harddisk0.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds to /Volumes/Time Machine Backups 5/Backups.backupdb/Daves-MacBook/2011-05-10-232604.inProgress/A7102112-8AFA-4D39-BF0F-199D9EFFF01B/Macintosh HD/Users/dave/Documents/Parallels/Windows XP.pvm/harddisk0.hdd

I would not include other OS stuff in a Time Capsule backup. Well, that's not entirely true. I have a small amount of Windows stuff in Crossover but the files are sitting on Macintosh HD in a folder called C Drive and I've never gotten errors about backing them up.
 
r0k said:
Is the destination disk full? Even if it is full, you should get a message about "deleting old backups" rather than simply failing like this with "low disk" showing up in the console...
Click to expand...

Not even close - the Time Capsule has 1.3TB available (it's a 2 TB disk). As for backing up my Parallels machine - I've never had a problem with that in the past (and no, the VM wasn't running during the backup).
 
moonchilddave said:
Where are you getting that from (file system corruption)? To me it was looking like a problem with Spotlight or my Parallels virtual machine - but what I do not know.

Although you could be right - I did find and fix problems with the main hard drive after the initial TM backup. I so just don't want to start over.
Click to expand...
These lines in the log:
Code: 
May 16 14:49:08 Daves-MacBook mds[43]: (/Volumes/Time Machine Backups 5/.Spotlight-V100/Store-V1/Stores/9F7FABF5-1F59-4031-965C-B83BC26F0975)(Error) IndexGeneral in fd_pwritewrite(/Volumes/Time Machine Backups 5/.Spotlight-V100/Store-V1/Stores/9F7FABF5-1F59-4031-965C-B83BC26F0975/live.2.indexUpdates, o:0, s:89856) err:28
May 16 14:49:08 Daves-MacBook mds[43]: (/Volumes/Time Machine Backups 5/.Spotlight-V100/Store-V1/Stores/9F7FABF5-1F59-4031-965C-B83BC26F0975)(Error) IndexCI in store_stream_flush:store_stream_flush write err:28
May 16 14:49:08 Daves-MacBook mds[43]: (/Volumes/Time Machine Backups 5/.Spotlight-V100/Store-V1/Stores/9F7FABF5-1F59-4031-965C-B83BC26F0975)(Error) IndexCI in indexPrepareForSyncBulk:indexPrepareForSync error: 28, live.2.
The Spotlight engine is encountering an I/O error when attempting to write its metadata index. 99% of the time, this is caused by file system errors.
 
wrldwzrd89 said:
These lines in the log:
Code: 
May 16 14:49:08 Daves-MacBook mds[43]: (/Volumes/Time Machine Backups 5/.Spotlight-V100/Store-V1/Stores/9F7FABF5-1F59-4031-965C-B83BC26F0975)(Error) IndexGeneral in fd_pwritewrite(/Volumes/Time Machine Backups 5/.Spotlight-V100/Store-V1/Stores/9F7FABF5-1F59-4031-965C-B83BC26F0975/live.2.indexUpdates, o:0, s:89856) err:28
May 16 14:49:08 Daves-MacBook mds[43]: (/Volumes/Time Machine Backups 5/.Spotlight-V100/Store-V1/Stores/9F7FABF5-1F59-4031-965C-B83BC26F0975)(Error) IndexCI in store_stream_flush:store_stream_flush write err:28
May 16 14:49:08 Daves-MacBook mds[43]: (/Volumes/Time Machine Backups 5/.Spotlight-V100/Store-V1/Stores/9F7FABF5-1F59-4031-965C-B83BC26F0975)(Error) IndexCI in indexPrepareForSyncBulk:indexPrepareForSync error: 28, live.2.
The Spotlight engine is encountering an I/O error when attempting to write its metadata index. 99% of the time, this is caused by file system errors.
Click to expand...

Thanks for the explanation - this seems like it's most likely the answer. Guess I'm starting over.
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back