Bug 1371595

Summary: [RHEL 7.3] /var/log/messages shows Error messages related to udisksd
Product: Red Hat Enterprise Linux 7 Reporter: Nanda Kishore Chinnaram <nanda_kishore_chinna>
Component: libatasmartAssignee: Lennart Poettering <lpoetter>
Status: CLOSED DUPLICATE QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.3CC: kasmith, linux-bugs, narendra_k, prabhakar_pujeri
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-31 02:16:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
messages none

Description Nanda Kishore Chinnaram 2016-08-30 15:02:08 UTC 
Description of problem:
After installing and booting into RHEL-7.3 Beta-1 we are seeing below error messages related to udisksd on R630 with Intel SSD Drives:-

" Aug 9 05:28:16 localhost udisksd[5705]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/INTEL_SSDSC2BB120G6R_PHWA62120160120CGN: Error updating SMART data: sk_disk_check_sleep_mode: Input/output error (udisks-error-quark, 0) " 

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


How reproducible:
Always

Steps to Reproduce:
1. Install RHEL 7.3 Beta-1 on R630 with Intel SSD Drives.
2.Boot into OS and check the /var/log/messages
3.Observe that there are error messages related to udisksd

Actual results:
Error messages are shown related to udisksd.

Expected results:
There should not be any Error messages.

Additional info:
There is already a BUG raised #1301824 for RHEL 7.2.
Comment 1 Nanda Kishore Chinnaram 2016-08-30 15:08:29 UTC 
Created attachment 1195954 [details]
messages
Comment 3 Karl Hastings 2016-08-31 02:16:21 UTC 
Closing this one as a duplicate of BZ #1301824.  Let's continue to work the issue there.

*** This bug has been marked as a duplicate of bug 1301824 ***