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

Similar Messages

Disk ejection problem

How can I force a disk to eject (CD or DVD)? I have tried restarting with the mouse button held down. The disk utility says that it is not mounted.

AppleCare said that the problem was that the disk was stuck between thisa and thata and that I needed to go to the Genius Bar. I unplugged everything and got it packed up and ready to go. But I had to try one last time, and this time Murphy came along and ejected it. She can be an enigmatic companion.
Thanks for your suggestions.

10.5.8 disk mounting problem

I updated to 10.5.8 and decided I would download the photoshop elements trial off Adobe's website. It was at 365 MB of 1.27 GB and it suddenly came up "mounting failed" I am currently trying to download it again, but my internet connection is slow so it will be awhile before I see if it happens again at 365 MB. Has anyone else had disk mounting problems in 10.5.8?

Speaking as someone who works a lot with PSE, I would say the odds are very high that this is an Adobe problem rather than a 10.5.8 problem. Wait a while and try the download again.

Disk mount problem

I have an external fw disk that stopped mounting properly, at least when I log in under my user name (with admin privileges). The disk shows up in disk utility with the little fw disk symbol and the proper capacity and model name: 372.6 GB OWC Mercury Elite Por-AL 800/400. But the icon for the volume, External HD, appears as a piece of paper with a folded corner. It does not appear in Finder but it is detected in terminal when I run the "mount" command. This problem occurs whether I plug the disk into my iMac (using fw 400) or laptop (using fw 800).
I tried logging in as "guest" and the disk mounts properly and I can access all the folders on it. When I end session as guest and log in under my user name, the same problem as described above recurs.
When I run repair disk, no problems are found.
Any help would be appreciated.
intel imac 20 Mac OS X (10.4.9) mbp core2duo

TomK,
I just had your same problem yesterday with my external USB LaCie Porsche disk. I've been using FW disks for years and this never happened to me before.
I tried running the disk tests with Disk Utility, switching the drive on and off, with no result.
Disk Warrior 3.0.3 solved the problem by rebuilding the directory structure. Now it works again and no file was (visibly) lost.
By adding up what I read in this thread, I get to the conclusion that the problem was in the disk (not in the finder prefs) and is not related with USB vs. FW, as at first I guessed.
I'm curious to know if and how you solved your problem.
Could you solve it using a standard Apple utility or some terminal command ?
I can manage unix commands if needed...
Thanks
Piero

Disk mounting

Does anybody no how to set my hard disk connected to my extreme so as it auto mounts.
This used to happen all the time & now I cannot even mount the drive on the desktop.
Any help would be most appreciated.
Dave

AirDisk is the definition of flaky. One minute they mount and are fine for a few days the next they won't mount. I too have gotten "password incorrect" message, or the disk show as folders and then when I click a folder representing the disk nothing happens although it says I'm connected. Most odf the time these issues appear after a disruption with the AEBS connection, especially a power loss. I've found that connecting the external disks directly to my Mac, ejecting them, and re-connecting to the AEBS will usually correct the problem. If this does not work I find once I have hardwired the disks to my Mac I sometimes need to repair the disks using Disk Utility, eject them, and then reconnect them to AEBS. This seems to work as a last resort.

Auto mount/eject external drive for time machine backup/restore

I have an Iomega ultramax drive connected via firewire 800 for my Time machine backups.
This drive will automatically spin down after a period of non-use. I like this as it means lower power usage and lower risk of data loss (head crashes etc..).
My problem is, when the drive spins down like this, some file open operations pause until the drive spins up again. I cannot remember exactly which applications I have had the problem with, but I assumed that this was part of the OS. This delay can be up to 5 seconds or so and is really annoying.
Assuming this is not just a specific third party application thing. My suggestion to Apple is to do one or both of the following:
1) Multi thread the file open dialog (process?) so that is comes up instantly, and then adds the drive when it has spun up.
2) Modify time machine so that it can automatically mount/eject the external drive just when doing backups and restores.
Currently I have a bit of a messy work around to this problem where I have a loadd scheduled shell script that runs every hour that mounts the drive, runs time machine to backup and the ejects the drive. It works, but is not perhaps as nice a solution as it could be.
Does anybody else suffer from this problem?

