External disk not seen after sleep on Yosemite

My sleep/wake issue on Yosemite affects the external disk (USB 3 connection) and the printer (HP 8600 all-in-one): On wake, after a long sleep, my iMac late 2012 shows an error message saying that the disk was not properly ejected and, in fact, the disk icon disappears from the desktop. The printer issue is even worse: no longer seen by the system after a long sleep but also right after a print, i.e.the next print won't start because the system no longer "sees" it.
About the printer, I originally thought it could be a driver issue but now that I see a similar problem occurring on the disk, I start thinking the driver could be only part of the problem.
Most of times, a restart fixes the problem but this is very annoying.

Similar Messages

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.

External disk not recognized after lateset mavericks update

Just updated my MacBook pro Retina to 10.9.5
since then, my external hd WD My passport Ultra does not mount on the finder. It is visible in Disk Utilty, but is greyed.
ANy suggestions?
Thanks

the WD ext disk has just appeared on desktop and did the usual back-up process...
Yesterday I checked it several times and disk utility even told me that the ext disk should be repaired, which it failed to do...
now it is working again. (must have just needed a good night's sleep...)
Should I still be worried? Any comments, please?

External HD not showing after Migration to Yosemite on New iMac

Morning All,
Just upgraded my wife's 8YO iMac using Migration Assistant.
Fixed the Hang Problem that occurred with that, but now the external media drive, with our family iTunes Library refuses to mount on the new computer. Mounts perfectly on my MacBook Air but does not show up on the iMac at all, not in Finder, not in Disk utility and not using any of the Terminal Window searches that I found. ,
Please help as my boys will get frustrated if they can't access their movies on Apple TV and there is a week of school holidays to go
Cheers Steve

Wish we new what version of OS X you have installed, that sure would be helpful.
How is the external media drive connected to the iMac, don't assume we know we have no idea!

ZTE Mf190s Internet USB Modem not working after upgrading to Yosemite.

ZTE Mf190s Internet USB Modem not working after upgrading to Yosemite. any salutation!!

Follow these steps:
go to system preferences.. Open Network..
CONFIGURATION: DEFAULT
TELEPHONE NUMBER : #99*
leave account name and password columns blank
Now go to ADVANCED
IN MODEM MENU
VENDOR : GENERIC
MODEL : GPRS / 3G
Press ok
Then CONNECT.. Enjoy.

How do i set colors on javascript coding page, colors are not seen after installing Firefox version 8

How do i set colors on javascript coding page, colors are not seen after installing Firefox version 8 . I am using WaveMaker application for web development

Make sure that you allow pages to choose their colors and that you haven't enabled High Contrast in the Accessibility settings.
*Tools > Options > Content : Fonts & Colors > Colors : [X] "Allow pages to choose their own colors, instead of my selections above"
*http://kb.mozillazine.org/Website_colors_are_wrong
*http://kb.mozillazine.org/Websites_look_wrong

My mac book pro is not booting after sleep

My mac book pro is not booting after sleep...Pls anyone help me!!!

Hello adibah2731,
We've an article that proivdes a host of useful tips that can get your Mac booting up again.
Troubleshooting: My computer won't turn on
http://support.apple.com/kb/TS1367
Cheers,
Allen

Why is airplay not selectable after sleep?

Why is airplay not selectable after sleep?
Even if I was using airplay prior to sleep, on wake up my MBP defaults to internal speakers and airplay is not selectable from the drop down menu. I have to reboot, which works but is tedious. Macbook Pro Retina, 3Ghz i7, OS10.9.5

Why is airplay not selectable after sleep?
Even if I was using airplay prior to sleep, on wake up my MBP defaults to internal speakers and airplay is not selectable from the drop down menu. I have to reboot, which works but is tedious. Macbook Pro Retina, 3Ghz i7, OS10.9.5

External Hard Drive will not mount after upgrading to Yosemite

After upgrading to Yosemite, my external 3TB hard drive will not mount... can't see in Finder, but does appear in Disk Utility. Follow steps to Repair disk, but get a message that D.U. cannot repair disk.

See mount section.
Disk Unmount Using Terminal
Disk Utility – Force Mount Disk

USB drives not mounting after sleep

I've started to experience a frustrating problem whereby any connected USB drive fails to mount after the Mac has been to sleep. Rather alarmingly I get an error message saying "disk not ejected properly"
The set-up I have is two USB drives connected to my early 2011 MacBook Pro via a D-Link mains powered USB hub. I'd planned to have the Mac wake up at 2am for SuperDuper to perform a backup but it's proving impossible as the drive is never available and I have to do a restart before the Mac sees it again.
I've tried a few solutions I've seen online such as installing Jettison (didn't work) and making sure Spotlight isn't indexing the drives (didn't work either).
Can anyone suggest anything else?
THANKS

You can boot OS X from USB2 or FireWire as well as internal drives. There are also two unused SATA ports hidden away inside that OS X can use, but Vista/XP won't see. There is a $24 kit from NewerTech to connect SATA cable, run out PCI slot adapter, and use eSATA shielded cable to a 2-drive enclosure ($67+).
I always boot from an alternate boot drive before ever doing an Mac OS update - repair the drive, do backup, other maintenance. And even sometimes apply the update from there (requires using a standalone downloaded combined update, which is preferred method). Never apply an update w/o a working bootable backup. Something that requires multiple licenses I suspect with XP/Vista.
I have external backup and restore drives for Vista, Mac OS boot drive, 2-drive RAID for Vista, and Vista boot drive.
All of my drives are GUID. Vista is 64-bit, and has some support for EFI (SP1 will bring better support for UEFI).
Disk arbitration has been updated and improved and some products even had to wait for later versions (10.4.8 introduced a number of fixes I understand). I would be more concerned with make of drives and whether they have GUID/GPL or MBR partition tables.

Mail App Not Opening After Upgrading to Yosemite

I upgraded to Yosemite this morning from Mountain Lion. Everything seemed to go well until I clicked Mail for the first time. The migration process started, but the app never opened and will not open. I immediately get a crash dialog and that's it. I click reopen and get the dialog box saying, "The last time you opened Mail, it unexpectedly quite while reopening windows." I can do this over and over again. I've read the other threads, but they are not helping me.
This is the log created after it attempts to open:
11/20/14 12:45:23.286 PM sharingd[1035]: 12:45:23.286 : Stopping Handoff advertising
11/20/14 12:45:25.288 PM sharingd[1035]: 12:45:25.288 : Stopping Handoff advertising
11/20/14 12:45:28.039 PM com.apple.xpc.launchd[1]: (com.apple.imfoundation.IMRemoteURLConnectionAgent) The _DirtyJetsamMemoryLimit key is not available on this platform.
11/20/14 12:45:28.082 PM bird[1037]: Assertion failed: ![_xpcClients containsObject:client]
11/20/14 12:45:28.083 PM bird[1037]: Assertion failed: ![_xpcClients containsObject:client]
11/20/14 12:45:28.091 PM bird[1037]: Assertion failed: ![_xpcClients containsObject:client]
11/20/14 12:45:29.706 PM Mail[1333]: *** Assertion failure in -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:], /SourceCache/Mail/Mail-1993/MailFramework/Accounts/MFMailAccount.m:4467
11/20/14 12:45:29.708 PM Mail[1333]: An uncaught exception was raised
11/20/14 12:45:29.709 PM Mail[1333]: Absolute path passed into -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:]: /Inbox/INBOX/Sent Messages
11/20/14 12:45:29.709 PM Mail[1333]: (
0   CoreFoundation                      0x00007fff8c70264c __exceptionPreprocess + 172
1   libobjc.A.dylib                     0x00007fff90a806de objc_exception_throw + 43
2   CoreFoundation                      0x00007fff8c70242a +[NSException raise:format:arguments:] + 106
3   Foundation                          0x00007fff86b5b5b9 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195
4   Mail                                0x00007fff8ce1bf5c -[MFMailAccount mailboxForRelativePath:isFilesystemPath:create:] + 251
5   Mail                                0x00007fff8cd79404 -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:] + 491
6   Mail                                0x00007fff8ce1d696 +[MFMailAccount mailboxForURL:forceCreation:syncableURL:] + 473
7   Mail                                0x00007fff8ce34168 __43+[MFMailbox queueUpdateCountsForMailboxes:]_block_invoke_2 + 68
8   CoreFoundation                      0x00007fff8c62cea6 __65-[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:]_block_invoke + 102
9   CoreFoundation                      0x00007fff8c62cdb9 -[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:] + 217
10 Mail                                0x00007fff8ce340b6 __43+[MFMailbox queueUpdateCountsForMailboxes:]_block_invoke + 275
11 Foundation                          0x00007fff86ba52e8 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7
12 Foundation                          0x00007fff86a91905 -[NSBlockOperation main] + 97
13 Foundation                          0x00007fff86a7059c -[__NSOperationInternal _start:] + 653
14 Foundation                          0x00007fff86a701a3 __NSOQSchedule_f + 184
15 libdispatch.dylib                   0x00007fff86032c13 _dispatch_client_callout + 8
16 libdispatch.dylib                   0x00007fff86036365 _dispatch_queue_drain + 1100
17 libdispatch.dylib                   0x00007fff86037ecc _dispatch_queue_invoke + 202
18 libdispatch.dylib                   0x00007fff860356b7 _dispatch_root_queue_drain + 463
19 libdispatch.dylib                   0x00007fff86043fe4 _dispatch_worker_thread3 + 91
20 libsystem_pthread.dylib             0x00007fff92efc6cb _pthread_wqthread + 729
21 libsystem_pthread.dylib             0x00007fff92efa4a1 start_wqthread + 13
11/20/14 12:45:29.709 PM Mail[1333]: *** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'Absolute path passed into -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:]: /Inbox/INBOX/Sent Messages'
*** First throw call stack:
0   CoreFoundation                      0x00007fff8c70264c __exceptionPreprocess + 172
1   libobjc.A.dylib                     0x00007fff90a806de objc_exception_throw + 43
2   CoreFoundation                      0x00007fff8c70242a +[NSException raise:format:arguments:] + 106
3   Foundation                          0x00007fff86b5b5b9 -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195
4   Mail                                0x00007fff8ce1bf5c -[MFMailAccount mailboxForRelativePath:isFilesystemPath:create:] + 251
5   Mail                                0x00007fff8cd79404 -[MFIMAPAccount mailboxForRelativePath:isFilesystemPath:create:] + 491
6   Mail                                0x00007fff8ce1d696 +[MFMailAccount mailboxForURL:forceCreation:syncableURL:] + 473
7   Mail                                0x00007fff8ce34168 __43+[MFMailbox queueUpdateCountsForMailboxes:]_block_invoke_2 + 68
8   CoreFoundation                      0x00007fff8c62cea6 __65-[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:]_block_invoke + 102
9   CoreFoundation                      0x00007fff8c62cdb9 -[__NSDictionaryM enumerateKeysAndObjectsWithOptions:usingBlock:] + 217
10 Mail                                0x00007fff8ce340b6 __43+[MFMailbox queueUpdateCountsForMailboxes:]_block_invoke + 275
11 Foundation                          0x00007fff86ba52e8 __NSBLOCKOPERATION_IS_CALLING_OUT_TO_A_BLOCK__ + 7
12 Foundation                          0x00007fff86a91905 -[NSBlockOperation main] + 97
13 Foundation                          0x00007fff86a7059c -[__NSOperationInternal _start:] + 653
14 Foundation                          0x00007fff86a701a3 __NSOQSchedule_f + 184
15 libdispatch.dylib                   0x00007fff86032c13 _dispatch_client_callout + 8
16 libdispatch.dylib                   0x00007fff86036365 _dispatch_queue_drain + 1100
17 libdispatch.dylib                   0x00007fff86037ecc _dispatch_queue_invoke + 202
18 libdispatch.dylib                   0x00007fff860356b7 _dispatch_root_queue_drain + 463
19 libdispatch.dylib                   0x00007fff86043fe4 _dispatch_worker_thread3 + 91
20 libsystem_pthread.dylib             0x00007fff92efc6cb _pthread_wqthread + 729
21 libsystem_pthread.dylib             0x00007fff92efa4a1 start_wqthread + 13

Reinstalling OS X Without Erasing the Drive
Boot to the Recovery HD: Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
Repair the Hard Drive and Permissions: Upon startup select Disk Utility from the main menu. Repair the Hard Drive and Permissions as follows.
When the recovery menu appears select Disk Utility. 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 click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the main menu.
Reinstall OS X: Select Reinstall OS X and click on the Continue button.
Note: You will need an active Internet connection. I suggest using Ethernet if possible because it is three times faster than wireless.
Also see:
Reinstall OS X Without Erasing the Drive
OS X Yosemite- Reinstall OS X
OS X Mavericks- Reinstall OS X
OS X Mountain Lion- Reinstall OS X
OS X Lion- Reinstall Mac OS X
     Note: You will need an active Internet connection. I suggest using Ethernet
                 if possible because it is three times faster than wireless.

External drive unmountable & invisible after sleep (osx 10.8.1)

Hello,
yesterday evening, the lid of my mbp (retina, medio 2012) was closed while it was displaying the screensaver, with an external USB disk plugged in.
After I opened the lid and logged back in, I saw a dialog mentioning that the disk was removed without being properly unmounted.
Since then. I have not only been able to mount it; but it doesn't show up at all.
Not in the finder, not in Disk Utility, not in the Terminal under /Volumes or under /dev/...
I tried the following, so far without any result:
restarting the Finder
rebooting the machine
resetting the pram & nvram
trying the disk on another mac
using either one of the MBP's two USB slots
I have used this disk in this enclosure to store my photo's and music on, until yesterday without any problems. The only thing that I wondered about was that it did not seem a lot faster than I was used to with USB 2 - but that wasn't really an issue.
Further details:
The disk is a 2.5 inch 700 GB disk in a USB 3.0 enclosure. It's formatted as Mac OS Extended (Journaled).
The disk has been used only a few months without any prior problems.
The enclosure is a König CMP-MOBSTOR96, it's about a month old.
The disk has run fine until now without using an additional power supply. There is, however, a 5 volt input on the enclosure.
The enclosure is connected to the MBP via the USB 3.0 cable that came with the enclosure.
I looked in the Console messages, and found that there were a couple of messages apparently related to this issue:
04-09-12 13:42:55,000 kernel[0]: USBF:
2540.458
[0xffffff802ed5ce00] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 2 of Hub at 0x14000000)
04-09-12 13:42:59,000 kernel[0]: USBF:
2544.946
[0xffffff802ed5ce00] The IOUSBFamily was not able to enumerate a device.
04-09-12 13:43:01,000 kernel[0]: USBF:
2546.268
[0xffffff802ed5ce00] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 2 of Hub at 0x14000000)
04-09-12 13:43:05,000 kernel[0]: USBF:
2551.148
[0xffffff802ed5ce00] The IOUSBFamily was not able to enumerate a device.
04-09-12 13:43:07,000 kernel[0]: USBF:
2552.470
[0xffffff802ed5ce00] The IOUSBFamily is having trouble enumerating a USB device that has been plugged in. It will keep retrying. (Port 2 of Hub at 0x14000000)
04-09-12 13:43:08,000 kernel[0]: USBF:
2553.790
[0xffffff802ed5ce00] The IOUSBFamily gave up enumerating a USB device after 10 retries. (Port 2 of Hub at 0x14000000)
04-09-12 13:43:08,000 kernel[0]: USBF:
2553.790
[0xffffff802ed5ce00] The IOUSBFamily was not able to enumerate a device.
I found some discussions googling for these messages that seemed to suggest that the cause of the problem is either the cable, insufficient power available to the drive, or failure of the enclosure.
But because this issue happened directly after the "disk not unmounted properly" warning message that followed the closing and opening of the MBP lid, it would be very unlikely that the enclosure or cable would have failed at exactly the same time.
I can (and will) get another enclosure and try it with that, but I was wondering if anyone had any other suggestions that I could look into? It is in any case a bit awkward that problems if this caliber arise after someone merely shuts the lid of the computer causing it to sleep. Also. it was in all likelyhood not writing to the disk at that time.
Thanks in advance!

