Home / Browse / S.M.A.R.T. Monitoring Tools / Mail / Archive

S.M.A.R.T. Monitoring Tools

Email Archive: smartmontools-support (read-only)

2002:	_Jan	_Feb	_Mar	_Apr	_May	_Jun	_Jul	_Aug	_Sep	_Oct (50)	_Nov (161)	_Dec (84)
2003:	_Jan (84)	_Feb (103)	_Mar (54)	_Apr (63)	_May (44)	_Jun (45)	_Jul (44)	_Aug (55)	_Sep (15)	_Oct (99)	_Nov (101)	_Dec (104)
2004:	_Jan (76)	_Feb (98)	_Mar (99)	_Apr (130)	_May (107)	_Jun (79)	_Jul (94)	_Aug (164)	_Sep (115)	_Oct (125)	_Nov (160)	_Dec (84)
2005:	_Jan (72)	_Feb (85)	_Mar (55)	_Apr (109)	_May (64)	_Jun (33)	_Jul (71)	_Aug (77)	_Sep (84)	_Oct (102)	_Nov (106)	_Dec (51)
2006:	_Jan (47)	_Feb (58)	_Mar (60)	_Apr (106)	_May (73)	_Jun (65)	_Jul (109)	_Aug (103)	_Sep (73)	_Oct (57)	_Nov (94)	_Dec (62)
2007:	_Jan (61)	_Feb (67)	_Mar (90)	_Apr (90)	_May (77)	_Jun (82)	_Jul (75)	_Aug (74)	_Sep (63)	_Oct (70)	_Nov (60)	_Dec (59)
2008:	_Jan (68)	_Feb (113)	_Mar (128)	_Apr (89)	_May (57)	_Jun (88)	_Jul (74)	_Aug (43)	_Sep (77)	_Oct (106)	_Nov (99)	_Dec (82)
2009:	_Jan (126)	_Feb (49)	_Mar (47)	_Apr (26)	_May (38)	_Jun (75)	_Jul (61)	_Aug (45)	_Sep (105)	_Oct (77)	_Nov (46)	_Dec (47)
2010:	_Jan (58)	_Feb (88)	_Mar (54)	_Apr (78)	_May (30)	_Jun (40)	_Jul (46)	_Aug (36)	_Sep (30)	_Oct (29)	_Nov (80)	_Dec (52)
2011:	_Jan (30)	_Feb (27)	_Mar (25)	_Apr (77)	_May (24)	_Jun (45)	_Jul (34)	_Aug (24)	_Sep (65)	_Oct (55)	_Nov (72)	_Dec (19)
2012:	_Jan (58)	_Feb (44)	_Mar (90)	_Apr (11)	_May (27)	_Jun (32)	_Jul (61)	_Aug (32)	_Sep (39)	_Oct (45)	_Nov (50)	_Dec (21)
2013:	_Jan (44)	_Feb (26)	_Mar (37)	_Apr (46)	_May (24)	_Jun (5)	_Jul	_Aug	_Sep	_Oct	_Nov	_Dec


S	M	T	W	T	F	S
				1	2	3
				(5)	(19)	(7)
4	5	6	7	8	9	10
(1)	(11)	(3)	(3)		(3)
11	12	13	14	15	16	17
	(3)		(2)		(1)	(5)
18	19	20	21	22	23	24
(2)	(2)	(3)	(5)	(6)	(1)	(3)
25	26	27	28	29	30	31
(4)		(1)

Re: [smartmontools-support] scterc for intel 320

From: Artem Bokhan <aptem@ng...> - 2012-03-05 05:51

On 03.03.2012 03:52, Christian Franke wrote:
> SCT status 0x0016h-0xBEFF are defined as "Reserved" by ATA ACS-2 revision 7.
>
> With the attached patch the bad status is ignored. Please try if possible.
>
./smartctl -l scterc /dev/sdb
smartctl 5.43 2012-02-27 r3515M [x86_64-linux-2.6.32-37-generic] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

Error unexcepted SCT status 0x000a (action_code=3, function_code=2)
Error unexcepted SCT status 0x000a (action_code=3, function_code=2)
SCT Error Recovery Control:
            Read:     10 (1.0 seconds)
           Write:     10 (1.0 seconds)




