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

abnospam

macrumors regular
Original poster
Jul 17, 2008
210
0
Hi Everyone - I have searched everywhere and can't find any help.

This is my situation. I have my TM backup to an SMB windows share and its been working fine for months. Two things changed recently: a) I installed Windows 7 on my windows box and b) I installed that TM update that provides greater reliability. Backups worked fine for weeks after both of these changes, but just this week backups failed and TM wanted to create a new backup. I tried to recreate a new backup, but it keeps failing with errors below. When I try to run a verify disk on the sparsebundle (with disk util) I always get errors, but of course, I can not fix the errors when the sparsebundle is on an SMB. I am currently running a chkdsk on the windows drive, but I don't think its damaged.

PHP:
8/18/10 11:39:02 PM	com.apple.backupd[800]	Copied 18.3 GB of 20.3 GB, 164128 of 640370 items
8/18/10 11:39:41 PM	com.apple.backupd[800]	Copied 164129 files (18.4 GB) from volume IntelSSD160.
8/18/10 11:39:43 PM	com.apple.backupd[800]	No pre-backup thinning needed: 828.7 MB requested (including padding), 578.34 GB available
8/18/10 11:39:51 PM	com.apple.backupd[800]	Copied 379 files (7.3 MB) from volume IntelSSD160.
8/18/10 11:39:51 PM	kernel	hfs: node=4844 fileID=4 volume=Backup of MYMBP device=/dev/disk3s2
8/18/10 11:39:51 PM	kernel	hfs: Runtime corruption detected on Backup of MYMBP, fsck will be forced on next mount.
8/18/10 11:39:51 PM	kernel	hfs: cat_delete() failed to delete thread record on volume Backup of MYMBP
8/18/10 11:39:51 PM	kernel	hfs: Runtime corruption detected on Backup of MYMBP, fsck will be forced on next mount.
8/18/10 11:39:51 PM	kernel	hfs: node=4844 fileID=4 volume=Backup of MYMBP device=/dev/disk3s2
8/18/10 11:39:51 PM	kernel	hfs: Runtime corruption detected on Backup of MYMBP, fsck will be forced on next mount.
8/18/10 11:39:51 PM	com.apple.backupd[800]	Starting post-backup thinning
8/18/10 11:39:51 PM	com.apple.backupd[800]	No post-back up thinning needed: no expired backups exist
8/18/10 11:39:51 PM	com.apple.backupd[800]	Backup completed successfully.
8/18/10 11:39:57 PM	com.apple.backupd[800]	Ejected Time Machine disk image.
8/18/10 11:39:57 PM	com.apple.backupd[800]	Ejected Time Machine network volume.
8/19/10 12:31:04 AM	com.apple.backupd[1120]	Starting standard backup
8/19/10 12:31:04 AM	com.apple.backupd[1120]	Attempting to mount network destination using URL: smb://GUEST:@192.168.1.107/TM
8/19/10 12:31:07 AM	com.apple.backupd[1120]	Mounted network destination using URL: smb://GUEST:@192.168.1.107/TM
8/19/10 12:31:19 AM	com.apple.backupd[1120]	QUICKCHECK ONLY; FILESYSTEM DIRTY
8/19/10 12:31:19 AM	com.apple.backupd[1120]	Runtime corruption detected on /Volumes/TM-1/MYMBP_58b035f1b3d1.sparsebundle (fsck_hfs -q termination status: 3)
8/19/10 12:31:19 AM	com.apple.backupd[1120]	Attempting to mount network destination using URL: smb://GUEST:@192.168.1.107/TM

Anyone encounter this? I essentially can not use TM right now. Could the TM update and/or windows 7 upgrade be a contributor? Any help is much appreciated.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.