RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1410233 - smartd trying to poll SCSI devices in ALUA stand-by state and indicates hard drive failing
Summary: smartd trying to poll SCSI devices in ALUA stand-by state and indicates hard ...
Keywords:
Status: CLOSED DUPLICATE of bug 1340462
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: smartmontools
Version: 7.3
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Michal Hlavinka
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-01-04 20:51 UTC by shivamerla1
Modified: 2017-03-26 17:20 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-26 17:20:12 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description shivamerla1 2017-01-04 20:51:18 UTC 
Description of problem:
smartd seems to poll SCSI devices in ALUA stand-by state and throws error saying hard drive is failing. Any read/write/Test Unit Ready commands on SCSI devices in TPG stand-by state will cause "NOT_READY, LOGICAL UNIT NOT ACCESSIBLE, TARGET PORT IN STANDBY STATE ( 2/4/b )" check condition. smartd should handle these errors and ignore them rather than alerting user that hard drive is failing.

Version-Release number of selected component (if applicable):
smartmontools

How reproducible:
consistently

Steps to Reproduce:
1. Map certain SCSI devices from storage array with both active/stand-by ALUA paths.
2. smartd starts throwing these errors on scan.


Actual results:
root@rtp-fuji-ops17 ~]# WARNING: Your hard drive is failing
Device: /dev/sdah, unable to open device
WARNING: Your hard drive is failing
Device: /dev/sdai, unable to open device
WARNING: Your hard drive is failing
Device: /dev/sdaj, unable to open device
WARNING: Your hard drive is failing
Device: /dev/sdak, unable to open device
WARNING: Your hard drive is failing
Device: /dev/sdal, unable to open device
WARNING: Your hard drive is failing
Device: /dev/sdam, unable to open device
WARNING: Your hard drive is failing
Device: /dev/sdan, unable to open device
WARNING: Your hard drive is failing
Device: /dev/sdao, unable to open device
WARNING: Your hard drive is failing
Device: /dev/sdap, unable to open device

Expected results:
smartd should not try to scan stand-by paths.

Additional info:
Comment 2 Michal Hlavinka 2017-03-26 17:20:12 UTC 
Closing as duplicate of bug #1340462, as that bug is not publicly visible. Here is what is going to change in next smartmontools update in rhel-7 (don't treat this as any guarantee, the process to fix this bug is ongoing, but many things can happen and it can be dropped from next release update)

Smartmontools daemon smartd was updated:
- "WARNING: Your hard drive is failing" message prefix was changed and it uses prefix "SMART Disk monitor:" now
- some less important messages (like can't talk with a disk - which can be caused by power saving mode) are no longer reported in terminals

Urgent messages, like some attribute indicating disk failure, are still reported (with the less scary message prefix)

All mail messages are still sent as configured

All messages are logged in syslog (journal). This includes messages like "can't read SMART values". This message is (and was) logged with INFO syslog priority. If you don't want to see info messages, but only important ones, use --priority options (man journalctl). For example
$ journalctl --priority=crit

*** This bug has been marked as a duplicate of bug 1340462 ***
Note You need to log in before you can comment on or make changes to this bug.