Limiting Transfer Rate of HDD

[rymock]

I have a Samsung Spinpoint M9T ST1500LM006, it is a SATA III (6gb/s) drive. I want to limit it to SATA I, what software lets me do this?

[pclab]

I don't think there's a software for that.
If I remember well, there were a few drives with the possibility of limit it with a jumper. But on these new drives, I don't think that's possible anymore.

[rymock]

The set max udma mode setting in MHDD can't do it?

The drive has no jumper settings, but the drive is downward compatible with SATA II and SATA I which means there must be someway to force it into either mode.

[Spildit]

With some expensive firmware tool for Samsung like PC-3000, MRT or SHT it "might" be possible.

At least with my full version of SHT i can set SATA 1 or 2 mode on any drive but i don't know if the "changes" are permanent or if they are lost at power off/on. I've never tested it.

[MindMergepk]

I have a Samsung Spinpoint M9T ST1500LM006, it is a SATA III (6gb/s) drive. I want to limit it to SATA I, what software lets me do this?

what you want to achieve by limiting the transfer rate ?

[rymock]

I have a Samsung Spinpoint M9T ST1500LM006, it is a SATA III (6gb/s) drive. I want to limit it to SATA I, what software lets me do this?

what you want to achieve by limiting the transfer rate ?

Original Playstation 3 models have trouble with SATA II and SATA III where the system will not boot properly sometimes. It's necessary that I force the drive in SATA I so I'm not gambling whether or not my console will start properly.

[Spildit]

Ok !

I've done some testing with the PAID LICENSED version of SHT and IT DOES WORK and IT DOES SURVIVE THE POWER OFF/ON :

POWER OFF - ON :

I would bet that doing this will set some "FLAG" most likely on the FIPS section of ROM so that the MCU knows at boot up what set of SATA speeds the drive should report to be able to use ...

[fzabkar]

I would bet that doing this will set some "FLAG" most likely on the FIPS section of ROM so that the MCU knows at boot up what set of SATA speeds the drive should report to be able to use ...

Sounds reasonable ....

http://forum.ru-board.com/topic.cgi?for ... imit=1&m=1

ActiveFW : 00
FWVer : 0001
SATA PLL cal done

DDR size detected = 8MB
*PA VID=0007 P
N=0000 Rev=0004
*PA VID=0007 PN=0000 Rev=0004
U
S_0SSC EN
SO_1
SSC EN
IS=2
CLA #36/56
Handoff RPM=742
SPOK

[Spildit]

Ok ....

As i was thinking.

SATA I or II settings are stored on the ROM code on the FIPS section as shown on the screen capture.

When you set SATA speed it will store the value on the ROM (like the PUIS FLAG) and the drive will "know" the SATA speed it's setted to when it's powered off/on.

A drive with SATA II speed should drop to SATA I if the machine where it's connected to only supports SATA I speed. It's like a "negotiation of speeds" at when the host detects the drive. The drive should report what speeds it supports and the host should decide what speed to use acording to what speeds it supports as well. If they both support SATA 3 then they should go for the high speed, if one of them only supports lower speed they should agree on the faster speed that both can handle.

At any rate this experience shows that it's possible to set SATA speeds on ROM on SAMSUNG drives.

Maybe there is a free utility to set the sata speed ? Like a vendor tool to do so ?

Regards.

[Spildit]

And on the FULL ROM DUMP :

ROM/FIPS Checksum :

[rymock]

Ok !

I've done some testing with the PAID LICENSED version of SHT and IT DOES WORK and IT DOES SURVIVE THE POWER OFF/ON :

Can you share this software, or do you know of any software that's very similar? I have no idea where to find SHT, I only speak English so it's hard to sift through these sites.

[fzabkar]

It may not work with your model but ...

Please note that this DEMO will READ the firmware but will not write it back to the drive.

SHT - Samsung HDD Tool Free Edition (DEMO) !
http://www.hddoracle.com/viewtopic.php?f=149&t=1084

SHT new 4.0.7 with new offer:
http://www.hddoracle.com/viewtopic.php?t=1506&p=8213

[fzabkar]

At any rate this experience shows that it's possible to set SATA speeds on ROM on SAMSUNG drives.

It seems that you are working out the function of the FIPS one byte at a time. :-)

Off topic: I wonder what the drive is trying to write to the FIPS when it gets corrupted?

[Spildit]

It may not work with your model but ...

Please note that this DEMO will READ the firmware but will not write it back to the drive.

SHT - Samsung HDD Tool Free Edition (DEMO) !
http://www.hddoracle.com/viewtopic.php?f=149&t=1084

SHT new 4.0.7 with new offer:
http://www.hddoracle.com/viewtopic.php?t=1506&p=8213

It doesn't work, i've tried.

Look :

On my Trinity M7E drive, i've used the DEMO to SET SATA to 1.5 G :

If i then do a check with the full version the ROM/FIPS was NOT CHANGED and the drive reports as SATA 2 :

This is the same if i use SRT :

DOESN'T WORK ON MODERN TRINITY DRIVES.

It reports as it had changed speed but it doesn't made changes to ROM neither the drive reports the new speed.

I thing SRT and the DEMO of SHT are using an old method that will NOT WORK on modern drives.

The PAID VERSION ($200 USD) of SHT is CONFIRMED TO WORK.

Also check here on ebay :

http://www.ebay.com/itm/1-5TB-Samsung-M ... 1134463509

ST1500LM006 = HM-M151RAD

This is FULLY SUPPORTED by the paid (not free) version of SHT 4.0.7

Also you WILL NOT BE ABLE to READ ROM on your drive with the DEMO as the drive is very recent and the DEMO only works with older drives.

Maybe you can use something like HDAT2 and see if you can set the SATA speed ?

Maybe there is a free vendor tool to set the SATA speed ?

If you aren't lucky SHT is an option but i don't think you would want to pocket out $200 USD to change the speed of one drive ...

[Spildit]

At any rate this experience shows that it's possible to set SATA speeds on ROM on SAMSUNG drives.

It seems that you are working out the function of the FIPS one byte at a time.

Off topic: I wonder what the drive is trying to write to the FIPS when it gets corrupted?

Well, i was lucky !

Off Topic - I've found out that SHT will read the full ROM by TTL but to read and WRITE to FIPS section/module you can use ATA and TTL.

b.jpg (25.92 KiB) Viewed 16985 times

This is interesting because it sugests that the drive can access to FIPS by VSC and FIPS can be manipulated as a ROM MODULE separated from the main ROM code.

It might be possible to fix FIPS by ATA even when it's damaged without the need of TTL.

If the drive is accessing FIPS to set drive settings as PUIS, SATA mode, etc it might be attempting to set something and because of a BUG or specific condition ends up clearing the FIPS section and/or damaging the checksum.

Also on drives that have the problem of "cleared" FIPS section .... look at my SHT screen capture ... it have an option to clear FIPS ...

Maybe there is some sort of VSC collision and some other ATA command clears the FIPS even when it shouldn't do so when the drive is in a certain condition ?

If there is the option/command to clear FIPS then we can assume that the command is "called" or executed in error and the result is cleared FIPS and damaged drive ?

[fzabkar]

ISTR that Ace's blog article stated that all one needed to do to repair a damaged FIPS was to write the FIPS header, fill the module with zeros and then write a valid checksum at the end. I could be wrong, though.

[Spildit]

Ok, here is some more testing !!!

Power up with the drive in SATA2, 3G mode :

Code:

