Lacie disk on FW not sleeping after installing Mavericks

"The G-Drive is used for Time Machine and for Carbon Copy Cloner image copies, so is not used in "normal" operation"

Perhaps the fact that you are using it with Time Machine is contributing to its normal operation? I would have no way of finding that out but hopefully someone from Apple is lurking and can comment. I am not using my g-drive as a Time Machine drive.

I have some OWC FW800 drives, three of them on one chain that work just fine (now) on a new iMac with 10.9.3 I have some others that are hooked up with the USB2.0 and they too work properly. This wasn't the case before. I have several different manufacturers types and I know in the past that not all FW were created equally. Some worked well to pass through data even when off others had to be on and spinning. I think that if there is a IEEE protocol, it's not followed or improperly structured. I see the most people are having trouble with LaCie, no surpise there.

For your Clean install, what did you use for the migration data source, Time Machine, or CCC?

PS What you describe is how my MacBook Pro now works (still not right, but much better). However, the iMac still has this and other issues with Mavericks.

It should be all going well around 10.9.9 just in time for the next big change.

I have 10.9.3 using my FW drive (WD in Macally enclosure) and used for TM would sleep as directed when first booted up. If I reboot the Mac then they will not sleep. Seems odd it works the first time and never again unless I remove the drive and start the cycle once again. USB3 works fine. I'm using a Mac Mini (late 2012).

"For your Clean install, what did you use for the migration data source, Time Machine, or CCC?"

I used a CCC image copy. One thing that was necessary after that was to Repair Permissions - they seemed to be a bit of a mess, but after doing that, things ran a lot more smoothly.

JPinCheshire wrote:

"For your Clean install, what did you use for the migration data source, Time Machine, or CCC?"

I used a CCC image copy. One thing that was necessary after that was to Repair Permissions - they seemed to be a bit of a mess, but after doing that, things ran a lot more smoothly.

By "clean install", do you mean that you completely erased your internal HD, installed the OS,set up a new Mac user account, re-installed all applications and utilities from their original DVDs etc, re-entered all your email accounts, and then copied across documents, images, movies, or did you use Migration Assistant to do all the above for you?

I ask because I used to do the above erase and clean install to avoid gitches being carried over but it is a very time-consuming process. I'm not sure that it succeeded in removing the glitches but if it did in your case, I might try it for OS 10.10.x

It looks like Apple is just going to skip fixing this issue with Mavericks and just jump to Yosemite. Wonder if the issue is fixed there or is it going to be another bag of spinning beach balls, external drive not spinning down and kernal panic attacks.

IMHO Mavericks has been the worst OS upgrade I have seen and dumping it as quick as possible may be the right solution that Apple is doing.

SteveKir wrote:

By "clean install", do you mean that you completely erased your internal HD, installed the OS,set up a new Mac user account, re-installed all applications and utilities from their original DVDs etc, re-entered all your email accounts, and then copied across documents, images, movies, or did you use Migration Assistant to do all the above for you?

I ask because I used to do the above erase and clean install to avoid gitches being carried over but it is a very time-consuming process. I'm not sure that it succeeded in removing the glitches but if it did in your case, I might try it for OS 10.10.x

No, I didn't do a CLEAN clean install - just erased the partition used the standalone installer to put virgin 10.9.3 on it and then used Migration Assistant to move my existing users and data across from the CCC clone. On a much earlier comment on this topic, someone who had had a good experience with this issue had done that and I thought it might not be too arduous a task that might clean up several years of debris accumulated as I have moved through the OSX versions. Maybe a naive expectation but not too tedious in my case.

I have a problem with my iomega firewire 800 drive, since the update to Mavericks (2 days after the release) the drive has never spun down. I even went to a large Apple store recently to try and get to the bottom of it. I waited around for 20 mins for help (lots of staff there, all useless) and got no help what so ever. Basically as I've found in the past the Apple Genius don't live up to their names (I'm a self employed IT consultant by the way).

I've now got a second machine running Linux and to be honest I've been so disappointed with apple support in the last couple of years I think I'm going to jump ship back to Linux. I'm already using Android on the phone and love it.

Don't blame your Iomega drive. No FW drive will sleep with Mavericks. It is a known issue. It will spin down when Mac powers down. You will need to use USB for full spin down function.

tbirdvet wrote:

Don't blame your Iomega drive. No FW drive will sleep with Mavericks. It is a known issue. It will spin down when Mac powers down. You will need to use USB for full spin down function.

This isn't true. I have several OWC FW800 drives that spin down during normal operations and remain that way until called upon. They work really nicely with Mavrics 10.9.3. It wasn't the case with 10.9.2. Others I have don't spin down so they are connected to USB.

That's because (according to OWC) that have their own energy (spin down) system. They do not rely on the OS (Apple) to provide the signal.

I didn't know that. Thanks for the reply.

If that's the case then why do my two OWC FW800 drives STILL not spin down to sleep even after upgrading to 10.9.3? They only spin down when imac is shutdown. Using USB is the only way they'll spin down to sleep.