Bug 886685
| Summary: | grub2 fails to boot when /boot partition is lvm on multipath device | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gustavo Luiz Duarte <gustavold> | ||||
| Component: | grub2 | Assignee: | Peter Jones <pjones> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 18 | CC: | awilliam, bcl, dcantrell, dennis, gustavold, karsten, mads, pfsmorigo, pjones | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | ppc64 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | RejectedNTH | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-01-12 01:22:19 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
Gustavo Luiz Duarte
2012-12-12 21:22:35 UTC
GRUB didn't added the booted device in the device list. I managed to add it (using ls with the device path) and boot:
Welcome to GRUB!
error: disk `lvm/fedora_tripaseca--12-boot' not found.
Entering rescue mode...
grub rescue> ls /
grub rescue>
grub rescue>
error: disk `lvm/fedora_tripaseca--12-boot' not found.
grub rescue> ls
(ieee1275//vdevice/v-scsi@30000002/disk@8200000000000000) (ieee1275//vdevice/v-s
csi@30000002/disk@8200000000000000,msdos1) (ieee1275//vdevice/v-scsi@30000002/di
sk@8300000000000000) (ieee1275//vdevice/v-scsi@30000002/disk@8300000000000000,ms
dos1)
grub rescue>
grub rescue> ls (ieee1275//vdevice/vfc-client@30000005/disk@20340080e52e9d74)/
error: unknown filesystem.
grub rescue>
grub rescue> ls /
./ ../ lost+found/ grub2/ initrd-plymouth.img .vmlinuz-3.6.9-4.fc18.ppc64p7.hmac
System.map-3.6.9-4.fc18.ppc64p7 config-3.6.9-4.fc18.ppc64p7 vmlinuz-3.6.9-4.fc1
8.ppc64p7 initramfs-3.6.9-4.fc18.ppc64p7.img
grub rescue>
grub rescue> ls
(lvm/fedora_tripaseca--12-boot) (lvm/fedora_tripaseca--12-root) (ieee1275//vdevi
ce/vfc-client@30000005/disk@20340080e52e9d74) (ieee1275//vdevice/vfc-client@3000
0005/disk@20340080e52e9d74,msdos5) (ieee1275//vdevice/vfc-client@30000005/disk@2
0340080e52e9d74,msdos3) (ieee1275//vdevice/vfc-client@30000005/disk@20340080e52e
9d74,msdos2) (ieee1275//vdevice/vfc-client@30000005/disk@20340080e52e9d74,msdos1
) (ieee1275//vdevice/v-scsi@30000002/disk@8200000000000000) (ieee1275//vdevice/v
-scsi@30000002/disk@8200000000000000,msdos1) (ieee1275//vdevice/v-scsi@30000002/
disk@8300000000000000) (ieee1275//vdevice/v-scsi@30000002/disk@8300000000000000,
msdos1)
grub rescue>
grub rescue> insmod normal
grub rescue> normal
GNU GRUB version 2.00
+--------------------------------------------------------------------------+
|Fedora |
|Advanced options for Fedora |
...
Created attachment 663725 [details]
This patch adds the bootpath to the device list
grub2-2.00-15.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/grub2-2.00-15.fc18 Package grub2-2.00-15.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing grub2-2.00-15.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-20739/grub2-2.00-15.fc18 then log in and leave karma (feedback). Discussed at 2013-01-07 QA meeting acting as an NTH review meeting: http://meetbot.fedoraproject.org/fedora-meeting/2013-01-07/fedora-qa.2013-01-07-16.01.log.txt . As we understand it, this bug only hits when the following factors are in place: * OpenFirmware-based system * /boot on LVM on multipath storage device That seems like too rare a combination to block release. In particular, in practice, OpenFirmware is almost never used on machines based on our primary architectures: this is effectively a ppc64 bug. ppc64 is a secondary arch and isn't committed to the package set frozen for primary arch release, we could pull the fixed grub2 into the ppc64 secondary arch release without pulling it into the PA releases. On that basis, this is rejected as NTH. grub2-2.00-15.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |