|AkG ||September 5, 2011 11:23 AM |
Originally Posted by MpG
Interesting. I was actually told to enable hot-plugging, but maybe that was a mistake. I'll give that a try. Wish this problem was more common, so I could actually replicate it. I thought it might be the controller, but I've also got a pair of 1TB drives also in raid0, and they show up as just fine, which led me to think the problem was with the drives themselves. It's a boot/OS/game drive, and I have no experience with imaging drives to move them around, so was hoping to avoid that. Might not be an option, tho.
And yeah, no worries. Definitely no defragging happening on them.
I posted this in a dif thread, but will post it here. Its from Tony on OCZ and has plenty of tips on best pracitces when you run into issues.
here you go..my last theory on this and probably my most honest.
1 Hotplugging is the route to all evil...P67, Z68 nightmare. It was so messed up initially you HAD to have it enabled to get any stability..now I feel it is the cause of our instability.
2 How OCZ initially flash the drives and then the platforms they go on once sold....we could be seeing an issue here BUT we feel we have a cure for this...read on
3 P67 and Z68 is far from a 100% working solution, look at the chipset errata, look at the changelogs on drivers...Intel are battling to get it working correctly
4 unstable overclocked systems, especially at IDLE. This is mainly an Intel CPU issue, people test on load, they NEVER test IDLE stability. I found my CPU will cause BSOD at 1.6GHZ with any voltage lower than 1V. if I leave everything on auto and speedstep down from an overcloked turbo mode it was going below 1V...I now set voltages manually with idle and load having the same vcore.
5 people flash drives and forget they need to reset the boards (cmos reset) The boards receive info from windows on how the drives are to be configured and run, if you change something on the drive you have to let windows see this fresh info...this means when we say you need to reset cmos...you need to reset cmos http://www.ocztechnologyforum.com/fo...ilies/wink.png
so back to No1
Hotplugging = we now think BAD...why?
If you boot a board up from new, you immediately go to bios, set hotplugging enabled on the sata ports and connect one of our SSD's; I feel this may set up the board to behave like it has a USB drive connected. Now add to this you may have flashed FW to the drive with hotplugging enabled also...this may permanently set up the drive so it mimics a removable device.
What I feel happens is the following...this is my theory, no one else's (apart from me&er http://www.ocztechnologyforum.com/fo...ilies/wink.png ) and it is why we have been testing with the following in mind.
A SF2281 controller (used on Vtx3 AGT3 etc) supports automatic partial to slumber. What i feel may be happening is the drive is transitioning from partial to slumber BUT because hotplugging is live/enabled (possibly the drive flashed with it enabled) when the drive hits slumber the host controller (P67 PCH) thinks the drive in some circumstances has been disconnected....hence we get a BSOD with a disconnection error.
Remember this would only happen most of the time during an idle or low drive activity period.
So...we have been testing the following way.
1 remove the drive
2 clear the cmos
3 set hotplugging to disabled, set up bios then f10 and exit,....now power off
4 attach the drive
5 reflash the FW to the drive with hotplugging disabled
6 once reflashed, power down the system, remove power to the drive for 1 minute, reconnect the drive and power on.
7 boot to windows... go to device manager, navigate to disk drives, navigate to the SSD drive, right click on it...uninstall
9 you will now be asked to reboot
10 boot back to windows, let the drive be installed again and reboot
11 boot back to windows, make sure power scheme is how you want it ( i run balanced with sleep and hybrid enabled and LSPM to moderate)
12 reboot then run WEI
No6 is MOST important, just had this confirmed by SandForce, the drive right after being flashed HAS to see a full power cycle...i want you guys to be ultra thorough about this, if you can remove the drive or minimum take the power cable off the drive for at least 30 seconds to a minute.
on a new system I would initially clear the cmos on a new board, attach the drive, set hotplugging to disabled, immediately then reflash the drives FW then consider a clear cmos again with a drive reconnect following and again set hotplugging to disabled...then install
I'm not sure the second cmos clear is needed but it can do no harm to be thorough.
What HAS to be in place with this though is Orom 10.6 or newer and RST 10.6 or newer used (Intel platforms) anything earlier is risky (Orom 10.5 looks OK BUT we were warned you needed 10.6 to be sure)
The point is many end users do not want to do all this, they want a FW flash to just cure it....ain't going to happen im afraid. The board needs to see a drive flashed with hotplugging disabled from a fresh boot with a cleared cmos, so the freshly flashed drive passes its acpi table down to the board and the board correctly runs and sets up the drive.
Now, im not saying this is a fix, i have worked with a few who had issues that have now gone away. Some had BSOD but now have slight stutter...not sure if this is related or could just be Orom 10.5 and the updated Orom will cure it...overall though it for sure is better.
My opinion is this though, P67/Z68 has some weird issues,when you look at the frequency of Orom and driver releases from Intel you can not help but think they are dealing with many problems.
I find from my personal testing AMD's sata 3 host controller is more mature, and while a little slower, is a lot more stable. We still have guys who see issues on AMD systems also, I feel the bulk of these are not the same bug as seen on Intel systems...and we will work with those end users to get a working drive on their platform.
I have studied the ACPI table on the Intel 510, it does not support Auto Partial to Slumber, and the drive supports but has disabled set for APM...now APM is old and may not be to relevant, BUT Auto Partial to Slumber is very new and is pretty much an Intel invention, and it strikes me very odd they are not using it on their new drives and new PCH chipset. Now...im thinking some PCH actually can work with drives that are transitioning from wake to partial to slumber just fine...but I also feel some PCH have an issue with this, and hence some have issues.
If you want to try hotplugging off...its not going to help you much if you just go to bios, set disabled and hope thats all that is needed....read back and follow the steps i outlined.
Again im not saying this is the cure, but its what we have been looking at away from the public forum
You can read the rest here: Where we are with Vertex3/Agility3/Solid3 drives