From: B 650 on
On 09/05/2010 17:33, Jaimie Vandenbergh wrote:
> On Sun, 09 May 2010 12:30:25 +0100, B 650<dunc.on.usenet(a)gmail.com>
> wrote:
>
>> On 08/05/2010 15:34, David Empson wrote:
>>> Mike Edwards<mike.edwards(a)rocksoft.demon.co.uk> wrote:
>>>
>>> Error -36 when reading a file from a hard drive almost certainly means
>>> you have bad sectors in the content of that file.
>>>
>>
>> Depends where it's being copied to. Since Snow Leopard upgrade, I've
>> started getting pretty regular -36 errors copying to any kind of
>> external drive. It's got so bad, I now do almost all of my copying
>> tasks as root on the command line (that seems to work fine). The
>> problem occurs on laptop and desktop, and with multiple drives, so I've
>> ruled out a common cause (other than my bad mojo of course....)
>
> By "any kind of external drive" what do you mean? USB, firewire, NAS,
> SAN, eSATA, flash, hard drive, iDrive?
>


good point, exhibited on USB hard drive, USB flash, firewire hard drive
& Samba share. Don't have access to any other types of drive

--
D
From: Jaimie Vandenbergh on
On Sun, 09 May 2010 18:33:10 +0100, B 650 <dunc.on.usenet(a)gmail.com>
wrote:

>On 09/05/2010 17:33, Jaimie Vandenbergh wrote:
>> On Sun, 09 May 2010 12:30:25 +0100, B 650<dunc.on.usenet(a)gmail.com>
>> wrote:
>>
>>> On 08/05/2010 15:34, David Empson wrote:
>>>> Mike Edwards<mike.edwards(a)rocksoft.demon.co.uk> wrote:
>>>>
>>>> Error -36 when reading a file from a hard drive almost certainly means
>>>> you have bad sectors in the content of that file.
>>>>
>>>
>>> Depends where it's being copied to. Since Snow Leopard upgrade, I've
>>> started getting pretty regular -36 errors copying to any kind of
>>> external drive. It's got so bad, I now do almost all of my copying
>>> tasks as root on the command line (that seems to work fine). The
>>> problem occurs on laptop and desktop, and with multiple drives, so I've
>>> ruled out a common cause (other than my bad mojo of course....)
>>
>> By "any kind of external drive" what do you mean? USB, firewire, NAS,
>> SAN, eSATA, flash, hard drive, iDrive?
>
>good point, exhibited on USB hard drive, USB flash, firewire hard drive
>& Samba share. Don't have access to any other types of drive

Blimey - that's close enough to everything to count. I was mostly
checking that it wasn't always a USB device, but you do seem to have
some real systemic issues.

Sorry to say I can't help diagnose, apart from "have a look in the
console logs when you next see them for any clues".

I've hardly ever seen any -36 errors, and none for a couple of months
at least, across four Macs that use quite a lot of NAS and USB hard
drive. I think I've only ever seen them with encrypted diskimages on
an AFP-mounted NAS share, when I had two or three copy operations
going at once, most from the host filesystem into the diskimage. Which
is pretty stressy, though still should not fail as it does.

Cheers - Jaimie
--
"Oh drat these computers, they're so naughty and so complex."
-- Marvin the Martian
From: B 650 on
On 09/05/2010 20:07, Jaimie Vandenbergh wrote:
> On Sun, 09 May 2010 18:33:10 +0100, B 650<dunc.on.usenet(a)gmail.com>
> wrote:
>
>> On 09/05/2010 17:33, Jaimie Vandenbergh wrote:
>>> On Sun, 09 May 2010 12:30:25 +0100, B 650<dunc.on.usenet(a)gmail.com>
>>> wrote:
>>>
>>>> On 08/05/2010 15:34, David Empson wrote:
>>>>> Mike Edwards<mike.edwards(a)rocksoft.demon.co.uk> wrote:
>>>>>
>>>>> Error -36 when reading a file from a hard drive almost certainly means
>>>>> you have bad sectors in the content of that file.
>>>>>
>>>>
>>>> Depends where it's being copied to. Since Snow Leopard upgrade, I've
>>>> started getting pretty regular -36 errors copying to any kind of
>>>> external drive. It's got so bad, I now do almost all of my copying
>>>> tasks as root on the command line (that seems to work fine). The
>>>> problem occurs on laptop and desktop, and with multiple drives, so I've
>>>> ruled out a common cause (other than my bad mojo of course....)
>>>
>>> By "any kind of external drive" what do you mean? USB, firewire, NAS,
>>> SAN, eSATA, flash, hard drive, iDrive?
>>
>> good point, exhibited on USB hard drive, USB flash, firewire hard drive
>> & Samba share. Don't have access to any other types of drive
>
> Blimey - that's close enough to everything to count. I was mostly
> checking that it wasn't always a USB device, but you do seem to have
> some real systemic issues.
>

Having googled it death, I'm forming the opinion that it's something to
do with the way I'm setting things up, as no-one else seems to be
getting this in the regularity that I am, and none of the workarounds
I've found are applicable or don't work.

I've just developed a bunch of rsync scripts for bulk copies, and do
other stuff on with cp/mv. I'm replacing my laptop relatively soon, so
with a fresh new machine, I can troubleshoot from the ground up as I set
it up to my tastes.

Cheers

--
D
From: Mike Edwards on

> > Error -36 when reading a file from a hard drive almost certainly means
> > you have bad sectors in the content of that file.
> >
>
> Depends where it's being copied to. Since Snow Leopard upgrade, I've
> started getting pretty regular -36 errors copying to any kind of
> external drive. It's got so bad, I now do almost all of my copying
> tasks as root on the command line (that seems to work fine). The
> problem occurs on laptop and desktop, and with multiple drives, so I've
> ruled out a common cause (other than my bad mojo of course....)

Duplicating file on the same HD or copying to another via FireWire.
From: B 650 on
On 10/05/2010 10:50, Mike Edwards wrote:
>>> Error -36 when reading a file from a hard drive almost certainly means
>>> you have bad sectors in the content of that file.
>>>
>>
>> Depends where it's being copied to. Since Snow Leopard upgrade, I've
>> started getting pretty regular -36 errors copying to any kind of
>> external drive. It's got so bad, I now do almost all of my copying
>> tasks as root on the command line (that seems to work fine). The
>> problem occurs on laptop and desktop, and with multiple drives, so I've
>> ruled out a common cause (other than my bad mojo of course....)
>
> Duplicating file on the same HD or copying to another via FireWire.

hmmm... I've not experienced -36 on an internal disk, but then I do very
little copying internally, so might be coincidence.

--
D