Hide Forgot
Description of problem: on shutdown of laptop (lenovo g780) the following messages hit the screen multiple times: - 1. Kernel not configured for semaphores (System V IPC). Not using udev synchronisation code. - 2. device-mapper: remove ioctl of fedora-root failed: Device or resource busy Command failed" This seems to be a newly introduced error with fedora 25. I did a fresh install and i got it, but another user got in with an upgrade ( as reported in https://www.reddit.com/r/Fedora/comments/5gt2lj/getting_error_messages_on_bootshutdown_after/ ). This is my sysinfo ( fpaste --sysinfo ) : https://paste.fedoraproject.org/501379/15904014/ according to https://bugzilla.redhat.com/show_bug.cgi?id=1305831#c25 there is already a bug report for the first message: https://bugzilla.redhat.com/show_bug.cgi?id=1385432 In https://bugzilla.redhat.com/show_bug.cgi?id=1305831#c27 a new dracut bug report was requested for the second part of the message. Quote: "The systemd/dracut shutdown hook is trying to deactivate a device which is still in use (not an LVM/device-mapper issue)." "That would be "dracut" component I suppose (if not, they will change to proper component surely)."
Still valid for Fedora 26. Can't find the lines that appear on shutdown from journalctl, though. I scrolled through everything.
Still valid for Fedora 27.
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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.
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.