Yes that is correct, the drive spins down and remains mounted.
To be perhaps clearer. The problem is not essentially a time machine problem, it is to do with whatever implements the file open capability that other apps use. In the above sitation, there is always a delay for the drive to spin up when I go to open a file (perhaps five seconds) in other applications. I assume this delay is caused by the file open process waiting until some data is retrieved from the external drive before giving me the option of choosing a file. This delay is annoying, as I do not ever want to open a file from my external drive (this is dedicated to time machine backups) when I am using pages, or any other application other than a time machine restore.
This particular issue is similar (but I suspect nowhere near as bad) as one of my pet hates about windows XP. In windows it appears that the explorer will wait for a response on all its connected drives (hard disks, mounted cds, network drives), so any sort of network connectivity or hardware delay will cause explorer to freeze. As explorer seems to be embedded in most things you do with the OS, this can cause anything or everything to freeze (web browsing, you name it).
In my setup, as I have the external drive totally dedicated to time machine backups, another thing that would fix the problem for me is the suggestion number 2 I suggested where time machine auto mounts for the backup and then ejects after the backup. With the feature, then the external drrive will only ever be mounted for short periods of time (the above problem does not ocurr if the external drive is not mounted), and when it is mounted it will be spinning, so I will never have my file open delay. I would however have a short delay when doing a time machine restore for the mount of the drive, but this is a much rarer event the using file open in all my other apps.
Thanks for the info on the feedback link, I will post this to that.

Known disk-mounting fault on iPod Video 80GB?

Is there a known disk mounting fault with the iPod Video 80GB?
I’m running iTunes Version 7.0.1.8 and have so far had two brand new 80GB iPod Video devices, purchased from a registered New Zealand reseller (TotallyMac.com).
Both iPods have successfully loaded my music library and have played perfectly, both on headphones and on my iPod hi-fi. However, when I subsequently plug the iPod into any of the USB 2 ports on my laptop, the iPod does not show up as a device in My Computer, File Explorer or in iTunes.
I’m running Windows XP, Service Pack 2.
The problem also occurs on a second PC – the iPod refuses to show as a device in My Computer, Windows File Explorer or in iTunes. However, it does show up in Device Manager, and the ‘Safely Remove Hardware’ icon shows on the Windows status bar when the iPod is connected. Even so, when the iPod is safely ejected, the iPod screen continues to show ‘Do Not Disconnect’, so the only way to safely eject the iPod is to reset it on the iPod.
I’ve tried restarting the computer, putting the iPod into disk mode and so on. Unfortunately, none of the advice on the Apple website for iPods that refuse to mount helps me – because I can’t get the iPod to appear as a device anywhere on my computer, I can’t rename the Drive Volume (to another letter instead of ‘E:’) or restore the iPod to factory settings.
I can’t help thinking that Apple has created a ‘Catch 22’ situation by removing the iPod Updater option in iTunes 7 – none of the previous versions of iPod Updater is compatible with iTunes 7, meaning it’s impossible for people who have a Disk Mount problem to restore their iPods. If you can’t get the iPod to show up in iTunes, how are you supposed to restore the device or solve disk mounting problems?
There appears to be no other way to restore the device if you’re using iTunes 7.
Why isn’t there a ‘restore’ option in the iPod’s own diagnostics menu, some combination of click-wheel buttons that will allow you to reformat/restore the drive?
My previous (40GB) Fourth-Generation iPod mounts perfectly on both this laptop and another PC, suggesting it is the new iPods that are the problem. Also, as I said, the new iPod fails to mount on the second PC, supporting this theory.
Both faulty iPods have been set to ‘manually update’ and I also ticked the ‘Enable Disk Use’ option and removed the checkmark from ‘Automatically open iTunes’.
It would be good to hear from someone else who has experienced similar difficulties, as I’m by no means a new iPod user and this has both me and the Apple service technicians I’ve spoken to completely stumped. Is it a known problem and, if so, will it be dealt with in future iTunes updates…?
Toshiba P20 Laptop PC Windows XP Pro

