MacBook Doesn't Wake Up (when External FireWire Drives attached)

Anybody else notice their MacBook not waking up from sleep when Fire Wire drives are attached, specifically through the FW port or the Express Card port.
Granted, the MacBook wakes up 50% of the time in general with nothing attached...kind of a crap shoot.

Hi, I have a macbook air for some time now. It works fine, starts reasonable fast and with one exception I'm pleased with it.If I closed the LID or press the on-off button the system sleeps. When I open the lid the next day (8 -12 hrs later) the system doesn't wake up. The log file which I presume is send to Apple did lead to a patch. I saw on the support site various conversations in respect to this issue with various results.
I see that the problem of James even returned and was not reported to be resolved until now.
In my log I have the following messages, "Sleep failure" of last few days. What should I do to resolve this, or is Apple delivering a patch for this?
<Start log copy>
17-09-14 03:14:01,755 powerd[16]: com.apple.message.domain: com.apple.sleep.failure
com.apple.message.signature: Capability Failure
com.apple.message.summarize: YES
Sender_Mach_UUID: 83C854AA-0FB9-30C2-8443-D10D781E0E25
17-09-14 09:24:37,960 powerd[16]: com.apple.message.domain: com.apple.sleep.failure
com.apple.message.signature: Platform Failure
com.apple.message.summarize: YES
Sender_Mach_UUID: 83C854AA-0FB9-30C2-8443-D10D781E0E25
20-09-14 03:31:14,288 powerd[16]: com.apple.message.domain: com.apple.sleep.failure
com.apple.message.signature: Capability Failure
com.apple.message.summarize: YES
Sender_Mach_UUID: 83C854AA-0FB9-30C2-8443-D10D781E0E25
20-09-14 09:56:41,453 powerd[16]: com.apple.message.domain: com.apple.sleep.failure
com.apple.message.signature: Platform Failure
com.apple.message.summarize: YES
Sender_Mach_UUID: 83C854AA-0FB9-30C2-8443-D10D781E0E25
<end log copy>
regards, Roderick.

