Bug 1286403 - filesystem.device appeared twice with different sysfs paths
filesystem.device appeared twice with different sysfs paths
Product: Fedora
Classification: Fedora
Component: systemd (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: systemd-maint
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-11-28 22:45 EST by George R. Goffe
Modified: 2016-07-19 15:23 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-07-19 15:23:10 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
tar.gz file containing two log files, /var/log/messages and konsole log (130.09 KB, application/x-gzip)
2015-11-28 22:45 EST, George R. Goffe
no flags Details

  None (edit)
Description George R. Goffe 2015-11-28 22:45:48 EST
Created attachment 1100085 [details]
tar.gz file containing two log files, /var/log/messages and konsole log

Description of problem:

Powering up one of 5 docking stations for external hard drives, one caused messages from systemd complaining about invalid sysfs disk entries. Additionally, e2fsck -f /dev/sdd1 claimed that there was no such file or device"

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


How reproducible:

poweroff poweron of said docking station produced the same error messages

Steps to Reproduce:

Actual results:

see log files included in this bug

Expected results:

Additional info:
Comment 1 Fedora End Of Life 2016-07-19 15:23:10 EDT
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.