Bug 2270209
| Summary: | Firmware RAID set not usable in anaconda when booting native UEFI: "ERROR:blivet:failed to determine name for the md array a7ff7f19-f142-4329-6b52-1dbafa835906" | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Williamson <awilliam> | ||||
| Component: | python-blivet | Assignee: | Vojtech Trefny <vtrefny> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 40 | CC: | blivet-maint-list, dlehman, japokorn, kparal, mkolman, neil, robatino, rvykydal, vponcova, vtrefny | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | RejectedBlocker | ||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2025-05-16 07: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
Adam Williamson
2024-03-19 01:20:12 UTC
Gonna propose as a Final blocker for discussion, though I might well ultimately be -1 to it. Also as Beta FE just in case. It would be good if folks can test firmware RAID on UEFI on other systems to see if this is a general issue or specific to my motherboard and/or RAID set. Created attachment 2022398 [details]
full journal
It looks like this affects Fedora 39 Final as well, so it's not a 40 regression. We signed off Beta today, so there's no point in Beta FE status any more. Clearing that nomination. Discussed at 2024-03-25 blocker review meeting: https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-03-25/f40-blocker-review.2024-03-25-16.00.html . We agreed to delay the decision on this as it's hard to tell how hardware-specific it is. We will try to test on more hardware, but also Vojtech, if you have any idea how widespread the effect of this is likely to be it would help with the blocker decision. Discussed at the 2024-04-01 blocker review meeting: https://meetbot-raw.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-04-01/f40-blocker-review.2024-04-01-16.01.html . We agreed to punt on this issue as the scope is not clear due to insufficient information required to make an informed decision. It was agreed that testing on more hardware would be very valuable to identifying the source of this regression. If anyone can test the available Beta artifacts against a system which uses Firmware raid (i.e., RAID implemented and supported by the motherboard, not by Software (e.g. mdraid) nor Hardware (external cards), it would be very welcome. I've tested F40 Beta on a firmware RAID in UEFI mode yesterday on Gigabyte GA-Z170M-D3H (Skylake-S). It worked fine. So this is probably hardware specific. -4 in https://pagure.io/fedora-qa/blocker-review/issue/1533 , marking rejected. Adam, I just tested the same hardware from comment 7 again in BIOS mode, and found out that I don't see any RAID devices! The error was the same "failed to determine name for the md array". In lsblk --fs, I saw /dev/sda and /dev/sdb as isw_raid_member, but there were no md* devices underneath them. However, I found a solution, for my case. I had to go to BIOS and switch Storage Boot Option Control from UEFI to Legacy. Then the RAID started to be available in BIOS mode (and continued to be available in UEFI as well). So quite possibly if you tinker with your BIOS options, you might be able to convince it to run under UEFI as well (or at least switch it from BIOS mode to UEFI mode). This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. 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 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed. Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed. |