*PA VID=0007 PN=0000 Rev=0004*PA VID=0007 PN=0000 Rev=0004ChipRev = 63B0U
S_0Shock Sensor Circuit Enabled
SO_1
Shock Sensor Circuit Enabled
IS=2
CLA #36/56
Handoff RPM=609
SPOK
mS1 00000003
A1O=5 A1G=419
O=509 S=-2
SK C:  5144 H:0
Loaded FIT ( 0: 0: 1)
CalibTable Loaded. Rev:0x17
ResoTable Loaded. Rev:0x01
Bump Limit Loaded. Rev:0x00
RRO1xTable Loaded. Rev:0x01
Ovly loaded to 0x0001CD00
Ovly loaded to 0x1005B800
FdtTable Loaded. Rev:0x02
[GL][90PT:0FF0,0204]
[GL][FULL:0FF0,0204]
Reading Serial Num Pass
Up MC

PwrOn RRO1x @ H0
Table) cos = -1605632, sin = -1520128
Coeff) cos = 120172, sin = 198801

DiskSlip : 202 [SrvTrk]
DiskSlip : 182 [SrvTrk]
TgtCyl:     842
Hd:   0 Zn:   0 Avg.:     200
TgtCyl:  176473
Hd:   0 Zn:   1 Avg.:    1126

SVCAL(0080,0000)-->PASS
RecordValid Ok : 0107E47D 0107E41D
P11FFS Enabled
ReadyTime = 2047533 us
ENG>mS1 00000003
SK C:132828 H:0
SoUL!
PK_4   C:  8496 H:0

Power on with drive in SATA1, 1.5G :

Code:

*PA VID=0007 PN=0000 Rev=0004*PA VID=0007 PN=0000 Rev=0004ChipRev = 63B0U
S_0Shock Sensor Circuit Enabled
SO_1
Shock Sensor Circuit Enabled
IS=5
CLA #36/55
Handoff RPM=787
SPOK
mS1 00000003
A1O=6 A1G=419
O=509 S=1
SK C:  5092 H:0
Loaded FIT ( 0: 0: 1)
CalibTable Loaded. Rev:0x17
ResoTable Loaded. Rev:0x01
Bump Limit Loaded. Rev:0x00
RRO1xTable Loaded. Rev:0x01
Ovly loaded to 0x0001CD00
Ovly loaded to 0x1005B800
FdtTable Loaded. Rev:0x02
[GL][90PT:0FF0,0204]
[GL][FULL:0FF0,0204]
Reading Serial Num Pass
Up MC

PwrOn RRO1x @ H0
Table) cos = -1605632, sin = -1520128
Coeff) cos = 108684, sin = 206668

DiskSlip : 202 [SrvTrk]
DiskSlip : 182 [SrvTrk]
TgtCyl:     842
Hd:   0 Zn:   0 Avg.:     200
TgtCyl:  176473
Hd:   0 Zn:   1 Avg.:    1125

SVCAL(0080,0000)-->PASS
RecordValid Ok : 0107E47D 0107E41D
P11FFS Enabled
ReadyTime = 1968033 us
ENG>mS1 00000003
SK C:132846 H:0
SoUL!
PK_4   C:  8496 H:0

Can't find any diference on terminal log.

[Spildit]

ISTR that Ace's blog article stated that all one needed to do to repair a damaged FIPS was to write the FIPS header, fill the module with zeros and then write a valid checksum at the end. I could be wrong, though.

It might work .... The problem is that you will loose the "settings" that are set by the FIPS module.

So i would PATCH with a known good copy instead of repair by fixing the header and write a zero filled module.

Here is my FIPS module on my test drive :

2AJV3nqM.d31 (FIPS)TERM.rar

(2.14 KiB) Downloaded 549 times

You would loose a considerable amount of data/settings by zero filling the FIPS (instead of patching) and there are settings there like PUIS, SATA Speed, etc .... so i don't think zero fill the FIPS would be viable (or possible) at all.

[NRA]

Guys, and how about DCO (DEVICE CONFIGURATION OVERLAY), or hardcore only?