update
I had kept the electronics part (with the SATA and USB connectors) of a damaged USB 2.0 enclosure. Using that on the above drive DOES work. Also reversely, putting another (known working) drive in the enclosure also fails to show up on the MBP.
Apparently, either the enclosure or the USB cable is broken. That's not strange in itself. But what puzzles me a lot is that it broke at the exact time that the lid of the MBP was closed (for a few minutes) and opened again, causing the "disk not unmounted properly" warning.
I'd really like to know if there is any imaginable way in which the one can have caused the other.
Of course, it is also possible that it is not truly broken but that it somehow, suddenly found the power supply through the USB cable insufficient. Which would be even weirder.
The good thing is that my data and disk are fine. Replacing the enclosure isn't a big deal. But I am hugely confused.

External Disks Ejected Improperly During Sleep

New MB Pro with a LaCie 2Big Thunderbolt external ejects the external drives when it goes to sleep. I'll put the system to sleep in the evening and find it on in the morning with the "Disks Not Ejected Properly" message. The problem is intermittent. I see a lot of discussion about this but no experts have weighed in and there is no solution that works (including the "Swiss" solution).
I'm very concerned about damaging the data on my external, is there a solution to this problem, or a workaround?

Ask Apple. This is a long-running problem that predates Maverick. If you search "improperly eject" you will find many ciscussions and many different machines and configurations involved. I've got an iMac and a LaCie 2big Thunderbolt running Time Machine. I've "temporarily" solved the issue by turning off "sleep." That is, I have unchecked everything in the "energy saver" section of preferences. Before I did that I got the "improperly ejected" message. I turned off the LaCie and turned it back on and it showed up, without apparent damage of any kind -- except that until I did that there would be no backups to TM, so if I didn't notice the "imp" message, I might go for hours or days without.
This is either an inherent problem with Apple soft or firmware, or Apple has not communicated the right information to manufacturers such as LaCie which are building HDs wiuth Thunderbolt, apparently primarily for the new Mac product line.
LaCie support recently advised me that "Apple has recently acknowledged problems within current versions of Mac OS X that can cause external drives to become improperly ejected during system sleep. Patches from Apple to correct these issues are forthcoming." We shall see ............