Similar Messages

  • IMac won't boot with SATA external firewire drive attached

    I have an 1T Hitachi SATA drive enclosed in a Macally firewire enclosure. If it is attached either in series with other IDE firewire drives or directly, my iMac will boot only to the Apple icon and will not engage the gear icon. If I disconnect the drive the iMac will boot normally with all the other IDE firewire drives attached. I've troubleshot with both Macally and Hitachi, received a replacement enclosure and have an RMA from Hitachi. Before I send the Hitachi back with the possibility of a replacement not fixing the problem, I am asking whether there is a known problem with external SATA drives in particular. TIA. -Dave

    I have the same problem exactly but with two firewire 800 drives attached. Both are LaCie d2 500 gb drives. I have tried each one as the first in the series with no luck. I have not tried to connect with any other type of cable.

  • Mini system installer disc doesn't install on a external firewire drive!

    The osx insteller disc came with my mine doesn't allow me to install the system onto a external firewire hard drive. I am wondering if the retail mac osx be any different?
    Would the retail version be able to create the GUID partition?
    .....Thanks a bunch.
    BTW, what is the normal cpu operaton temperature and the max fan speed?
    Message was edited by: Cup of Tea

    The OSX installer should be able to install on your external, though if you're talking about an external drive connected to an Intel Mac, it MUST be partitioned in the GUID scheme first. Both original install disk and retail Tiger can perform this partitioning using Disk Utility. Simply boot to the install disk or retail Tiger, exit the installer, run Disk Utility, select the external drive (the top entry showing drive name and size), click the partition tab, then the options button, then the top option for GUID Partition Table. Click OK, then the Partition button.

  • Airport disconnects when external firewire drive is connected.

    Hi,
    This is a weird one. I bought an external firewire/USB2 enclosure a few days ago which I paired up with Western Digital 320GB drive. I haven't used it a lot as it's only for backups.
    Today I was having trouble connecting to my Airport Express network in Windows XP (Bootcamp). Well it was Windows so I just thought it was being flaky. Then when I rebooted into OS X I had the same problem. I thought long and hard trying to work out what was different and pretty soon realised it was the drive. I had it connected to back up the Windows partition. It seems that airport just dies the minute the drive is connected via Firewire (but not USB2).
    It's an el cheapo from ST Labs, called the S-111
    System profiler lists the following:
    Manufacturer: Prolific PL3507 Combo Device
    Model: 0x1
    GUID: 0x50770E00071002
    Maximum Speed: Up to 400 Mb/sec
    Connection Speed: Up to 400 Mb/sec
    Sub-units:
    (1394-ATAPI rev1.10) Unit:
    Unit Software Version: 0x10483
    Unit Spec ID: 0x609E
    Firmware Revision: 0x12804
    The system.log says the following:
    Sep 16 19:29:02 josh diskarbitrationd[67]: disk1s2 hfs 3D4319C6-A855-366D-AC5D-3856B6826C3E Backup /Volumes/Backup
    Sep 16 19:29:03 josh diskarbitrationd[67]: disk1s3 msdos 00000000-0000-0000-0000-000000000000 UNTITLED /Volumes/UNTITLED
    Sep 16 19:29:22 josh kernel[0]: vmnet: bridge-en1: interface en is going DOWN
    Anyone have any ideas?
    Josh

    OK. I know no one answered this one but I'm going to update this just in case anyone has a similar problem.
    Seems I jumped the gun (a little).
    I hadn't tried both firewire 400 ports on the external drive. I tried the other and the problem disappeared.
    So the lesson I've (re)learned is that you should try every possible port/cable configuration possible before seeking help.
    Josh

  • Macbook Pro will not boot on external Firewire drive. Mybook with 2 partitions containing 2 OSX images using CCC. Volumes will not display when booting but do display when the internal drive is running OSX using Startup utility.

    I've reset SMC and PRAM several times. Activiatng Terminal from Recovery HD displays the following:
    -bash-3.2# diskutil list
    /dev/disk0
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *250.1 GB   disk0
       1:                        EFI                         209.7 MB   disk0s1
       2:                  Apple_HFS Macintosh HD            249.2 GB   disk0s2
       3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
    /dev/disk1
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:     Apple_partition_scheme                        *1.3 GB     disk1
       1:        Apple_partition_map                         30.7 KB    disk1s1
       2:                  Apple_HFS Mac OS X Base System    1.3 GB     disk1s2
    /dev/disk2
       #:                       TYPE NAME                    SIZE       IDENTIFIER
       0:      GUID_partition_scheme                        *2.0 TB     disk2
       1:                        EFI                         209.7 MB   disk2s1
       2:                  Apple_HFS MyBook1                 999.8 GB   disk2s2
       3:                  Apple_HFS MyBook2                 767.2 GB   disk2s3
    Any comments are greatly appreciated.

    Applejack is just a command-line "front-end" for a number of different command-line tools you can use in single-user mode, and I'm not sure whether it's Lion-compatible.  You can always try booting into single-user mode and executing:
    /sbin/fsck -fy
    That's unlikely to solve your problems, though.  Since you can't boot from two different hard drives and your optical drive, that indicates there's a more serious hardware issue, or multiple hardware issues.

  • Finder Crashes When External Hard Drive Attached (see 1390772 also)

    Chris Johnson started this thread under a different question and I wanted to make the problem more obvious in the title. Not sure the ettiquete of the board and if I should paste the prior thread into this one.
    Here is the link:
    http://discussions.apple.com/thread.jspa?threadID=1390772&tstart=0
    Thanks!
    B

    hi RSB--
    i would try a few things for this. go to utilities > disk utility and then select the macintosh hd. click on "repair disk permissions". also i would boot to the install disk for your current operating system and run disk repair. http://docs.info.apple.com/article.html?artnum=106214. another thing to try is to select any of the drives (just highlight, don't double click) and then press the apple and the i keys on the keyboard to bring up an information window. at the bottom portion of the window you will find your read/write/execute privileges. try to make sure everything is owned by you if possible and that you have full privileges. you may have to unlock the window to make changes. let me know if any of that helps the situation. [ 8 ) ]

  • Disappearing external Firewire drive.

    Hi friends.
    My wife's mini has a LaCie external firewire drive attached. She uses it with Backup and it just suddenly disappeared.
    It appears to be on and working- but not showing up on her desktop. Is there a way on restart-- to force her mini to look for peripherals it's not seeing? I always get such great help on this forum. Thanks in advance. Dan

    I'm curious if/how that link worked out for you. I have been observing problems with Firewire/USB for the past month or more that I allowed my clients to upgrade to 10.4.9 and 10.4.10.
    I am finally starting to cross over into the belief that an update within 10.4.9/10.4.10 caused a failure with external Firewire drives -- now I will include USB drives in that belief. I was skeptical for a long while but the coincidences don't line up.
    My guess is that Apple updated the Firewire/USB bridge -- perhaps they even made it more efficient. The cost may be that various external drive enclosure manufacturers who coexisted (or even accommodated) Apple's previous bridge, now fail. I don't know if you recall the 10.3.x update that took down Firewires for quite some time to come. The only solution that worked for me then was to boot into OS 9, mount the drive there, and then restart in OS X. A very round-about solution.
    So far, I have observed the following failures in the past couple months:
    Powerbook G4 1.4Ghz (or so): failed USB LaCie hard drive, no clicking/non-harddrive malfunction
    Mac Pro -- Intel Core Duo: two failed Firewire enclosures (Nexstar Vantecs). The drives inside were perfect but the enclosures ceased functioning first on an iMac G5 and then continued to disappear on a Mac Pro tower.
    One of these enclosures had also disappeared from a new iMac - Intel. I could get the thing to mount and then it would disappear overnight -- my thought is that perhaps the drives don't remount after sleep? I did not do extensive tests.
    I have had another client on an as-of-yet-unknown machine (purchased in last couple years) lose a LaCie Firewire drive... no clicks or hardware failure indications. I will investigate this week.
    I had yet another client lose two LaCie drives connected to a Dual 1.0 Ghz G4 Tower. One LaCie drive enclosure seemed to fail completely at Firewire 800 speed and transfer slowly but reliably when dumbed down to Firewire 400. The other LaCie was unreadable even when I transferred the drive to another enclosure. I am still investigating.
    On a Mac Mini (Intel) new enclosures from PPA Galaxy Metal Gear would not daisy chain without disappearing.
    I admit that I don't want to believe that the recent OS updates could have caused this -- especially after the debacle of 10.3.x. But it is definitely possible and not altogether unlikely. Consider this discussion about a LaCie firmware update tool meant to make them compatible: http://lovemac.org/2007/04/28/external-lacie-firewire-disappeared-from-the-deskh elp/
    Not having attempted the Firmware update yet myself, I cannot vouch for it. Firmware updates are not to be taken lightly but they are just the sort of thing that might make the Firewire/USB bridge in the LaCie's compatible with Apple's updates/fixes. Of course, that leaves the other vendors' drives high-and-dry.
    Usually, Apple or Apple defenders like to say that the vendors should be writing perfect code and it's not Apple's fault if they optimize or fix code which breaks the vendors' equipment. I think this is a ridiculous argument. Granted, in our legal system, Apple would not usually be obliged to accommodate "faulty" code (even if they might happen to have been the originators of it). But what is the true definition of faulty code? In the realm of technology and computers, there are likely countless kludges and fixes and patches. The whole idea and goal is FUNCTION (ideally). Optimizing or standardizing code is important of course. It means that future authors can rely on the accuracy of the previous authors. But the world -- especially the tech world -- stands to gain more from consistency... from the language of the vernacular. If all the equipment and all the operating systems up to a point have deigned to speak in a consistent kind of pidgin, then it doesn't make complete sense to "fix" it to be some more "accurate" or "refined" grammar. Language works because it's locally consistent, not because it's accurate to some holy grail of grammar.
    Specifically: Apple can't switch code midstream and say "oh, I made the code 'accurate,' not my fault if your stuff was built on bad code." Up until that point THEIR stuff was built on "bad" code too! It's a ridiculous argument but what can you do.
    At this point, I imagine that Apple attempted to fix something with 10.4.9 and 10.4.10 that it had tried to fix before with OS 10.3.X. Instead, I believe it created an intermittent failure in Firewire/USB drives that leaves the drives inoperable as often as unmountable. It's just a theory based on having seen enough updates and upgrades have a really bad effect. I think people think we live in some future where we can trust our technology and tech manufacturers to get things right (or at least get things right often enough). Surely they're doing the best they can...no doubt.
    I'm a little frustrated I should ramp down my expectations. I know. It's not like this is 2020 or 2050. It's really only 2007.
    Good luck to us all.

  • I have a new 2.0GHz Intel Core i7 macbook pro and my external firewire drive is causing the laptop to lock up

    I have a new 2.0GHz Intel Core i7 macbook pro and my external firewire drive is causing the computer to lock up. The drive seems to sleep and then never wakes and the laptop locks up. I've had this drive connected to an older 2.0 core duo macbook pro and a 3.0GHz quad core macpro with no issues. It's a ministack v3 drive, 2GBs, fw400+800, sata and usb. Any ideas? And can I stop the drive from going to sleep?
    Thanks.

    Check with the drive's manufacturer to see if they might have a firmware update for the enclosure; it sounds like the enclosure's firmware isn't properly detecting the FireWire wakeup sequence.
    Obviously this could also be a bug with the new MBP's firmware, so it wouldn't hurt to ask the Genius Bar at your local Apple Store; in particular, ask them to show you that the sleep/wakeup sequence on your MBP works with some other FireWire drive.

  • Audio cutting out when using D2 external Firewire Drive

    Hi,
    I have just upgraded to Logic Studio, using the following setup:
    Macbook Pro
    Motu 828
    AMT 8
    Logic Studio
    D2 Lacie 500GB Firewire Drive
    As the MacBook's internal hard drive is not sufficient to record and playpack efficiently, I was advised to get an external Firewire Drive. Given that I have very little space on my laptop - (am running windows on a partition also) I am trying to save my logic files to the external HD. When creating tracks specifically using Audio Instruments, the playpack keeps cutting out.
    I am connecting the HD via usb 2. I am also having to freeze the tracks in order to record more layers. There is lots of clipping and latency. I thought by using the external, this problem would be resolved.
    The HD is not playing back the tracks fast enough, and keeps cutting the audio out. The audio cuts out everytime the blue light on the drive flashes.
    I cannot save the files to the MackBook HD as there is notenough space.
    Is there something very wrong with my setup?
    any advice would be really appreciated.
    ps. I am a bit of a newbie
    thank you in advance.
    Spy

    Connect it via firewire 800. USB2 is not good for audio or video streaming.
    I have 3 D2's connected to my mac pro, works like a charm.
    good luck.

  • Macbook causes external firewire drive to operate constantly

    I have a Macbook 1.83MHz with 2GB of RAM installed. Whenever I connect my 80GB LaCie external firewire drive, the drive commenses to do a rapid cycle as if I were copying a large file to it and does not stop for the duration of being attached to the computer. Searching through files on the hard drive is very slow, and if I click on a file in column view, the finder beachballs for several minutes while the info or preview is being generated. The drive is the only device in the chain and worked great with my previous machine, a dual 867MHz G4 mirror drive.
    Any thoughts as to what might be going on? Thanks.

    well, i attached my other firewire drive and it started doing the same thing, but i was able to add it to spotlight's "ignore" list and the problem went away. so this is probably the issue, but i can't make it stop on the original firewire drive because whenever i try to add it to spotlight's ignore list, the beachball spins for a few seconds then nothing shows up in the list.
    checked firmware, everything up to date. next step is to reformat...
    too bad spotlight doesn't default to NOT indexing everything you stick into the computer... (or at least dump indexing way back in the priority queue so it doesn't get in the way like this)

  • Files corrupted when written to external Firewire drive

    I recently discovered that files transferred from my internal ATA drives to my external Firewire drives have been getting corrupted.
    The corruption is most noticable in Quicktime movies where I can see individual video frames with pixelated blocks of color and short noise bursts in the audio. My concern, however, is that it is happening to any file type and the corruption may not be noticed until it is too late.
    I read a few posts from the end of last year that stated the Firewire ports of the B & W G3s have problems. The general solution appeared to be the use a dedicated PCI card.
    Here are my questions:
    (1) Is there a formal aritcle discussing this problem? (I didn't find one)
    (2) Copying files is a VERY basic function of an operating system. Shouldn't there be some kind of error generated if a copied file doesn't match the source? (like a checksum error).
    (3) If a PCI Firewire card is the answer, is there anything to watch out for when selecting one?
    (4) I'd like a better way to compare souce and destination files after a copy. What application can I use to do a low-level comparison of two files?
    Thanks,
    John

    John,
    My reference to RAM was by way of example. Another example of error opportunities is in rebuilding the desktop. I have had files lost because of the desktop changing when the removable media or external hard drive is changed to a computer with a different OS. Rebuilding the desktop restored the files.
    The guys that wrote Disk Warrior could give the brutal full on why files appear, disappear and get corrupted. I choose to not trust any one medium so I backup my backups. Sometimes a reliable routine is better than an explaination.
    No one has responded to my inquiry about why jpeg files are corrupted when copied from the B&W to a PC zip disk but not to an external HDD. I should try that with a PC formatted HDD. The odd thing is that quicktime will read the corrupted file but jpegview will not. Or the otherway around. I have forgotten the details because I gave up on trying to get an answer.
    I would be interested in reading more about file transfers during the process of burning a CD and how buffer underun technology works. As you said, the answer may be so detailed that the explanation wouldnot be understandable without becoming a text book!
    Jim

  • Blue screen of death when La Cie external firewire drive connected

    I tested a LaCie external firewire drive on my iMac and it worked fine. I packed it up well and posted it to a friend who gets the blue screen of death when the LaCie is connected to her iMac. She's not even trying to boot from it.
    My iMac is 9.1  and hers is 8.1.  We are both running Snow Leopard.  Was there some problem once upon a time with chipsets or am I mis-remembering?
    TIA

    Create an ISO (Encore) or folder on your hard drive (Encore or Premiere Elements) and then use the FREE http://www.imgburn.com/index.php?act=download to write files or folders or ISO to disc for DVD or BluRay (send the author a PayPal donation if you like his program)
    Imgburn will read the ACTUAL disc brand from the disc, which is not always the same as the box label (Memorex is notorious for buying "anything" and putting it inside a Memorex box)
    When you write to disc with Imgburn, use the SLOWEST possible speed setting, so your burner has the best chance to create "good, well formed" laser burn holes... since no player is required to read a burned disc, having a "good" one from a high quality blank will help

  • Blue Screen Result When Installing To External Firewire Drive

    I can't afford to have problems with programs not running on Leopard on my 17" G4 1.67 GHz 2 GB RAM PowerBook so I am trying to install it on an external Firewire drive. I was hoping to test out Leopard with certain applications by running it from the external drive.
    The Firewire drive has two partitions, one has my backup clone of the PowerBook and the other just has files and about 35 GB of free space. The installation would be a new installation so none of the files that deal with login or Application Enhancer that are being talked about in other threads are an issue.
    My first attempt to install brought up a blue screen after the installation restart. I left it there for about 30 minutes then powered off the PowerBook by holding down the power button. I started it again and held down the option key, picked the install disk as startup, went through the disk utility repair disk (found no problems). After that I picked the new install on the external from the startup preferences and it simply restarted to a blue screen. I left that one for about 20 minutes then powered down.
    I went back to the Powerbook Tiger OS system, deleted all the installed folders on the external and tried a completely new install. Once again it went to the blue screen after the Leopard install restart. This time I left it overnight and this morning the display was dark and upon waking it up with a tap of the space bar was greeted by the bluescreen again.
    I talked to my Apple hardware rep who knows the equipment that I am working with and we talked about all the steps I went through and he has no explanation why it won't work on the external.
    I would love to hear from anyone that may have insight for this particular external FW drive installation perspective.

    Joe-
    Is the drive partitioned to APM? (Sorry I took Anton's reply to be yours.) What was the type fo partitioning onthe disk with the success? I am not knowledgable enough in those error messages on the system.log file, but one thought is - after the memory upgrade, did you clear the PRAM (long shot, but do it anyway)? The machine booting on one external Firewire drive (#2) implies the problem is with the external FW disk (#1) you are using. Some other people had the bus error, but with Time Machine. (Not to go on a tangent, but TM seems to have problems when the disk name has non-alphanumeric in it.)
    Hoping someone who knows the syslog errors and the boot sequence will pipe in here.

  • When I try to burn a CD off of my MacBook Air (from iTunes) using the external CD drive, it acts like it is burning the CD, but then when I try to play it the CD is blank.

    When I try to burn a CD off of my MacBook Air (from iTunes) using the external CD drive, it acts like it is burning the CD, but then when I try to play it the CD is blank.

    Many thanks for the diagnostics.
    Failed while scanning for CD / DVD drives, error 2380.
    Error while opening iTunes CD driver.  This could be caused by a corrupted iTunes file or a conflict with other older CD burning applications, either currently installed or previously installed and uninstalled incorrectly.
    With that one, I'd start with solution 3 from the following document:
    iTunes for Windows: Optical drive is no longer recognized, or "Disc burner or software not found" alert after install

  • What to set when capturing to an external firewire drive?

    When capturing to an external firewire drive that will also be used to edit the video, what do I need to set in the Scratch Disk window? Just the scratch disk? Do I need to also set the waveform cache? thumbnail cache? autosave vault?
    Thanks.

    Depends on your overall configuration/workflow...but I'll usually set my external for Video Capture/Video Render/Audio Render. Then both cache files to my system drive and my Autosave Vault to the external...unless I have an additional internal or second external. I keep my Project files on the system/startup drive.
    When you click on the 'Set' button, it's best to simply select the root of whatever drive you want to use. This alleviates the possibility of uncontrolled heirarchy of 'scratch folders' cluttering up your system. If you select the root, then FCP creates a "Capture Scratch" folder at the root level, and each new project gets it's own folder within the main "Capture Scratch" folder.
    Setting your autosave vault somewhere other than where your project file is located, can save your butt, if your system drive (or wherever your project file is located) decides to crash.
    Others may do it differently, as I do on occasion...just depends on what drives/Mac I have available at the time.
    Hope that helps.
    K

Maybe you are looking for