[opensuse] Hard disk weirdness on an ancient laptop
![](https://seccdn.libravatar.org/avatar/f0ad86a443e23d8412160985c73d3b1b.jpg?s=120&d=mm&r=g)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I got an ancient laptop (Pentium IV, 0.5GiB) as a present from a friend (you may remember the video problem I had with it, solved). It is "running" openSUSE 12.3. The hard disk it came with was totally useless. 20GB, full of write errors. So I bought a new one for it - I was lucky to locate a new unit with parallel IDE, 2.5" size, expensive for what it is: Hitachi Travelstar HD 2.5" 80GB IDE/ATA, 37.15€ plus 21% tax. Oh, well... no alternative. Well, I had located a 20GB unit, 15€ plus shipping, private person. Too small, probably. The 80GB unit I got from a reputable dealer, that I get almost all my hardware currently. The unit came sealed in its original bag. However... Smartctl test says it is an old unit: +++···················································· AmonLanc:~ # smartctl -a /dev/sda smartctl 6.0 2012-10-10 r3643 [i686-linux-3.7.10-1.1-default] (SUSE RPM) Copyright (C) 2002-12, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Hitachi Travelstar 5K160 Device Model: Hitachi HTS541680J9AT00 Serial Number: SB024CJGG8ZLMD LU WWN Device Id: 5 000cca 572c415d7 Firmware Version: SB2OA7AH User Capacity: 80,026,361,856 bytes [80.0 GB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: ATA/ATAPI-7 T13/1532D revision 1 Local Time is: Sat Aug 17 23:02:46 2013 CEST SMART support is: Available - device has SMART capability. SMART support is: Enabled ... SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000b 100 100 062 Pre-fail Always - 0 2 Throughput_Performance 0x0005 100 100 040 Pre-fail Offline - 0 3 Spin_Up_Time 0x0007 162 162 033 Pre-fail Always - 1 4 Start_Stop_Count 0x0012 094 094 000 Old_age Always - 10256 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 100 100 040 Pre-fail Offline - 0 9 Power_On_Hours 0x0012 056 056 000 Old_age Always - 19423 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 455 191 G-Sense_Error_Rate 0x000a 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 58 193 Load_Cycle_Count 0x0012 099 099 000 Old_age Always - 10908 194 Temperature_Celsius 0x0002 177 177 000 Old_age Always - 31 (Min/Max 16/60) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 223 Load_Retry_Count 0x000a 100 100 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 19423 - # 2 Extended captive Completed without error 00% 19399 - # 3 Short offline Completed without error 00% 19399 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. AmonLanc:~ # ····················································++- 19423 hours? How is that possible? And so many values at zero? If I am the victim of a fraud, surely it can not have 20Khours, right? That's too much for a laptop unit, they tend to break down earlier than 6000 hours. Maybe a refurbished disk, old chipset, new platter assembly? A bug in smartctl? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlIP8/AACgkQtTMYHG2NR9XFFgCfUHFLReua+6mBgz2J5xho52Ua h/sAnA7Kmoehx1lkmKHJ/KVVcUbsbtF4 =lybL -----END PGP SIGNATURE-----
![](https://seccdn.libravatar.org/avatar/b4047644c59f2d63b88e9464c02743fd.jpg?s=120&d=mm&r=g)
On 8/17/2013 3:06 PM, Carlos E. R. wrote:
19423 hours? How is that possible?
And so many values at zero?
If I am the victim of a fraud, surely it can not have 20Khours, right? That's too much for a laptop unit, they tend to break down earlier than 6000 hours.
Maybe a refurbished disk, old chipset, new platter assembly? A bug in smartctl?
Its quite possible that smartctl might not be accurate on an old drive like that. (I would have opted for buying a newer controller, unless its a laptop). Perhaps older models report values from the controller and not the disk itself, but also it is common for there to be some discrepancy in the UNITS used for storage See: http://sourceforge.net/apps/trac/smartmontools/wiki/FAQ#smartctlreportstheag...
smartctl reports the age as thousands of hours for my Maxtor/Hitachi/Fujitsu disk , yet it is only a few days old
On recent disks, Maxtor has started to use Attribute 9 to store the power-on disk lifetime in minutes rather than hours. In this case, use the: '-v 9,minutes' option to correctly display hours and minutes.
Some models of Fujitsu disks use Attribute 9 to store the power-on disk lifetime in seconds. In that case, use the: '-v 9,seconds' option to correctly display hours, minutes and seconds.
-- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2013-08-17 at 15:19 -0700, John Andersen wrote:
Its quite possible that smartctl might not be accurate on an old drive like that. (I would have opted for buying a newer controller, unless its a laptop).
It is a laptop, or I would have thought of that (I hope), seeing how difficult it is to obtain ATA drives.
Perhaps older models report values from the controller and not the disk itself, but also it is common for there to be some discrepancy in the UNITS used for storage
See: http://sourceforge.net/apps/trac/smartmontools/wiki/FAQ#smartctlreportstheag...
smartctl reports the age as thousands of hours for my Maxtor/Hitachi/Fujitsu disk , yet it is only a few days old
On recent disks, Maxtor has started to use Attribute 9 to store the power-on disk lifetime in minutes rather than hours. In this case, use the: '-v 9,minutes' option to correctly display hours and minutes.
Some models of Fujitsu disks use Attribute 9 to store the power-on disk lifetime in seconds. In that case, use the: '-v 9,seconds' option to correctly display hours, minutes and seconds.
AmonLanc:~ # smartctl -v 9,minutes -A /dev/sda | grep Power_On 9 Power_On_Minutes 0x0012 056 056 000 Old_age Always - 323h+45m AmonLanc:~ # smartctl -v 9,seconds -A /dev/sda | grep Power_On 9 Power_On_Seconds 0x0012 056 056 000 Old_age Always - 5h+23m+45s AmonLanc:~ # Hum... that could be right, seconds :-? Five hours sounds correct. But other values are also wrong: 4 Start_Stop_Count 0x0012 094 094 000 Old_age Always - 10256 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 455 193 Load_Cycle_Count 0x0012 099 099 000 Old_age Always - 10908 SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 19424 - Weird. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlIQAk4ACgkQtTMYHG2NR9UsYACdEyznpKmvvYCoiKxkS5k0ojWB qbwAn1BnlqvrhdMVhfDx3WHQDLpqSfJy =BXha -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/b4047644c59f2d63b88e9464c02743fd.jpg?s=120&d=mm&r=g)
On 8/17/2013 4:07 PM, Carlos E. R. wrote:
On Saturday, 2013-08-17 at 15:19 -0700, John Andersen wrote:
Its quite possible that smartctl might not be accurate on an old drive like that. (I would have opted for buying a newer controller, unless its a laptop).
It is a laptop, or I would have thought of that (I hope), seeing how difficult it is to obtain ATA drives.
Perhaps older models report values from the controller and not the disk itself, but also it is common for there to be some discrepancy in the UNITS used for storage
See: http://sourceforge.net/apps/trac/smartmontools/wiki/FAQ#smartctlreportstheag...
smartctl reports the age as thousands of hours for my Maxtor/Hitachi/Fujitsu disk , yet it is only a few days old
On recent disks, Maxtor has started to use Attribute 9 to store the power-on disk lifetime in minutes rather than hours. In this case, use the: '-v 9,minutes' option to correctly display hours and minutes.
Some models of Fujitsu disks use Attribute 9 to store the power-on disk lifetime in seconds. In that case, use the: '-v 9,seconds' option to correctly display hours, minutes and seconds.
AmonLanc:~ # smartctl -v 9,minutes -A /dev/sda | grep Power_On 9 Power_On_Minutes 0x0012 056 056 000 Old_age Always - 323h+45m AmonLanc:~ # smartctl -v 9,seconds -A /dev/sda | grep Power_On 9 Power_On_Seconds 0x0012 056 056 000 Old_age Always - 5h+23m+45s AmonLanc:~ #
Hum... that could be right, seconds :-? Five hours sounds correct. But other values are also wrong:
4 Start_Stop_Count 0x0012 094 094 000 Old_age Always - 10256 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 455 193 Load_Cycle_Count 0x0012 099 099 000 Old_age Always - 10908
SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 19424 -
The -v command applies to a specific variable printed, so setting seconds/minutes for v9 would ONLY correct attribute 9, not the others as well. By leaving it on for a couple hours, you could deduce what the units should be set to in the -v parameter. Still assuming it should be minutes (because it is a Hitachi), 323+ hours sounds like a disk that was returned after 12-15 days of use, and not a totally new disk. I might live with that. But I'd still question my supplier. Power cycle count of 455 seems a bit high for any factory test regimen. Factory testing might be 5 hours but its not going to be 300 hours. -- _____________________________________ ---This space for rent--- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Saturday, 2013-08-17 at 16:20 -0700, John Andersen wrote:
On 8/17/2013 4:07 PM, Carlos E. R. wrote:
Hum... that could be right, seconds :-? Five hours sounds correct. But other values are also wrong:
4 Start_Stop_Count 0x0012 094 094 000 Old_age Always - 10256 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 455 193 Load_Cycle_Count 0x0012 099 099 000 Old_age Always - 10908
SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Extended offline Completed without error 00% 19424 -
The -v command applies to a specific variable printed, so setting seconds/minutes for v9 would ONLY correct attribute 9, not the others as well.
I know. But all parameters need correction.
By leaving it on for a couple hours, you could deduce what the units should be set to in the -v parameter.
I was already running that test, look: AmonLanc:~ # ( smartctl -A /dev/sda | grep Power_On_Hours ) ; sleep 3600 ; ( smartctl -A /dev/sda | grep Power_On_Hours ) 9 Power_On_Hours 0x0012 056 056 000 Old_age Always - 19425 9 Power_On_Hours 0x0012 056 056 000 Old_age Always - 19426 AmonLanc:~ # 1 unit increase per hour. It looks like hours with an offset.
Still assuming it should be minutes (because it is a Hitachi), 323+ hours sounds like a disk that was returned after 12-15 days of use, and not a totally new disk. I might live with that. But I'd still question my supplier.
Indeed. But the plastic envelope (the antistatic kind) was sealed.
Power cycle count of 455 seems a bit high for any factory test regimen.
Factory testing might be 5 hours but its not going to be 300 hours.
It matches the setting as seconds. Some time at factory, plus the time I installed openSUSE and decided to run the test. Still, 5 hours might be too low. - -- Cheers, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iEYEARECAAYFAlIQDBEACgkQtTMYHG2NR9XwRgCeP+aMydm9/UHA+WsHCk2+J7Bh dg8AoJJnR4wlum0ZQyvJMs5mbLvvALF3 =wXFw -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/25bbc96d9c53647354cb724e744b2222.jpg?s=120&d=mm&r=g)
"Carlos E. R." <carlos.e.r@opensuse.org> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I got an ancient laptop (Pentium IV, 0.5GiB) as a present from a friend
(you may remember the video problem I had with it, solved). It is "running" openSUSE 12.3.
The hard disk it came with was totally useless. 20GB, full of write errors. So I bought a new one for it - I was lucky to locate a new unit
On the paper label it may have the date of manufacture or a date code. Does it have either? Greg -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 2013-08-18 16:18, Greg Freemyer wrote:
The hard disk it came with was totally useless. 20GB, full of write errors. So I bought a new one for it - I was lucky to locate a new unit
On the paper label it may have the date of manufacture or a date code.
Does it have either?
Yes, "JUN 08". (I made a scan/photo of the backside before inserting in the laptop) I understand it is "new" not as manufactured now, but manufactured 2008 and not sold at the time. The retailer just bought more units than they were able to sell at the time, for which I'm fortunate. -- Cheers / Saludos, Carlos E. R. (from 12.3 x86_64 "Dartmouth" at Telcontar)
participants (4)
-
Carlos E. R.
-
Carlos E. R.
-
Greg Freemyer
-
John Andersen