Dr_Zoom

Q: External HD over Firewire Disconnects Suddenly, any Solutions?

Hi

 

I'm using a MacBook Pro (Mid 2010) with a connected external harddisk (G-Tech G-Drive mini) via Firewire. While I have no problems with the disk connected to my Mac Pro, I have sudden disconnects on my MacBook Pro.

 

The harddisk is attached directly to the computer. Using USB, the disk is working fine without any problems (but of course slower than with FW800).

 

Is this a known problem? Are there any solutions to avoid this disconnects?

 

best regards

Tobias

MacBook Pro, OS X Mountain Lion

Posted on Aug 9, 2012 8:02 AM

Close

Q: External HD over Firewire Disconnects Suddenly, any Solutions?

  • All replies
  • Helpful answers

  • by Courcoul,

    Courcoul Aug 9, 2012 8:08 AM in response to Dr_Zoom
    Level 6 (14,193 points)
    Aug 9, 2012 8:08 AM in response to Dr_Zoom

    Check the cable. This sound like a connectivity issue.

  • by Dr_Zoom,

    Dr_Zoom Dr_Zoom Aug 9, 2012 8:42 AM in response to Courcoul
    Level 1 (0 points)
    Aug 9, 2012 8:42 AM in response to Courcoul

    I use the same cable on the Mac Pro as on the MacBook Pro. For the Mac Pro it is working, but for the MacBook Pro it is not. So I think it can not be the cable.

     

    On the MacBook Pro I also get this messages in the log:

    FireWire (OHCI) Lucent ID 5901 built-in: 591 bus resets in last 3 minutes.

     

    The message is repeating. On the Mac Pro, I never get this message (using the same cable).

  • by Courcoul,

    Courcoul Aug 9, 2012 8:40 AM in response to Dr_Zoom
    Level 6 (14,193 points)
    Aug 9, 2012 8:40 AM in response to Dr_Zoom

    No idea. I've been using FW since it first came out replacing SCSI way back then; have 12 FW drives or optical burners. And have never had "disappearing drives". But a friend did have a Mac with a finicky (damaged, I would call it) USB port that would suddenly disconnect like you describe.

     

    Only thing I can think of is if you are running some sort of virtualization software, like VMware Fusion, Parallels Desktop, Oracle VirtualBox. The virtualizer may be "grabbing" the device and taking it away from Mac OS X.

  • by Linc Davis,

    Linc Davis Linc Davis Aug 9, 2012 1:01 PM in response to Dr_Zoom
    Level 10 (208,037 points)
    Applications
    Aug 9, 2012 1:01 PM in response to Dr_Zoom

    Is it bus-powered or AC-powered? If bus, try AC.

  • by Dr_Zoom,

    Dr_Zoom Dr_Zoom Aug 10, 2012 5:41 AM in response to Linc Davis
    Level 1 (0 points)
    Aug 10, 2012 5:41 AM in response to Linc Davis

    I will try this. Bought an AC adapter, would be then this this port which can not provide enough power for the drive. The drive is working fine on the MacBook Pro using the USB port, but of course not that fast as expected.

  • by Courcoul,

    Courcoul Aug 10, 2012 7:33 AM in response to Dr_Zoom
    Level 6 (14,193 points)
    Aug 10, 2012 7:33 AM in response to Dr_Zoom

    If USB can power it (0.5A max, as per spec), it will be a piece of cake for FW (1.5A). And your Mac has native and fully compliant FW ports, in comparison to new 2012 owners who must use a TB to FW adapter that has nowhere near the current capacity of the FW spec. But i still get this gut feeling that the problem is physical. Do you have any other FW cable you can try?

     

    Also, can try to do an SMC and a PRAM/NVRAM reset, in case the port's flaky due to to corruption of the firmware config. Occurs every so often on the USB ports ("my right USB port don't work!", lots of threads like that), might conceivably occur to FW too.

  • by Dr_Zoom,

    Dr_Zoom Dr_Zoom Aug 10, 2012 8:14 AM in response to Courcoul
    Level 1 (0 points)
    Aug 10, 2012 8:14 AM in response to Courcoul

    This is interesting. I didn't know that FireWire has that high specification for power.

     

    I actually did an SMC reset. Or at least I think I did one. But there was no feedback about the reset, so I wasn't really sure if I actually did reset the SMC or not.

     

    I followed this guide: http://support.apple.com/kb/HT3964

     

    But, owning this MacBook Pro (Mid 2010), I wasn't sure if I should follow the instructions using the keyboard combination, or if I really can remove the battery physically. So I tried the instructions with the keys to press and the power button.

     

    Beside of the power supply, I also bought a second FW cable. As soon they arrive I will try both.

  • by Courcoul,

    Courcoul Aug 10, 2012 8:51 AM in response to Dr_Zoom
    Level 6 (14,193 points)
    Aug 10, 2012 8:51 AM in response to Dr_Zoom

    Your 2010 model is already Unibody/non-replaceable-battery, so the key sequence procedure is the one to use. I've heard rumors that some users get flashy lights in the connector and/or the charge indicators, but mine has been totally silent when I do the deed. As for the PRAM/NVRAM reset, exercise your fingers and press simultaneously Option-Command-P-R prior to the startup chime. Even Apple recommends you hold down the keys for at least 3-4 chime repeats to make sure all the crud is flushed out. Hope it helps.

  • by Dr_Zoom,

    Dr_Zoom Dr_Zoom Aug 10, 2012 9:27 AM in response to Courcoul
    Level 1 (0 points)
    Aug 10, 2012 9:27 AM in response to Courcoul

    Tried this as well. Things did not change much.

     

    Aug 10 18:21:34 ### kernel[0]: FireWire (OHCI) Lucent ID 5901 built-in: 365 bus resets in last 3 minutes.

    Aug 10 18:24:48 ### kernel[0]: FireWire (OHCI) Lucent ID 5901 built-in: 305 bus resets in last 3 minutes.

     

    But now it did not disconnect so far. It is just slow like ****.

  • by Linc Davis,

    Linc Davis Linc Davis Aug 10, 2012 10:48 AM in response to Dr_Zoom
    Level 10 (208,037 points)
    Applications
    Aug 10, 2012 10:48 AM in response to Dr_Zoom

    The Firewire bus is not working. Either you have a malfunctioning device, or a malfunctioning motherboard.

  • by Laurent Seroude,

    Laurent Seroude Laurent Seroude Aug 7, 2014 2:57 PM in response to Linc Davis
    Level 1 (69 points)
    Mac OS X
    Aug 7, 2014 2:57 PM in response to Linc Davis

    we are many with this exact same problem with FireWire + this issue does not affect all drives that I have (if it was the port or motherboard, all drives should have the problem). This problem started with Lion and has been ignored buy Apple.....