Nano not seen after update

Since installing the latest iTunes update my 4 gig Nano is NOT seen at all by my G4 iMac. I cannot even install the iPod update. I reset the Nano, did repair disk permissions, restarted the computer, nothing changed. Used a different USB port. Nothing changed.
running OS X 10.4.7
Allan

Since installing the latest iTunes update my 4 gig
Nano is NOT seen at all by my G4 iMac. I cannot even
install the iPod update. I reset the Nano, did repair
disk permissions, restarted the computer, nothing
changed. Used a different USB port. Nothing changed.
running OS X 10.4.7
Allan
After I wrote this question I went back to my computer and decided to do some additional troubleshooting. I tried some of the other USB ports and found that fianally the Nano was seen by the computer and I was able to update it with the new software with no problem.
So now I know that I may have a problem with one of my USB ports in my iMac which may not be easier to solve but at least I have been able to get my Nano to work with my iMac.
So I have solved my own problem - word to the wise - many times the solution to your problem is right in front of you if you take the time to do more troubleshooting yourself.
Allan

Thunderbolt ethernet not waking after sleep

I have the same problem with my MBP retina with Maverickks 10.9.1 losing connectivity after waking after sleep while on battery.
People from apple support don't help in solving the problem.
Does any one have the right solution? I would appreciate.
Apple please fix this problem!!!

Thanks for the link, Judy.
As far as I know, I am up-to-date as far as OS updates are concerned. At least this is what the mac is telling me when I go to updates. The article you've linked here looks to be more specifically for OSX Lion and Snow Leopard, but not Yosemite.
I would think that the likely fix here is to upgrade the firmware for thunderbolt, but I don't know how to check what macbook pro thunderbolt firmware or what thunderbolt display firmware is present. What I see in System Information doesn't match the firmware updates associated with your link.
Here's what I have in System Information/Hardware/Thunderbolt Device Tree:
Vendor Name:
Apple Inc.
Device Name:
MacBook Pro
UID:
0x0001000A1
Route String:
0
Firmware Version:
20080d.0
Domain UUID:
F05339A8-AD68-2B57
Port:
Status:
Device connected
Link Status:
0x2
Speed:
Up to 10 Gb/s x2
Receptacle:
1
Port Micro Firmware Version:
1.2.1
Cable Firmware Version:
0.1.18
Cable Serial Number:
C4M202701HCDNWFAG
Thunderbolt Display:
Vendor Name:
Apple Inc.
Device Name:
Thunderbolt Display
Vendor ID:
0x1
Device ID:
0x8002
Device Revision:
0x1
UID:
0x00010001001
Route String:
1
Firmware Version:
22.2
Port (Upstream):
Status:
Device connected
Link Status:
0x2
Speed:
Up to 10 Gb/s x2
Port Micro Firmware Version:
0.0.21
Cable Firmware Version:
0.1.18
Cable Serial Number:
C4M202701HCDN
Port:
Status:
No device connected
Link Status:
0x7
Speed:
Up to 10 Gb/s x2
Port Micro Firmware Version:
0.0.21
Do you know from this info if they need updating? It's not really made clear what to look for from the article. The article refers to Thunderbolt firmware v1.0, the Thunderbolt display firmware update is v1.1.
Any ideas? Is there somewhere else I should look for this info?
Regards
Craig.

External disk not seen after sleep on Yosemite

Similar Messages

Maybe you are looking for