Kobalt G150 (Clevo P150hm) Issue with dual SSD

I bought one of these laptops recently and am having an issue with my laptop I was wondering if anyone else has a similar problem or is using a similar configuration with no problems.
Here is how I have the machine set up :

Port0 : Drive 1 Intel 510 OS windows 7 (Primary SSD slot)
Port2: Drive 2 Intel 510 Secondary OS Server 2008 ( Using Optical bay adapter)

Boot into either OS from power off using power on button -> Both drives detected and working normally

While in Either OS select to restart the machine from the start menu -> Primary drive detected and 50% chance of secondary drive being detected.

Port 2 is reported as a SATA 2 port by Intel Storage management software I am just wondering if this issue could be caused by some backward compatability issue with using a SATA 3 drive in this port.

Originally I had vertex 3 Drives in this configuration which had the same problem ( now replaced by reseller with Intel 510)

Has anyone else got this model with a optical bay adaptor and using it successfully without the above issue.

 

have you informed kobalt ashman as cant see any posts about it on there.

 

http://www.kobaltcomputers.co.uk/fo...tant-announcement-regarding-OCZ-Vertex-3-SSDs
"Hmm thats an interesting announcement. I had recieved my G150 with vertex 3 ssds a few weeks ago. The first SSD which was shipped with the laptop seemed to work ok and I have had no problems with it. After recieveing the second SSD last week and placing it the drive caddy I have started to get the odd BSOD and have also noticed that the second drive seems to disappear (not detected by the bios) if I restart the machine. Guess I will start a support ticket. "

I have had a support ticket open with them on this issue for quite a while.

 

Just to add that we have been communicating with Ashman about this, But at the moment we are trying to work it out!

More specifically would be interested to hear of people who have 2 x 250gb intel Drives in a P150HM/P170HM and see what their experience is

Pman

 

with the P150HM the port configuration is as follows
Port 0: Sata 3 -> Primary HDD slot
Port 1: Sata 3 -> ESATA
Port 2: Sata 2 ->Optical drive slot

I don't have a P170HM but I am assuming as it has 2 HDD slots it is probably
Port 0: Sata 3 -> Primary HDD slot
Port 1: Sata 3 -> Secondary HDD slot
So with the P170HM you might need to use an optical drive adaptor to get the same issue.

It would be good to get some comments from other re-sellers who offer Optical drive caddys to see if they have had any reports of these issues.

 

Here's what we know about the following types of drives:

- Intel Drives, have been just fine in all the P's and W's laptops, in single or dual configurations (In caddy). That would be the old X25-M's, the 510 series and the 320 series.

- The C300's the same thing once you do the LPM fix. Same with the M4's.

- We've had one set of P3's act goofy in a dual drive configuration, but we attributed that to a bunk drive.

- The vertex's.. There is a reason we don't have them on our site, we cannot keep the vertex 3's stable in any configuration in any of the P's or W series. They always have random BSOD and other stability issues. We've worked with OCZ to get some custom firmware builds to try and get it stable, and we still couldn't. We saw the same types of issues all the way back in January with the vertex 2's on 25nm..


So thats our info =)

 

What versions of the bios have you tested these with as I am currently getting this issue with an intel 510. Note: I dont get any BSOD with the intel drives just the issue on rebooting with the secondary drive not being always detected (roughly 50% of the time). Additionally have you tested these with 250 gb drives ( not that that should make any difference).
Thanks

 

Very good post, that should be stickied for SSDs for these notebooks and it's spot on. My C300 was wonky but the LPM registry fix solved all issues.

 

My Vertex 2E has only a 80% chance of being detected correctly on BIOS startup. I just reboot and off it goes.

I've been too lazy to see if there's a BIOS update for it.