01-11-2014 08:27 AM
I was curious if perhaps TRIM enabler was causing problems, but it turns out it was disabled. I just turned it back on, so we'll see if anything changes.
Of course, this wouldn't explain anything under Windows where TRIM is automatically supported.
01-11-2014 09:26 AM
I have just purchased a 240GiB Sandisk Extreme II disk for a new Haswell i7, 8GB RAM laptop. Machine is terrifically fast, great transfer scores in disk benchmarks, BUT I have exactly the same problem reported here:
- Slow to come out of sleep, every time.
- Disk light stays on during this period, and windows 8 (yuk) freezes during this period, which could be as long as 10 seconds.
The interesting thing is, that coming out of hibernate is faster than out of sleep!
Looking forward to any ideas on how to resolve this...
01-19-2014 07:45 AM
I'm still having this problem on OS X. I just Bootcamp'ed my laptop and installed Windows 8 on it. So far, I've been unable to replicate the problem there. However, I also don't even have the option to disable HIPM or anything like it under the Hard Disk power settings. I'm guessing that's due to the BIOS compatibility layer that Macs use, but if anyone knows how to turn on HIPM anyways then I can see if that recreates the problem.
I'm not sure if OS X supports HIPM / DIPM at all - there doesn't seem to be a definitive answer online.
01-19-2014 07:49 AM
Same problem here :/
I'm using a Macbook Pro 8,1 and had a ADATA SSD 120GB at 6GB/s. Switched to Sandisk Extreme II 480GB at 6GB/s. Previous to the switch I had no problems whatsoever besides the lack of space, hence the change. Now, with a clean install of MAC OS X Mavericks, the behavior is as described by deviantintegral in this very post - just mouse hovering for a while...
By the looks of it, I think that a firmware update would come handy.
Any news on that?
02-25-2014 01:24 PM
I'm having a similar problem with a 480 GB SanDisk EX II on a Z87 desktop mother board, Windows 8 PC.
Just got the EX II, so just have it connected to the PC, not an OS drive. It works fine in all situations except waking from S3 Sleep.
Upon waking from Sleep, the EX II is not seen in Windows Explorer, Disk Management, etc. The EX II does not appear after a minute or so as some other users have reported, but I'm not using it as an OS drive yet. A restart of the PC will cause the EX II to function normally again. It works fine from a cold boot. It won't wake spontaneously after coming out of Sleep.
I'm using the latest Intel IRST driver, 12.9, and the EX II is connected to an Intel SATA III port. I tried adding the HIPM and DIPM settings in the power options, with no affect after trying various options. I have Link power management disabled.
I have three other SSDs in this PC, and none of them have this issue. I realize that these slightly older SSDs may not have the same options/features enabled that the EX II does, but I'm surprised this issue was never seen in testing. I tried going into Sleep, and waking the PC within one minute, and the EX II is not seen/active in Windows.
02-25-2014 03:07 PM - edited 02-25-2014 03:19 PM
I heard back from sandisk on the 5th Feb:
"We have been looking into this issue which you are experiencing.
Its been 3 weeks and I've no more news. I am also suprised that for me this is such an easy issue to reproduce, so how come sandisk and frankly more people (eg ssd reviewers) didn't spot and raise this issue sooner?
PS: Edited to ask: has anyone else raised a support ticket with Sandisk? I'm not sure they read these forums.
02-25-2014 04:23 PM
Peter_S, no I didn't create a support ticket with SanDisk about this, just noticed it yesterday. Until I'm sure something is really wrong with a product, I don't report issues that may not truly exist.
Regarding more news, keep in mind issues like this, which can be related to the SSD controller's firmware or the SSD controller itself, are very complex things. The environment the SSD is used in (hardware and software) are variables that add to the complexity. The SanDisk EX II is not the only SSD that uses the Marvell 9187 controller, and this controller has been used for a while now. If those SSDs do not have this issue, that narrows down the problem, but knowing that takes time.
It is rare that a fix is one small thing that will not affect other things about the controllers operation. Even if a fix is simple, verifying the fix takes time, not to mention creating and testing the fix, such as a firmware update. It is irresponsible for a manufacture to quickly release a fix for a problem without testing it thoroughly, which takes time.
Why didn't reviewers find this problem? Either they never tested waking from Sleep, or the environment they used for testing does not cause the problem. I suppose they would consider testing that rather mundane.
02-25-2014 05:26 PM
I emailed SanDisk support, linking to this thread. They responded saying that it's a known OS X issue, but I'm not totally sure of that as many of the links they sent are for years-old unrelated issues. I might try calling to see if that gives better results, or perhaps Apple just to see if perhaps it is a known issue and the support tech just didn't have the full background.
And, this wouldn't explain any of the trouble people are having on Windows. Here's the response I got: