Bug 1599966
| Summary: | Failure to boot following upgrade to fedora 28 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | James Paterson <jp> | ||||
| Component: | dracut | Assignee: | dracut-maint-list | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 28 | CC: | cheese, dracut-maint-list, harald, jonathan, jp, msuchy, zbyszek | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2019-05-28 22:06:31 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: |
|
||||||
Does it work with: rd.md.uuid=32ef2172-f056-6fa7-66a8-2f7fcf8b1798 ?? With both uuid's changed: rd.md.uuid=945c987c-b60d-ffe7-94f8-52aa109376dd rd.md.uuid=32ef2172-f056-6fa7-66a8-2f7fcf8b1798 fix for /lib/dracut/modules.d/90mdraid/parse-md.sh : https://github.com/dracutdevs/dracut/commit/99df3d22be14690260371311086a439c83fdc6b4 Apologies for the delay - I was out of town and could not access the console. I have changed the uuids to use "-" rather than ":" in grub.cfg. Rebooting the system again results in the drop to emergency shell with the notifications: Warning: /dev/disk/by-id/md-uuid-32ef2172-f056-6fa7-66a8-2f7fcf8b1798 does not exist Warning: /dev/disk/by-id/md-uuid-945c987c-b60dffe7-94f852aa-109376dd does not exist Checking in the by-id folder shows only one md-uuid disk: md-uuid-32ef2712:f0566fa7:66a82f7f:cf8b1798 changing the first UUID in the grub.cfg file to match the UUID in the "by-id" folder removes the first warning, but not the second. I noted that there was only one RAID personality recognized in emergency shell (md127), but in the dev folder and in /proc/mdstat. When booting to the working fedora 24 kernel, both md126 and md127 are recognized. Is there another place that I should be changing the uuid? maybe in the initramfs? This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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. |
Created attachment 1457983 [details] rdsosreport from reboot Description of problem: Upgrading from Fedora 24 to Fedora 28. Following upgrade, booting into OS from fails in dracut after ~ 5mins dropping to emergency shell with warning that /dev/disk/by-id/md-uuid-32ef2172:f056:6fa7:66a8:2f7fc8b1798 does not exist. However, the UUID is detected in the startup sequence (exists in the rdsosreport) booting with previous kernel (fedora 24) and initramfs succeeds. Examining the logs seems to show that neither the /boot (raid0) nor /home (LVM on raid0) are properly detected and brought up, but the / is detected (LVM on raid0, same PV and VG as /home). Configuration of the system: sd[ab]1 -> raid0 -> /boot sd[ab]2 -> swap sd[ab]3 -> raid0 -> LVM PV -> VG -> / and /home Version-Release number of selected component (if applicable): fully updated F28 How reproducible: only on upgrade with LVM on raid for one server (only one going through this process) so I don't know how reproducible. I have seen similar reports involving md arrays and LVM2. Steps to Reproduce: 1. upgrade from F24 to F28 with LVM on Raid 2. reboot, reboot fails 3. Actual results: Drop into dracut on reboot Expected results: Boot into OS Additional info: I have attempted a few modifications to the config files and rebuilding the initramfs, but without success.