Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Time Machine problems

14 views
Skip to first unread message

Daniel Cohen

unread,
Sep 13, 2012, 4:07:53 AM9/13/12
to
Had some Time Machine problems recently. backupd report is given
below.(times not listed, it covers at least one automatic and one manual
attempt)

Does this indicate something seriously wrong? My external drive
(mains-powered) behaved well under Snow Leopard, but I upgraded recently
to Mountain Lion, and though the drive seems to work there's a lot more
activity than before. I am wondering if the drive is coincidentally just
beginning to fail, or if there are issues with ML and my drive.



Backup failed with error: 2
Error: (22) setxattr for key:com.apple.backupd.HostUUID
path:/Volumes/Wells/Backups.backupdb/DelphiMac size:37
Error: (22) setxattr for key:com.apple.backupd.HostUUID
path:/Volumes/Wells/Backups.backupdb/DelphiMac size:37
Backing up to: /Volumes/Wells/Backups.backupdb
Starting manual backup
Backup failed with error: 2
Error: (22) setxattr for key:com.apple.backupd.HostUUID
path:/Volumes/Wells/Backups.backupdb/DelphiMac size:37
Error: (22) setxattr for key:com.apple.backupd.HostUUID
path:/Volumes/Wells/Backups.backupdb/DelphiMac size:37
Backing up to: /Volumes/Wells/Backups.backupdb
Starting automatic backup
Backup completed successfully.
Post-back up thinning complete: 1 expired backups removed
Deleted /Volumes/Wells/Backups.backupdb/DelphiMac/2012-09-12-071412 (336
KB)
Error: Error Domain=NSOSStatusErrorDomain Code=-50 "The operation
couldn't be completed. (OSStatus error -50.)" (paramErr: error in user
parameter list) deleting backup:
/Volumes/Wells/Backups.backupdb/DelphiMac/2012-09-13-073328.inProgress/7
06E671A-769F-42E9-8D98-B344883746E5
Starting post-backup thinning


--
<http://www.decohen.com>
The Labyrinth of the Heart: Changed Myths for Changing Lives
book and e-book <http://www.decohen.com/labyrinth>
Send e-mail to the Reply-To address, not the From address.

Salvatore

unread,
Sep 13, 2012, 9:24:29 AM9/13/12
to
["Followup-To:" header set to comp.sys.mac.hardware.storage.]
On 2012-09-13, Daniel Cohen <dcohe...@talktalk.net> wrote:
> Had some Time Machine problems recently. backupd report is given
> below.(times not listed, it covers at least one automatic and one manual
> attempt)
>
> Does this indicate something seriously wrong? My external drive
> (mains-powered) behaved well under Snow Leopard, but I upgraded recently
> to Mountain Lion, and though the drive seems to work there's a lot more
> activity than before. I am wondering if the drive is coincidentally just
> beginning to fail, or if there are issues with ML and my drive.

I'm using Mountain Lion and the Time Machine backups don't appear to be
any slower. Mount the drive and check it for errors using Disk Utility.

--
Blah blah bleh...
GCS/CM d(-)@>-- s+:- !a C++$ UBL++++$ L+$ W+++$ w M++ Y++ b++

Daniel Cohen

unread,
Sep 13, 2012, 11:56:28 AM9/13/12
to
Disk Utility at first had some trouble recognising the drive. It is
partitioned into three, and DU showed drives with generic names disk1s2
and so on instead of their given names. But when I finally got the
partition to show with its given name, no errors were shown.

And I have just had a good TM backup. Backups haven't been slow. When I
said "more activity than before" I meant that the disk seemed to spin up
and down (I could hear a click and a whir) more often than before.

Kevin McMurtrie

unread,
Sep 14, 2012, 12:10:48 AM9/14/12
to
In article <1kqcrxc.1gfw3t6tgejcwN%dcohe...@talktalk.net>,
The file structures used by Time Machine are very complex and they
frequently trigger bugs in the OS. Use Disk Utility to repair the
backup disk. If there's a Time Machine sparsebundle on it, repair that
too.

If you can't get that to work, hold down the Option key and select
"Verify Backups" from the Time Machine icon in the system menu. I don't
know if that performs repairs so I'd use it as a last resort. Failing
verification causes your backup to be locked as read-only, and therefore
unrepairable. You'll have to start over or remove the lock using
command line developer tools.
--
I will not see posts from Google because I must filter them as spam
0 new messages