Page 1 of 1

Incorrect info for ST500DM002

Posted: 2014.07.06. 15:33
by _HU_
Hello,

I'm trying your tool and the latest version reports incorrectly the generation of my Seagate Barracuda. I have a ST500DM002-1BD142 and this disk is from 7200.14 generation, whereas HD Sentinel detects it as a 7200.12. The Seagate website states that my disk is a 7200.14 gen, as you can see at http://www.seagate.com/es/es/internal-h ... M002#specs .

HD Sentinel report:

Code: Select all

Disk Information

Disk Family,Barracuda [b]7200.12[/b] 500DM002
Form Factor,"3.5"" "
Capacity,500 GB (500 x 1.000.000.000 bytes)
Number Of Disks,1
Number Of Heads,2
Rotational Speed,7200 RPM
Rotation Time,"8,33 ms"
Average Rotational Latency,"4,17 ms"
Disk Interface,Serial-ATA/600
Buffer-Host Max. Rate,600 MB/seconds
Buffer Size,16384 KB
Drive Ready Time (typical),8.5 seconds
Average Seek Time,"8,5 ms"
Track To Track Seek Time,"1,0 ms"
Full Stroke Seek Time,? ms
Width,"101,6 mm (4,0 inch)"
Depth,"147,0 mm (5,8 inch)"
Height,"20,0 mm (0,8 inch)"
Weight,"415 grams (0,9 pounds)"
Acoustic (Idle),"2,1 Bel"
Acoustic (Min performance and volume),"2,3 Bel"
Acoustic (Max performance and volume),"2,3 Bel"
Required power for spinup,2.000 mA
Power required (seek),"5,8 W"
Power required (idle),"4,5 W"
Power required (standby),? W
Manufacturer,Seagate Technology
Manufacturer Website,http://www.seagate.com/www/en-us/products
Regards

Re: Incorrect info for ST500DM002

Posted: 2014.07.07. 08:48
by hdsentinel
Hello,

Thanks for your attention, it may be a typo when the database updated with this model.

I can confirm that it's fixed, so the online database now properly shows 7200.14
http://www.hdsentinel.com/storageinfo_d ... ST500DM002

and the next software update will also show this.

Thanks again for your attention and help !

Re: Incorrect info for ST500DM002

Posted: 2016.04.14. 02:42
by _HU_
Hello,

This small bug is again present on HDS 4.70 (I've not tried version 4.71).

Regards.

Re: Incorrect info for ST500DM002

Posted: 2016.04.20. 14:24
by hdsentinel
Hi,

Thanks for your attention and sorry for the troubles!
I'm sure it will be fixed again - and this time hopefully permanently ;)