Ejecting Firewire HD

I seem to have trouble ejecting my Firewire HD.
I am running only the Finder and I get this Finder message upon ejecting.
"The disk xxxx is in use and could not be ejected. Try quitting applications and try again."
I do not have a USB drive or cables on hand to try it so if someone is having trouble with this as well could you please post if it a FW or USB drive.
Thanks for you attention to the matter.

I have the same problem. I cannot eject an eSata connected to my MacBook Pro. I also cannot eject / unmount an USB drive also. In fact, sometimes I cannot even copy files to my external drive. I have to shutdown and restart Leopard.
This is started to get real annoying. If this is not fixed soon, I may have to ditch Leopard. I cannot work like this.

Similar Messages

  • Eject Firewire Hard Drive, Won't Stop Running

    I upgraded my Early 2009 Mac Pro OS to 10.9 today, but I found a problem about my external firewire hard drive.
    If I eject firewire hard drive under 10.8, the hard drive will stop running/rotating. Then I unplug the firewire cable. After I upgrade to 10.9 OS, the firewire hard drive will not stop running/rotating after I eject it. I cannot see any external hard drive icon on desktop, but I can hear the hard drive running sound.
    I'm not sure if it's safe to unplug cable under running condition after succeful eject. How's many people have the same problem with me?
    Thank you!

    I have a dozen OWC cases and they have all continued to work (but can't say about 10.9) and they are getting "dated."
    Apple though often changes drivers, IOKIt and how external drives are treated, 10.5.0 thru 10.5.2 the rules changed and changed back and forth. Some drives had to be off during startup. Users have had trouble with 10.6 as well with their drives, often USB and/or FW from major vendors (WD etc) not working.
    Do either of you get the "drive was not ejected properly" message on the next time you do connect and power it back on or after a restart?
    One of the reasons I prefer waiting for the .2 or later releases.

  • My Lacie Rugged Keeps Ejecting Firewire

    My Lacie keeps ejecting it's self.
    I'm on a mac book pro. (Latest Update)
    Firewire 800
    Lacie Rugged.
    Worried I will lose all my work.

    Lacie doesnt make it, the drives inside LACIE are Seagates.
    Your data isnt lost, NOR your drive corrupted,........if the below doesnt fix it, you CAN crack up the box, and remove the HD and stick it into the ONLY RELIABLE HD connection that exists, that being a HD dock , get a USPEED theyre the best.
    3.5" drives have a power issue (sometimes) thru firewire, they use more power than do 2.5" laptop external HD.  3.5" is a bit of a hog (depending on mfg) on power demands for spinning up and use. .........Ive almost entire steered away from ANY 3.5" unless it has its own power cord.
    Ive got nearly 100 Hard drives, Ive see this more than a few times. the only 100% reliable connector for external drives is (most often) a 2.5" drive thru USB , or MOST reliable, a HD docking station.  But a LOT of HD docks are junk get a good one, ...again, the best is USPEED
    http://www.amazon.com/Uspeed-External-Docking-Station-Chipsets/dp/B005UA3I72/ref =sr_1_1?ie=UTF8&qid=1372930214&sr=8-1&keywords=uspeed+dock
    software program from the Seagate website that is designed to stop the auto-eject feature. Once that was installed the problem was gone. One drive is connected via Firewire 800, the other two are just plain vanilla USB connections.Go to this page and read about half way down. http://seagate.custkb.com/seagate/crm/selfservice/search.jsp?DocId=207851&NewLan g=en

  • System hardlocks when ejecting firewire drives

    Anyone else having this issue?  I've had it since the 2.6.16 kernels, and I'm currently running -8.  I have both an ipod and an external hard drive that will hang the system about 75% of the time when I "safely remove" or use the eject command and unhook them.  Both are firewire.  I can't find anything in the logs.

    I may have solved this.  Sometime during recent upgrades my system started loading the eth1394 module along with the regular 1394 modules.  I've never seen this before, and have no use at all for it - more to the point, it was screwing with my existing ethernet.  Reasoning there might be a connection, I've added eth1394 to my blacklist, and so far have not been able to make my box hang.  I've also upgraded to 2.6.16.2 w/o issue.

  • Can't Eject Firewire drives

    I've been using a collection of 500GB firewire G-Drives for pro-audio & time machine backups.
    Up until now, they work great with my old 2006 MBP (OS 10.4) , and my late 2008 MBP (OS 10.5.6)
    I just got a new 2009 MBP with Leopard 10.5.6 and whenever I mount the drives, I cannot eject them.
    Its a mystery. No applications are open. Spotlight is not running. Everytime I try to eject a drive I get a message saying its in use.
    My only remedy is to shut down the computer, and turn them off.
    Any ideas?

    Means corrupted system files. You should reinstall OS X. You may try this:
    How to Perform an Archive and Install
    An Archive and Install will NOT erase your hard drive, but you must have sufficient free space for a second OS X installation which could be from 3-9 GBs depending upon the version of OS X and selected installation options. The free space requirement is over and above normal free space requirements which should be at least 6-10 GBs. Read all the linked references carefully before proceeding.
    1. Be sure to use Disk Utility first to repair the disk before performing the Archive and Install.
    Repairing the Hard Drive and Permissions
    Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Installer menu (Utilities menu for Tiger.) After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported, then quit DU and return to the installer.
    2. Do not proceed with an Archive and Install if DU reports errors it cannot fix. In that case use Disk Warrior and/or TechTool Pro to repair the hard drive. If neither can repair the drive, then you will have to erase the drive and reinstall from scratch.
    3. Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When you reach the screen to select a destination drive click once on the destination drive then click on the Option button. Select the Archive and Install option. You have an option to preserve users and network preferences. Only select this option if you are sure you have no corrupted files in your user accounts. Otherwise leave this option unchecked. Click on the OK button and continue with the OS X Installation.
    4. Upon completion of the Archive and Install you will have a Previous System Folder in the root directory. You should retain the PSF until you are sure you do not need to manually transfer any items from the PSF to your newly installed system.
    5. After moving any items you want to keep from the PSF you should delete it. You can back it up if you prefer, but you must delete it from the hard drive.
    6. You can now download a Combo Updater directly from Apple's download site to update your new system to the desired version as well as install any security or other updates. You can also do this using Software Update.

  • Cannot eject FireWire drives

    Hi,
    Whenever I mount a firewire drive, I cannot eject it again - I always get a -47 error, saying the drive is busy. I have TimeMachine turned OFF, so that shouldn't be causing the problem. Also, I never had any problems with this under Tiger.
    Any ideas? I have tried all possible ways of unmounting the drive, but nothing works (except pulling the plug obviously.....)

    Hi,
    Whenever I mount a firewire drive, I cannot eject it again - I always get a -47 error, saying the drive is busy. I have TimeMachine turned OFF, so that shouldn't be causing the problem. Also, I never had any problems with this under Tiger.
    Any ideas? I have tried all possible ways of unmounting the drive, but nothing works (except pulling the plug obviously.....)

  • Lost Email Messages in Inbox

    I've recently purchased a new PowerBook to replace my older Powerbook, and recently used the Migration tool to move all my files, settings, applications etc across to the new machine.
    Mail 2, upon starting for the first time does it usual conversion of stuff and correctly notes the 28174 messages. However when it say you can start using Mail, it only displays the most recent mail messages for the last seven days (273 messages). Which is not the 10198 messages I have on my old Powerbook in my Inbox (this about the last six years of mail). And I do archive mail regularly into other folders.
    I've tried rebuilding the mailbox, checking permssions - the mbox file size it identical to my old machine (518Mb). I've subsequently quit Mail, removed all the folders under ~/Library/Mail, restarted my old Powerbook in firewire mode and tied doing an import through Mail 2 with exactly the same result.
    I note a few other people have posted similar experiences with Mail 2. Given this is my first experience with Tiger (10.4.5), until I see this being resolved
    I'll use my old Powerbook (10.3.9). Thus far not impressed at all.
    PowerBook G4   Mac OS X (10.4.5)  
    PowerBook G4   Mac OS X (10.4.5)  

    I ended up going back and completely reinstalling the new PowerBook from scratch in case something was up and tried migrating again - same situation.
    Next I removed all the files/folders under the /Users/~/Library/Mail directory (ie blank slate)
    Having read similar posting from people, I then broke up my Inbox into folders by year received on the old Powerbook and then rebuild each of the mail folders. This had the Inbox down to 701 messages, with each of the folders holding between 396 to 1783 messages each. Restarted my old Powerbook
    in firewire mode and then performed a Import Mailboxes. Once the import was
    done, the old messages broken into various folders looked ok (ie number of messages matched), however the Inbox showed only 243 messages not the 701 messages originally there. In fact it appeared that only messages received in March were displayed and nothing else. I tried performing a Rebuild of the mailbox and all the messages (all 243) disappered. Searching
    failed, as did any further Rebuilds.
    So again I cleaned out the Mail directory on the new Powerbook, ejected firewire Powerbook drive and restarted the old Powerbook as normal. On
    the old Powerbook, I then created another folder and moved all 701 messages in the Inbox to the newly created folder, thus the Inbox was empty. Restarted the old Powerbook in firewire mode and repeated the Import Mailbox process.
    The seemed to go ok, all the messages were there, however I could not move the messages back to the Inbox from the folder. Given the previous experience with rebuilding a mailbox, I tried Rebuilding any of the folders partly to see if the same thing would re-occur - which it did, any mailbox selected and then a Rebuild performed would appear to delete all messages within the folder.
    If I look at any of the folders directory using Terminal, I see the following:
    -rw------- 1 evans evans 136022756 Apr 1 16:10 Incoming_Mail
    -rw-r--r-- 1 evans evans 541600 Apr 1 16:10 IncomingTable_ofContents
    -rw-r--r-- 1 evans evans 356 Apr 1 22:30 Info.plist
    drwx------ 1784 evans evans 60656 Apr 1 23:00 Messages
    The Incoming_Mail file is basically a mbox file (comparing it to 10.3's Mail),
    IncomingTable_ofContents, is a concatenation of Subject (with additional formatting). Info.plist is a file containing display information for the folder itself and finally Messages is a folder containing the Mail 2 of the individual messages.
    Out of curiosity I wondered if the TableofContents file was somehow being corrupted, so I removed the file and then went to look at the folder - oddly enough I could now view all the messages, whereas before after doing a Rebuild they completely vanished.
    In other folders I found the Messages folder has a name of Messages-T0x4c5c70-fTrRll, removing IncomingTable_ofContents in this instance made no difference, nor did removing the Messages-T0.. folder and renaming the Incoming_Messages to mbox and trying a Rebuild again.
    I've subsequently cleaned out the Mail folder on the new Powerbook and again perfomed a Import Mailboxes.
    From observations there appears to definitely be a problem when importing mail from 10.3.x as well as performing a mailbox rebuild, though I've yet to
    determine the cause of the failures.
    So looks like its back to the old Powerbook and reliable 10.3.9.

  • Firewire 800 keeps ejecting my disk

    Thought it was a fluke, but it keeps happening. My LaCie drive keeps disconnecting and I get an error message that it was improperly disconnected. I've tried two different firewire cables. I'm not touching the cord. It just suddenly loses the connection. Is it possible that I have a bad firewire port? I just bought the MacBook today. Should I return it for a replacement?

    Hi,
    I am encountering a similar eject disk problem. When attempting to clone (with CCC) iMac's internal HD to external firewire 800 connected HD, the cloning stops fairly quickly and Firewire HD is ejected with an error message stating disk has not been properly ejected. The result is that the cloning partition becomes corrupted and can't be repaired by disk utility.
    Since I am using a quad interface HD NewerTech Voyager Q ''toaster'' for internal drives, I managed to make a functional clone the iMac HD with usb connection.
    But if I attempt to boot with firewire connection the corruption problem is recreated > Backup screwed.
    I was wondering if my firewire port could be dead ? I tried multiple times formatting the HD and start the process again but firewire connection and cloning leads to failure at each trial.
    Any idea ? (Note: everything in my setup seems up to date)

  • Ejecting a Firewire DV camera daisy chained vis a External Firewire HD

    I have my firewire DV camera daisy chained via my firewire external Hard drive.
    When I unplug my firewire dv camera, after a little while I get a message on my mac that a device was removed incorrectly and the external firewire dirve dismounts.
    This only happens after I have unplugged my DV cam, so am I supposed to eject the cmera somehow??
    It doesn't show as an external drive so I wouldn't have a clue where to even start looking.
    Any ideas?

    This only happens after I have unplugged my DV cam, so am I supposed to eject the cmera somehow??
    This would depend on the "capturing" application. In most cases you simply tell the application that capture is completed by pressing a "Done" button, disconnect button, ESC key, or similar action to let the application know that it can close the device protocol and allow the device to be removed.

  • Firewire removable drive eject problem

    Hi
    I have one of those intermittent failures which is driving me crazy. I've got a Granite Digital removable FW-800 drive hooked up to my Quad (10.4.7). Also have a SATA removable drive bay. Most of the time, external drives work just great, and there's no problem.
    However... often enough to make me ask it here, I'll eject the drive, via drag to the trash in the dock, or via contextual menu "eject" and, after a bit longer pause than usual, the icon will disappear from the finder's desktop. Everything looks good, but...
    ... when I go to turn off the drive, or remove it, I get an "improperly put away...may damage drive" message.
    And then... it's totally impossible to restart or shut down the machine. A power off is needed.
    Leaving aside comments on how long the software should be looking for an obviously missing drive before simply giving up (hint: infinity is too long) there's this.
    What's happening? (don't say that something is open on the drive... nothing is) and two, is there something I can do once I get this message to prevent the infinite look? Terminal command? Anything?
    OK: one more thing - am I the only person this happens to?
    TIA
    Tracy
    ex-programmer and Mac user since 1984...

    Gleaned from a string of several painful experiences...
    When "OFF" isn't really "off."
    When it's a switch on the back of some, and certainly firewire boxes fall into the "some" category, peripheral boxes. I spent I don't know how many hours chasing this down because I forgot something I'd learned a few years ago: it's OK to switch off the power to an external firewire box using the switch on the back of the box, but it's NOT OK to switch it off by turning off (unplugging) the "brick" or using a master controller that turns off the AC power.
    Why? Because "off" isn't really "off"... keeping the "brick" alive keeps the system informed about the firewire device's presence; turn it off "at the wall" and you're going to seriously confuse the system. In my system, it would work this way: if I left the box switch in the "on" position, then when I turned on the wall power, the hard drive would show up on my desktop.
    Now, I was always religious about ejecting the drive before I powered down, but my mistake was powering down "at the wall" instead of using the switch on the back of the box. I figured I'd save the power drained by the brick when I wasn't using the drive.
    Bad mistake. About 50% of the time, when I'd eject the -next- drive I mounted externally, I'd get a message saying "improper device removal"... and my system would -seriously- choak up. Nothing would run; nothing would quit and I'd be faced with a forced hard power-off of my whole system.
    Once I recalled what the heck I was doing wrong, and reverted to "once powered on, leave it on" the problems went away.
    The problem seems to affect external SATA drives as well (although I'm not as positive of that as I am of the firewire issue.) So: leave the boxes plugged into the wall, and only use the switches on the back to turn them on and off. If the wall-wart bricks are eating up extra power, I'm afraid that's the price you pay for the modern age.
    hth
    Tracy

  • Firewire issues?  Cannot Eject anything firewire..

    So.. anything I connect via firewire, cf card in a firewire reader, external firewire hard drives, ipods.. will not eject.. when I try to eject any of these items I get a message saying "The disk ___ is in use and could not be ejected. Try quitting applications and try again" ... I have no applications running and this applies to all my firewire devices.. is it possible the whole firewire system is no good? or possibly a corrupt preference in the system? any thoughts? I have disconnected all devices and tried just one at a time thinking that maybe one particular device was causing the problem but it seems to be system wide..

    Okay.. so the cd was actually not hard to eject, I have found if you hit the eject button during startup it will usually spit out the disc and it did.. so I have it out now. Without a disc inserted the eject key on the keyboard will open and close the drawer. But I am still unable to eject any drives, ipod, etc.. and actually.. I needed to install a program for something else and the disk image that was created from the dmg file is now on my desktop and my computer will not allow it to be ejected. Any other thoughts? The computer works fine otherwise with no apparent problems.

  • Disk mounting/ejecting problems... ESPECIALLY FireWire

    Ever since upgrading to Leopard my 3 Lacie external drives have been VERY wonky.
    I've tried a FireWire hub, as well as daisy-chaining them via FW800 (they're the triple interface kind), but getting more than one to mount is always a crap shoot. I've tried USB, and that seems to work much better, although I have an older Mac that only has USB 1.0, so it's pretty much NOT an option.
    The other thing is when I do get any of the 3 mounted, actually EJECTING them is a challenge. Firstly, if it DOES actually eject, the finder window automatically closes. Which seems to be a bug (because it happens with ANY mountable disks, etc). However, most of the time I get a "cannot eject because this disk is in use" error, even when I am in NO WAY using the disk! No apps open!??
    Argh! I know Apple doesn't read these forums (although, as a fan and stock holder, I wish they did)... but there seems to be a LOT of FireWire issues that cropped up with Leopard.
    Any hints?
    e

    I've had the same problem, I use three LaCie triple interface disks, they used to work great but now they start unmounting on their own or getting stuck all of a sudden...so great when you're in the middle of rendering a sequence on Final Cut !
    Whenener I manage to run disk utility on them (which is not always the case), they seem OK.
    Is there really a problem with the handling of firewire by Leopard? Anyway to fix it? These jinxes really cause me problems for my work
    Thx for your help

  • Excessive disk I/O after ejecting external storage device (USB, firewire)

    Hi all,
    I've noticed a problem in my macbook pro that every times after I ejected a storage device, say SanDisk through a USB 2.0 card reader, I found about 20G+ bytes were wrote on the start disk. The excessive disk I/O brought the performance to its knees, and I can only recover it by reboot the computer. It looks like the data written on the disk were gone after reboot. Is there a way I can trace what has been written?
    Thanks

    Jovahn,
    Welcome to the Apple Discussions!
    Unfortunately, external USB drives are not well supported on PPC Macs such as the eMac (later Intel CPU Macs do have better support for USB external USB drives, including booting). Regrettably, if the USB drive manufacturer doesn't have decent Mac drivers available, I don't know of a real fix, short of selling the USB drive and picking up a Firewire one. Or, pick up a Firewire enclosure, which is fairly cheap, and put the actual hard drive from the external USB enclosure in the Firewire enclosure --- PT: HD drive replacement tips should provide some good pointers.

  • FireWire 800 / Can't eject disk

    First I was having issues with my external hard drive arbitrarily disconnecting and giving me the message that it was improperly disconnected. (When I hadn't touched it.) I read here on the forums and disconnected everything to reset the fuse. Waited 10 minutes and rebooted, then connected. It seemed to work, but now I cannot properly eject it. I get a message that it wasn't ejected "because one or more programs may be using it." But I'm not using it. What gives? Do I force eject it?

    I just had the disconnect problem again. Any idea what's causing it? I have two firewire 800 cables, and I've tried them both...just in case one had a kink or a short in it. I just connected the drive, it came up, and I got the message asking if I wanted to back up to the disk using Time Machine. I said "decide later," and it suddenly disconnected and gave me an error message that the disk was improperly disconnected.

  • Connecting 2 Firewire Drives daisy chained on a MacBook Pro Retina:  1rst FW8-Dr is ejected by OSX 10.8.2 as soon as I power up the 2nd FW-800 Dr.

    OSX 10.8.2 seems to eject a FW-800 Drive to any attempt to connect in daisy chain a second.
    - Connecting one single Firewire-800 drive (G drive) seems to work fine (connection through a Thunderbolt-FW800 adapter)
    - As soon as I try to connect a second FW-800 G drive in daisy chain, when I turn the power on to the second: Mountain Lion ejects to first with the message "improperly ejected" and both drives are not visible. I do not use separate power supply for the FW-Drives.
    - The same thing happens with for the second drive instead of a true FW-800, it is an SSD 128 GB mounted on an enclosure with a FW-800 interface.

    Hi Mate,
    I've got a non-retina MBP i5, and it's not behaving like that, so no way should yours be.  Can't hear it at all until it really comes under load.  But even then it's relatively quiet.  Quite concerning that it's happening to you with nothing loaded up.
    Something is obviously taking up cpu power just by having the audio engine running, have you checked OSX Activity monitor and checked where your processor(s) are being used?
    Also, check your audio options and make sure the audio buffer isn't set ridiculously low.
    Agree that Apple expansion options are expansive - However, at least they're working on getting the software reduced, Logic X being an example of that.

Maybe you are looking for