Bug 2144409

Summary: SSD's Error Information Log Entries keep increasing with every reboot
Product: Red Hat Enterprise Linux 8 Reporter: GV <rhel>
Component: smartmontoolsAssignee: Michal Hlavinka <mhlavink>
Status: CLOSED MIGRATED QA Contact: CS System Management SST QE <rhel-cs-system-management-subsystem-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.7Keywords: MigratedToJIRA
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-09-22 03:23:38 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:
Embargoed:
Attachments:
Description Flags
smartctl -a
none
nvme error-log output
none
nvme smart-log output none

Description GV 2022-11-21 08:14:59 UTC 
Created attachment 1926043 [details]
smartctl -a

Starting with RHEL 8.6 I see "Error Information Log Entries" for a NVME Seagate FireCuda 530 ZP2000GM30013 SSD listed by smartctl increasing with every reboot. The SSD have the latest firmware. The other two SSDs does not have this issue (Intel).

It's seems to be tha same issue reported here:
https://forum.proxmox.com/threads/pve-7-1-new-smart-error-on-every-hard-disk-at-every-reboot.101063/

Can you fix this issue? Thank you!
Comment 1 GV 2022-11-21 08:15:43 UTC 
Created attachment 1926044 [details]
nvme error-log output
Comment 2 GV 2022-11-21 08:16:07 UTC 
Created attachment 1926046 [details]
nvme smart-log output
Comment 3 Jeff Moyer 2022-11-21 14:23:17 UTC 
This appears to be a smartmontools issue:
  https://www.smartmontools.org/ticket/1222
Comment 4 RHEL Program Management 2023-09-22 03:20:24 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 5 RHEL Program Management 2023-09-22 03:23:38 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.