Try forcing the iPod into disk mode:
http://docs.info.apple.com/article.html?artnum=93651
And then see if you can change the Volume Drive Letter:
http://docs.info.apple.com/article.html?artnum=93499
If nothing else works, you may want to give this a shot:
http://docs.info.apple.com/article.html?artnum=302538
Since you did say the iPod continues to show Do Not Disconnect after ejecting it, I'm thinking maybe there's something on your computer that's interfering with the iPod.
Also, when the iPod comes up in Device Manager, does it have any kind of warning on it? You may need to uninstall the iPod's drivers, and then restart the computer with the iPod attached to reinstall it. This may not be the case, though, since the iPod is still showing Do Not Disconnect while it's plugged in.
You may also want to make sure you have the iPod connected to a USB port directly on the rear of the computer, or try a different USB cable.
Also, you might want to try restarting the iPodService
http://docs.info.apple.com/article.html?artnum=93716
CG

Word for mac 2011 keyboard commands hang when network disk mounted

After much trial and error, I have found that, for my system, at least, MS Word for Mac 2011 hangs on keyboard commands when a network disk is mounted on my desktop.
Just wanted to alert all who get the beach ball when use keyboard commands in MS Word.
Symptom was that Cmd-C would take 8-13 seconds or so to copy 1 word, versus immediate when using menu commands. Same with Cmd-V paste. Also, opening a document took much longer.
Once I ejected network disk, problem disappeared.
Hopefully this will save someone else the time I spent tracking down the issue. I'd still love to know the root problem, though, as I prefer to have a remoe disk mounted on desktop while I work, and now I can't.

Follow these instructions to uninstall MacKeeper. They have been tested with the most recent version of MacKeeper (v 2.8). Earlier versions than the one released in 2012 require more extensive work to uninstall all its components.
The effects of having actually used MacKeeper to do anything are a completely different matter. The fastest way to take an exquisitely designed and painstakingly engineered Mac and make it run like a steaming pile of dung is to install and use such ill-conceived "cleaning" or "security" products. This is just one example of a broad category of time- and money-wasters capable of causing damage that can only be rectified by reinstalling OS X, restoring from a backup, or completely erasing your system and rebuilding it from the ground up. Never install such junk on a Mac.
If you used MacKeeper to encrypt any files or folders, use MacKeeper to un-encrypt them first.
Quit the MacKeeper app if it is running.
Open your Applications folder: Using the Finder's Go menu, select Applications.
Drag the MacKeeper icon from your Applications folder (not the Dock) to the Trash.
You will be asked to authenticate (twice):
You do not need to provide a reason for uninstalling it:
Just click the Uninstall MacKeeper button. You will be asked to authenticate again.
After it uninstalls you may empty the Trash and restart your Mac. All that will remain is an inert log file that does nothing but occupy space on your hard disk.

Disk Mounting error

Trying to download a program and get the "disk mounting failed" message.
Using an EMac with OS 10.3.9, downloading a .dmg file about 5.6MB using Safari 1.3.1(v312.3.3). I've gotten all the updates and Java fixes I can think of. I am able to download other files w/o problem. The file I'm trying to download is Limewire. I've been on their discussion board but no results.
Any sugesstions?
Oh, the Safari downloads about 180kb of the file and then gives me the error and I'm using a cable modem connection.
EMac Mac OS X (10.3.9)

