1 31 32 33 34 35 Previous Next 925 Replies Latest reply: Jul 6, 2014 1:20 PM by willhowe Go to original post
  • 480. Re: Disk Drive ejecting itself
    Andy2006 Level 1 Level 1 (0 points)

    My original post about this is on P24 of this thread. If you read the whole page, it'll give you the required kexts to downgrade and tell you which ones not to mess with so your KB/trackpad will still work. Honestly, at this point I think Apple ought to move this solution to the top of the thread and make it a sticky. It's the only one that seems to reliably work.

  • 481. Re: Disk Drive ejecting itself
    macdim Level 1 Level 1 (0 points)

    It's not a perfect solution. I did this and it worked for a short time but eventually I had issues again. The only thing that fixed it was the genius bar swapping the whole system out for a new one. Obviously this isn't possible if you're out of warranty, but if you have warranty, to go the Apple store and have them address the problem.

  • 482. Re: Disk Drive ejecting itself
    Andy2006 Level 1 Level 1 (0 points)

    I've had literally no issues with this solution that I didn't cause myself (by letting Software Update install an updated version of OS X). This includes an always-connected Drobo with 4x2TB drives and a variety of smaller "Passport" style drives that get connected on a random basis, plus a few thumb drives.

     

    Makes me wonder if your issues started again because of a software update. But it makes no matter; my machine is long out of warranty and doesn't really get used for anything other than serving a massive iTunes library to an AppleTV, so I don't really need to update the OS on a regular basis. Now that it's working, I don't plan on messing with it unless and until somebody can verify that this solution works under Lion, too.

  • 483. Re: Disk Drive ejecting itself
    oscarfromguilford Level 1 Level 1 (0 points)

    I want to clarify what I actually did to get this working (having ignored, as pointed out, some of the finer points of this thread's earlier suggestions).

     

    My problem started in Snow Leopard and persisted or even worsened in Lion (to which I had upgraded - not a clean install).

     

    So, I dragged the Lion kexts (IOUSBFamily.kext, IOUSBMassStorageClass.kext) to the desktop and replaced them with 10.6.4 kexts of the same name.

     

    When I had all the trouble, I deleted the 10.6.4 kexts, and dragged the Lion ones BACK from the Desktop. It was then that I rebuilt permissions, zapped PRAM, reset SMC, booted in Safe Mode).

     

    So, it is now working, still (I am now backing up my 1TB OptiBay drive with no issues) with the SAME exact Lion kexts with which it was failing before.

     

    Go figure.

  • 484. Re: Disk Drive ejecting itself
    KCNottm Level 1 Level 1 (0 points)

    I'm a late-comer to this problem but I have similarities.

     

    I'm on an iMac 10.4.11 (a bit old, I admit) and I'm running a Western Digital My Passport with it. My problem has recently started; if I let the Mac go to sleep, when I wake it I get the error message telling me that a "Device Removal" has happened which was not the way to eject such a device (yes, I know about that). However, I haven't ejected the WD; all I have done is wake the Mac up from sleeping.

     

    When I ok on that error message, I then get the big overlay on the screen telling me to do a restart by holding the power button for several seconds. I do that and everything is ok. Until perhaps a few days when it will happen again.

  • 485. Re: Disk Drive ejecting itself
    Kelly Davis Level 1 Level 1 (15 points)

    Well I was pretty bummed out today to discover that despite what I said earlier about having fixed the problem by reverting the kexts, the problem is still occurring. I verified that an update had not replaced the older kexts. The 10.6.4 ones were still all there, so unfortunately, that does not look like a (permanent) fix.

  • 486. Re: Disk Drive ejecting itself
    oscarfromguilford Level 1 Level 1 (0 points)

    Yup. Me too.

     

    Because of its intermittent nature, this is obviously a difficult problem to study with rigor. There is no question that the problem can be made better for an extended time, and can become worse for no clear reason. I offer the following as simply more data to try to bring to bear on this.

     

    When I got it fixed a few days ago, I was able to read/write well over 2 TB with no problems. This was with Lion 10.7.2 kexts. Then the problem re-surfaced, for no clear reason, i.e., what I was doing with what hardware and what software had not changed.

     

    Downgrading to 10.6.4 kexts, repairing permissions, rebuilding caches did NOT work this time. I couldn't get the drive (any of my USB drives)  to stay mounted through two minutes of read/write operations.

     

    Re-upgrading to 10.7.2 kexts with all necessary operations (repair permissions, rebuild caches) did not fix the problem either.

     

    While it is undoubtedly voodoo, here is what DID fix the problem (again), or I should say, here is what I did after which the problem continues for now not to reveal itself in spite of another TB's worth of read/writes:

     

    1) Delete 10.7.2 versions of IOUSBFamily.kext and IOUSBMassStorageClass.kext from System/Library/Extensions/

     

    2) Drag stored versions of the SAME kexts BACK into that location, effectively only "touching" them, I suppose, since they are copies of ones that were installed when I was HAVING the problem - mine are on the Desktop.

     

    2) Shut down computer (after being sure that Lion recovery disk is on the startup volume).

     

    3) Restart, holding down Command-Option-R, thus booting into Lion recovery. Run Disk Utility and repair permissions. Reboot holding down shift key to boot into safe mode.

     

    4) Shut down. Remove battery and power, hold down power button long enough to reset SMC. Replace power and battery, boot computer holding down Command-Option-P-R long enough to zap PRAM.

     

    Then I was back in business - 1TB cloned and counting. I have two future experiments planned WHEN I need to fix it again (who has time to do nothing but investigate this problem?) - I would like to see which of the above I could eliminate. I will try JUST zapping PRAM and resetting SMC without messing with the kexts at all. Also, I will try signing in as root and seeing whether that helps. It would be nice to narrow the software/hardware gap on this question a bit more.

  • 487. Re: Disk Drive ejecting itself
    Richard E. Cooke Level 2 Level 2 (220 points)

    You have  to rule out some variables.  What your doing is not going to isolate the problem, you made a good start, but now you have to be much more careful.

     

    i posted this a few months ago, its the general-purpose diagnostic procedure for electronic devices.  If you follow it, you will either figure out the true root cause on your own, or you will be able to post enough information for people like me to figure it out for you.

     

    If you want help (especially from me) then you have to do this, in order:

     

    - Google your drive make and model, see if anybody else is having the same problem. If you are the only person on the planet with drive "XYZ" with a problem then chances are you have a hardware problem in the drive, computer, hub, or cables (not necessarily in that order).

     

    - if there is a support site for the drive post a question there about your symptoms (and read/search previous posts). Again, if your the only person in the world with a problem...

     

    - Search this thread for you drive make (not model) to see if there have been other problems with their products (actually this is a good idea for a google search too). I tell clients to do this BEFORE they buy something for the first time. This comes under "buyer beware" I think.

     

    - Do some experiments. Try the drive on other computers, different cables, no hub, different USB jacks. Try READiNG only small files, then large. Try WRITING small files, then large. Try it after it's been OFF overnight. Try it after the computer and hub have been OFF overnight. Try it with nothing else running on the computer. Change the drive format, does it matter if it's FAT32, NTFS, or OSX Journaled?

     

    - Post your symptoms and test results here. If you want help and not just platitudes and "me too"s you must include the drive make, model and any other potentially useful info like date of manufacturer, the disk drive make/model iniside. Go into System Profiler and grab all the USB info.

     

    - Check to see if the drive has the same chip ID as the two we have already found in problem drives. Googling the chip ID sometimes can tell you quite quickly if there is a problem and a fix.

     

    I know this is potentially a lot of work, I go through this process nearly weekly for clients. Their problems are different, but the process is the same.

     

    The only "quick fix" is to find a solution or workaround with Google. I will spend a few hours reading every post even remotely related to a problem, looking for clues to the problem or a fix. In most cases a workaround is acceptable - it depends on how annoying the workaround is.

  • 488. Re: Disk Drive ejecting itself
    oscarfromguilford Level 1 Level 1 (0 points)

    Okay, gotcha. Will leave it to the pros.

     

    I seem to be able to get it to work long enough to reduce but not eliminate the annoyance factor, and like yours, my time is at a premium. I _wish_ I had the time to follow your diagnostic algorithm, but I am at least glad that the annoyance factor is not driving me to have to take that time, or more likely,to  buy a new computer, which _still_ might not solve the problem. Good luck with it, and at least I am subscribed to the thread, so perhaps some day we will have an answer.

     

    P.S. When I get a chance, I WILL investigate the chipsets of all four USB drives that I have this problem with (that is, all the external drives I own) all of which participate in the problem. There is no question that that will be enlightening, to me at least.

  • 489. Re: Disk Drive ejecting itself
    oscarfromguilford Level 1 Level 1 (0 points)

    Problem: External USB drives self-ejecting during read/write, and not remounting until power cycle. Temporary fixes consistently good for up to 2TB read/writes are touch kexts, repair permissions, reset SNC, zap PRAM.

     

    Occured in Snow Leopard, persists in 10.7.2

     

    Computer:

     

    Model Name:          MacBook Pro

      Model Identifier:          MacBookPro4,1

      Processor Name:          Intel Core 2 Duo

      Processor Speed:          2.6 GHz

      Number of Processors:          1

      Total Number of Cores:          2

      L2 Cache:          6 MB

      Memory:          4 GB

      Bus Speed:          800 MHz

      Boot ROM Version:          MBP41.00C1.B03

      SMC Version (system):          1.28f3

     

    Drives Exhibiting Problem As We Speak, two, both JMicron Technology Corp:

     

    Capacity:          320.07 GB (320,072,933,376 bytes)

      Removable Media:          Yes

      Detachable Drive:          Yes

      BSD Name:          disk2

      Product ID:          0x2338

      Vendor ID:          0x152d  (JMicron Technology Corp.)

      Version:          1.00

      Serial Number:          081213FC1403

      Speed:          Up to 480 Mb/sec

      Manufacturer:          JMicron

      Location ID:          0xfa200000 / 2

      Current Available (mA):          500

      Current Required (mA):          2

      Partition Map Type:          GPT (GUID Partition Table)

      S.M.A.R.T. status:          Not Supported

     

     

    Capacity:          200.05 GB (200,049,647,616 bytes)

      Removable Media:          Yes

      Detachable Drive:          Yes

      BSD Name:          disk2

      Product ID:          0x2338

      Vendor ID:          0x152d  (JMicron Technology Corp.)

      Version:          1.00

      Serial Number:          080229D00410

      Speed:          Up to 480 Mb/sec

      Manufacturer:          JMicron

      Location ID:          0xfa200000 / 2

      Current Available (mA):          500

      Current Required (mA):          2

      Partition Map Type:          GPT (GUID Partition Table)

      S.M.A.R.T. status:          Not Supported

     

     

    One drive which had the problem in Snow Leopard is running a Time Machine backup right now. It has shown no problem so far where the above two have shown it in the current state of the computer. But it is at just 10GB read/write so far.

     

    Capacity:          3 TB (3,000,592,977,920 bytes)

      Removable Media:          Yes

      Detachable Drive:          Yes

      BSD Name:          disk2

      Product ID:          0x50a1

      Vendor ID:          0x0bc2  (Seagate LLC)

      Version:          1.00

      Serial Number:          NA0L0H3H

      Speed:          Up to 480 Mb/sec

      Manufacturer:          Seagate

      Location ID:          0xfa200000 / 2

      Current Available (mA):          500

      Current Required (mA):          0

      Partition Map Type:          GPT (GUID Partition Table)

      S.M.A.R.T. status:          Not Supported

  • 490. Re: Disk Drive ejecting itself
    Kelly Davis Level 1 Level 1 (15 points)

    I was able to get it working again, with the 10.6.8 USB kexts, but it isn't clear why it started working. All I did was disk repair and reboot a couple of times. I don't expect it to continue working, though.

     

    Also, as for troubleshooting the USB hardware, my wife has an aluminum MBP running 10.6.8 as well, and using the same drive/enclosure has never had any of these problems with time machine (there are 2 partitions which each of our machines use for time machine backups). Given this fact, as well as the numerous and varied posts on this thread from individuals with different hardware, as well as the fact that the problem did not start ocurring until recently, the possibility that this is just a problem with a particular chipset is unlikely (though it is possible it is an interaction with some software issue and a particular set of hardware).

  • 491. Re: Disk Drive ejecting itself
    oscarfromguilford Level 1 Level 1 (0 points)

    Yes, and I think that's why Richard E. Cooke wants such precise information - otherwise, we'll never figure it out - it's true. It would be nice, however, if there were someone with enough USB knowledge to at least imagine why these repairs and reboots fix things for awhile. Some sort of timing issue, I guess.

     

    My 3TB drive above is still grinding away, 150 GB in, while the JMicron drives were self-ejecting to a fare-thee-well. If nothing else, it seems that some drives are more vulnerable than others. I agree with your implication that theorizing helps too - that AND precise data

     

    Onward, if not upward ...

  • 492. Re: Disk Drive ejecting itself
    Richard E. Cooke Level 2 Level 2 (220 points)

    Oscar, I love you! (in a purely platonic sense)  Data is what I need to be of assistance!

     

    The Jmicron chip in your drive interface is the same one I have in my Thermaltake Drive Dock.  I posted my sucessful test results with that one here:

    https://discussions.apple.com/message/13373292#13373292

     

    And if you read the pages before this post you will find the two drive chips that exibit the problem in drive bays from two different vendors, as observed by two different people.  As in science, collaboration of findings is key.

     

    However, the mistake I think most people here are making is jumping the gun on blamstorming.  Some people in this group make wild claims about cause and effect that make my toes curl.

     

    Please, everybody, take a step back.  Calm down.  Think logically.  Rule out factors and reduce variables.

     

    Those of you that have a drive that has worked "for ever" and then "suddenly fails" one day.  Its most likley a hardware problem.  Overheating would be my prime candidate, followed by a dying drive.

     

    Those of you that have a drive that works "for a while" then stops working, and only starts working after you hop on your left foot swigning a chicken over your head.... Well I think you might need professional help.  Really.   Its Technology, not witchcraft.  Seriously, anything electronic that "works for a while" I translate to "it works until it warms up"   Yup.  Hardware problem again.  Overheating again.

     

    A really quick test is to put the software back the way it was. And turn your computer and drive OFF over night.  I mean shut down, maybe unplugged from the wall - not standby or sleep or suspend.  Then test it in the morning.  Try to write a few small files onto the drive, then read them back.  Then do a few files at a time, then a few more.  Then only large files.  If the drive fails "after a while" turn everything OFF overnight again, and next morning repeat the test in reverse order.  See if it fails at the same point (# of minutes since power ON) again.  If it does, then its thermal.  If it fails after the same size/number of files is copied than you are experiencing the problem we documented around page 25 of this thread with several specific USB chips inside of your drive bay or dock.  Nothing to do with Apple, and they can't help you - except to sell you a drive that works.

     

    If you experience something else, post your observations here - as detailed as you can - and I'll help you analyze them. 

     

    oh, and please start by directly plugging the drive into the computer: NO HUBS!!!!  Try and use good cables, with no obvious signs of damage.  And don't run any other software on your computer - not even e-mail - during the test.  Disable TM too if your using it.  Again, we need to reduce the number of variables and things that can interfere with the test.

     

    Good luck and happy testing.

  • 493. Re: Disk Drive ejecting itself
    ticzon Level 1 Level 1 (5 points)

    I have experience the drop of my USB external devices (external HD, and USB Drobo) with the use of each OS after 10.6.4. Even with 10.6.8, drops occurred within days of using the OS. After doing the final 10.6.8 upgrade July 2011, I down graded my OS back to 10.6.4 and the OS has been solid as a rock. No drops of the USB connection for the last 4 months. This include moving large files by doing drag and drop or via time machine. My iTunes library has been moved and copied several times for backup purposes (just a little over 111 GB) and I have not seen a drop or lost file. There is must be something in the OS that changed as we went from 10.6.4 to 10.6.5 thru 10.6.8.

     

    I want to upgrade 10.6.8 so I can use the WIFI sync features with my iPhone 3GS / 2 iPhone 4 / and my new iPhone 4S. But it not worth it to start having my USB drives start dropping again and even worst, corrupt a file or disk.

     

    As Apple gets bigger and more people are now moving to the Mac, I fear we will  continue to see a decrease in quality in apple software.

  • 494. Re: Disk Drive ejecting itself
    William Boyd, Jr. Level 6 Level 6 (10,490 points)

    ticzon wrote:

     

    I want to upgrade 10.6.8 so I can use the WIFI sync features with my iPhone 3GS / 2 iPhone 4 / and my new iPhone 4S.

    That feature comes with iTunes 5, which according to its page should work on "Mac OS X version 10.5 or later".  Have you found other information that WiFi sync doesn't work with OS X 10.6.4 if you install iTunes 5?

1 31 32 33 34 35 Previous Next