From: Jens S. <jen...@us...> - 2006-08-30 21:47:40
Attachments:
smartctl-a.dreambox.2
|
Hi, I have a Seagate Barracuda 7200.9 ST3400633A which is (according to knowndrives.cpp, revision 1.141) not yet in the database. It contains a few unknown IDs and one of these Unknown_Attribute tests failed. root@dm7025:~# smartctl -H /dev/ide/host0/bus0/target0/lun0/disc smartctl version 5.33 [mipsel-unknown-linux-gnu] Copyright (C) 2002-4 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED Please note the following marginal Attributes: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 190 Unknown_Attribute 0x0022 037 025 045 Old_age Always FAILING_NOW 31581955620927 Is this critical? I attached the output of smartctl -a, Jens |
From: Bruce A. <ba...@gr...> - 2006-08-31 23:11:51
|
I don't know what this attribute it. Some vendors use this one to keep the maximum temperature that the drive has been at. The normal formula is value = 100 - T where T is temp in Celsuis. If true then the failure threshold is 55 Celsuis, your current drive temp is 63C and your highest ever drive temp was 75C. Since this exceeded the design failure threshold temp, the 'usage' attribute is failing. Note: all the above is an educated guess. Is this drive running hot? Bruce On Wed, 30 Aug 2006, Jens Seidel wrote: > Hi, > > I have a Seagate Barracuda 7200.9 ST3400633A which is (according to > knowndrives.cpp, revision 1.141) not yet in the database. > > It contains a few unknown IDs and one of these Unknown_Attribute tests > failed. > > root@dm7025:~# smartctl -H /dev/ide/host0/bus0/target0/lun0/disc > smartctl version 5.33 [mipsel-unknown-linux-gnu] Copyright (C) 2002-4 Bruce Allen > Home page is http://smartmontools.sourceforge.net/ > > === START OF READ SMART DATA SECTION === > SMART overall-health self-assessment test result: PASSED > Please note the following marginal Attributes: > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE > 190 Unknown_Attribute 0x0022 037 025 045 Old_age Always FAILING_NOW 31581955620927 > > Is this critical? > > I attached the output of smartctl -a, > > Jens > |
From: Jens S. <jen...@us...> - 2006-09-01 13:48:03
|
Hi Bruce, thanks for CC:ing me. On Thu, Aug 31, 2006 at 06:11:48PM -0500, Bruce Allen wrote: > I don't know what this attribute it. Some vendors use this one to keep > the maximum temperature that the drive has been at. The normal formula is > value = 100 - T where T is temp in Celsuis. If true then the failure > threshold is 55 Celsuis, your current drive temp is 63C and your highest > ever drive temp was 75C. Since this exceeded the design failure threshold > temp, the 'usage' attribute is failing. > > Note: all the above is an educated guess. You guessed correctly. All time I compare attribute 190 with the temperature the sum of both is 100. Can you add this ID to the database? (Or maybe just skip it in the output, since it's a duplication and also violates the "values should always not smaller than the threshold" rule). > Is this drive running hot? Yep, this is well known for the Dreambox 7025 satellite reciever. The manufacturer means it's tolerable ... > On Wed, 30 Aug 2006, Jens Seidel wrote: > >I have a Seagate Barracuda 7200.9 ST3400633A which is (according to > >knowndrives.cpp, revision 1.141) not yet in the database. > > > >It contains a few unknown IDs and one of these Unknown_Attribute tests > >failed. How about the other IDs? Device Model: ST3400633A Device is: Not in smartctl database [for details use: -P showall] ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 187 Unknown_Attribute 0x0032 070 070 000 Old_age Always - 30 189 Unknown_Attribute 0x003a 100 100 000 Old_age Always - 0 Already answered: 190 Unknown_Attribute 0x0022 052 025 045 Old_age Always In_the_past 31336889843760 194 Temperature_Celsius 0x0022 048 075 000 Old_age Always - 48 (Lifetime Min/Max 0/29) PS: I miss my mail in the mailing archive, probably because of the attachment. I found it on http://thread.gmane.org/gmane.linux.utilities.smartmontools/3948/focus=3948. There is also no way to reply to a mail from the archive (as I tried first), because the headers are not available. IIRC SourceForge admins can enable mbox creation ... Jens |
From: Bruce A. <ba...@gr...> - 2006-09-02 09:25:09
|
> thanks for CC:ing me. No problem. >> I don't know what this attribute it. Some vendors use this one to keep >> the maximum temperature that the drive has been at. The normal formula is >> value = 100 - T where T is temp in Celsuis. If true then the failure >> threshold is 55 Celsuis, your current drive temp is 63C and your highest >> ever drive temp was 75C. Since this exceeded the design failure threshold >> temp, the 'usage' attribute is failing. >> >> Note: all the above is an educated guess. > > You guessed correctly. All time I compare attribute 190 with the > temperature the sum of both is 100. OK. > Can you add this ID to the database? I did that some time ago. It's in CVS but has not made its way to tarball yet. > (Or maybe just skip it in the output, since it's a duplication and also > violates the "values should always not smaller than the threshold" rule). This is too much of a hassle to put into the code ... and also does not violate the rule since the value should not be smaller than the threshold. If it is you have exceeded the design temp of the drive. >> Is this drive running hot? > > Yep, this is well known for the Dreambox 7025 satellite reciever. The > manufacturer means it's tolerable ... Suggest that you add a fan if you possibly can... Cheers, Bruce > How about the other IDs? > > Device Model: ST3400633A > Device is: Not in smartctl database [for details use: -P showall] > > ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE > 187 Unknown_Attribute 0x0032 070 070 000 Old_age Always - 30 > 189 Unknown_Attribute 0x003a 100 100 000 Old_age Always - 0 I don't recognize this. How about writing to Seagate (pass any info back here please). > PS: I miss my mail in the mailing archive, probably because of the > attachment. I found it on > http://thread.gmane.org/gmane.linux.utilities.smartmontools/3948/focus=3948. > There is also no way to reply to a mail from the archive (as I tried > first), because the headers are not available. IIRC SourceForge admins > can enable mbox creation ... What does 'enable mbox creation' mean? I'm happy to do it but don't understand what it means. Is there a downside? Cheers, Bruce |
From: Jens S. <jen...@us...> - 2006-09-02 13:34:02
|
On Sat, Sep 02, 2006 at 04:25:02AM -0500, Bruce Allen wrote: > >>value = 100 - T where T is temp in Celsuis. If true then the failure > >You guessed correctly. All time I compare attribute 190 with the > >temperature the sum of both is 100. > OK. > >Can you add this ID to the database? > I did that some time ago. It's in CVS but has not made its way to tarball > yet. Great, I just looked at knowndrives.cpp from CVS but didn't found it there ... > >(Or maybe just skip it in the output, since it's a duplication and also > >violates the "values should always not smaller than the threshold" rule). > > This is too much of a hassle to put into the code ... and also does not > violate the rule since the value should not be smaller than the threshold. > If it is you have exceeded the design temp of the drive. You're right. It's the temperature ID where maximal values are not wanted, but since the threshold is 0 the "temperature < 0" test will probably never fail :-)) > >How about the other IDs? > > > >Device Model: ST3400633A > >Device is: Not in smartctl database [for details use: -P showall] > > > >ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED > >WHEN_FAILED RAW_VALUE > >187 Unknown_Attribute 0x0032 070 070 000 Old_age Always > >- 30 > >189 Unknown_Attribute 0x003a 100 100 000 Old_age Always > >- 0 > > I don't recognize this. How about writing to Seagate (pass any info back > here please). I didn't found this in the hard disk data sheet but found www.t13.org/docs2005/e05148r0-ACS-SMARTAttributesAnnex.pdf instead. This document was written by the T13 Technical Committee and Seagate and it also mentions you, Bruce, in section 3.1.4! It contains in table 1 (from smartmontools): IDs 187 vendor specific 189 vendor specific as well as (table 2, T13): IDs 014-189 Reserved Did you made an error and should not display 014-189 because these are *not* vendor specific or is the document wrong? > >PS: I miss my mail in the mailing archive, probably because of the > >attachment. I found it on > >http://thread.gmane.org/gmane.linux.utilities.smartmontools/3948/focus=3948. > >There is also no way to reply to a mail from the archive (as I tried > >first), because the headers are not available. IIRC SourceForge admins > >can enable mbox creation ... > > What does 'enable mbox creation' mean? I'm happy to do it but don't > understand what it means. The mbox format is the most common way to store emails. To enable creating downloadable mailing list archives in this format (on a monthly basis?) you need to activate it via http://sourceforge.net/projects/smartmontools -> Admin -> Lists/Forum -> "Mailing List Archives:" -> "Mailing list archives may be obtained in mbox format by contacting the SourceForge.net team by submitting a Support Request". This simplifies the task of reading and searching the archive (since you can use your preferred offline email client after download). > Is there a downside? Yes, it's (much?) easier for spamers to obtain email adresses. Why did I ask for it? Your mail was bogusly marked as SPAM by my email provider so that I did not found it instantly and first tried to reply manually to your mail. Since I could not set the In-Reply-To: header to your Message-ID: I would break the thread this way. Maybe not very important so feel free to ignore it but ... Jens |
From: Bruce A. <ba...@gr...> - 2006-09-03 11:09:15
|
Jens, Thank you for the detailed reply. > never fail :-)) > >>> How about the other IDs? >>> >>> Device Model: ST3400633A >>> Device is: Not in smartctl database [for details use: -P showall] >>> >>> ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED >>> WHEN_FAILED RAW_VALUE >>> 187 Unknown_Attribute 0x0032 070 070 000 Old_age Always >>> - 30 >>> 189 Unknown_Attribute 0x003a 100 100 000 Old_age Always >>> - 0 >> >> I don't recognize this. How about writing to Seagate (pass any info back >> here please). > > I didn't found this in the hard disk data sheet but found > www.t13.org/docs2005/e05148r0-ACS-SMARTAttributesAnnex.pdf > instead. This document was written by the T13 Technical Committee and > Seagate and it also mentions you, Bruce, in section 3.1.4! That's neat -- I didn't know about this document! > It contains in table 1 (from smartmontools): > IDs > 187 vendor specific > 189 vendor specific > > as well as (table 2, T13): > IDs > 014-189 Reserved > > Did you made an error and should not display 014-189 because these are > *not* vendor specific or is the document wrong? I don't understand your question. Please re-phrase it. >> What does 'enable mbox creation' mean? I'm happy to do it but don't >> understand what it means. > > The mbox format is the most common way to store emails. To enable > creating downloadable mailing list archives in this format (on a monthly > basis?) you need to activate it via > http://sourceforge.net/projects/smartmontools -> Admin -> Lists/Forum -> > "Mailing List Archives:" -> "Mailing list archives may be obtained in > mbox format by contacting the SourceForge.net team by submitting a Support > Request". If you follow this link, you will find that it does not 'enable' mail box creation. It simply allows you to make a "one-time" request for a human being at SF to generate an archive in mbox format and provide it to you privately. > Why did I ask for it? Your mail was bogusly marked as SPAM by my email > provider so that I did not found it instantly and first tried to reply > manually to your mail. Since I could not set the In-Reply-To: header to > your Message-ID: I would break the thread this way. Maybe not very > important so feel free to ignore it but ... Any other solution? Cheers, Bruce |
From: Jens S. <jen...@us...> - 2006-09-03 14:18:24
|
Hi Bruce, On Sun, Sep 03, 2006 at 06:09:04AM -0500, Bruce Allen wrote: > >It contains in table 1 (from smartmontools): > >IDs > >187 vendor specific > >189 vendor specific > > > >as well as (table 2, T13): > >IDs > >014-189 Reserved > > > >Did you made an error and should not display 014-189 because these are > >*not* vendor specific or is the document wrong? > > I don't understand your question. Please re-phrase it. You consider the attributes 187 and 189 as vendor specific but the T13 document mentions that these attributes are reserved. I think this means that IDs 187, 189 are *not* vendor specific but maybe reserved for future extensions or whatever ... It's just a wild guess but since the document uses both "reserved" and "vendor specific" attributes these states are different from each other and currently contradict in T13 and smartmontools. > If you follow this link, you will find that it does not 'enable' mail box > creation. It simply allows you to make a "one-time" request for a human > being at SF to generate an archive in mbox format and provide it to you > privately. Oh, it's seems I misunderstood it. OK, forget about it, it's not very important. > >Why did I ask for it? Your mail was bogusly marked as SPAM by my email > >provider so that I did not found it instantly and first tried to reply > >manually to your mail. Since I could not set the In-Reply-To: header to > >your Message-ID: I would break the thread this way. Maybe not very > >important so feel free to ignore it but ... > > Any other solution? No, just CC: everyone as you did for me :-)) Jens |
From: Bruce A. <ba...@gr...> - 2006-09-04 09:10:31
|
>> I don't understand your question. Please re-phrase it. > > You consider the attributes 187 and 189 as vendor specific but the > T13 document mentions that these attributes are reserved. I think this > means that IDs 187, 189 are *not* vendor specific but maybe reserved for > future extensions or whatever ... The smartmontools code attempts to provide interpretations for any attributes that we know about. There are no known interpretations for attributes in the range 14-189 inclusive. > It's just a wild guess but since the document uses both "reserved" and > "vendor specific" attributes these states are different from each other > and currently contradict in T13 and smartmontools. There are NO standards for Attributes. The T13 document tries to provide some guidance about existing industry practices. But there are no standards. Cheers, Bruce |