Sign in with
Sign up | Sign in
Your question
Solved

Trouble with getting new Samsung 840 EVO SSD detecting SATA3 (6gbps) connection - SOLVED

Tags:
  • SSD
  • Samsung
  • Storage
  • Speed
  • Evo
Last response: in Storage
Share
October 6, 2014 6:53:12 PM

SOLVED

- - - - - - -

Solved my own problem.

It was actually just a simple matter of updating the BIOS to F5 (from F4). I had assumed the software that came with the mobo would update itself to the newest version but it didn't. Just had to download from mobo website, plug in a USB, and install.

Getting proper SATA3 readings now.

- - - - - - - -

Hi all,

I'm having trouble getting my new Samsung 840 EVO SSD detecting the SATA3 (6gbps) connection. Both my Intel RST and Samsung Magician are showing a SATA2 connection and utility shows read/write at 250mbps actual. The Samsung Magician shows I "have SATA3 (6gbps) available" but that I'm using SATA2.

I have a Gigabyte H97D3H mobo and LinkDepot cables. I'm running F4 BIOS and Intel RST v13.2.4. This was a clean install on Windows7 and it actually used to work fine at SATA3 (~1 month ago). However, yesterday when I ran a new performance check I saw these problems. Already spoke to Gigabyte and Samsung support and was not much help so far.

HOWEVER. At the advice of Samsung, I tried switching the SATA port so I moved my SSD from 0 to 4 (because the 4/5 ports are on the "side" while the 0/1/2/3 are grouped together so it's possible they're "different" which they sort of are). For some reason it worked again and I was reading SATA3; weird because the H97 is supposed to have all SATA3 ports. Afterwards, I unplugged and replugged it to redo cable management and now it's not working again. Tried changing ports, cables, restarting, and running Windows Install manager's troubleshoot.

Does anyone have any ideas what my problem might be? Both Gigabyte and Samsung think it's a driver/Intel problem though they don't know for sure.

More about : trouble samsung 840 evo ssd detecting sata3 6gbps connection solved

a b G Storage
October 6, 2014 7:00:30 PM

They didn't mention the long term storage slow down problem?

There is no driver yet, to my knowledge.

Not sure if this is your problem, but a few weeks ago, it was discovered, data that is not accesses for a while, will be slow to read.

It effects the EVO, and not the PRO.
m
1
l
a b G Storage
October 6, 2014 7:00:39 PM

What other drives do you have in the system that are SATA - and what ports are they plugged into?
m
0
l
Related resources
a b G Storage
October 6, 2014 7:04:44 PM

There will be a fix for the Evo next week
m
0
l
a b G Storage
October 6, 2014 7:06:04 PM

I heard that.
Is it for sure.

Edit
Is that Nuga
m
0
l
October 6, 2014 7:30:40 PM

ronintexas said:
What other drives do you have in the system that are SATA - and what ports are they plugged into?
Only a CDROM on port3.

millwright said:
They didn't mention the long term storage slow down problem?

There is no driver yet, to my knowledge.

Not sure if this is your problem, but a few weeks ago, it was discovered, data that is not accesses for a while, will be slow to read.

It effects the EVO, and not the PRO.
I don't understand. Of course there are drivers for the hardware.

Are you saying that if I don't use data on the EVO (not PRO) that it becomes inaccessible and/or slow to read? Can you point me to a source on this? Even if this is true, I'm not sure how this affects me since I have new everything.

Paul NZ said:
There will be a fix for the Evo next week
Wait, so a recent driver update is causing my issue and all I have to do is wait for someone to fix it?
m
0
l
a b G Storage
October 6, 2014 7:44:47 PM

It wasn't a firmware update, that caused the problem.

It has been an undiscovered problem from the start.(the original firmware has a problem)

I can Guarantee, your EVO has the problem, as they all do.

It may not be your only problem, but you do have it just like everyone else.

Me included.
m
0
l
October 6, 2014 7:48:57 PM

millwright said:
It wasn't a firmware update, that caused the problem.

