Bug 706782 - smartd can't handle two /dev/sgX devices provided by mptsas controller
Summary: smartd can't handle two /dev/sgX devices provided by mptsas controller
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: smartmontools
Version: 5.6
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Michal Hlavinka
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-23 00:10 UTC by harald kapper
Modified: 2013-01-08 07:21 UTC (History)
3 users (show)

Fixed In Version: smartmontools-5.42-1.el5
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-01-08 07:21:29 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0041 0 normal SHIPPED_LIVE smartmontools bug fix and enhancement update 2013-01-07 15:28:22 UTC

Description harald kapper 2011-05-23 00:10:36 UTC
Description of problem:
smartmontools to be used to handle multiple sas/sata HDDs connected through (IBM calls it) a LSI-Basic-RAID-Controller (eg. LSI 1064E) the mptsas exposes the discs through /dev/sg0, /dev/sg1 ... in order to handle these eg. using smartmontools - running smartd on any one _single_ /dev/sgX works fine, also smartctl works with any disc, but as soon as /etc/smartd.conf contains multiple /dev/sgX entries all but the very last entry fail and get logged with errors.
workaround: we configured multiple smartd startupscripts and config-files specifying only one disc per startupscript and running daemon works, but it's quite an awfull solution.

Version-Release number of selected component (if applicable):
5.38-2.el5

How reproducible:
use eg. IBM x3250 servers with LSI-BASIC-Controller (BR10il on LSI1064E) configure smartd to use /dev/sg0 and /dev/sg1 (if you have two discs in the raid) - look into /var/log/messages after restarting service smartd

Steps to Reproduce:
1. edit /etc/smartd.conf
2. restart /etc/init.d/smartd
3. tail -f /var/log/messages
  
Actual results:
Device: /dev/sg0, not capable of SMART self-check

Expected results:
Device: /dev/sg0, is SMART capable. Adding to "monitor" list.

Additional info:

Comment 1 Michal Hlavinka 2011-05-23 09:13:37 UTC
Thanks for reporting this. To make this bug report more useful, please add following information:

1) output of 
lspci -nn

2) what do you have in /etc/smartd.conf

3) does it work for you with smartcl -a .... ? What options are you using?

Comment 2 harald kapper 2011-05-30 23:07:41 UTC
lspci -nn says:


[root@k72 ~]# lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Core Processor DMI [8086:d130] (rev 11)
00:03.0 PCI bridge [0604]: Intel Corporation Core Processor PCI Express Root Port 1 [8086:d138] (rev 11)
00:05.0 PCI bridge [0604]: Intel Corporation Core Processor PCI Express Root Port 3 [8086:d13a] (rev 11)
00:08.0 System peripheral [0880]: Intel Corporation Core Processor System Management Registers [8086:d155] (rev 11)
00:08.1 System peripheral [0880]: Intel Corporation Core Processor Semaphore and Scratchpad Registers [8086:d156] (rev 11)
00:08.2 System peripheral [0880]: Intel Corporation Core Processor System Control and Status Registers [8086:d157] (rev 11)
00:08.3 System peripheral [0880]: Intel Corporation Core Processor Miscellaneous Registers [8086:d158] (rev 11)
00:10.0 System peripheral [0880]: Intel Corporation Core Processor QPI Link [8086:d150] (rev 11)
00:10.1 System peripheral [0880]: Intel Corporation Core Processor QPI Routing and Protocol Registers [8086:d151] (rev 11)
00:1a.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 05)
00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 05)
00:1c.4 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 [8086:3b4a] (rev 05)
00:1c.5 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6 [8086:3b4c] (rev 05)
00:1c.6 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 7 [8086:3b4e] (rev 05)
00:1c.7 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 8 [8086:3b50] (rev 05)
00:1d.0 USB Controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b34] (rev 05)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev a5)
00:1f.0 ISA bridge [0601]: Intel Corporation 3400 Series Chipset LPC Interface Controller [8086:3b14] (rev 05)
00:1f.2 IDE interface [0101]: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA IDE Controller [8086:3b20] (rev 05)
00:1f.3 SMBus [0c05]: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller [8086:3b30] (rev 05)
00:1f.5 IDE interface [0101]: Intel Corporation 5 Series/3400 Series Chipset 2 port SATA IDE Controller [8086:3b26] (rev 05)
01:00.0 SCSI storage controller [0100]: LSI Logic / Symbios Logic SAS1064ET PCI-Express Fusion-MPT SAS [1000:0056] (rev 08)
06:00.0 PCI bridge [0604]: Vitesse Semiconductor VSC452 [SuperBMC] [101b:0452] (rev 01)
07:00.0 VGA compatible controller [0300]: Matrox Graphics, Inc. MGA G200EV [102b:0530]
0b:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network Connection [8086:10d3]
15:00.0 Ethernet controller [0200]: Intel Corporation 82574L Gigabit Network Connection [8086:10d3]

-----------

smartd.conf (working) contains:

/dev/sg0 -a -d sat -l error -l selftest -W 4,45,55 -m root

not-working:
/dev/sg0 -a -d sat -l error -l selftest -W 4,45,55 -m root
/dev/sg1 -a -d sat -l error -l selftest -W 4,45,55 -m root

-------------

smartctl -a /dev/sg0 and smartctl -a /dev/sg1 works fine.

regards
hk

Comment 3 RHEL Program Management 2011-09-23 00:54:32 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 4 RHEL Program Management 2012-04-02 10:52:00 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release.  Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products.  This request is not yet committed for inclusion in
a release.

Comment 10 errata-xmlrpc 2013-01-08 07:21:29 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0041.html


Note You need to log in before you can comment on or make changes to this bug.