> Christian
>

Re: [smartmontools-support] scterc for intel 320

From: Christian Franke <Christian.Franke@t-...> - 2012-03-05 06:39

Artem Bokhan wrote:
> On 03.03.2012 03:52, Christian Franke wrote:
>> SCT status 0x0016h-0xBEFF are defined as "Reserved" by ATA ACS-2 
>> revision 7.
>>
>> With the attached patch the bad status is ignored. Please try if 
>> possible.
>>
> ./smartctl -l scterc /dev/sdb
> smartctl 5.43 2012-02-27 r3515M [x86_64-linux-2.6.32-37-generic] 
> (local build)
> Copyright (C) 2002-12 by Bruce Allen, 
> http://smartmontools.sourceforge.net
>
> Error unexcepted SCT status 0x000a (action_code=3, function_code=2)
> Error unexcepted SCT status 0x000a (action_code=3, function_code=2)

ATA-8 ACS rev 6a:
000Ah Invalid Function code in SCT Read/Write Long command

ACS-2 rev 7:
000Ah Obsolete



> SCT Error Recovery Control:
>            Read:     10 (1.0 seconds)
>           Write:     10 (1.0 seconds)
>
>

Do these values make sense?


Thanks,
Christian

Re: [smartmontools-support] scterc for intel 320

From: Artem Bokhan <aptem@ng...> - 2012-03-05 07:49

On 05.03.2012 13:39, Christian Franke wrote:
>> SCT Error Recovery Control:
>>            Read:     10 (1.0 seconds)
>>           Write:     10 (1.0 seconds)
>>
>>
>
> Do these values make sense?
>

I do not know and probably only intel's engineers do know but I do not have 
personal contacts with intel. I do not see any way to check that but I would 
like to get reinsured before production usage.

All information I have is intel's specification.

http://www.intel.com/content/dam/www/public/us/en/documents/product-specifications/ssd-320-specification.pdf

  SMART Command Transport (SCT)
With SMART Command Transport (SCT), a host can send commands and data to an
SSD and receive status and data from an SSD using standard write/read commands to
manipulate two SMART Logs:
• Log Address E0h ("SCT Command/Status") — used to send commands and retrieve
status
• Log Address E1h ("SCT Data Transfer") — used to transport data
The Intel SSD 320 Series supports the following standard SCT actions:
• Write Same — Intel SSD 320 Series implements this action code as described in the
ATA specification.
• Error Recovery Control — Intel SSD 320 Series accepts this action code, and will
store and return error-recovery time limit values.
• Feature Control - Intel SSD 320 Series supports feature code 0001h (write cache)
and feature code 0002h (write cache reordering)

ps. Is it possbile to check which write cache type is set (write cache/write 
cache reordering) with smartmontools?

>
> Thanks,
> Christian
>

Re: [smartmontools-support] scterc for intel 320

From: Christian Franke <Christian.Franke@t-...> - 2012-03-05 18:59

Artem Bokhan wrote:
> On 05.03.2012 13:39, Christian Franke wrote:
>>> SCT Error Recovery Control:
>>>            Read:     10 (1.0 seconds)
>>>           Write:     10 (1.0 seconds)
>>>
>>>
>>
>> Do these values make sense?
>>
>
> I do not know and probably only intel's engineers do know but I do not 
> have personal contacts with intel. I do not see any way to check that 
> but I would like to get reinsured before production usage.
>
> All information I have is intel's specification.
>
> http://www.intel.com/content/dam/www/public/us/en/documents/product-specifications/ssd-320-specification.pdf 
>
> ...
> • Error Recovery Control — Intel SSD 320 Series accepts this action 
> code, and will
> store and return error-recovery time limit values.

This statement does not imply that changing these values has any effect :-)


> • Feature Control - Intel SSD 320 Series supports feature code 0001h 
> (write cache)
> and feature code 0002h (write cache reordering)
>
>
> ps. Is it possbile to check which write cache type is set (write 
> cache/write cache reordering) with smartmontools?

