Time Machine disk not mounting after sleep

Greetings,
I am having a problem with the external USB disk (500GB Iomega) that I have set up for Time Machine not remounting after my iMac wakes back up. Nothing I have tried, short of rebooting, seems to cause the Mac to notice the drive. I have tried turning the drive off and back on, but that didn't work, and neither did unplugging and re-plugging the USB cable. (I suppose obviously) Time Machine won't do any backups and complains that "The storage location for Time Machine backups can't be found." Time Machine Set Up says "Next Backup: When Disk is Connected." If I reboot, the disk will show up and Time Machine will commence backups, but then, after the machine sleeps, I have the same problem again.
When I first plugged the drive in last night the computer immediately recognized it, mounted it, and asked me if I wanted to use it for Time Machine. I didn't have to do anything. I then successfully started Time Machine and it did its initial and several hourly backups as expected. Then the machine went to sleep and the disk never came back (short of a reboot).
The computer is a brand new 24-inch, 2.8Ghz, iMac with Leopard installed from the included DVD immediately after opening the box - I did nothing before installing Leopard.
This is my first Mac (I am a Unix refugee) so I may very well be doing something entirely stupid, but surely external disks should still be mounted (or automount) after the computer returns from sleep. What am I doing wrong? I also don't see any way to force Leopard to mount the drive, but I probably just don't know where to look.
To be completely clear... the drive is plugged directly into the iMac on USB, no external hub. There is no networking involved with this disk. I didn't make any kind of settings to the disk (either to the disk itself- there aren't any, or on the iMac when I plugged the disk in). The only thing I did was answer "Yes" when Time Machine popped up a window asking if I wanted to use the new disk for backups. Last time the disk was mountet (before the computer went to sleep again) I ran the Disk Utility and it said the drive was fine.
Thanks,
Mark
P.S. I'm sorry if this has been discussed elsewhere but I couldn't find it. Like I say, I'm new to the Mac and to these forums, so please forgive me if this post is redundant.

