This discussion is archived
1859 Views 6 Replies Latest reply: Aug 13, 2009 10:45 AM by The hatter
Currently Being ModeratedJul 11, 2009 7:21 PM (in response to RUNYYFan)Hi-
How is the problem drive interfaced?
What make is the housing?
I/O errors are often due to a failed controller or inferior/failed cabling.
Though the hard drive itself may be healthy, the housings controller may be failing/failed.G4AGP(450)Sawtooth, 2GHz 7447A, 2GB, Raptor/SE16/Firmtek, 9800 Pro/ATI Silencer, Mac OS X (10.5.5), DVR-116, 23"ACD, Ratoc USB2.0, QCam Ultra, 520W PSU, iPhone 3Gs, iPod Classic
Currently Being ModeratedJul 12, 2009 4:42 AM (in response to japamac)Hi!
The interface is a FireWire 400.
The housing is an OWC Mercury Elite-AL Pro aluminum case.Mac Pro and MBP, Mac OS X (10.5.7), MP: 320GB, 5 GB RAM, 7200 GC; MBP: 75 GB, 1 GB RAM
Currently Being ModeratedJul 12, 2009 5:08 AM (in response to RUNYYFan)Hi-
Try it with USB 2.0.
If that works, try a new FW400 cable.
If problems continue, the controller could be bad.
Finally, try the drive in a different housing to confirm the drives function.
If a SATA drive, could even try it internally.
I like the OWC housings (I have several) but, as with any other hardware, they can fail.G4AGP(450)Sawtooth, 2GHz 7447A, 2GB, Raptor/SE16/Firmtek, 9800 Pro/ATI Silencer, Mac OS X (10.5.5), DVR-116, 23"ACD, Ratoc USB2.0, QCam Ultra, 520W PSU, iPhone 3Gs, iPod Classic
Currently Being ModeratedJul 13, 2009 1:20 PM (in response to japamac)Worked fine connected as USB. Tried another FireWire and it worked.
Thanks for your help!Mac Pro and MBP, Mac OS X (10.5.7), MP: 320GB, 5 GB RAM, 7200 GC; MBP: 75 GB, 1 GB RAM
Currently Being ModeratedAug 13, 2009 9:53 AM (in response to RUNYYFan)I was getting the same "-36" error while trying to backup to a Lacie firewire external drive.
I had a lot of people telling me to re-format, erase, reinstall, run utility programs ... yada, yada, yada.
First off, test to see if it is the connection type (firewire). I reconnected the offending external drive via USB, restarted the drive and ... BINGO! ... all transfers went perfectly.
Once i knew it was the firewire connection and not the drive itself i simply unplugged my iSight camera (the only other firewire device connected to my machine), reconnected my external drive via firewire and the problem is now corrected.
Firewire buses seem to be very finicky things ... i would suggest eliminating all firewire devices from the machine (except, of course, the external drive you're trying to transfer to) and see if the problem goes away.
Like i said, i simply unplugged my iSight camera and the transfer to my external drive went perfect and my transfer rates went from an average of 4MB/sec to over 19MB/sec.
P.S. BTW - prior to the error and after i corrected the error by unplugging the iSight camera, my internal and external drives all checked out 100% on Disk Utility, Disk Warrior and TechTool Pro.Dual 2 gig G5, 6 gigs RAM: Dual 1.33ghz G4, Mac OS X (10.4.10)
Currently Being ModeratedAug 13, 2009 10:45 AM (in response to Paul Williams3)SoftRAID found that any consumer electronics should never share a FW bus with hard drives due to problems, interference, lack of good cable shielding.
The yada is to make sure there were no file or directory errors after you rule out hardware like case, ports etc. And some brands of FW don't have problems.
There are $39 Firewire shielded Isolator cables on the market, but little demand.Mac Pro 8800GT WD VelociRaptor 10k, Mac OS X (10.5.7), Windows 7 Core i7 920 9800GTX APC RS1500