S3700 SSD SATA2 mode instead of SATA3

[idata]

Hello!

I have several Intel SSD DC 3700 Series drives.

100GB, 200GB and 400GB and all have firmware 5DV12270.

100GB and 400GB drives work fine but the 200GB SSD works only in SATA2 mode with the same ports (SATA3) and cables (SATA3) with which the 100GB and 400GB drives work as SATA3 mode.

What could be the problem?

[idata]

Here is output of isdct:

- Intel SSD DC S3700 Series -

AccessibleMaxAddressSupported : False

AggregationThreshold : Device does not support this command set.

AggregationTime : Device does not support this command set.

ArbitrationBurst : Device does not support this command set.

BusType : 11

CoalescingDisable : Device does not support this command set.

ControllerCompatibleIDs : PCI\\VEN_8086&DEV_1E02&REV_04PCI\\VEN_8086&DEV_1E02PCI\\VEN_8086&CC_010601PCI\\VEN_8086&CC_0106PCI\\VEN...

ControllerDescription : @oem23.inf,%pci\\ven_8086&dev_1e02&cc_0106.devicedesc%;Intel(R) 7 Series/C216 Chipset Family SATA AHCI Controller

ControllerID : PCI\\VEN_8086&DEV_1E02&SUBSYS_84CA1043&REV_04\\3&11583659&0&FA

ControllerIDEMode : False

ControllerManufacturer : @oem23.inf,%intel%;Intel Corporation

ControllerService : iaStorA

DIPMEnabled : False

DIPMSupported : False

DevicePath : \\\\.\\PHYSICALDRIVE0

DeviceStatus : Healthy

DigitalFenceSupported : False

DownloadMicrocodePossible : True

DriverDescription : Intel(R) 7 Series/C216 Chipset Family SATA AHCI Controller

DriverMajorVersion : 12

DriverManufacturer : Intel Corporation

DriverMinorVersion : 8

DriverVersion : 12.8.0.1016

DynamicMMIOEnabled : The selected drive does not support this feature.

EnduranceAnalyzer : 3635.46 years

ErrorString :

Firmware : 5DV12270

FirmwareUpdateAvailable : The selected Intel SSD contains current firmware as of this tool release.

HDD : False

HighPriorityWeightArbitration : Device does not support this command set.

IOCompletionQueuesRequested : Device does not support this command set.

IOSubmissionQueuesRequested : Device does not support this command set.

Index : 0

Intel : True

IntelGen3SATA : True

IntelNVMe : False

InterruptVector : Device does not support this command set.

IsDualPort : False

LatencyTrackingEnabled : The selected drive does not support this feature.

LowPriorityWeightArbitration : Device does not support this command set.

Lun : 0

MaximumLBA : 390721967

MediumPriorityWeightArbitration : Device does not support this command set.

ModelNumber : INTEL SSDSC2BA200G3

NVMePowerState : Device does not support this command set.

NativeMaxLBA : 390721967

OEM : Generic

OpalState : Unsupported

PLITestTimeInterval : 10080 minutes

PNPString : SCSI\\DISK&VEN_INTEL&PROD_SSDSC2BA200G3\\4&15828421&0&000000

PathID : 0

PhySpeed : 6.0 Gbps

PhysicalSectorSize : 4096 bytes

PhysicalSize : 200049647616

PortNumber : 0

PowerGovernorAveragePower : 8500 milliwatts

PowerGovernorBurstPower : 9500 milliwatts

PowerGovernorMode : 0 Unconstrained. Limited by maximum budget

Product : Taylorsville

ProductFamily : Intel SSD DC S3700 Series

ProductProtocol : ATA

ReadErrorRecoveryTimer : 0

RemoteSecureEraseSupported : False

SCSIPortNumber : 0

SMARTEnabled : True

SMARTHealthCriticalWarningsConfiguration : Device does not support this command set.

SMARTSelfTestSupported : True

SMBusAddress : Device does not support this command set.

SMI : False

SSCEnabled : False

SanitizeBlockEraseSupported : True

SanitizeCryptoScrambleSupported : True

SanitizeSupported : True

SataGen1 : True

SataGen2 : True

SataGen3 : True

SataNegotiatedSpeed : 3.0 Gbs

SectorSize : 512

SecurityEnabled : False

SecurityFrozen : True

SecurityLocked : False

SecuritySupported : True

TCGSupported : False

TargetID : 0

TempThreshold : Device does not support this command set.

TemperatureLoggingInterval : 1 minute(s)

TimeLimitedErrorRecovery : Device does not support this command set.

TrimSize : 6

TrimSupported : True

VolatileWriteCacheEnabled : Device does not support this command set.

WWID : 2778522436000306637

WriteAtomicityDisableNormal : Device does not support this command set.

WriteCacheEnabled : True

WriteCacheReorderingStateEnabled : True

WriteCacheState : 1

WriteCacheSupported : True

WriteErrorRecoveryTimer : 0

eDriveSupported : False

[idata]

Hi fptas1979,

That's a weird behavior as your other drives are working correctly under the same conditions according to your description.In some cases, issues related to SATA modes may be related to the BIOS and chipset used. Although this may not be the root cause here, I still recommend you to check that the BIOS and chipset are updated.On the other hand, have you tried to use those drives in another system just to see if the same behavior happens?Additionally, could you please share the Intel® SSD DCT output for the other drives and the SMART details of all drives too?Please confirm also if you are using the drives as storage or bootable units.I'll be waiting for your response.Have a nice day.Regards,Diego V.

[idata]

Hello!

Thanks for the answer!

Today I tried my drives on another test desktop motherboard Asus H110M. It has 4 SATA3 ports.

The OS was installed on the WD 1 TB HDD.

All SSD drives were used as a storage.

I connected my Intel DC S3700 drives (100, 200 and 400 GB models). 200GB model worked in SATA2 mode.

The output of isdct is in the file 1.txt.

Then I disconnected the cables from 200 and 400 GB drives (but not from the motherboard) and exchanged the cables. The result was the same (file 2.txt)

Then I disconnected the cables from the 200 and 100GB models and exchanged them.

Again 200GB worked in the mode SATA2 (3.txt)

Smart details is in the file 1smart.txt

I do not know what else to do.

I also think that before updating the firmware from 5DV10270 to 5DV12270 the drive worked in SATA3 mode, but I did not have any screenshots, logs or anything similar to confirm this.

Is it possible to downgrade the firmware from 5DV12270 to 5DV10270?

How?

[idata]

Thank you for the information and detailed description.

Please let me investigate about this issue because I'm not sure why it's happening. However, it's interesting that it worked fine on the previous firmware version.I haven't seen any reports about this issue after updating the firmware to the latest one. I'll investigate on this as well. Unfortunately, it's not possible to downgrade the firmware.I'll post here my findings as soon as possible.Have a nice day.Regards,Diego V.