Greetings,
intelligenceresigned wrote:
Ok, I went into console, and forced my iMac to sleep to see what the console would show was actually happening. I am not a very computer savvy person, but this is what the console said:
Nov 8 21:50:27 steve-freunds-computer kernel[0]: USBF: 48332.754 AppleUSBEHCI[0x52ab000]::Found a transaction past the completion deadline on bus 0xfa, timing out! (Addr: 3, EP: 2)
I believe this may be related to the problem. The AppleUSBEHCI appears to identify the offending driver/controller as the EHCI controller (Enhanced Host Controller Interface), or the controller that handles usb 2.0 High Speed (usually usb 1.1 and 2.0 Full Speed are handled by something that would be called a UHCI or Universal Host Controller Interface) USB High Speed is the fastest of the three usb speeds and although the interface is compatable with the slower speeds, works rather differently than the other two. Beyond that I'll have to look into what this message means (I'm brand new to the Mac - I've only had this one a couple of weeks).
*Could others that are seeing this problem please post how many usb ports on the computer, not total devices connected to hubs or anything, but actual, physical ports on the computer that they are using?* Experimenting a little, on mine at least, I have not had the problem discussed in this thread when only two (out of the three available) of the physical USB ports on the Mac are used. Again on mine at least, it also doesn't seem to matter what, with the exception of external hubs, is plugged into the ports. Replacing the external drive with a flash drive or iPod Touch produces the same results, so it doesn't appear to have anything to do with the Iomega drive that I started seeing the problem with - it may be that that was just the third thing I plugged in (or not - I realize that I am a sample of one).
It also seems to be that things connected to an external hub continue to work after the other two ports have failed. This is probably why most keyboards (mercifully) keep working - they are usually hubs (Apple's external ones are). I can't guarantee this however because I haven't really tested it - just observed it so far to be the case for me so far. Hubs do work differently than ordinary usb "functions" as the usb spec calls them.
Lastly...
If you have Xcode installed (assuming you have it installed in the default /Developer location) there is a tool in /Developer/Applications/Utilities called "USB Prober" that can provide some useful USB information.
In my case, once a device stops working I see the status of the non-functioning devices reported as:
High Speed device @ 2 (0xFA200000): ............................................. External HD (did not respond to inquiry - 0xe00002ed, might be Suspended)
High Speed device @ 3 (0xFA400000): ............................................. HP Color LaserJet 2605dn (did not respond to inquiry - 0xe0004051, might be Suspended)
And indeed the usb ports in question do appear to be behaving as if the host (the Mac) has them suspended - but I can't be entirely sure. I will try to look into this some more later if I can.
Thanks,
Mark
P.S. To save questions: I've tried all the easy stuff: Switched cables, swapped out the hub I have on one of the ports, tried different devices in the ports (so far an HP printer, Iomega external disk, iPod Touch, and Sony usb flash drive). Nothing resolved the issue. My keyboard and mouse are connected to a 2.0 High Speed hub. I've tried using another hub, but it didn't make any difference.

Similar Messages

  • Time Machine Disk not mount

    Time Machine has been making its regular backups but now for some reason, Time Machine is not recognizing the external disk. I have tried restarting the machine, powering off and on the external drive, changing firewire ports and nothing has worked. Does anyone have any ideas I have not tried? Thanks!

    Colin1 wrote:
    Hopefully the sheer weight of numbers of TC owners complaining about the back-up function not working will eventually move Apple to investigate. I have tried everything and believe it is a problem caused by the OSX 10.5.4 update, at least that's when my similar problems started.
    I'm hoping that's what it is. My BRAND NEW iMac + BRAND NEW 500GB TC Can't talk,
    It tells me that the TC failed to mount everytime Time Machine starts.
    My TC at home (1TB) & this MacBook Pro haven't given me this ever since Feb., until last night. Luckily, I restored to a TC backup from a few days ago on my MacBook Pro & it's backing up fine so far now at home.
    My local Apple store is stunned at my work one, though.

  • Time Machine disk not mounting

    I have an external HD with Time Machine running. My computer is going to the shop later today. All of a sudden, my little external HD didn't want to mount (and it's only 8 months old). I used Disk Utility and got it to mount, but it said it couldn't repair it. It said I should backup what I could and erase the drive. However, since Disk Utility hung while trying to finish, I decided to try it again on another Mac. This time it ran through the repair and said the disk is fine. It finished off with this statement: "Updating boot support partitions for the volume as required."
    So here's my dilemma:
    I'd rather NOT erase this drive, since it's got my Time Machine backup on it. On the other hand, if it is failing, I'd like to know why and take action before it causes a problem (i.e. warranty and the ability to get back up quickly when my Mac comes back). I do have other backups, but none as handy as this one.
    If you have experienced this, I'd like to hear from you. And, if there is already a thread about this, I couldn't find it.
    Thanks very much!

    I have a 2TB WD Western Digital portable external hard drive partitioned into two drives, one for storage and the other for Time Machine.  For some reason my Time Machine drive wasn't mounting.  I could not verify, repair, or even eject the HD at all for that matter.  The Storage partition was working fine so I know that this is a software issue.  I did what Linc Davis recommended and booted up into Recovery Mode and tried to verify and repair using the Disk Utility there with no luck.  However I was able to mount the drive using the blue "Mount" button in Disk Utility and then I restarted the computer.  Then my Time Machine partition was there and I was able to verify it and it has no problems.  I then even performed a back up with no issues.
    So this is in fact a software problem.  The only thing that has changed for me is that I have just cloned my start up drive and put in a new SSD.  Also I had to unplug my MacBook Pro battery to reset the SMC (even the keyboard was not working) due to the bug where your computer turns off and dies because of Lightning strike (plugging in a Lightning cable).  Which would also be a software bug.  That post is here... My Mac randomly just turned off and now it wont turn back on, the charger light is faintly flashing green and amber?!?!

  • Time machine disk not found after installing Mountain Lion

    Since doing the upgrade, ML cannot find my external FW backup disk. I have tried resetting the PRAM (Command+Option+P+R) but this has no effect. I am running on a iMac 2.4GHz intel core 2 duo with 4Gb of Ram. Everything else seems ok, although boot-ups seem to take longer than previously under Lion
    Any help/advice welcome.
    Thanks
    Ray

    Thanks Pondini, but the mac failed to find the drive at all. Solved it now by resetting the SMC - basically powering down, disconnecting the power cable for a few minutes and then switching back on again.
    Best regards
    Ray

  • Why is Time machine backup not working after Mavericks upgrade?

    Why is Time machine backup not working after Mavericks upgrade?

    I had the same problem due to the Fire Wire port.  Apple tested it told me it is OK!, I tried a new cable, and have tested both ports on my back up device.  I find it strange that as soon as I installed Mavericks.  The drive does work using USB.  It could be a coincidence, I don't absolutely know at this point, my back up drive ports could stop working, but I doubt it!

  • Time Machine does not start after external hard drive is connected

    Time Machine does not start after external hard drive is connected

    These are the iCloud storage options: http://www.apple.com/icloud/includes/lightbox-storage.html
    Also bear in mind that:
    1. restoring data over icloud takes time
    2. iCloud is not designed as a replacement to Time Machine.

  • Possible solution: Time Machine can not mount disk

    Like many of you, my Time Machine started acting up after working fine for months.
    I have an external USB (Western Digital 500GB) drive connected to a Airport Extreme (N-speed) as an AirDisk.
    I have an iMac (iSight 160GB) connected via ethernet to the AEX and a MacBook (60GB) connected to the AEX. Both have less than half HD usage.
    After a few months, the MacBook would fail to backup properly: “Unable to Mount” message after the TM process was going for a few minutes. I could access the WD drive in R/W mode otherwise from the same machine. I read on these boards that I should erase the sparsebundle on the WD drive associated with the MacBook. I did that, and all was then well.
    Fast forward a few months, again the same problem on the same machine. I ran DiskWarrior against the WD drive to ensure permissions were fine. Mind you that the iMac TM backup’s have been working fine all along.
    Yesterday I solved my problem by reading various tips on these boards:
    - Always mount the AirDisk via “==> Go ==> Connect to Server” within the Finder
    o As per Apple KnowledgeBase article
    - *Proper Computer Name*
    o Ensure that your computer has a proper name in the Sharing Preference pane.
    o Go into System Preferences --> Sharing.
    o Is the box labeled “Computer Name” empty? If it is blank, you need to put in a name for your computer. Otherwise Time Machine won’t be able to perform backups. Additionally, Time Machine needs to differentiate this computer from others on your network (i.e. "Bills MacBook" vs "Office iMac"). As a result, no two Macs should have the same name. If the "Computer Name" field is blank, create a unique name for this Mac.
    o Also, Time Machine may experience problems if your computer name includes certain characters. Make sure the computer name only includes ASCII characters from the following set.
    o (0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ)
    o Once a change in the computer name occurs, you should stop and restart Sharing on the affected computer. Uncheck and then recheck Sharing in the Services list on the left.
    The combination of these two steps has my MacBook working smoothly once again with Time Machine, Airport Extreme and an AirDisk.
    GOOD LUCK

    Most likely, the power interruption corrupted the sparse bundle containing your backups.
    Try to repair them per #A5 in the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.

  • Time Machine - Browse other Time Machine disk - not showing all files

    I have an Xserve, running 10.6 server, where we keep all of our files. It backs up via Time Machine. Many users use the shared drives on the Xserve, and I encourage them to put their files there. We work in a design / production house, so many people collaborate on files. Due to the nature of the business, with frequent design changes, we need to go "back in time" and pull out previous versions of designs, etc. Usually I handle this by remotely accessing the Xserve, starting up time machine, and pulling out the old versions of files from the backups.
    However, when I'm not in, I wanted to make this option available to another user, without giving her full access to the server. I discovered the "Browse Other Time Machine" option, and after making my Time Machine disk (actually a rack-mount Mercury Pro RAID array) shared, I was able to mount it on her Mac, also running 10.6. I thought this would be a nice solution.
    The problem is, in some directories, when browsing from her computer, Time machine is showing no backups. It's impossible to go back more than a few snapshots with it. Meanwhile, if I do it on the server, everything is fine. So I thought perhaps it was a permissions issue, but I don't want to muck up the permissions on my time machine drive and risk losing everything. I did add her account as a user with read-only access to the time machine drive, and told it to apply to all sub folders. This didn't make any difference.
    What is the issue? Is it permissions? Or is my Time Machine too large (6TB) that it can't load all the data over the network? Has anyone encountered this before? What is the best way to troubleshoot?

    If you still have the old imac connect tbe two with an ethernet cable and use migration assistant. Move your data to a new Mac - Apple Support

  • External hard drive time machine backups not mounting

    I have used Seagate 500.11 external hard drive as a backup location for the time machine for over two years. I just got a message that it had not updated in over thirty days.  It is not listed on FInder, but it is listed on the disc utility.  The Time machine backups  are grayed out on the disc utility screen and cannot be mounted, even after the repair and verification tests said that their volumes were ok.  What should I do?

    Time Machine does not create bootable clones. It does not even create a bootable backup. If that's what you prefer then do not use Time Machine.
    If you use Time Machine then you must allocate at least twice as much space for the backups than the capacity of the drive you are backing up. A 2 TB backup drive would be suitable for a 1 TB main drive or smaller.
    If you plan to create a bootable backup, then partition the backup drive with one partition the size required for the clone. Then use the other partition for you additional storage neeeds.

  • Time Machine will not backup after Snow Leopard.

    Pertinent information:
    Macbook Pro pre-aluminum body
    Time Machine backing up over network to a ppc mini with 500 gb external drive.
    This worked fine with Leopard for over a year. I installed Snow Leopard last week and this is the first time I got a chance to try a Time Machine backup. Doesn't see to want to backup no matter what I do.
    I tried:
    - Renaming the sparsebundle
    - Disconnecting/reconnecting the external drive.
    - Re-selecting disk in Time Machine config and nothing works.
    - Even ran Verify Disk and Repair Disk on the external drive. Found a header error, but Disk Utility said it was minor and fixed it.
    It seems that Time Machine isn't even trying to figure out what needs to be backed up. Here is the log. Below this snippet of the log I will post some of the other things I see...
    09/12/2009 - 7:01PM Sep 12 2009 7:01:31 PM com.apple.backupd[5688] Starting standard backup
    09/12/2009 - 7:01PM Sep 12 2009 7:01:31 PM com.apple.backupd[5688] Attempting to mount network destination using URL: afp://[email protected]/Backup
    09/12/2009 - 7:01PM Sep 12 2009 7:01:31 PM com.apple.backupd[5688] Mounted network destination using URL: afp://[email protected]/Backup
    09/12/2009 - 7:01PM Sep 12 2009 7:01:31 PM com.apple.backupd[5688] Warning: Destination /Volumes/Backup does not support TM Lock Stealing
    09/12/2009 - 7:01PM Sep 12 2009 7:01:31 PM com.apple.backupd[5688] Warning: Destination /Volumes/Backup does not support Server Reply Cache
    09/12/2009 - 7:01PM Sep 12 2009 7:01:33 PM com.apple.backupd[5688] Disk image /Volumes/Backup/mbphome_001ec2038641.sparsebundle mounted at: /Volumes/Backup of mbphome
    09/12/2009 - 7:01PM Sep 12 2009 7:01:34 PM com.apple.backupd[5688] Backing up to: /Volumes/Backup of mbphome/Backups.backupdb
    09/12/2009 - 7:01PM Sep 12 2009 7:01:36 PM com.apple.backupd[5688] Event store UUIDs don't match for volume: Macintosh HD
    09/12/2009 - 7:01PM Sep 12 2009 7:01:38 PM com.apple.backupd[5688] Node requires deep traversal:/ reason:must scan subdirs|new event db|
    09/12/2009 - 7:01PM Sep 12 2009 7:01:47 PM com.apple.backupd[5688] Stopping backupd to allow ejection of backup destination disk!
    09/12/2009 - 7:01PM Sep 12 2009 7:01:47 PM com.apple.backupd[5688] Backup canceled.
    09/12/2009 - 7:01PM Sep 12 2009 7:01:47 PM com.apple.backupd[5688] Failed to eject volume (null) (FSVolumeRefNum: -138; status: -36; dissenting pid: -1)
    09/12/2009 - 7:01PM Sep 12 2009 7:01:48 PM com.apple.backupd[5688] Ejected Time Machine network volume.
    Notice the:
    Destination /Volumes/Backup does not support TM Lock Stealing
    and:
    Destination /Volumes/Backup does not support Server Reply Cache
    Does anybody know what that means?
    I also see this maybe every third time I try a manual backup. There are many more lines, I'll post a few for you to get the gist:
    09/12/2009 - 6:49PM Sep 12 2009 6:49:36 PM com.apple.backupd[5560] Error: (6) getxattr for key:com.apple.backupd.SnapshotState path:/Volumes/Backup of mbphome/Backups.backupdb/mbphome/2009-08-16-173353
    09/12/2009 - 6:49PM Sep 12 2009 6:49:36 PM com.apple.backupd[5560] Error: (6) getxattr for key:com.apple.backupd.SnapshotState path:/Volumes/Backup of mbphome/Backups.backupdb/mbphome/2009-08-20-192750
    09/12/2009 - 6:49PM Sep 12 2009 6:49:36 PM com.apple.backupd[5560] Error: (6) getxattr for key:com.apple.backupd.SnapshotState path:/Volumes/Backup of mbphome/Backups.backupdb/mbphome/2009-08-27-220252
    09/12/2009 - 6:49PM Sep 12 2009 6:49:36 PM com.apple.backupd[5560] Error: (6) getxattr for key:com.apple.backupd.SnapshotState path:/Volumes/Backup of mbphome/Backups.backupdb/mbphome/2009-09-09-013744
    Can't really find any info on any of these errors. I search through discussions and it doesn't seem that anybody is having the same problems as I'm having, seems they are having different problems.
    Thanks in advance for any kind of information you can provide on this problem.

    Unfortunately a "full reset" didn't do it. The log looks almost exactly the same...
    09/12/2009 - 11:26PM Sep 12 2009 11:26:47 PM com.apple.backupd[1141] Starting standard backup
    09/12/2009 - 11:26PM Sep 12 2009 11:26:47 PM com.apple.backupd[1141] Attempting to mount network destination using URL: afp://[email protected]/Backup
    09/12/2009 - 11:26PM Sep 12 2009 11:26:48 PM com.apple.backupd[1141] Mounted network destination using URL: afp://[email protected]/Backup
    09/12/2009 - 11:26PM Sep 12 2009 11:26:48 PM com.apple.backupd[1141] Warning: Destination /Volumes/Backup-1 does not support TM Lock Stealing
    09/12/2009 - 11:26PM Sep 12 2009 11:26:48 PM com.apple.backupd[1141] Warning: Destination /Volumes/Backup-1 does not support Server Reply Cache
    09/12/2009 - 11:26PM Sep 12 2009 11:26:50 PM com.apple.backupd[1141] Disk image /Volumes/Backup-1/mbphome_001ec2038641.sparsebundle mounted at: /Volumes/Backup of mbphome
    09/12/2009 - 11:26PM Sep 12 2009 11:26:50 PM com.apple.backupd[1141] Backing up to: /Volumes/Backup of mbphome/Backups.backupdb
    09/12/2009 - 11:26PM Sep 12 2009 11:26:52 PM com.apple.backupd[1141] Event store UUIDs don't match for volume: Macintosh HD
    09/12/2009 - 11:26PM Sep 12 2009 11:26:54 PM com.apple.backupd[1141] Stopping backupd to allow ejection of backup destination disk!
    09/12/2009 - 11:26PM Sep 12 2009 11:26:54 PM com.apple.backupd[1141] Node requires deep traversal:/ reason:must scan subdirs|new event db|
    09/12/2009 - 11:26PM Sep 12 2009 11:26:54 PM com.apple.backupd[1141] Backup canceled.
    09/12/2009 - 11:26PM Sep 12 2009 11:26:55 PM com.apple.backupd[1141] Ejected Time Machine disk image.
    09/12/2009 - 11:26PM Sep 12 2009 11:26:55 PM com.apple.backupd[1141] Ejected Time Machine network volume.
    Still confused over the "does not support TM Lock Stealing" and "does not support Server Reply Cache"? Are those the possible causes? I'm really at a loss cause like I said in my reply before, Time Machine just always worked.

  • Time Machine disk not recognised

    My G5 PowerMac has been away for repair; it's needed a new logic board. It was away for nearly two weeks. Now Time Machine doesn't recognise the external drive which contains the Time Machine backups from last November. It wants to do a backup from scratch and says there isn't enough space on the disk.
    Is there any way of getting the Time Machine to recognise the previous backups and start adding to them?
    I'll be very grateful for any advice.

    To TM, it is a different computer. The logic board includes your Ethernet "Mac Address", which is a unique number that TM uses to be sure it knows which Mac is which.
    There is a fairly elaborate way to attempt to persuade TM that the existing backups really are for your "new" Mac: http://www.macosxhints.com/article.php?story=20080128003716101
    It is very easy for the inexperienced user of Terminal (and the not-so-inexperienced as well) to make an error with Terminal, get no error message, and have it not work, so try it at your own risk.
    But there is an alternative: hold down the Option key while selecting the TM icon in your Menubar. The +Enter Time Machine+ option changes to +Browse Other Time Machine Disks.+ That's a bit misleading, but it will take you into the normal TM interface where you can see and restore from the old set of backups.
    Even if you're successful with the Terminal work, your first backup with the new logic board may be a full one -- every file and folder on your system. If TM decides to do that, you cannot prevent it.
    So if your TM disk/partition isn't at least 2.5 times the size of the data it's backing-up, your best bet may be to just erase it with Disk Utility and let TM start over.

  • Time Machine disk not showing up in Migration Assistant

    I have backed up my Snow Leopard with Time Machine and I'm trying to import my stuff into Lion using Migration Assistant. However, my Time Machine disk is not showing up in Migration Assistant even though it's connected and shows in Finder. Any idea why?

    I couldn't migrate from Snow Leopard drive either -- Snow Leopard used PGP encyption, migration copied the files, but they seem inaccessible to Lion with "permission denied" errors.
    It sounds like you did migrate successfully. It's normal for the permissions to be wrong -- Migration Assistant creates a new account with the files from the old one.
    What I would do in your place is start over. First, decrypt the SL volume and uninstall PGP. You should do that anyway, because PGP is a turkey and not needed in Lion. Erase the Lion volume (assuming you have no data on it that isn't already on your SL volume), reinstall Lion, and then use Setup Assistant, not Migration Assistant, to do the migration.

  • Time Machine does not backup after using second Mac on different volume.

    Hi.
    I use an airport extrem with an external usb hdd. It has 3 partitions. On the first one I made an TM-backup (MBP 2.2 Leo), all worked fine. Then I made a second TM-backup (MacBook) on the second partition. Worked fine too. But now TM on my MBP is not able to backup any more. When TM starts, it just "prepares" but never actually backs up.
    What is the Problem and how do i fix it?
    08.05.08 19:43:48 /System/Library/CoreServices/backupd[192] Backing up to: /Volumes/Backup of Thomas MBP/Backups.backupdb
    08.05.08 19:43:51 /System/Library/CoreServices/backupd[192] Event store UUIDs don't match for volume: Mac HD
    08.05.08 19:43:51 /System/Library/CoreServices/backupd[192] Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
    Message was edited by: Thomas_xp

    Time Machine will only back up HFS+ (Mac OS Extended) formatted drives. Reformatting will erase the drive so make sure everything on it is safely copied elsewhere and verify a few test files before erasing the drive. Getting rid of the FAT32 formatting has been problematic for quite a few people. The directions in this article are for good for getting rid of the FAT32 formatting. They are for formatting a Time Machine disk but the directions will work just as well for your purposes.

  • Time Machine does not show after installing Lion?!

    I upgraded to Lion and now my Time Machine does not work. When I connect the disk it starts and then shuts down. It does not show neither on desktop or on Time Machine. Any ideas. I hate the thought of reinstalling Snow Leopard but...
    Thank you in advance
    Matej

    No reason to reinstall Snow Leopard.
    What's shown on the Time Machine Preferences window for Latest Backup?  If it shows "Error" in red, see #C2 in Time Machine - Troubleshooting.
    If not, a clue may be lurking in your logs.  Use the widget in #A1 of Time Machine - Troubleshooting to display the backup messages from your logs.  Locate the backup in question, then copy and post all the messages here.

  • Time machine disk not ejecting

    I'm having trouble ejecting my Time Machine disk from my mid-2012 retina MBP since installing Yosemite.  If I control-click on the disk image and select EJECT, the image grays out a little but won't eject.  If I try to start Disk Utility, it hangs and won't start.  However, if I first start Disk Utility and then select the Time machine drive and select Unmount followed by Eject, the disk will eject.
    Anybody else having this problem?  I don't recall having this issue with earlier versions of OS X.

    Well, nobody replied but I'll post what solved the problem:  installing an app called "Mountain."  I also noticed that a recent Yosemite update including a fix for Time Machine problems but I don't know if it address this problem.  In any event, since installing Mountain, I never have a problem ejecting discs.

Maybe you are looking for