No. Please create a ticket. I'll probably add this when I have more time.

Christian

Re: [smartmontools-support] Bad sector high on disk outside OS partition - how to handle?

From: Whit Blauvelt <whit@tr...> - 2012-03-05 14:55

Just to update the list for the archives and future searchers: The probes
look to be from udisks-daemon, as they start in the boot process immediately
after it is invoked by the discovery of an SD card in my case. It runs under
udev, and is a successor to HAL for monitoring media and such. Once active,
it also repeatedly - at least in the version distributed with Ubuntu 10.04 -
polls all other media, including the sectors of hard drives where GPT would
be, regardless of whether GPT are actually used on those hard drives. 

So when a sector reserved for the secondary GPT became unreadable in my
case, udisks-daemon's polling of the sector (which was the only use that
sector had ever had, so could have led to its failure in the first place)
continued so aggressively as to retard boot by several minutes, and steal
resources from the system after boot. I've filed a bug with Ubuntu. It's not
the only distro using udisks-daemon though.

Whit

[smartmontools-support] scterc for megaraid

From: Artem Bokhan <aptem@ng...> - 2012-03-05 06:00

Alex, some time ago you disabled scterc for megaraid. It was possible to set 
scterc but it was not possbile to read.

May you send a patch which will enable scterc for current version? I will check 
if it really sets scterc for device and how it affects firmware.

Re: [smartmontools-support] scterc for megaraid

From: Alex Samorukov <ml@os...> - 2012-03-05 07:30

On 03/05/2012 06:55 AM, Artem Bokhan wrote:
>
>
> May you send a patch which will enable scterc for current version? I 
> will check if it really sets scterc for device and how it affects 
> firmware.
https://sourceforge.net/apps/trac/smartmontools/browser/trunk/smartmontools/os_linux.cpp#L1057 
and up to 
https://sourceforge.net/apps/trac/smartmontools/browser/trunk/smartmontools/os_linux.cpp#L1067

You can comment this out and this will disable all megaraid quicks.

Re: [smartmontools-support] scterc for megaraid

From: Artem Bokhan <aptem@ng...> - 2012-03-05 09:59

<html>
  <head>
    <meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    On 05.03.2012 14:30, Alex Samorukov wrote:
    <blockquote cite="mid:4F546B99.80506@..." type="cite">On
      03/05/2012 06:55 AM, Artem Bokhan wrote:
      <br>
      <blockquote type="cite">
        <br>
        <br>
        May you send a patch which will enable scterc for current
        version? I will check if it really sets scterc for device and
        how it affects firmware.
        <br>
      </blockquote>
      <a class="moz-txt-link-freetext" href="https://sourceforge.net/apps/trac/smartmontools/browser/trunk/smartmontools/os_linux.cpp#L1057">https://sourceforge.net/apps/trac/smartmontools/browser/trunk/smartmontools/os_linux.cpp#L1057</a>
      and up to
<a class="moz-txt-link-freetext" href="https://sourceforge.net/apps/trac/smartmontools/browser/trunk/smartmontools/os_linux.cpp#L1067">https://sourceforge.net/apps/trac/smartmontools/browser/trunk/smartmontools/os_linux.cpp#L1067</a><br>
      <br>
      You can comment this out and this will disable all megaraid
      quicks.
      <br>
    </blockquote>
    Here are results:<br>
    <br>
    1. Megaraid allow to pass scterc set commands to drive. I set scterc
    with LSI, then attached sata connector from onboard sata controller
    without losing power and checked the value of scterc.<br>
    2. Setting of scterc does not cause "Unexpected sense" errors in FW
    log.<br>
    3. Getting of scterc <b>does</b> cause "Unexpected sense" errors in
    FW log.<br>
    <br>
    Please allow scterc set commands for current version of
    smartmontools.<br>
  </body>
</html>

Re: [smartmontools-support] scterc for megaraid

From: Christian Franke <Christian.Franke@t-...> - 2012-03-05 10:36

