Bug 2131852
Summary: | iso-scan boot no longer works in F37 image | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Petr Menšík <pemensik> | ||||
Component: | dracut | Assignee: | dracut-maint-list | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 37 | CC: | awilliam, bob, dracut-maint-list, fgrose, jamacku, jonathan, knossos456, laszlo.gombos, lnykryn, matthias, pvalena | ||||
Target Milestone: | --- | Keywords: | Regression | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | AcceptedFreezeException | ||||||
Fixed In Version: | dracut-059-14.fc39 | Doc Type: | If docs needed, set a value | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2023-10-09 22:25:45 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: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 2143447 | ||||||
Attachments: |
|
Description
Petr Menšík
2022-10-03 22:44:39 UTC
# find /dev/disk /dev/disk /dev/disk/by-uuid /dev/disk/by-uuid/B2EC-4779 /dev/disk/by-uuid/D025-5080 /dev/disk/by-label /dev/disk/by-label/PhhEFI-boot /dev/disk/by-label/PhhData /dev/disk/by-partuuid /dev/disk/by-partuuid/29611640-f0a1-4559-8025-f8cfeadcfce1 /dev/disk/by-partuuid/ccad76b3-4f9a-4758-a772-6f045ded28b1 /dev/disk/by-partuuid/3b19ea75-f92d-49e4-a6e0-72983fd89a39 /dev/disk/by-partlabel /dev/disk/by-partlabel/EFI\x20system\x20partition /dev/disk/by-partlabel/PhhName /dev/disk/by-partlabel/BIOS\x20boot\x20partition /dev/disk/by-id /dev/disk/by-id/usb-Kingston_DataTraveler_3.0_408D5CE57214E44179A85CBF-0:0-part1 /dev/disk/by-id/usb-Kingston_DataTraveler_3.0_408D5CE57214E44179A85CBF-0:0-part3 /dev/disk/by-id/usb-Kingston_DataTraveler_3.0_408D5CE57214E44179A85CBF-0:0-part2 /dev/disk/by-id/usb-Kingston_DataTraveler_3.0_408D5CE57214E44179A85CBF-0:0 /dev/disk/by-diskseq /dev/disk/by-diskseq/2 /dev/disk/by-diskseq/1 /dev/disk/by-path /dev/disk/by-path/pci-0000:02:00.0-usb-0:1:1.0-scsi-0:0:0:0-part3 /dev/disk/by-path/pci-0000:02:00.0-usb-0:1:1.0-scsi-0:0:0:0-part1 /dev/disk/by-path/pci-0000:02:00.0-usb-0:1:1.0-scsi-0:0:0:0-part2 /dev/disk/by-path/pci-0000:02:00.0-usb-0:1:1.0-scsi-0:0:0:0 Created attachment 1915845 [details]
rdsosreport
Hmm, interesting. In F36 image by-label device is present, unlike in F37. Not sure what is the difference. $ tree /dev/disk /dev/disk ├── by-id │ ├── dm-name-live-base -> ../../dm-1 │ ├── dm-name-live-rw -> ../../dm-0 │ ├── usb-Kingston_DataTraveler_3.0_408D5CE57214E44179A85CBF-0:0 -> ../../sda │ ├── usb-Kingston_DataTraveler_3.0_408D5CE57214E44179A85CBF-0:0-part1 -> ../../sda1 │ ├── usb-Kingston_DataTraveler_3.0_408D5CE57214E44179A85CBF-0:0-part2 -> ../../sda2 │ └── usb-Kingston_DataTraveler_3.0_408D5CE57214E44179A85CBF-0:0-part3 -> ../../sda3 ├── by-label │ ├── Anaconda -> ../../dm-0 │ ├── Fedora-WS-Live-36-1-5 -> ../../loop0 │ ├── PhhData -> ../../sda1 │ └── PhhEFI-boot -> ../../sda3 ├── by-partlabel │ ├── BIOS\x20boot\x20partition -> ../../sda2 │ ├── EFI\x20system\x20partition -> ../../sda3 │ └── PhhName -> ../../sda1 ├── by-partuuid │ ├── 29611640-f0a1-4559-8025-f8cfeadcfce1 -> ../../sda1 │ ├── 3b19ea75-f92d-49e4-a6e0-72983fd89a39 -> ../../sda2 │ └── ccad76b3-4f9a-4758-a772-6f045ded28b1 -> ../../sda3 ├── by-path │ ├── pci-0000:02:00.0-usb-0:1:1.0-scsi-0:0:0:0 -> ../../sda │ ├── pci-0000:02:00.0-usb-0:1:1.0-scsi-0:0:0:0-part1 -> ../../sda1 │ ├── pci-0000:02:00.0-usb-0:1:1.0-scsi-0:0:0:0-part2 -> ../../sda2 │ └── pci-0000:02:00.0-usb-0:1:1.0-scsi-0:0:0:0-part3 -> ../../sda3 └── by-uuid ├── 2022-05-04-21-36-58-00 -> ../../loop0 ├── 626a3537-c047-4e1d-b6ad-a10855a3b5f9 -> ../../dm-1 ├── B2EC-4779 -> ../../sda3 └── D025-5080 -> ../../sda1 $ ls /run/initramfs/ -l total 34 drwxr-xr-x. 5 root root 32768 Dec 31 1969 isoscan lrwxrwxrwx. 1 root root 27 Oct 3 19:09 isoscandev -> /dev/disk/by-uuid/D025-5080 drwxr-xr-x. 1 root root 2048 May 4 17:36 live lrwxrwxrwx. 1 root root 40 Oct 3 19:09 livedev -> /dev/disk/by-label/Fedora-WS-Live-36-1-5 drwxr-xr-x. 3 root root 60 Oct 3 19:09 log drwxr-xr-x. 2 root root 40 Oct 3 19:09 squashfs drwxr-xr-x. 2 root root 40 Oct 3 19:09 url-lib Anyway, if you know more appropriate component for this issue, please move it to the right component. This menuentry booted fine for me: menuentry 'Live Fedora 37 Beta' --class fedora --class gnu-linux --class gnu --class os { insmod part_gpt insmod btrfs set root='hd1,gpt4' set isolabel=Fedora-WS-Live-37_B-1-5 set isofile=Fedora-Workstation-Live-x86_64-37_Beta-1.5.iso loopback loop ($root)/$isofile linux (loop)/images/pxeboot/vmlinuz iso-scan/filename=$isofile root=live:LABEL=$isolabel ro rd.live.image rd.live.debug initrd (loop)/images/pxeboot/initrd.img } I've just stumbled over what appears to be the same issue. It seems like iso-scan.sh is racing with udev(?) to access block devices before they've been populated. Testing with QEMU I find that an image only semi-reliably boots from a SATA device and I've yet to observe it boot successfully from a USB device. In both cases, upping the debug logging makes successful boots possible/more reliable *** Bug 2181989 has been marked as a duplicate of this bug. *** FEDORA-2023-a93b472cd3 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-a93b472cd3 FEDORA-2023-c10e6a6049 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-c10e6a6049 FEDORA-2023-f71507e281 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-f71507e281 FEDORA-2023-f71507e281 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-f71507e281` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-f71507e281 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-a93b472cd3 has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-a93b472cd3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-a93b472cd3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-c10e6a6049 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-c10e6a6049` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-c10e6a6049 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. I can confirm that the fix worked for me on Fedora 37, 38 & 39 Beta (all affected). Since the Fedora 37 & 38 live iso files will most probably never be updated, I created a quick and dirty shell script that can be used/adapted to locally "re-spin" them: https://gist.github.com/thias/22efc28196e26fa5ce7fecfc04e189f2 +6 in https://pagure.io/fedora-qa/blocker-review/issue/1382 , marking accepted FE. Note, we do have semi-unofficial respins for the latest release at https://dl.fedoraproject.org/pub/alt/live-respins/ , so the next respins after the F38 update is pushed stable should have this fix. BTW, Matthias, could you give the updates positive karma if you tested them? That'll help us get them pushed out. thanks. FEDORA-2023-c10e6a6049 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-f71507e281 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-a93b472cd3 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. |