That's what I thought, but learned differently. Well, read my thread, a few people taught me a few things on OS X, I was very grateful.
OCZ Vertex 2 in 2010 Mac Pro 6-Core - Known issue with Sandforce SSD's
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
OWC Mercury Extreme Pro SSD Problem
- Thread starter denm316
- Start date
- Sort by reaction score
That's what I thought, but learned differently. Well, read my thread, a few people taught me a few things on OS X, I was very grateful.
OCZ Vertex 2 in 2010 Mac Pro 6-Core - Known issue with Sandforce SSD's
That's what I thought, but learned differently. Well, read my thread, a few people taught me a few things on OS X, I was very grateful.
OCZ Vertex 2 in 2010 Mac Pro 6-Core - Known issue with Sandforce SSD's
AH ok ignore me then.
What is this hibernation mode in regard to laptops then.
It just saves the state if you run out of power?
I rarely run out of power when close the lid or put it to sleep, it certainly not a major issue if it doesn't save things.
Thats what it does?
If you use hibernation, every time you put your computer to sleep it's writing onto the HDD/SSD (assuming it's set to 3 or 7 like most)... that way in case the computer loses battery while sleeping it'll have a saved image on the HDD/SSD.
I don't ever lose power or go to sleep without saving stuff... so I'm setting mine to 0 when I get home today, as I just read about this.
I've got this same issue with my 120GB GSKILL Phoenix Pro.
When it wakes from an idle sleep, it hangs.
After a hard shutdown, my computer won't load the kernel (most of the time).
BUT: when it won't load the kernel, if I hook up an external with a clone, then the computer boots fine. BUT not from the clone. From the original.
And there have been a few occasional hangs for no apparent reason.
These issues aren't very hard to live with, but it is irritating that the product doesn't work without issues. More than anything, I'm fascinated why these issue are appearing.
When it wakes from an idle sleep, it hangs.
After a hard shutdown, my computer won't load the kernel (most of the time).
BUT: when it won't load the kernel, if I hook up an external with a clone, then the computer boots fine. BUT not from the clone. From the original.
And there have been a few occasional hangs for no apparent reason.
These issues aren't very hard to live with, but it is irritating that the product doesn't work without issues. More than anything, I'm fascinated why these issue are appearing.
For what t's worth, I just got a Extreme Pro 240GB this weekend (w/343A13F0 FW). I am not having the sleep problem. Some of the things I did are:
1. set hibernate mode to 0
sudo pmset -a hibernatemode 0
2. delete the unnecessary sleep file to regain disk space equal to memory (I saved 8 GBs), since hibernate is disabled
sudo rm /var/vm/sleepfile
3. disable sudden motion sensor
sudo pmset -a sms 0
4. disable disk sleep
sudo pmset -a disksleep 0
The result is my pmset -g looks like this:
Currently in use:
womp 1
halfdim 1
sms 0
hibernatefile /var/vm/sleepimage
gpuswitch 2
disksleep 0
sleep 0
hibernatemode 0
ttyskeepawake 1
displaysleep 0
acwake 0
lidwake 1
One other thing is I reset PRAM when booting after the initial install.
1. set hibernate mode to 0
sudo pmset -a hibernatemode 0
2. delete the unnecessary sleep file to regain disk space equal to memory (I saved 8 GBs), since hibernate is disabled
sudo rm /var/vm/sleepfile
3. disable sudden motion sensor
sudo pmset -a sms 0
4. disable disk sleep
sudo pmset -a disksleep 0
The result is my pmset -g looks like this:
Currently in use:
womp 1
halfdim 1
sms 0
hibernatefile /var/vm/sleepimage
gpuswitch 2
disksleep 0
sleep 0
hibernatemode 0
ttyskeepawake 1
displaysleep 0
acwake 0
lidwake 1
One other thing is I reset PRAM when booting after the initial install.
So you have turned off your g-force sensor with sms set to 0? Also you have disabled any disk spindown time? I know with SSD it prob. doesn't matter but any other HDD's attached are affected aren't they?
When you say no "sleep issues" what exactly are you meaning? Do you mean if you let your machine idle to sleep it wakes up fine? I assume you haven't tested this as you have sleep set to 0 (disable).
That's the ONLY issue I have. I can close the lid and open it all day, works perfect. My issue is if I let it "idle sleep" then wake it up, I have a total freeze.
My only diff. between you is my sms is enabled, and my disksleep (spindown) is set to 10 min. for my optibay and externals.
My sleep 0 setting is only for AC Power.
Here's pmset -g when I'm on battery:
halfdim 1
sms 0
hibernatefile /var/vm/sleepimage
gpuswitch 2
disksleep 0
sleep 1
hibernatemode 0
ttyskeepawake 1
displaysleep 1
acwake 0
lidwake 1
But to answer your question, I do not have a problem with any kind of sleep (including idle timeout sleep) and the SSD.
Also, from the pmset manpage:
OTHER ARGUMENTS
...
noidle - while continuousy running, pmset prevents idle sleep.
OTHER ARGUMENTS
...
noidle - while continuousy running, pmset prevents idle sleep.
Are you in the optibay or main bay? Forget if you mentioned that...
On battery power, my sleep is set to 0 (DISABLED AS THAT'S THE ONLY TIME I EVER HAVE ISSUES), disksleep set to 10, sms set to 1... those are our differences. I have no idea what would cause the issue I'm having then.... disksleep just refers to the spindown (SSD's dont' even spindown)... possibly something weird with the sms (the shock sensor)... I dunno.
Guess I could set mine to yours and see what happens.
I would hate to set my spindown to disable as I want my optibay to spindown as often as possible as I hate the noise, the SSD has spoiled me.
halfdim 1
sms 1
hibernatefile /var/vm/sleepimage
gpuswitch 2
disksleep 10
sleep 0
hibernatemode 0
ttyskeepawake 1
displaysleep 1
acwake 0
lidwake 1
That's my settings right now on battery power.
The ONLY diff. with ours is the sms and the spindown... my sleep is disabled between if I idle sleep I get a hang on wake... if I shut my lid to sleep I'm fine... so freaking weird.
Guess it's testing time to figure out which of those 2 are the culprit.
sms 1
hibernatefile /var/vm/sleepimage
gpuswitch 2
disksleep 10
sleep 0
hibernatemode 0
ttyskeepawake 1
displaysleep 1
acwake 0
lidwake 1
That's my settings right now on battery power.
The ONLY diff. with ours is the sms and the spindown... my sleep is disabled between if I idle sleep I get a hang on wake... if I shut my lid to sleep I'm fine... so freaking weird.
Guess it's testing time to figure out which of those 2 are the culprit.
Okay, so I tested it...
It's the FREAKING DISKSLEEP & SMS
I changed mine to 0 (which disables spindown... as there is no spindown on a SSD) and the SMS to 0 which disables the gforce sensor
Issue 100% fixed.
No hang on wake from idle at all.
Damn... that's really weird.
I tried it with sms 1 and disksleep 0 and every other combination, didn't work. sms and disksleep both have to be 0 if you want this setup.
Please Note: terminal gives you a warning saying that you shouldn't have the computer set to sleep from idle and disksleep set to disable at the same time... says things might not work properly. In normal circumstances probably not, in this one though, it's doing what folks want.. how good or bad that is for the computer is to be seen.
For me, just shutting the lid when I want it to sleep is good enough for now
It's the FREAKING DISKSLEEP & SMS
I changed mine to 0 (which disables spindown... as there is no spindown on a SSD) and the SMS to 0 which disables the gforce sensor
Issue 100% fixed.
No hang on wake from idle at all.
Damn... that's really weird.
I tried it with sms 1 and disksleep 0 and every other combination, didn't work. sms and disksleep both have to be 0 if you want this setup.
Please Note: terminal gives you a warning saying that you shouldn't have the computer set to sleep from idle and disksleep set to disable at the same time... says things might not work properly. In normal circumstances probably not, in this one though, it's doing what folks want.. how good or bad that is for the computer is to be seen.
For me, just shutting the lid when I want it to sleep is good enough for now
Last edited:
Yeah, to me, I'm not sure I like the disksleep (spindown) set to 0 (disable) as I want my other HDD's to spindown.... and I don't like disabling my force sensor either.
So I just set sleep to never and shut the lid when I want it to sleep, it's a quick dirty easy fix for me.
For those not wanting to do that though, if you set disksleep and sms to 0 it will fix your issues.
The same setup that racetripper posted.
Here is what sms does:
sms - use Sudden Motion Sensor to park disk heads on sudden changes in G
force (value = 0/1)
To me, I'd rather have that built in safety feature active. I know the SSD doesn't have "disk heads" but my optibay does and until I'm told otherwise, I'm assuming that any of those commands effects all HDD's connected to the machine.
If it def. doesn't effect the optibay (if somebody can tell me this 100% for sure) then I don't have any issues turning it off.
So I just set sleep to never and shut the lid when I want it to sleep, it's a quick dirty easy fix for me.
For those not wanting to do that though, if you set disksleep and sms to 0 it will fix your issues.
The same setup that racetripper posted.
Here is what sms does:
sms - use Sudden Motion Sensor to park disk heads on sudden changes in G
force (value = 0/1)
To me, I'd rather have that built in safety feature active. I know the SSD doesn't have "disk heads" but my optibay does and until I'm told otherwise, I'm assuming that any of those commands effects all HDD's connected to the machine.
If it def. doesn't effect the optibay (if somebody can tell me this 100% for sure) then I don't have any issues turning it off.
Last edited:
I'm just jinxed i think, my MBP just does not like SSD's
Installed via external enclosure, seems to work fine like that.
Once inside the MBP doesn't work smoothly, lots of spinning ball and just slow.
Its not connected to the sleep aspect, as the computer has not gone to sleep
to effect it, not even closed the lid etc..
OWC had it back and done all the FW updates, have it back and still no joy
They have been brilliant about it cannot fault their customer service.
The drive seems to be fine just something internally it doesn't like it.
Odd when my normal HDD works fine.
i dont think i'll even risk a Crucial or none Sandforce controlled one as i'll just end up having issues again too would be my 3rd by then, enough is enough
Think i'll eBay this one
Installed via external enclosure, seems to work fine like that.
Once inside the MBP doesn't work smoothly, lots of spinning ball and just slow.
Its not connected to the sleep aspect, as the computer has not gone to sleep
to effect it, not even closed the lid etc..
OWC had it back and done all the FW updates, have it back and still no joy
They have been brilliant about it cannot fault their customer service.
The drive seems to be fine just something internally it doesn't like it.
Odd when my normal HDD works fine.
i dont think i'll even risk a Crucial or none Sandforce controlled one as i'll just end up having issues again too would be my 3rd by then, enough is enough
Think i'll eBay this one
Is this still a problem with the newest firmware? Hopefully putting my OWC in this weekend and all I can recall from reading this is setting the setting to 0, is that all you have to do to fix this sleep issue currently or do you have to also untick the option for putting the drive to sleep when not in use?
Yes it is still an issue with all sandforce controlled SSD's
If you set your sleep to 0, you are disabling sleep from idle timeout. If I do that, then I can shut my lid and wake it up all is good... it just obviously doesn't timeout sleep.
If you want the timeout sleep to work, you need to set disksleep (NOT normal sleep) to 0 (disables spindown) and then set sms to 0 (disables gforce sensor that parks disk head (there is none in an SSD).
Please note if you then ALSO set sleep to 0 (disabling it) you are then making it to where the machine won't sleep from idle anyways... so it'd be pointless to set disksleep (NOT sleep) and sms to 0.
Having an Intel X-25M, and an OCZ Vertex 2 (which is faster than the OCW SSDs) I can tell you the Intel is NOT 1/2 the speed. Write speed may be capped around 100MB (on 160GB model, but I've seen more) but everything else is up to snuff or far better.
In real world use you're not usually going to be pushing that R/W Max anyway so it's pretty moot unless all you care about is a HD speed test I guess..
OCZ and OWC are specced out the same, so the OCZ is NOT faster as you stated. OWC has proven to degrade less than OCZ, which to me counts more than the raw speed from specs (as you said, in real world use you don't see those specs anyways).
Intel is a good SSD, it's just slower. I mean that is a fact. Again, real world, probably won't notice it much if at all, but it is.
If/when I buy a new SSD in two years time (when GB is up to 500GB for reasonable... hopefully)... I'll be debating between intel and OWC.
In my eyes the Intel SSDs with their basically flawless performance thus far are a top contender... they just need to up the speeds a tad.... I like OWC's as well.
I've heard some mixed reviews of Crucial SSD's... and would never buy OCZ as I just don't like their customer service at all.
How is your intel BTW? Is it running flawless like 99% of people are stating? As far as any sleep/hibernation issues are concerned?
The only thing I LOVE about OWC is all the 3rd party reviews/benchmarks for degradation that I've seen. So far I have seen none in my own drive, and the benchmarks are showing VERY little compared to some of the others taking quite a big hit.
Last edited:
I had read an indepth comparison of the OWC drives and it wasn't very favorable, admitted this was a few mos. ago but ill look for it when I get a sec. I'd honestly rather deal with a company that has total control over their firmware and hardware working together. Not just slapping a new case on someones stuff. (Obviously OCZ does this too)
I've only dealt with OCZ support via the forums and so-far they have been responsive. I am a pretty big Intel fan tho, so I usually lean that way.
I have personally not had a single issue with my intel and I have not applied any sleep tweaks, etc. I just use it as usual. There has also been zero slowdown, My 80GB is about 70% full and still the same test speeds as when I first installed it long ago.
We have a few Intel units at work, these are about 6-7 mos old, constant DB use and as far as I see they are performing the same as ever.
Yeah Intel is the only one with the control over it all I believe. OCZ and OWC are almost the same drives for the most part both sandforce controlled.
So out of the two you have, which do you prefer? Your OCZ or Intel? Which gives less issues?
You can dig up bad stuff about any drive. My experience with OCZ customer service was poor, so I won't buy from them again, that's the only reason I don't have one for the most part. Plus the OWC deal I got was better and it came with a REALLY nice USB external case for my old HDD.
Last edited:
Both of them have had zero issues, I use my MBP (so the Intel) more often, but run the iMac (OCZ) Harder.... The Intel I have had longer, was originally in my iMac months ago until I just needed a bit more room so I got a 120G Vertex2 after using my cousins OCZ in a dell laptop he had for almost a year.
I can say the OCZ had slowed some, and only has about 50% used on it, where as I said the Intel has about 70% and its testing (using Quickbench) exactly the same as it did on day one.
Its funny I almost got the OWC Drive but had some newegg credit and leaned on the OCZ... as you said I'm waiting for at least a 300GB range and hopefully the intel G3 picks up the write speed and has further improvements so I can go that direction again. Then I guess I'd move the OCZ to the MBP... if it's still alive
(The OCZ Drive that is)