I just had the very same problem (with a CD instead of DVD, but same error) and found your unanswered post. I checked out another site, and it suggested that the I/O problem has something to do with data corruption....
And then I remembered that when watching DVD's - if they are dirty, they won't play...
And I ejected the CD, and found some gummy jam like substance on the data side.
Cleaned it off, and now it works fine....hope this helps you or others!

Disk not ejected properly

Hi I'm having this issue since I upgraded to Mavericks where almost every time I put my computers to sleep I get the "Disk not ejected propoerly" message and every disk but the system one is not mounted and cannot be found by Disk Utility.
I have a Mac Mini late 2009 and a Macbook Pro 15 mid 2009 and I'm having this issue in both machines. Never had any issues before in any of my machines, not in Leopard, Snow Leopard or Lion.
On my Mini I have two external USB drives and on my MBP I have a SSD, where the system is installed, and a HD (I replaced my optical drive with a bay to install the extra disk).
I researched the issue and found a couple of threads where people sugested to buy a 3rd party app that would unmount the disks at sleep and remount them at wake, but I think this shouldn't be a issue, since it never happened with any version of OSX I had used before.
Is anybody else having this issue as well? Is there any word from Apple on this subject? Can I hope for a fix?
Thanks

I get this error as well, and my two external SSD drives are practically useless under Mavericks. Many freezes during read/writes. Have had several pretty critical issues with Mavericks so far- really regret upgrading. My fault for upgrading so early, I almost never do that. Paying for it now. Hopefully a forthcoming patch will fix at least the external drive problems, this is a real killer.
Update: at least it seems Mavericks has not corrupted the data on my SSD's. I have been able to mount them on my wife's Air (w/ Mountain Lion) and copy the disks over the network. Not ideal at all, but at least this saves me days of downloading backups from Backblaze. And the SSD's are still viable.
iMac 27" late 2012
Message was edited by: Bitmatt

Disk Not Ejected Properly on wake

In the past week or so I am getting the standard Disk Not Ejected properly message everytime I wake my iMac up. However, all of my disks are still mounted properly and accessible so I have no idea what it thinks has been ejected.
I have been running on Mountain Lion with no issues since it became available and this problem has only just started.
Any suggestions?

I am one of those who had experienced this kind of problem. My former Time Machine disk used to automatically eject itself when my iMac sleeps, hence upon waking up my iMac. i always get the error message that the disk was not properly ejected.
From what I was able to gather from my experience, until the time that I found a workable solution, I think I can say that the problem is most probably caused by the incompatibility of certain external drives with how the iMac operates when on sleep and upon waking up. Some external drives are just not able to cope with how the iMac tries to remount a connected disk after it wakes up from sleep. There are just some external drives that cannot continue to be mounted after the iMac wakes from sleep. There are just some external drives that are not responsive enough. In other words, the existence of the problem lies with the type of external drive you are using.
My former Time Machine disk, the problematic one, was an Imation M300 Apollo 1 TB external disk. It unmounts everytime my iMac went to sleep, but does not remount after waking up the iMac. The disk will continue to be unmounted until I physically remove its USB connector and replug it in the iMac.
I replaced my former Time Machine disk with my current one, a Transcend Storejet 1 TB. And the problem went away. The Transcend disk continue to be mounted after the iMac is woken up even from the longest of sleep. I have even the energy saving option "put the hard disk to sleep..." checked. The Transcend disk comes with a Y cable, i.e. it has two USB connectors, but I only connect the one for both data and power--and it still remains mounted even after waking the iMac from sleep.
The sad realization, however, is that since there are only some external drives that are not able to work with the iMac, no matter how many those some may seem to be, it will be highly unlikely for Apple to itself fix this kind of a problem.
I, therefore, make the following recommendations:
1. Check first if your problematic disk has a firmware upgrade available. In some cases, the firmware upgrade may be enough to make the disk more responsive to the iMac waking up.
2. If there is no firmware upgrade available, check if your power/data USB cable is properly working.
3. If your power/data USB cable is in order, and the problem still persists, I think it is inevitable that you have to replace the problematic disk with a newer one that could respond well with the iMac's wake/sleep operation. With what disk will you replace your problematic one? I can only recommend from my personal experience the Transcend disk I mentioned earlier. You may also search this forum on other brands of disks that may also work.
Regards.