Artem Bokhan wrote:
> Here are results:
> 
> 1. Megaraid allow to pass scterc set commands to drive. I set
> scterc     with LSI, then attached sata connector from onboard sata
> controller     without losing power and checked the value of scterc.
> 2. Setting of scterc does not cause "Unexpected sense" errors in FW   
>  log.
> 3. Getting of scterc DOES cause "Unexpected sense" errors in
> FW log.
> 

This is typically a false warning because the kernel/driver/firmware
does not properly interpret the SAT ATA RETURN DESCRIPTOR sense data. It
contains the ATA output register values. This sense data is only
requested for SMART STATUS and for SCT ERC GET.

So the CHK_COND bit check at os_linux.cpp:1057-1061 should be left as
is.

> Please allow scterc set commands for current version of
> smartmontools.
> 

Should IMO only be done if the set command (SMART WRITE LOG) does not
cause serious problems on other affected controllers.

Christian

Re: [smartmontools-support] scterc for megaraid

From: Artem Bokhan <aptem@ng...> - 2012-03-05 11:17

On 05.03.2012 17:35, Christian Franke wrote:
> Artem Bokhan wrote:
>> Here are results:
>>
>> 1. Megaraid allow to pass scterc set commands to drive. I set
>> scterc     with LSI, then attached sata connector from onboard sata
>> controller     without losing power and checked the value of scterc.
>> 2. Setting of scterc does not cause "Unexpected sense" errors in FW  
>>   log.
>> 3. Getting of scterc DOES cause "Unexpected sense" errors in
>> FW log.
>>
> This is typically a false warning because the kernel/driver/firmware
> does not properly interpret the SAT ATA RETURN DESCRIPTOR sense data. It
> contains the ATA output register values. This sense data is only
> requested for SMART STATUS and for SCT ERC GET.
Yes, I meant that sct erc get must be disabled.

>
> So the CHK_COND bit check at os_linux.cpp:1057-1061 should be left as
> is.
>
>
>> Please allow scterc set commands for current version of
>> smartmontools.
>>
> Should IMO only be done if the set command (SMART WRITE LOG) does not
> cause serious problems on other affected controllers.
For 9260/9280 (modern controllers) it does not cause problems. It should ok for 
others too because it does not contain the ATA output register values as I 
understand.


> Christian
>
>
>

Re: [smartmontools-support] SSD Device statistics

From: Artem Bokhan <aptem@ng...> - 2012-03-05 06:21

On 03.03.2012 04:05, Christian Franke wrote:
> smartctl -l directory
./smartctl -l directory /dev/sdb
smartctl 5.43 2012-02-27 r3515M [x86_64-linux-2.6.32-37-generic] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net

General Purpose Log Directory Version 1
SMART           Log Directory Version 1 [multi-sector log support]
GP/S  Log at address 0x00 has    1 sectors [Log Directory]
GP/S  Log at address 0x01 has    1 sectors [Summary SMART error log]
GP/S  Log at address 0x02 has    8 sectors [Comprehensive SMART error log]
GP/S  Log at address 0x03 has    8 sectors [Ext. Comprehensive SMART error log]
GP/S  Log at address 0x04 has    8 sectors [Device Statistics log]
GP/S  Log at address 0x06 has    1 sectors [SMART self-test log]
GP/S  Log at address 0x07 has    1 sectors [Extended self-test log]
GP/S  Log at address 0x09 has    1 sectors [Selective self-test log]
GP/S  Log at address 0x10 has    1 sectors [NCQ Command Error log]
GP/S  Log at address 0x11 has    1 sectors [SATA Phy Event Counters]
GP/S  Log at address 0x80 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x81 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x82 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x83 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x84 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x85 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x86 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x87 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x88 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x89 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8a has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8b has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8c has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8d has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8e has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x8f has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x90 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x91 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x92 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x93 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x94 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x95 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x96 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x97 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x98 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x99 has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9a has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9b has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9c has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9d has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9e has   16 sectors [Host vendor specific log]
GP/S  Log at address 0x9f has   16 sectors [Host vendor specific log]
GP/S  Log at address 0xe0 has    1 sectors [SCT Command/Status]
GP/S  Log at address 0xe1 has    1 sectors [SCT Data Transfer]