Currently Being ModeratedJul 24, 2011 1:01 PM (in response to fasterfox)
I should also mention that the I've tried using Disk Utilities repair function. It found errors that it supposedly fixed, but the problem hasn't gone away.
Currently Being ModeratedJul 24, 2011 5:35 PM (in response to fasterfox)
See #C10 in Time Machine - Troubleshooting.
Currently Being ModeratedJul 24, 2011 6:37 PM (in response to Pondini)
Ok, I just gave that a shot. Another thing I did was move the external drive from the USB hub to port on the laptop because I saw that suggestion somewhere in my research. I'll know in a day or so if the problem is gone.
Currently Being ModeratedAug 6, 2011 5:09 PM (in response to fasterfox)
I still can't find a solution to this problem. A few other things I've noticed:
- I can't reboot the computer after this problem occurs until I unplug the hard drive. I can shut down successfully, but when I start up again the start up chime repeats endlessly. I have to power down and remove the drive for it to work. When I'm back in OSX, I can plug the drive and use my computer normally for about another day.
- I can't unmount the disk through finder. Finder tries to unmount, but it fails.
Currently Being ModeratedAug 22, 2011 12:21 AM (in response to fasterfox)
I have the same problem when trying to use time machine to backup the internal HD to an external USB HD.
No solution so far...
Currently Being ModeratedSep 9, 2011 4:09 AM (in response to fasterfox)
It seems that the problem is relatedd to the external USB drive, not to the iMac nor Lion.
I used a Verbatim 1.5TB HD and always got the problem.
Now I use a Wester Digital Elements 1.5 TB - without any problems!
After googling a bit, I found out that the Verbatim drive has some sort of "Green Mode" to save power (at least they claim it does so). But I assume, thanks to this green mode, the drive falls asleep after 10min and then has to wake up, if it is needed by time machine. But it seems to take too long to wake up, and I get one of those error messages.
Currently Being ModeratedSep 9, 2011 7:38 AM (in response to Thomas Goetz)
I switched to a Western Digital hard drive a few weeks ago, and I haven't had a single problem since then. The green mode explanation makes a lot of a sense. It's a shame that it ruined a good hard drive for probably many mac users.
Currently Being ModeratedNov 16, 2011 6:06 PM (in response to fasterfox)
I'm having the same problems, but they only started with my upgrade to Lion. The same backup disks worked just fine for months under Snow Leopard. I never once saw this message under Snow Leopard.
I can get a successful back by right-clicking on my time machine disk on my desktop and ejecting it. First I get an dialog that says my disk "wasn't ejected beause one or more programs may be using it." But if I "Force Eject" and remount the disk using Disk Utility. My next backup runs just fine.
Currently Being ModeratedNov 16, 2011 7:28 PM (in response to fasterfox)
I'm getting the exact same error, exact same circumstances. UPgraded to Lion and bam. Also, I'm having the same problem with the disk not unmounting and having to force it to unmount after Time Machine tries and fails to run. Really frustrating. It's clear that several of us are having the exact same problem. Also, my backup disk that isn't working is a new Toshiba 1T. I'm going to try my old Toshiba 1T and see if maybe it's this particular backup drive. (I also am backing up Time Machine to a partition, so that's another variable I changed since I got the new drive - basically need to eliminate the drive as the problem, by using the old drive that worked before I upgraded to Lion, and then I'll try to backup on the new drive without a partition and see if that's the problem.
Oh, and I did everything that was suggested above - ran disk utility, ran disk warrior, plugged the drive directly into my computer, unplugged it, rebooted, reset time machine preferences, etc. Everything. It did the same thing again, it works the first time or few times, then it refuses to back up and gives the same folders error.
Currently Being ModeratedJan 24, 2012 7:05 PM (in response to wirtes)
Same, identical problem but with snow leopard. The external drive is a LaCie 1TB connected (USB) to an IMac. If I force eject and reconect I can do the back manually but the next automatic scheduled back up will fail. I also have a disk partition. Disk utility found no errors.
Currently Being ModeratedFeb 4, 2012 10:26 AM (in response to fasterfox)
I just unplug / turn off the external disk. Then the backup works fine. Pretty clunky and disconcerting when you get the "improperly disconnected drive" error but what else can you do? I particulary like the can't eject because tone or more programs are using it" error. Can't eject because a program is using it but the program can't use the disk bcause of the error. Good one.
Currently Being ModeratedFeb 4, 2012 10:43 AM (in response to magnificentnile1)
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 one of the backups in question, and see if there are any "indexing" messages. If there are a lot of them, the Spotlight index may be damaged.
If so, see the pink box in #D2 of the same link.
Currently Being ModeratedMar 4, 2012 6:37 AM (in response to fasterfox)
I think this is not just a problem with time machine because I had the same problem with a 4 drive raid array that was created on my MBP, then when I bought my MP i hooked it up and there were immediately problems similar to your description. First the array would spin up but was very slow to copy to. I tried to delete the array but was unsuccessful. ultimately i had to re boot the array as an incomplete (3 drives instead of 4) then zero the drives and creat a new set. I used 3 instead of 4 this time just in case it was a power issue. The new array worked fine and copied files at acceptable speeds. Then after working in itunes for about 2 hours, i started getting spinning balls which is strange for a MP 6 core with 16 gb ram and a 5870 with a striped "0" work disk. It was the raid set again. I realized that it must have something to do with conflicts between a program indirectly using the drive(mds,spotlight,time machine etc.) and the program diirectly using the drive(itunes). Anyway...this worked for me.
the instructions in the following thread fixed for the time being.
Currently Being ModeratedSep 12, 2013 10:02 PM (in response to magnificentnile1)
Fast forward 15 months, same problem here.