Mac mini mid 2010 hard disk keeps ejecting itself

My mac mini is set up with two sata disks installed, one is a 128 ssd and the other a 1tb hdd. Since installing mountain lion, the hdd keeps ejecting itself, and i get a message saying - this hard disk was not properly ejected. then i wont find the disk in finder, or disk utility!. I then have to remove the hdd from the mac mini and plug it into a usb caddy, which finds it no problem, and then when i put it back in the mac mini, it works again!! so the disk is not faulty i dont think. It then works for a period as random as a few hours, to a few weeks and then i will randomly get the "this disk was not ejected properly" message and it has again dissapeared. I use the mac mini as a media centre and it isnt really being pushed hard when the failure happens.
Anyone have any ideas as to whats wrong?

Hello, Sorry for the late reply.
When i open console after the ejection i get the message:
01/11/2012 22:32:42.000 kernel[0]: Failed to issue COM RESET successfully after 3 attempts. Failing...
01/11/2012 22:32:42.000 kernel[0]: disk1s2: no such device.
Hope this gives a clue, i'm tearing my hair out over it. there is absolutely nothing wrong with the disk itself.
If i do a full shutdown and restart, it finds the disk again no problems, but if i simply choose to restart from the menu, it does not find the disk again.
Thanks for any help you can give on this. I have only been experiencing this issue since i upgraded to mountain lion.
Drive information:
SAMSUNG HN-M101MBB:
Capacity:          1 TB (1,000,204,886,016 bytes)
Model:          SAMSUNG HN-M101MBB
Revision:          2AR10001
Serial Number:          S2R8J90B815515
Native Command Queuing:          Yes
Queue Depth:          32
Removable Media:          No
Detachable Drive:          No
BSD Name:          disk1
Rotational Rate:          5400
Medium Type:          Rotational
Bay Name:          Lower
Partition Map Type:          GPT (GUID Partition Table)
S.M.A.R.T. status:          Verified
Volumes:
disk1s1:
Capacity:          209.7 MB (209,715,200 bytes)
BSD Name:          disk1s1
Content:          EFI
living room:
Capacity:          999.86 GB (999,860,912,128 bytes)
Available:          648.66 GB (648,662,093,824 bytes)
Writable:          Yes
File System:          Journaled HFS+
BSD Name:          disk1s2
Mount Point:          /Volumes/living room
Content:          Apple_HFS
Volume UUID:          D6125397-BAE7-3496-9B9C-6534EEE0B660

GNOME, nautilus, devicekit-disks: mount USB disk

Hi,
I recently upgraded and have now nautlius 2.28.2-1 together with devicekit-disks 009-1 installed.
As usual mounting/unmounting USB disks in nautilus stopped working. I searched the wiki, forums, bugs and google to gather information about this topic, but you know ...
When I try to mount a disk (they all show up in nautilus) nautilus pops up an error declaring me "Not Authorized". After quite some reading I think nautilus now uses devicekit-disks to actually mount my USB disks, so I tried to mount it with devicekit-disks:
[resi@nomad ~]$ devkit-disks --mount /dev/sdc
Mount failed: Not Authorized
In older versions of nautilus I used to edit some files in /etc to grant myself permissions (PolicyKit.conf), but this does not work anymore.
I found a hint and edited /usr/share/polkit-1/actions/org.freedesktop.devicekit.disks.policy (this one is coming with devicekit-disks) and modified the default for the actions org.freedesktop.devicekit.disks.filesystem-mount action:
<allow_any>yes</allow_any>
Having done so I can now mount the USB disks using nautilus, devicekit-disks or palimpsest (suffering from the same "Not Authorized" problem). Unmounting has a little flaw though, it seems like nautilus tries to eject the medium when unmounting, but then again its "Not Authorized" to do so.
However, this is the only solution I could come up with. Since the file I modified will probably be replaced without notice during the next upgrade I fear I will have to go all the way again, not remembering anymore what I did to fix this (otoh, after writing this I probably will).
And since the values in org.freedesktop.devicekit.disks.policy are declared as defaults (and by the fact it lives under /usr) I assume there has to be a site configuration file somewhere in /etc.
Where should I but my customizations? I mean, whats the proper way to do so?
Thanks,
Christoph
P.S.: I like nautilus, it makes me unhappy to use thunar/pmount/whatever to mount my disks.

