Forum - Main Forums : Mac Music

Today's Active Topics · FORUM INDEX · Search Forum · Who's Online? · FAQs/Help · Calendar

Main Forums >> Mac Music

Print Thread

Pages: 1

action711

Joined: 07/01/03
Posts: 327
Loc: United Kingdom

error code 36 new

#346916 - 31/08/06 02:12 PM

I seem to be getting a lot of error 36 occurences on my second internal SATA drive, where I keep all my samples.

It happens when I read or open or copy the files. Some samples are fine, but ones that I've created recently seem to be more prone to it.

Does anyone have any ideas?

I'm thinking it could be a physical fault on the disk, as it's more new stuff that mabe written to the same part of the disk after I've erased the old corrupted files.

I'm swapping the disk anyway, I have a spare.

I ran Disk Warrior on it but it all came up fine>?>

--------------------
check out my tunes - www.myspace.com/jamesjackson711

Post Extras:

bugsstar

Joined: 16/07/05
Posts: 136
Loc: Belgium

Re: error code 36 new

[Re: action711]
#347110 - 31/08/06 09:29 PM

it mostly is a fault in the hard drive, no software can fix it.
you have the correct tools.

Post Extras:

Bronnie

Joined: 24/02/05
Posts: 3
Loc: Sydney, Australia

Re: error code 36 new

[Re: bugsstar]
#347116 - 31/08/06 09:46 PM

Hi

Try to Apple support website and do a search for error code 36.

kind regards
B

Post Extras:

action711

Joined: 07/01/03
Posts: 327
Loc: United Kingdom

Re: error code 36 new

[Re: action711]
#347469 - 01/09/06 05:05 PM

I did already, it's an I/O error (bummers), whatever that means. Thinking about it, sounds like a problem with accessing it on the disk.

I've changed the disk to a brand new jobbie and tried to recreate the problems and everything is sweet, so it looks like it was a physical problem after all.

Anyone want to buy a semi buggered Hard drive?

--------------------
check out my tunes - www.myspace.com/jamesjackson711

Post Extras:

Mel David
member

Joined: 01/05/00
Posts: 76
Loc: Sydney

Re: error code 36 [Re: action711]
#347494 - 01/09/06 06:16 PM

Quote action711:

... I've erased the old corrupted files.

It's best not to delete any corrupt files you find as it may be a bad sector. If you delete it, then the bad sector would just get used again andpossibly corrupt other data.

Best thing to do with corrupted files is to rename them, for example call it "Bad Sector 001" and move it to a folder on the top level of that hard disk called "Bad Sectors".
You can hide the "Bad Sectors" folder if you want using a utility on OS X Developer Tools.

My secondary HD has bad sectors on it but I've already found all the bad sectors on the disk. I don't get any more read/write errors on this HD, which is over 4 years old now, but it still works fine.

Post Extras:

Pages: 1

Extra Information
1 registered and 16 anonymous users are browsing this forum. Moderator: David Etheridge, James Perrett, zenguitar, Martin Walker, Forum Admin, Hugh Robjohns, Zukan, Frank Eleveld, Will Betts,	Forum Permissions You cannot start new topics You cannot reply to topics HTML is disabled UBBCode is enabled	Rating: Thread views: 1305