It has been an undiscovered problem from the start.(the original firmware has a problem)

I can Guarantee, your EVO has the problem, as they all do.

It may not be your only problem, but you do have it just like everyone else.

Me included.
Could I get a source please?

And again, does this apply to simple read/write in general?

I'm not asking about accessing old data.

m
0
l
a b G Storage
October 6, 2014 7:53:44 PM

I doesn't effect wrights.(edited from reads)

It only effects data that hasn't been accessed in a while.

The longer it has been since it has been accessed the slower it gets, because it is correcting errors.

No data loss has been reported.





m
0
l
October 6, 2014 8:03:01 PM

millwright said:
I doesn't effect wrights.(edited from reads)

It only effects data that hasn't been accessed in a while.

The longer it has been since it has been accessed the slower it gets, because it is correcting errors.

No data loss has been reported.
That's a really interesting problem that I wasn't aware of, thanks.

This is still different from my issue though isn't it. Read/write reports generated by utility softwares create new files to test. And I'm reading 250mbps on those. Plus my utility software themselves are telling me that I am not on SATA3, even though I am. Getting lower than desirable speeds is one thing, to not be detecting the correct form at all is another.

I've updated my original post to reflect this. I'm looking into SATA3 detection (over SATA2) issues, not pure speed issues.
m
0
l
a b G Storage
October 6, 2014 8:15:54 PM

It dose sound like you have another problem.

That's the only one I know about though.
m
1
l
a b G Storage
October 6, 2014 8:30:17 PM

There is a problem with several motherboards having BIOS issues with the SAMSUNG SSD drives. Several were laptops - and in some cases, they had to downgrade the BIOS to a previous version to get it to recognize the Samsung SSD as a SATA III drive. I couldn't find anything on Gigabyte's website.
m
0
l
October 6, 2014 8:55:34 PM

ronintexas said:
There is a problem with several motherboards having BIOS issues with the SAMSUNG SSD drives. Several were laptops - and in some cases, they had to downgrade the BIOS to a previous version to get it to recognize the Samsung SSD as a SATA III drive. I couldn't find anything on Gigabyte's website.
The Samsung tech was saying something along those lines. It sounds like a real hassle to do though, ugh. What are some issues that can occur if you downgrade your wares?
m
0
l
a b G Storage
October 6, 2014 9:01:10 PM

Unless there is an issue I need to fix - I leave the BIOS alone....there is always a small chance of "bricking" the mobo in changing the BIOS versions. Always follow their directions exactly.

I didn't take the time to go through all of Gigabyte's forums - I just did a search that didn't find a match. There may be a similar mobo that was having those issue - or it could be a different SSD. Sometimes it can take hours looking through their forums to find the answer....
m
1
l
October 6, 2014 9:06:30 PM

ronintexas said:
Unless there is an issue I need to fix - I leave the BIOS alone....there is always a small chance of "bricking" the mobo in changing the BIOS versions. Always follow their directions exactly.

I didn't take the time to go through all of Gigabyte's forums - I just did a search that didn't find a match. There may be a similar mobo that was having those issue - or it could be a different SSD. Sometimes it can take hours looking through their forums to find the answer....

:( 

m
0
l
October 7, 2014 12:14:09 PM

Bump for the new day? incase someone has any ideas. I'll be speaking to support again as well
m
0
l

Best solution

October 7, 2014 5:43:55 PM

Solved my own problem.

It was actually just a simple matter of updating the BIOS to F5 (from F4). I had assumed the software that came with the mobo would update itself to the newest version but it didn't. Just had to download from mobo website, plug in a USB, and install.

Getting proper SATA3 readings now.
Share
a b G Storage
October 7, 2014 5:47:06 PM

It wont update itself if you dont run it. Its not windowsupdate. And the BIOS cant update itself unless you do it
m
0
l
a b G Storage
October 8, 2014 6:16:42 AM

Agreed, there has never been an automatic BIOS update, for any computer.
m
0
l
!