me again ... this whole *kit stuff seems so odd to me.
I finally read all the devicekit, then the policykit docs, Syu-ed and have now devicekit-disks 009-3 installed.
Using polkit-actions without arguments prints a list of registered actions (known to policykit). This list was pretty short:
[resi@nomad ~]$ polkit-action
org.freedesktop.policykit.read
org.freedesktop.policykit.revoke
org.freedesktop.policykit.grant
org.freedesktop.policykit.modify-defaults
PolicyKit considers all *.policy files under /usr/share/PolicyKit/policy/, only the policykit package installs its files (well, its one file) there.
devicekit-disks (and probably some other packages providing *.policy files) seems to forget about that. So I added a symlink:
[root@nomad policy]# ln -s /usr/share/polkit-1/actions/org.freedesktop.devicekit.disks.policy /usr/share/PolicyKit/policy/
Thats not enough, the file seems to be out of date. I had to replace all auth_admin_keep defaults with auth_admin_keep_session until the file validated.
And hurray:
[resi@nomad ~]$ polkit-action
org.freedesktop.policykit.read
org.freedesktop.policykit.revoke
org.freedesktop.policykit.grant
org.freedesktop.policykit.modify-defaults
org.freedesktop.devicekit.disks.filesystem-mount
org.freedesktop.devicekit.disks.filesystem-mount-system-internal
org.freedesktop.devicekit.disks.filesystem-check
org.freedesktop.devicekit.disks.filesystem-check-system-internal
org.freedesktop.devicekit.disks.filesystem-unmount-others
org.freedesktop.devicekit.disks.filesystem-lsof
org.freedesktop.devicekit.disks.filesystem-lsof-system-internal
org.freedesktop.devicekit.disks.drive-eject
org.freedesktop.devicekit.disks.drive-detach
org.freedesktop.devicekit.disks.change
org.freedesktop.devicekit.disks.change-system-internal
org.freedesktop.devicekit.disks.drive-ata-smart-refresh
org.freedesktop.devicekit.disks.drive-ata-smart-selftest
org.freedesktop.devicekit.disks.drive-ata-smart-retrieve-historical-data
org.freedesktop.devicekit.disks.luks-unlock
org.freedesktop.devicekit.disks.luks-lock-others
org.freedesktop.devicekit.disks.linux-md
org.freedesktop.devicekit.disks.cancel-job-others
org.freedesktop.devicekit.disks.inhibit-polling
org.freedesktop.devicekit.disks.drive-set-spindown
polkit-auth shows my authorizations, thus:
[resi@nomad ~]$ polkit-auth | grep mount
org.freedesktop.devicekit.disks.filesystem-mount
org.freedesktop.devicekit.disks.filesystem-mount-system-internal
org.freedesktop.devicekit.disks.filesystem-unmount-others
It seems to me that I am authorized for all actions listed above, I guess thats because this user is in both the wheel and root groups.
However, when I try to actually mount something nothing has changed.
[resi@nomad ~]$ devkit-disks --mount /dev/sdc
Mount failed: Not Authorized
Since policykit is now properly configured I can use polkit-action or polkit-gnome-authorization to modify the default values in the way polkit expects me to (not tampering with with the *.policy files).
[resi@nomad ~]$ polkit-action --action org.freedesktop.devicekit.disks.filesystem-mount
action_id: org.freedesktop.devicekit.disks.filesystem-mount
description: Mount a device
message: Authentication is required to mount the device
default_any: yes (factory default: no)
default_inactive: yes (factory default: no)
default_active: yes
But even now mounting fails because I'm not authorized.
Back to the start, if I change the factory defaults in org.freedesktop.devicekit.disks.policy mounting succeeds.
I think there might be 2 bugs involved here:
1.) missing links to policy files in /usr/share/PolicyKit/policy/
2.) policykit fails to consider overrides for factory defaults
What do you think?

