Prev: .pdf question
Next: -1080 Error and Interrupted TM Backup (Typo/Correction)
From: Nick Naym on 9 Apr 2010 10:30
I initiated a TM backup on a brand-new volume. It's been running for a
couple of days (100 GB out of 300 GB completed).

Unfortunately, my system began to behave strangely earlier -- Safari would
freeze whenever I tried to print from it; Grab would freeze whenever I tried
to save a snapshot. I force-quit those apps repeatedly, but upon retrying,
the results were the same. I then tried to force quit (i.e., "Relaunch")
Finder (that has worked for me occasionally in the past), but couldn't: It
(Finder) appeared to have actually quit (vanished from the Force Quit
window; my Desktop vanished as well), and when I attempted to open it as I
would any other app (via its Dock icon), I got the dialog:

"The application Finder.app can't be opened.

-10810"

Ultimately, I had to do a hard restart (via the power button) to get things
working again.

My questions are this:

1. I never experienced a Finder-can't-be-opened error before. What could be
going on?

2. TM is now running again. However, it seems to have lost the entire 100 GB
of data it had backed up: As of this moment, it's showing 900 MB of 300 GB
completed. I thought TM recovers (though often somewhat slowly) from
interruptions. Am I wrong?




--
iMac (27", 3.06 GHz Intel Core 2 Duo, 4 GB RAM, 1 TB HDD) � OS X (10.6.3)

From: Steven Fisher on 9 Apr 2010 12:35
In article <C7E4B24F.585EE%nicknaym@_remove_this_gmail.com.invalid>,
Nick Naym <nicknaym@_remove_this_gmail.com.invalid> wrote:

> 1. I never experienced a Finder-can't-be-opened error before. What could be
> going on?

I believe -10810 occurs because something has spawned processes out of
control. I'd run Activity Monitor in case it happens again, so you can
see what's being spawned.

> 2. TM is now running again. However, it seems to have lost the entire 100 GB
> of data it had backed up: As of this moment, it's showing 900 MB of 300 GB
> completed. I thought TM recovers (though often somewhat slowly) from
> interruptions. Am I wrong?

As far as I know, that's right.


Steve
From: Nick Naym on 9 Apr 2010 12:50
In article sdfisher-2158A2.09353609042010(a)shawnews.vc.shawcable.net, Steven
Fisher at sdfisher(a)spamcop.net wrote on 4/9/10 12:35 PM:

> In article <C7E4B24F.585EE%nicknaym@_remove_this_gmail.com.invalid>,
> Nick Naym <nicknaym@_remove_this_gmail.com.invalid> wrote:
>
>> 1. I never experienced a Finder-can't-be-opened error before. What could be
>> going on?
>
> I believe -10810 occurs because something has spawned processes out of
> control. I'd run Activity Monitor in case it happens again, so you can
> see what's being spawned.
>

OK.

>> 2. TM is now running again. However, it seems to have lost the entire 100 GB
>> of data it had backed up: As of this moment, it's showing 900 MB of 300 GB
>> completed. I thought TM recovers (though often somewhat slowly) from
>> interruptions. Am I wrong?
>
> As far as I know, that's right.
>

I'm wrong, or TM should've recovered? If the latter, any idea why it didn't?


>
> Steve

--
iMac (27", 3.06 GHz Intel Core 2 Duo, 4 GB RAM, 1 TB HDD) � OS X (10.6.3)

From: Steven Fisher on 9 Apr 2010 12:59
In article <C7E4D317.58632%nicknaym@_remove_this_gmail.com.invalid>,
Nick Naym <nicknaym@_remove_this_gmail.com.invalid> wrote:

> I'm wrong, or TM should've recovered? If the latter, any idea why it didn't?

Oh, to clarify: Time Machine should recover. Eventually.

If it's really stalled and not just slow, I'd open the Console and see
if it backupd or mds is generating an errors. Do you have any custom
Spotlight importers installed? Perhaps one of them is causing problems.


Steve
From: Nick Naym on 9 Apr 2010 13:32
In article sdfisher-23ADFD.09590609042010(a)shawnews.vc.shawcable.net, Steven
Fisher at sdfisher(a)spamcop.net wrote on 4/9/10 12:59 PM:

> In article <C7E4D317.58632%nicknaym@_remove_this_gmail.com.invalid>,
> Nick Naym <nicknaym@_remove_this_gmail.com.invalid> wrote:
>
>> I'm wrong, or TM should've recovered? If the latter, any idea why it didn't?
>
> Oh, to clarify: Time Machine should recover. Eventually.
>
> If it's really stalled and not just slow, I'd open the Console and see
> if it backupd or mds is generating an errors.


AFAICT, the only "unusual" entries were the following (and others of the
same type -- i.e., details of the items in parenthesis vary, but everything
else is the same):

CoreEndianFlipData: error -4940 returned for rsrc type open (id 128, length
12, native = no)

com.apple.backupd[504]: SystemFlippers: didn't consume all data for vers ID
1 (pBase = 0x100196700, p = 0x100196733, pEnd = 0x100196734)

CoreEndianFlipData: error -4940 returned for rsrc type FREF (id 129, length
7, native = no)



> Do you have any custom
> Spotlight importers installed? Perhaps one of them is causing problems.

What is a "Spotlight importer?"




--
iMac (27", 3.06 GHz Intel Core 2 Duo, 4 GB RAM, 1 TB HDD) � OS X (10.6.3)

 |  Next  |  Last
Pages: 1 2
Prev: .pdf question
Next: -1080 Error and Interrupted TM Backup (Typo/Correction)