Error messages during backup
40 views
Skip to first unread message
davenik
May 1, 2010, 3:02:35 PM5/1/10
to backmyfruitup
Hello,
I recently had a backup fail, looked in the console, and saw several
errors similar to this one:
> 5/1/10 2:58:01 AM kernel disk3s2: 0x16 (UNDEFINED).
After that failed backup, I ran a backup manually and it worked. Then
I used Disk Utility to verify the sparsebundle image on my Droboshare
- but it found no errors.
Things appear to be working, but I get a dozen or more UNDEFINED
errors in the console each time Time Machine runs a backup.
Are these safe to ignore?
Should I try repairing the disk with DiskWarrior?
Thanks,
Dave
--
You received this message because you are subscribed to the Google Groups "backmyfruitup" group.
To post to this group, send email to backmy...@googlegroups.com.
To unsubscribe from this group, send email to backmyfruitu...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/backmyfruitup?hl=en.
I recently had a backup fail, looked in the console, and saw several
errors similar to this one:
> 5/1/10 2:58:01 AM kernel disk3s2: 0x16 (UNDEFINED).
After that failed backup, I ran a backup manually and it worked. Then
I used Disk Utility to verify the sparsebundle image on my Droboshare
- but it found no errors.
Things appear to be working, but I get a dozen or more UNDEFINED
errors in the console each time Time Machine runs a backup.
Are these safe to ignore?
Should I try repairing the disk with DiskWarrior?
Thanks,
Dave
--
You received this message because you are subscribed to the Google Groups "backmyfruitup" group.
To post to this group, send email to backmy...@googlegroups.com.
To unsubscribe from this group, send email to backmyfruitu...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/backmyfruitup?hl=en.
Jon Stevens
May 1, 2010, 6:21:05 PM5/1/10
to backmy...@googlegroups.com
I'd look into repairing the disk on the machine you are backing up.
Also backups only tend to fail for me when I close my laptop during a backup. (duh)
jon
davenik
May 12, 2010, 9:58:53 AM5/12/10
to backmyfruitup
jon,
Plot thickens: after repairing my disk with Disk Utility connected via
firewire, I was unable to get the Drobo to get out of standby mode
when connected to either the DroboShare or my Mac via USB. I contacted
Drobo support, and they asked for a diagnostic file. They called back
and had me RMA the unit.
The new Drobo arrived and I immediately ran a backup via Wi-Fi/bmfu. I
continued to see the "kernel disk4s2: 0x16 (UNDEFINED)" errors. I
connected the Drobo to my Mac via firewire; Disk Utility again
reported damage, which it fixed. Another Wi-Fi backup, more
(UNDEFINED) errors. So then I ran Disk Utility *and* Diskwarrior over
firewire. Another Wi-Fi backup, again with (UNDEFINED) errors - but
only 3, which is fewer than before.
Time Machine thinks the backups are successful. So my questions is,
can I ignore these errors or are they a sign, at this point, of
something wrong with the physical disks in the Drobo? If the latter, I
have two disks - is there any way to figure out which of the two is
bad, assuming both aren't? I realize I'm straying a few kiloparsecs
off the backupmyfruit reservation, so if I need to take these
questions elsewhere, that's fine. I'd be more than happy to ignore the
error, but I suspect that would be unwise.
Plot thickens: after repairing my disk with Disk Utility connected via
firewire, I was unable to get the Drobo to get out of standby mode
when connected to either the DroboShare or my Mac via USB. I contacted
Drobo support, and they asked for a diagnostic file. They called back
and had me RMA the unit.
The new Drobo arrived and I immediately ran a backup via Wi-Fi/bmfu. I
continued to see the "kernel disk4s2: 0x16 (UNDEFINED)" errors. I
connected the Drobo to my Mac via firewire; Disk Utility again
reported damage, which it fixed. Another Wi-Fi backup, more
(UNDEFINED) errors. So then I ran Disk Utility *and* Diskwarrior over
firewire. Another Wi-Fi backup, again with (UNDEFINED) errors - but
only 3, which is fewer than before.
Time Machine thinks the backups are successful. So my questions is,
can I ignore these errors or are they a sign, at this point, of
something wrong with the physical disks in the Drobo? If the latter, I
have two disks - is there any way to figure out which of the two is
bad, assuming both aren't? I realize I'm straying a few kiloparsecs
off the backupmyfruit reservation, so if I need to take these
questions elsewhere, that's fine. I'd be more than happy to ignore the
error, but I suspect that would be unwise.
Jon Stevens
May 12, 2010, 11:22:33 AM5/12/10
to backmy...@googlegroups.com
My backups complete successfully without errors.
jon
jon
Toby
May 12, 2010, 11:54:50 AM5/12/10
to backmy...@googlegroups.com
Since you are checking the disk with Disk Utility, I assume you
formatted the Drobo as HFS+. Droboshare doesnt fully support HFS+ and
seems to nuke journaling among other issues. That could be the cause
of the disk errors. Reference the first line of BMFU Setup Guide v2:
"#1. For the best results, you should be using ext3 as your filesystem
on your Drobo. There is a caveat in that you won't be able to run Disk
Utility on your Drobo unless you purchase a $40 piece of software. I
also haven't tested this.
NTFS and FAT32 do not support symbolic links properly, so they won't
work. The Linux implementation of HFS+ (what is running on the
DroboShare) has a bug with deleting files as well as with resource
forks. So, the only way to free up deleted space on your Drobo for
files that have been deleted with BackMyFruitUp, is to run Disk
Utility.
If you are only using your Drobo for storing TimeMachine backups, you
are pretty safe with HFS+. I use this solution because I don't delete
files on my Drobo and I only use it for TM. "
Note that while formatted as ext3, you can use a linux live cd to fsck
ext3 if needed. I forget if fsck is available on droboshare itself.
- Strydre
formatted the Drobo as HFS+. Droboshare doesnt fully support HFS+ and
seems to nuke journaling among other issues. That could be the cause
of the disk errors. Reference the first line of BMFU Setup Guide v2:
"#1. For the best results, you should be using ext3 as your filesystem
on your Drobo. There is a caveat in that you won't be able to run Disk
Utility on your Drobo unless you purchase a $40 piece of software. I
also haven't tested this.
NTFS and FAT32 do not support symbolic links properly, so they won't
work. The Linux implementation of HFS+ (what is running on the
DroboShare) has a bug with deleting files as well as with resource
forks. So, the only way to free up deleted space on your Drobo for
files that have been deleted with BackMyFruitUp, is to run Disk
Utility.
If you are only using your Drobo for storing TimeMachine backups, you
are pretty safe with HFS+. I use this solution because I don't delete
files on my Drobo and I only use it for TM. "
Note that while formatted as ext3, you can use a linux live cd to fsck
ext3 if needed. I forget if fsck is available on droboshare itself.
- Strydre
davenik
May 12, 2010, 9:02:17 PM5/12/10
to backmyfruitup
Thanks Strydre.
Well, if I can ignore UNDEFINED errors (and I only see them when I
look in the log), I'm good.
But if it's true that problems will crop up with HFS+, I can move to
ext3 - it just will be painful 'cause the backup file is large.
Jon says "If you are only using your Drobo for storing TimeMachine
backups, you are pretty safe with HFS+." That pretty much describes
me, though I am putting some SuperDuper clones on it, too.
Worth reformatting and starting over with ext3?
Best,
Well, if I can ignore UNDEFINED errors (and I only see them when I
look in the log), I'm good.
But if it's true that problems will crop up with HFS+, I can move to
ext3 - it just will be painful 'cause the backup file is large.
Jon says "If you are only using your Drobo for storing TimeMachine
backups, you are pretty safe with HFS+." That pretty much describes
me, though I am putting some SuperDuper clones on it, too.
Worth reformatting and starting over with ext3?
Best,
Jon Stevens
May 12, 2010, 9:34:03 PM5/12/10
to backmy...@googlegroups.com
The issue is with delete of files over AFP.
If you are only adding files to your drobo and never deleting files
over AFP, you should be fine.
I use hfs+
jon
If you are only adding files to your drobo and never deleting files
over AFP, you should be fine.
I use hfs+
jon
davenik
May 13, 2010, 2:29:09 PM5/13/10
to backmyfruitup
Jon,
I think from what you are saying is that I can continue to use hfs+
and ignore those (UNDEFINED) errors - as I noted, Time Machine seems
to think the backups are successful - it's only when I neurotically
peek into the console logs that I see the errors.
I just made a small contribution to your project from a different
(sputnik) email - really appreciate that you'e doing this.
I think from what you are saying is that I can continue to use hfs+
and ignore those (UNDEFINED) errors - as I noted, Time Machine seems
to think the backups are successful - it's only when I neurotically
peek into the console logs that I see the errors.
I just made a small contribution to your project from a different
(sputnik) email - really appreciate that you'e doing this.
Jon Stevens
May 13, 2010, 2:33:36 PM5/13/10
to backmy...@googlegroups.com
What I'm saying is that I don't see those errors myself. I'd try a
restore to ensure that things are backing up and restoring
successfully. Maybe all of this will go away with the new version of
netatalk... we shall see.
I really really appreciate the donation. Keeps the motivation to stay
up till 2am working on this stuff going. =)
jon
restore to ensure that things are backing up and restoring
successfully. Maybe all of this will go away with the new version of
netatalk... we shall see.
I really really appreciate the donation. Keeps the motivation to stay
up till 2am working on this stuff going. =)
jon
davenik
May 20, 2010, 10:42:37 AM5/20/10
to backmyfruitup
Jon,
OK, I followed your advice and tried a restore, saved the file to the
desktop. When I tried to open it, I got a message that the file was
corrupt and couldn't be opened.
Since I had already run Disk Utility and Disk Warrior repairs on the
backup image, I decided the safest thing at this point would be to
reformat the Drobo and start clean.
So I did. And I ran a backup of my disk (about 380 GB). And it looked
like it would actually complete in less than 24 hours, which seemed
like a good sign (the original backup, on the Drobo that I RMA'ed,
took close to 3 days and nights). And there were absolutely no
(UNDEFINED) errors! Yay!
And it did complete! But then, on the next backup attempt that it
initiated, it failed to mount the disk image, then found the
filesystem dirty, renamed the sparsebundle, and displayed a dialog
that said "Time Machine completed a verification of your backups. To
improve reliability Time Machine must create a new backup for you." I
clicked "Backup Now", but then the console reported that it was unable
to delete the old backup image, and Time Machine exited. At that
point, if I tried a backup, it would keep failing.
I thought perhaps Time Machine failed because it "remembered" the
backups I had done on the old, defective Drobo, and that somehow that
was throwing it off. (Complete speculation on my part.) I started from
scratch again - reformatting the Drobo and reinstalling Backmyfruitup.
And in the Time Machine preference pane, I selected None first (to
clear its record of past backups) before selecting DroboCapsule. I
added DroboCapsule to Spotlight's privacy panel to bake sure it
wouldn't get indexed. I also reduced to a bare minimum other
applications running while Time Machine was working.
And the same thing happened. Backup completed successfully the first
time, but afterwards I go the same series of errors culminating in
Time Machine asking to create a new backup. (This time though, I did
not request a new backup, so I preserved the existing sparsebundle.)
Here is the last part of the log:
5/19/10 2:07:38 PM com.apple.backupd[8527] Copied 84.7 GB of 355.7 GB,
549831 of 2548935 items
5/19/10 3:07:43 PM com.apple.backupd[8527] Copied 96.6 GB of 355.7 GB,
718209 of 2548935 items
5/19/10 3:32:35 PM com.apple.backupd[8527] Error: (-8084) SrcErr:YES
Copying /Users/dave/Library/Mail/SearchHistory.plist to (null)
5/19/10 4:07:44 PM com.apple.backupd[8527] Copied 111.5 GB of 355.7
GB, 773785 of 2548935 items
5/19/10 5:07:45 PM com.apple.backupd[8527] Copied 136.0 GB of 355.7
GB, 776587 of 2548935 items
5/19/10 6:07:46 PM com.apple.backupd[8527] Copied 163.4 GB of 355.7
GB, 779342 of 2548935 items
5/19/10 7:07:47 PM com.apple.backupd[8527] Copied 190.3 GB of 355.7
GB, 783460 of 2548935 items
5/19/10 8:07:50 PM com.apple.backupd[8527] Copied 216.7 GB of 355.7
GB, 788095 of 2548935 items
5/19/10 9:07:51 PM com.apple.backupd[8527] Copied 242.8 GB of 355.7
GB, 791377 of 2548935 items
5/19/10 10:07:51 PM com.apple.backupd[8527] Copied 266.9 GB of 355.7
GB, 793888 of 2548935 items
5/19/10 11:07:52 PM com.apple.backupd[8527] Copied 294.3 GB of 355.7
GB, 793888 of 2548935 items
5/20/10 12:08:01 AM com.apple.backupd[8527] Copied 320.2 GB of 355.7
GB, 796870 of 2548935 items
5/20/10 12:18:47 AM com.apple.backupd[8527] Copied 797369 files (321.1
GB) from volume sputnik.
5/20/10 12:20:56 AM com.apple.backupd[8527] No pre-backup thinning
needed: 3.73 GB requested (including padding), 15.67 TB available
5/20/10 12:20:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:21:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:22:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:23:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:24:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:25:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:26:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:27:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:28:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:29:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:30:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:31:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:32:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:33:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:34:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:35:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:36:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:37:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:38:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:39:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:40:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:41:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:42:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:43:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:44:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:45:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:46:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:47:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:48:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:49:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:50:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:51:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:52:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:53:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:54:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:55:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:56:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:57:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:58:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:59:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:00:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:01:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:02:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:03:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:04:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:05:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:06:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:07:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:08:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:09:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:10:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:11:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:12:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:13:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:14:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:15:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:16:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:17:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:18:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:19:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:20:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:21:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:22:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:23:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:24:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:25:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:26:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:27:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:28:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:29:16 AM com.apple.backupd[8527] Copied 0 bytes of 1021.9
MB, 0 of 455 items
5/20/10 1:44:59 AM com.apple.backupd[8527] Copied 16236 files (828.0
MB) from volume sputnik.
5/20/10 1:47:32 AM com.apple.backupd[8527] Starting post-backup
thinning
5/20/10 1:47:32 AM com.apple.backupd[8527] No post-back up thinning
needed: no expired backups exist
5/20/10 1:47:33 AM com.apple.backupd[8527] Backup completed
successfully.
5/20/10 1:47:41 AM com.apple.backupd[8527] Ejected Time Machine disk
image.
5/20/10 1:47:45 AM com.apple.backupd[8527] Ejected Time Machine
network volume.
5/20/10 2:01:00 AM com.apple.backupd[13203] Starting standard backup
5/20/10 2:01:00 AM com.apple.backupd[13203] Attempting to mount
network destination using URL: afp://;AUTH=No%20User%20Authent@DroboCapsule._afpovertcp._tcp.local/DroboCapsule
5/20/10 2:01:01 AM com.apple.backupd[13203] Mounted network
destination using URL: afp://;AUTH=No%20User%20Authent@DroboCapsule._afpovertcp._tcp.local/DroboCapsule
5/20/10 2:01:01 AM com.apple.backupd[13203] Warning: Destination /
Volumes/DroboCapsule-1 does not support TM Lock Stealing
5/20/10 2:01:01 AM com.apple.backupd[13203] Warning: Destination /
Volumes/DroboCapsule-1 does not support Server Reply Cache
5/20/10 2:01:14 AM com.apple.backupd[13203] QUICKCHECK ONLY;
FILESYSTEM CLEAN
5/20/10 2:01:16 AM com.apple.backupd[13203] Failed to mount disk
image /Volumes/DroboCapsule-1/starts-macbook-
pro-121_64b9e8b7c5ea.sparsebundle (DIHLDiskImageAttach returned: 109)
5/20/10 2:01:16 AM com.apple.backupd[13203] Mount failed... waiting 60
seconds and trying again.
5/20/10 2:01:17 AM com.apple.backupd[13203] Ejected Time Machine
network volume.
5/20/10 2:02:17 AM com.apple.backupd[13203] Attempting to mount
network destination using URL: afp://;AUTH=No%20User%20Authent@DroboCapsule._afpovertcp._tcp.local/DroboCapsule
5/20/10 2:02:17 AM com.apple.backupd[13203] Mounted network
destination using URL: afp://;AUTH=No%20User%20Authent@DroboCapsule._afpovertcp._tcp.local/DroboCapsule
5/20/10 2:02:17 AM com.apple.backupd[13203] Warning: Destination /
Volumes/DroboCapsule-1 does not support TM Lock Stealing
5/20/10 2:02:17 AM com.apple.backupd[13203] Warning: Destination /
Volumes/DroboCapsule-1 does not support Server Reply Cache
5/20/10 2:02:20 AM com.apple.backupd[13203] QUICKCHECK ONLY;
FILESYSTEM DIRTY
5/20/10 2:02:20 AM com.apple.backupd[13203] Runtime corruption
detected on /Volumes/DroboCapsule-1/starts-macbook-
pro-121_64b9e8b7c5ea.sparsebundle (fsck_hfs -q termination status: 3)
5/20/10 2:02:21 AM com.apple.backupd[13203] Network destination
already mounted at: /Volumes/DroboCapsule-1
5/20/10 2:02:21 AM com.apple.backupd[13203] Warning: Destination /
Volumes/DroboCapsule-1 does not support TM Lock Stealing
5/20/10 2:02:21 AM com.apple.backupd[13203] Warning: Destination /
Volumes/DroboCapsule-1 does not support Server Reply Cache
5/20/10 2:02:21 AM com.apple.backupd[13203] Backup verification failed
for image /Volumes/DroboCapsule-1/starts-macbook-
pro-121_64b9e8b7c5ea.sparsebundle!
5/20/10 2:02:21 AM com.apple.backupd[13203] Moved previous backup
image to /Volumes/DroboCapsule-1/starts-macbook-
pro-121_64b9e8b7c5ea_2010-05-20-020221.sparsebundle
5/20/10 6:55:38 AM com.apple.backupd[13203] Recovery backup declined
by user.
5/20/10 6:55:38 AM com.apple.backupd[13203] Backup canceled.
5/20/10 6:55:39 AM com.apple.backupd[13203] Ejected Time Machine
network volume.
At this point, there is a file called starts-macbook-
pro-121_64b9e8b7c5ea_2010-05-20-020221.sparsebundle on DroboCapsule,
but when I attempt to mount it, I get a warning stating that there are
"no mountable filesystems".
One thing I've noticed these past two backup attempts, that I don't
recall from prior backups, is that the volume is referred to as
DroboCapsule-1, not DroboCapsule. But in the Finder it appears simply
as "DroboCapsule".
Any idea what might be going on? I feel like I'm so close!
Best,
Dave
On May 13, 11:33 am, Jon Stevens <latch...@gmail.com> wrote:
> What I'm saying is that I don't see those errors myself. I'd try a
> restore to ensure that things are backing up and restoring
> successfully. Maybe all of this will go away with the new version of
> netatalk... we shall see.
OK, I followed your advice and tried a restore, saved the file to the
desktop. When I tried to open it, I got a message that the file was
corrupt and couldn't be opened.
Since I had already run Disk Utility and Disk Warrior repairs on the
backup image, I decided the safest thing at this point would be to
reformat the Drobo and start clean.
So I did. And I ran a backup of my disk (about 380 GB). And it looked
like it would actually complete in less than 24 hours, which seemed
like a good sign (the original backup, on the Drobo that I RMA'ed,
took close to 3 days and nights). And there were absolutely no
(UNDEFINED) errors! Yay!
And it did complete! But then, on the next backup attempt that it
initiated, it failed to mount the disk image, then found the
filesystem dirty, renamed the sparsebundle, and displayed a dialog
that said "Time Machine completed a verification of your backups. To
improve reliability Time Machine must create a new backup for you." I
clicked "Backup Now", but then the console reported that it was unable
to delete the old backup image, and Time Machine exited. At that
point, if I tried a backup, it would keep failing.
I thought perhaps Time Machine failed because it "remembered" the
backups I had done on the old, defective Drobo, and that somehow that
was throwing it off. (Complete speculation on my part.) I started from
scratch again - reformatting the Drobo and reinstalling Backmyfruitup.
And in the Time Machine preference pane, I selected None first (to
clear its record of past backups) before selecting DroboCapsule. I
added DroboCapsule to Spotlight's privacy panel to bake sure it
wouldn't get indexed. I also reduced to a bare minimum other
applications running while Time Machine was working.
And the same thing happened. Backup completed successfully the first
time, but afterwards I go the same series of errors culminating in
Time Machine asking to create a new backup. (This time though, I did
not request a new backup, so I preserved the existing sparsebundle.)
Here is the last part of the log:
5/19/10 2:07:38 PM com.apple.backupd[8527] Copied 84.7 GB of 355.7 GB,
549831 of 2548935 items
5/19/10 3:07:43 PM com.apple.backupd[8527] Copied 96.6 GB of 355.7 GB,
718209 of 2548935 items
5/19/10 3:32:35 PM com.apple.backupd[8527] Error: (-8084) SrcErr:YES
Copying /Users/dave/Library/Mail/SearchHistory.plist to (null)
5/19/10 4:07:44 PM com.apple.backupd[8527] Copied 111.5 GB of 355.7
GB, 773785 of 2548935 items
5/19/10 5:07:45 PM com.apple.backupd[8527] Copied 136.0 GB of 355.7
GB, 776587 of 2548935 items
5/19/10 6:07:46 PM com.apple.backupd[8527] Copied 163.4 GB of 355.7
GB, 779342 of 2548935 items
5/19/10 7:07:47 PM com.apple.backupd[8527] Copied 190.3 GB of 355.7
GB, 783460 of 2548935 items
5/19/10 8:07:50 PM com.apple.backupd[8527] Copied 216.7 GB of 355.7
GB, 788095 of 2548935 items
5/19/10 9:07:51 PM com.apple.backupd[8527] Copied 242.8 GB of 355.7
GB, 791377 of 2548935 items
5/19/10 10:07:51 PM com.apple.backupd[8527] Copied 266.9 GB of 355.7
GB, 793888 of 2548935 items
5/19/10 11:07:52 PM com.apple.backupd[8527] Copied 294.3 GB of 355.7
GB, 793888 of 2548935 items
5/20/10 12:08:01 AM com.apple.backupd[8527] Copied 320.2 GB of 355.7
GB, 796870 of 2548935 items
5/20/10 12:18:47 AM com.apple.backupd[8527] Copied 797369 files (321.1
GB) from volume sputnik.
5/20/10 12:20:56 AM com.apple.backupd[8527] No pre-backup thinning
needed: 3.73 GB requested (including padding), 15.67 TB available
5/20/10 12:20:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:21:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:22:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:23:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:24:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:25:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:26:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:27:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:28:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:29:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:30:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:31:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:32:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:33:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:34:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:35:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:36:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:37:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:38:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:39:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:40:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:41:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:42:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:43:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:44:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:45:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:46:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:47:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:48:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:49:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:50:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:51:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:52:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:53:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:54:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:55:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:56:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:57:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:58:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 12:59:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:00:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:01:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:02:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:03:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:04:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:05:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:06:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:07:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:08:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:09:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:10:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:11:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:12:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:13:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:14:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:15:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:16:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:17:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:18:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:19:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:20:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:21:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:22:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:23:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:24:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:25:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:26:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:27:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:28:56 AM com.apple.backupd[8527] Waiting for index to be
ready (100)
5/20/10 1:29:16 AM com.apple.backupd[8527] Copied 0 bytes of 1021.9
MB, 0 of 455 items
5/20/10 1:44:59 AM com.apple.backupd[8527] Copied 16236 files (828.0
MB) from volume sputnik.
5/20/10 1:47:32 AM com.apple.backupd[8527] Starting post-backup
thinning
5/20/10 1:47:32 AM com.apple.backupd[8527] No post-back up thinning
needed: no expired backups exist
5/20/10 1:47:33 AM com.apple.backupd[8527] Backup completed
successfully.
5/20/10 1:47:41 AM com.apple.backupd[8527] Ejected Time Machine disk
image.
5/20/10 1:47:45 AM com.apple.backupd[8527] Ejected Time Machine
network volume.
5/20/10 2:01:00 AM com.apple.backupd[13203] Starting standard backup
5/20/10 2:01:00 AM com.apple.backupd[13203] Attempting to mount
network destination using URL: afp://;AUTH=No%20User%20Authent@DroboCapsule._afpovertcp._tcp.local/DroboCapsule
5/20/10 2:01:01 AM com.apple.backupd[13203] Mounted network
destination using URL: afp://;AUTH=No%20User%20Authent@DroboCapsule._afpovertcp._tcp.local/DroboCapsule
5/20/10 2:01:01 AM com.apple.backupd[13203] Warning: Destination /
Volumes/DroboCapsule-1 does not support TM Lock Stealing
5/20/10 2:01:01 AM com.apple.backupd[13203] Warning: Destination /
Volumes/DroboCapsule-1 does not support Server Reply Cache
5/20/10 2:01:14 AM com.apple.backupd[13203] QUICKCHECK ONLY;
FILESYSTEM CLEAN
5/20/10 2:01:16 AM com.apple.backupd[13203] Failed to mount disk
image /Volumes/DroboCapsule-1/starts-macbook-
pro-121_64b9e8b7c5ea.sparsebundle (DIHLDiskImageAttach returned: 109)
5/20/10 2:01:16 AM com.apple.backupd[13203] Mount failed... waiting 60
seconds and trying again.
5/20/10 2:01:17 AM com.apple.backupd[13203] Ejected Time Machine
network volume.
5/20/10 2:02:17 AM com.apple.backupd[13203] Attempting to mount
network destination using URL: afp://;AUTH=No%20User%20Authent@DroboCapsule._afpovertcp._tcp.local/DroboCapsule
5/20/10 2:02:17 AM com.apple.backupd[13203] Mounted network
destination using URL: afp://;AUTH=No%20User%20Authent@DroboCapsule._afpovertcp._tcp.local/DroboCapsule
5/20/10 2:02:17 AM com.apple.backupd[13203] Warning: Destination /
Volumes/DroboCapsule-1 does not support TM Lock Stealing
5/20/10 2:02:17 AM com.apple.backupd[13203] Warning: Destination /
Volumes/DroboCapsule-1 does not support Server Reply Cache
5/20/10 2:02:20 AM com.apple.backupd[13203] QUICKCHECK ONLY;
FILESYSTEM DIRTY
5/20/10 2:02:20 AM com.apple.backupd[13203] Runtime corruption
detected on /Volumes/DroboCapsule-1/starts-macbook-
pro-121_64b9e8b7c5ea.sparsebundle (fsck_hfs -q termination status: 3)
5/20/10 2:02:21 AM com.apple.backupd[13203] Network destination
already mounted at: /Volumes/DroboCapsule-1
5/20/10 2:02:21 AM com.apple.backupd[13203] Warning: Destination /
Volumes/DroboCapsule-1 does not support TM Lock Stealing
5/20/10 2:02:21 AM com.apple.backupd[13203] Warning: Destination /
Volumes/DroboCapsule-1 does not support Server Reply Cache
5/20/10 2:02:21 AM com.apple.backupd[13203] Backup verification failed
for image /Volumes/DroboCapsule-1/starts-macbook-
pro-121_64b9e8b7c5ea.sparsebundle!
5/20/10 2:02:21 AM com.apple.backupd[13203] Moved previous backup
image to /Volumes/DroboCapsule-1/starts-macbook-
pro-121_64b9e8b7c5ea_2010-05-20-020221.sparsebundle
5/20/10 6:55:38 AM com.apple.backupd[13203] Recovery backup declined
by user.
5/20/10 6:55:38 AM com.apple.backupd[13203] Backup canceled.
5/20/10 6:55:39 AM com.apple.backupd[13203] Ejected Time Machine
network volume.
At this point, there is a file called starts-macbook-
pro-121_64b9e8b7c5ea_2010-05-20-020221.sparsebundle on DroboCapsule,
but when I attempt to mount it, I get a warning stating that there are
"no mountable filesystems".
One thing I've noticed these past two backup attempts, that I don't
recall from prior backups, is that the volume is referred to as
DroboCapsule-1, not DroboCapsule. But in the Finder it appears simply
as "DroboCapsule".
Any idea what might be going on? I feel like I'm so close!
Best,
Dave
On May 13, 11:33 am, Jon Stevens <latch...@gmail.com> wrote:
> What I'm saying is that I don't see those errors myself. I'd try a
> restore to ensure that things are backing up and restoring
> successfully. Maybe all of this will go away with the new version of
> netatalk... we shall see.
CrastinatorPro
May 20, 2010, 11:01:11 AM5/20/10
to backmyfruitup
Apple recently issued an update to TM. I installed it and it
immediately scanned my sparse bundle and declared it corrupt with the
same message you quote. It was unable to delete it so I reformatted
and started again (in doing so I fixed a number of problems that were
haunting me).
It sounds like you got the same treatment, but just after you had
reformatted and started again. In other words the message
I just had a quick look on Apple Support for details of the update,
but couldn't find anything (strange!).
> network destination using URL: ...
>
> read more »
immediately scanned my sparse bundle and declared it corrupt with the
same message you quote. It was unable to delete it so I reformatted
and started again (in doing so I fixed a number of problems that were
haunting me).
It sounds like you got the same treatment, but just after you had
reformatted and started again. In other words the message
"Time Machine completed a verification of your backups. To improve
reliability Time Machine must create a new backup for you."
may not have anything to do with your previous problem.
reliability Time Machine must create a new backup for you."
I just had a quick look on Apple Support for details of the update,
but couldn't find anything (strange!).
>
> read more »
Jon Stevens
May 20, 2010, 12:32:53 PM5/20/10
to backmy...@googlegroups.com
Face it... 10.6.3 with BMFU is probably not going to work right now.
I'm also not quite sure what you mean by 'saved the file to the
Desktop'. What file?
fyi...
http://www.earthtimes.org/articles/show/data-robotics-develops-seamless-integration,1309783.shtml
I've got netatalk 2.1 compiled on my DShare, but things aren't quite
working right yet. netatalk 2.1.1 is coming out soon which fixes a non
TM related bug that I've been seeing and I've been waiting for that.
That said, the procedure for using BMFU is going to have to change...
You are going to have to setup defined size AFP partitions cause the
sparsebundles with 10.6.3 auto grow to the size of the partition. That
is how the DroboFS works. I've got to spend a bit of time figuring out
how they create those partitions. BMFU may be out of luck if it isn't
possible with the Drobo/DroboShare.
jon
I'm also not quite sure what you mean by 'saved the file to the
Desktop'. What file?
fyi...
http://www.earthtimes.org/articles/show/data-robotics-develops-seamless-integration,1309783.shtml
I've got netatalk 2.1 compiled on my DShare, but things aren't quite
working right yet. netatalk 2.1.1 is coming out soon which fixes a non
TM related bug that I've been seeing and I've been waiting for that.
That said, the procedure for using BMFU is going to have to change...
You are going to have to setup defined size AFP partitions cause the
sparsebundles with 10.6.3 auto grow to the size of the partition. That
is how the DroboFS works. I've got to spend a bit of time figuring out
how they create those partitions. BMFU may be out of luck if it isn't
possible with the Drobo/DroboShare.
jon
davenik
May 20, 2010, 1:48:40 PM5/20/10
to backmyfruitup
Jon,
OK - phew. It's not just me.
By "saved the file to the desktop" - I did a restore from my previous
Time Machine backup (which was throwing the (UNDEFINED) errors) to
check its integrity, which you suggested doing. While Time Machine let
me grab an old file from its archive and restore the file to my
current desktop, I was unable to open it - it was corrupt. That's when
I decided to reformat and start over.
Hope things work up for BMFU!
Best,
Dave
On May 20, 9:32 am, Jon Stevens <latch...@gmail.com> wrote:
> Face it... 10.6.3 with BMFU is probably not going to work right now.
>
> I'm also not quite sure what you mean by 'saved the file to the
> Desktop'. What file?
>
> fyi...http://www.earthtimes.org/articles/show/data-robotics-develops-seamle...
OK - phew. It's not just me.
By "saved the file to the desktop" - I did a restore from my previous
Time Machine backup (which was throwing the (UNDEFINED) errors) to
check its integrity, which you suggested doing. While Time Machine let
me grab an old file from its archive and restore the file to my
current desktop, I was unable to open it - it was corrupt. That's when
I decided to reformat and start over.
Hope things work up for BMFU!
Best,
Dave
On May 20, 9:32 am, Jon Stevens <latch...@gmail.com> wrote:
> Face it... 10.6.3 with BMFU is probably not going to work right now.
>
> I'm also not quite sure what you mean by 'saved the file to the
> Desktop'. What file?
>
Reply all
Reply to author
Forward
0 new messages