You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

10.8.5 puts drives to sleep... forever

Today I updated two systems to 10.8.5: A Mac Pro (Early 2009) and a Mac Mini Server (Late 2012).


Prior to the update I had "Put hard drives to sleep when possible" unchecked in Energy Saver, since I use both systems constantly--and drive sleep just results in lower performance, and more wear-and-tear on the drives.


After 10.8.5, drives will sleep (despite the setting), then never wake up. The drives themselves may spin up, but the OS does not see them. E.g., Finder will give a spinning beach ball when attempting to view the drive, any app with a file open on such a drive will lock up, Terminal will hang on ls of the drive, etc.


This is happening on internal and external drives on both systems.


The only way to get the drives back is to reboot.



Given the severity of this issue, I am restoring my systems from Time Machine backups to OS X 10.8.4.

MAC MINI SERVER (LATE 2012), OS X Mountain Lion (10.8.4)

Posted on Sep 12, 2013 7:17 PM

Reply
82 replies

Oct 8, 2013 5:49 PM in response to jobalo

Correct me if I'm wrong, but the (newly available) OSX 10.8.5 Combo updater dated October 3 2013 (same release date as the supplemental update) has the supplemental update baked in. Therefore if you've downloaded this version off Apple's website, you don't require any additional supplemental update downloaded separately.


In any event, it appears to have fixed the issue on my end, but I haven't given it in-depth observation yet.

Oct 8, 2013 9:51 PM in response to orchetect

I had the same problem with an early 2008 mac pro. Since it was too much inatallation to go back to 10.8.5, Itried to intall 10.8 on top of 10.8.5 and than upgraded to 10.8.4.

Somehow, it worked.

I am sure my system is a mess but i needed to get thing working again and they did.

Yesterday I updated again with and installed the supplemental update. It did not fix the problem. I will have to try my first trick again.

Oct 9, 2013 7:00 AM in response to orchetect

orchetect wrote:


Correct me if I'm wrong, but the (newly available) OSX 10.8.5 Combo updater dated October 3 2013 (same release date as the supplemental update) has the supplemental update baked in. Therefore if you've downloaded this version off Apple's website, you don't require any additional supplemental update downloaded separately.


In any event, it appears to have fixed the issue on my end, but I haven't given it in-depth observation yet.


You are correct. In addition Software Update can tell the difference and will offer the supplemental update if needed.

Oct 9, 2013 10:08 AM in response to jobalo

I to have been having the same problems with both Ext Drives and a RIAD 6 Setup.

What really annoys me is this was deffenitly an Apple fault. As proven by the 10.8.5 Supplemental update.

In my case this has cursed me masive problems, and lost of working time.

This is because I had a SATA RAID 6 setup with 8 drives in 6 in the RAID plus two Hot Spares.

Before I new anything about this fault I can back to my Mac which i'd left on over lunch to find the RAID totally currupted. After may may rebuild attemps I thought the RAID was stable again. However to be sure I got two new 4TB Seagate Ext drives to copy to.

I copied across from the RAID to the first Ext Drive. When I got back and checked the copy the data amouts all added up. So I thought I had a safe spare copy, which was luckly because at that time the RAID crashed again.

I them decided to copy the copy to the other new Ext Drive to make sure I still had two safe copies of my data.

On doing this I was give some of Apples favourite error messages. Telling me that firstly the information on the first Ext Drive was currupted and second that the second drive had ejected during the copy and hence become unfixable by Disk utility.

So for me the outcome of Apples error has cursed me the lost of all the data on my RAID plus all the Coped data on the two new back ups which a brought just for this.


If this is not bad enough after wasting all day today doing the updates trying to rebuild the RAID and reformmating the two new ext drives. You would be mistaken as during this time three out of four of the internal drives in my 2009 Mac Pro unmouted and could not be seen by disk utiliy or even in the System Report.

After some time and a restart I had a massage come up saying that disk utilily was rebuilding two of these drives which I have RAID together. The other drive which was a time machine copy of my MAC HD was still no where. So I pulled that drive and put it into a drive reader though USB and it came up but again totaly currupted. So before I could put it back into the MAC I had to reformate it.


This means that this error has taken out eight out of nine drives. All of which I an still working on and do not now yet if the data is safe. Plus distroyed my RAID which again I do not now if I can recover the data from.


So well done MAC for yet another great week of working on repairs and not paid work.

Oct 13, 2013 11:15 AM in response to Eric Root

I've had the same & worst happen to me 10.8.5 has crashe:


ESATA RAID


EXT Firewire drives


EXT USB 2 drives


Internal time machine drive plus two others.


So only my internal Mac Hd drive has not been damaged.


I've done the 10.8.5 Supplemental 1 update but if anything this has only made it worst.


So my mac has been out of action for six weeks.


Email & phone mac level one support. I now have been give a personnal contact as the macs unusable.


To my amazement althought he agrees that 10.8.5 probley cursed all my problems.


He says i'm the only person he has heard of with this problem.


I Guess he does not read the forums.


So please everybody halse Apple as this is due to a bug they missed in 10.8.5 and tried to fix with the update but failed again.

Oct 27, 2013 2:47 PM in response to furrytoes

I'm seeing the same behavior after installing Mavericks. I thought prehaps it was due to having "wake for wifi network" enabled, but I disabled the option and have the same behavior.


Ironically, the opposite behavior was just fixed in 10.8.5. Now, instead of narcolepsy, they have insomnia. I haven't checked the Mavericks forum, but if this isn't already a thread there, perhaps we can move this new discussion there.

10.8.5 puts drives to sleep... forever

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.