Hide Forgot
Created attachment 1196245 [details] excerpt from /var/log/messages that contains relevant log entries Description of problem: smartd is issuing a false "Drive is Failing" error to all consoles and to /var/log messages after a SATA hotswap event. I am using a pair of SATA drives for rotating backup media. My PC case has a hotswappable SATA bay on top. I plug in the volume named "Backup-01", which the system auto-mounts. I perform a backup. I unmount the drive using the umount command, and verify that the drive has been unmounted. Then I plug in the volume named "Backup-02" to perform a redundant backup. Everything proceeds as expected, but during the backup to the second volume, the console and messages file are populated with the following false alarm: WARNING: Your hard drive is failing Device: /dev/sde [SAT], unable to open device The system had initially mounted the "Backup-01" volume on SATA6 as /dev/sde1. The system subsequently mounted the "Backup-02" volume on SATA6 as /dev/sdf1. The system was smart enough to catch the hotplug event, check the drive serial numbers, verify that the drive had been changed, and proceeded to mount the drive using a new device map to /dev/sdf instead of /dev/sde. All operations proceed as normal until smartd, which is apparently unaware of the drive swap, looks for /dev/sde which is no longer present, and issues the drive is failing false alarm. The smartd errors are not triggered immediately. They can take quite some time to occur. Version-Release number of selected component (if applicable): F24 How reproducible: Always Steps to Reproduce: 1. Hot-Swap SATA drives using the same SATA channel for both. 2. Begin using second drive 3. Smartd will eventually give a false alarm that the drive that was removed has failed. Actual results: Smartd issues false alarm for failing drive. Expected results: Smartd should be aware that hot-swaps have occurred. Additional info:
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.