Prev: iCal meeting
Next: it is interesting to play texas hold'em poker on line
From: Nick Naym on 21 Oct 2009 00:42
In article C7026761.493F2%nicknaym@[remove_this].gmail.com, Nick Naym at
nicknaym@[remove_this].gmail.com wrote on 10/19/09 6:58 PM:

....
....
>
> It's pretty clear that something is seriously hosed, and that I'll need to
> bite the bullet and use DU to erase my TM volume. But before I do, I'm
> wondering if the following system log entries offer any insight:
>
> authexec[4289]: executing
> /System/Library/ScriptingAdditions/StandardAdditions.osax/Contents/MacOS/uid
>
> and
>
> /usr/sbin/ocspd[4870]: starting
>
>
> (There are a whole slew of other strange entries, but these two jumped out
> at me, as I don't recall ever seeing anything like them before.)
>

I was planning on erasing my TM drive today -- it had been "Finishing
backup..." for 24 hours. However, when I checked my machine this morning,
apparently TM actually finished the backup.

Curious, I later ran another backup, just to see if everything was back to
"normal." It failed. But this time TM actually _told_ me it failed (rather
than just stalling till I quit):

Copy stage failed with error:11
Backup failed with error: 11

I haven't a clue what an "error 11" TM backup failure means, nor could I
find anything when I did a quick Google, beyond folks who had similar "error
11" failures who also didn't know, and solved the problem by erasing the TM
drive and starting over. But scrolling back through the system log to the
beginning of this failed backup, I found this:


Starting standard backup

Backing up to: /Volumes/Seagate Barracuda/Backups.backupdb

Event store UUIDs don't match for volume: Nick's HD

Node requires deep traversal:/
reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustabl
e|


So it appears that there's a TM database _somewhere_ that is hosed.

<sigh>...I sure wish there was something to be learned from this whole
episode (which began immediately after I did the E&I).


--
iMac (24", 2.8 GHz Intel Core 2 Duo, 2GB RAM, 320 GB HDD) � OS X (10.5.8)

From: P. Sture on 23 Oct 2009 15:51
In article <C704096C.494FF%nicknaym@[remove_this].gmail.com>,
Nick Naym <nicknaym@[remove_this].gmail.com> wrote:

> I was planning on erasing my TM drive today -- it had been "Finishing
> backup..." for 24 hours. However, when I checked my machine this morning,
> apparently TM actually finished the backup.

<snip>

At this point Nick, I seriously think that you are best off calling it a
draw, erasing/reformatting your backup disk and starting again. Credit
where it's due for perseverance, but there are times when you have to
give up and move on.

--
Paul Sture
From: Nick Naym on 23 Oct 2009 20:08
In article paul.nospam-64A54F.21512723102009(a)pbook.sture.ch, P. Sture at
paul.nospam(a)sture.ch wrote on 10/23/09 3:51 PM:

> In article <C704096C.494FF%nicknaym@[remove_this].gmail.com>,
> Nick Naym <nicknaym@[remove_this].gmail.com> wrote:
>
>> I was planning on erasing my TM drive today -- it had been "Finishing
>> backup..." for 24 hours. However, when I checked my machine this morning,
>> apparently TM actually finished the backup.
>
> <snip>
>
> At this point Nick, I seriously think that you are best off calling it a
> draw, erasing/reformatting your backup disk and starting again. Credit
> where it's due for perseverance, but there are times when you have to
> give up and move on.


I absolutely agree...it's just that I'd really like to understand what
exactly has been going on -- what those error messages mean, why I am
getting them, what's actually "broken," and why I suddenly began to run into
problems after doing a completely clean reinstallation.

--
iMac (24", 2.8 GHz Intel Core 2 Duo, 2GB RAM, 320 GB HDD) � OS X (10.5.8)

 | 
Pages: 1
Prev: iCal meeting
Next: it is interesting to play texas hold'em poker on line