Time Machine backups cause error message "Disk No Ejected Properly"

I have a 2011 iMac using OS X version 10.9.4. I have had to change the external hard drive used with my Time Machine to get more storage. Every time the Time Machine backs up (every hour), I get the message "Disk Not Ejected Properly" Eject "FreeAgent GoFlex Drive" before disconnecting or turning it.
I am concerned about any damage that is happening because of this message. I researched this on this forum and other users had a similar problem. I tried 2 of the easier solutions: 1) make sure none of the boxes are checked in System Energy Saver (ie. put hard disks to sleep when possible, etc.) and 2) buy and connect a USB hub that has it's own power supply to keep the external hard drive powered constantly. Neither of these solutions has worked for me. I still get the message. So I have two questions. First, is damage being done to my computer because it "thinks" that I did not properly eject the disc. And, second, is there anything else I can do to stop this message besides not using the freeagent disc?

I had the same problem. it turned out to be a cable issue. Contact seagate for replacement cable.
http://www.seagate.com/support-all/

Time Machine Disk Self-ejects, and more

I'm using a 1 TB FreeAgent GoFlex external USB drive as my Time Machine back up. Half the time it works perfectly, other times it suddenly ejects itself and I get a message about how the disk was ejected improperly. If I pop out the USB cable, then plug it back in, the disk remounts and goes on as before. Other times it will begin backing up, and seems to get stuck in "back up" mode. It keeps evaluating the main hard drive until it's time to shut down for the day. I can't make it stop. If I go ahead and shut down, the computer quits everything down to the bare desktop, then locks up. If I shut down while not stuck in "evaluating" the computer shuts down normally.
How do I make the disk quit self ejecting?
How do I keep it from getting stuck "evaluating" the disk?

I have a similar problem which only recently developed with my Seagate FreeAgent Desktop Classic. The drive ejects only during TM backups. Here's the message from the TM widget:
Starting standard backup
Backing up to: /Volumes/TM/Backups.backupdb
Event store UUIDs don't match for volume: Macintosh HD
No pre-backup thinning needed: 309.2 MB requested (including padding), 365.05 GB available
Unable to rebuild path cache for source item. Partial source path:
Error: (-39) SrcErr:YES Copying (null) to (null)
Copied 8845 files (84.6 GB) from volume Macintosh HD.
No pre-backup thinning needed: 534.6 MB requested (including padding), 280.31 GB available
Stopping backup.
Error: (-43) SrcErr:NO Copying /Users/angeloferraro/Library/Preferences/Macromedia/Flash Player/#SharedObjects/EC6L7AJD to (null)
Copied 8625 files (184.9 MB) from volume Macintosh HD.
Copy stage failed with error:11
Stopping backupd because the backup volume was ejected!
Error writing to backup log. NSFileHandleOperationException:* -[NSConcreteFileHandle writeData:]: Input/output error
Backup failed with error: 27
have reformatted the external drive which has not helped.
No problem if TM is switched off. No disk errors with Apple's native disk utility, however Seagate's drive manager reports that "the selected drive failed its most recent diagnostic test" but does not provide any further information.
Have sent an email to seagate and awaiting their reply. Drive still under warranty.

Disk mounting/ejecting problems... ESPECIALLY FireWire

Similar Messages

Maybe you are looking for