Any log of finder errors

[Dan Shoop]

At 1:00 PM -0600 3/16/07, Scott Ribe wrote:
>  > Not that I'm aware.
>
>Thanks. I figure if it's there, you would know it. Oh well.
>
>>  Moreover your assessment of the error is probably wrong, it's merely
>>  un unexpected IO Error. It could be from a variety of things. I'd
>>  fsck the disk first as volume corruption is more likely than drive
>>  failure.
>
>In 20 years I have never, ever, seen a Mac give an IO error from drive
>corruption or indeed any source other than failing hardware--my
>understanding is it's a pretty low-level error, meaning the drive was unable
>to read the block, verify the checksum, and pass the bits out. Of course
>I've also only seen a very small number of IO errors so I don't have a big
>statistical base to work from, but experience (and understanding of what it
>means) lead me to think of "error -36" as meaning "impending meltdown". *NO*
>other file system error code points so directly to hardware; anything other
>error and I'd take several more steps before starting to price drives ;-)

IO errors could occur at any spot in the IO stack. For instance you 
could have had a firewire glich. These are not uncommon when in TDM.
-- 

-dhan

------------------------------------------------------------------------
Dan Shoop                                                   AIM: iWiring
Systems & Networks Architect                      http://www.ustsvs.com/
shoop at iwiring.net                                http://www.iwiring.net/
1-714-363-1174

"The wise man doesn't give the right answers, he poses the right
questions." -- Claude Levi-Strauss

------------------------------------------------------------------------

iWiring provides systems and networks support for Mac OS X, unix, and
Open Source application technologies at affordable rates.