Bug 1064323
| Summary: | partial devices showing up until dmraid-activation.service is restarted | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | chris |
| Component: | dmraid | Assignee: | LVM and device-mapper development team <lvm-team> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 22 | CC: | agk, anaconda-maint-list, bmr, chris, dwysocha, g.kaviyarasu, heinzm, jbrassow, jonathan, lvm-team, prajnoha, prockai, vanmeeuwen+fedora, zkabelac |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-07-19 10:59:35 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
chris
2014-02-12 12:31:35 UTC
Could you please send the output of "lsblk" and "udevadm info --export-db" for both working and non-working case? Thanks. + the output of "systemctl status dmraid-activation.service" for both working and non-working case. I was able to reproduce it after some reboots. I hope I got all the information you need. I also added two screenshots of nautilus to show what i mean. Maybe i should add, that I use this computer also with windows7 dualboot. And actually it seems like this problem only appears if i write to the software raid in windows and then restart and boot linux. at least that was the case the last three times. the software raid has a ntfs filesystem and is only a data storage for windows and fedora, so no root filesystem. Created attachment 862476 [details]
screenshot of the problem in nautilus
Created attachment 862477 [details]
screenshot of nautilus after restarting the dmraid service
Created attachment 862478 [details]
lsblk when everything is ok
Created attachment 862479 [details]
systemctl when everything is ok
Created attachment 862480 [details]
udevadm when everything is ok
Created attachment 862481 [details]
lsblk when the problem occurs
Created attachment 862482 [details]
systemctl when the problem occurs
Created attachment 862483 [details]
udevadm when the problem occurs
the bug is still there in fedora 22. Now, I can't even resolve it with restarting the service. and it is now on every reboot Created attachment 1032485 [details]
errors in journalctl
But now I have at least error entries in the log.
I do not see any evidence to indicate that this is an installation issue. It appears that the installation went successfully, but the installed system is not starting the dmraid services correctly. Reassigning back to dmraid. (In reply to chris from comment #0) > Description of problem: > I have 2 discs combined to a mirrored software raid by a gigabyte mainboard. > Usually there is no problem with this raid. But sometimes after login i can > see > the raid volume plus the two separate discs it consists of e.g. in nautilus. > after restarting the dmraid-activation.service they disappear and everything > is as expected. Do you have access problems to the raid when you see the component devices in Nautilus or does it just work fine? If it works fine, this may be a confusing filter issue exposed by Nautilus showing the component devices when it should not. > > Version-Release number of selected component (if applicable): > dmraid.x86_64 version 1.0.0.rc16 23.fc20 > > How reproducible: > I don't know. it seems random. I don't use Linux/Fedora any longer on that computer. But if i recall correctly, there were no access problems when selecting the correct shortcut for the raid. I have no idea what would have happened if i had accessed one of the single hard drives and changed some files. 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 bug. Thank you for reporting this bug and we are sorry it could not be fixed. |