| Summary: | "boot loader install failed" during install on FC disk with kickstart parameter "--ondisk=/dev/disk/by-id/xxxx" | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-node | Reporter: | Wei Wang <weiwang> | ||||||||
| Component: | Installation & Update | Assignee: | Fabian Deutsch <fdeutsch> | ||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Wei Wang <weiwang> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | high | ||||||||||
| Version: | 4.0 | CC: | bugs, cshao, fdeutsch, huiwa, huzhao, leiwang, vpodzime, weiwang, yaniwang, ycui | ||||||||
| Target Milestone: | --- | Flags: | rule-engine:
planning_ack?
rule-engine: devel_ack? cshao: testing_ack+ |
||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2016-05-31 09:49:03 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | Node | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
Please attach logs and/or a screenshot Created attachment 1153329 [details]
bootloader_failed
Since the issue occur during installation, so cannot get logs.
You can switch to another terminal to get the logs. Created attachment 1153356 [details]
log files
In program.log: 10:15:40,884 INFO program: Running... grub2-install --no-floppy /dev/sda 10:15:42,240 INFO program: Installing for i386-pc platform. 10:15:42,241 INFO program: grub2-install: error: unable to identify a filesystem in hd0; safety check can't be performed. 10:15:42,241 DEBUG program: Return code: 1 10:15:42,243 INFO program: Running... grub2-set-default 0 Vratislav, do you see anything else? No, not really. What is on the disk /dev/sda in the end? Where does the /boot partition end up? And is such configuration supported by grub? The test machine have two kinds of disk, one is local disk, the other is FC disk. My test want to install rhevh-ngn on FC disk. So the local disk /dev/sda is not used, and all of my partitions are on FC disk. From the kickstart file we can see # clear all the system partition clearpart --all # part two pvs and /boot in one FC disk /dev/disk/by-id/scsi-360*22 part pv.01 --size=100000 --ondisk=/dev/disk/by-id/scsi-36005076300810b3e0000000000000022 part pv.02 --size=50000 --ondisk=/dev/disk/by-id/scsi-36005076300810b3e0000000000000022 part /boot --size=10000 --ondisk=/dev/disk/by-id/scsi-36005076300810b3e0000000000000022 volgroup testgroup pv.01 pv.02 in addition, grub has set FC as boot disk. The problem I see is that the bootloader destination is not specified in the kickstart and thus it is attempted to be installed to the first disk, i.e. /dev/sda. However, /boot is on the FC device which and nothing makes sure that the bootloader can actually be installed to /dev/sda. From the kickstart file attached, you can see bootloader --location=mbr and "/dev/disk/by-id/scsi-36005076300810b3e0000000000000022" is boot disk. (In reply to weiwang from comment #9) > From the kickstart file attached, you can see > bootloader --location=mbr This means the bootloader will be installed to the MBR (Master Boot Record) area of the first disk - i.e. '/dev/sda'. Just like what can be found in the program.log. > > and "/dev/disk/by-id/scsi-36005076300810b3e0000000000000022" is boot disk. Unless this is '/dev/sda', the /boot partition is on a different disk than the boot loader is attempted to be installed. Seems to be that the bootloader and /boo are on different devices, which does not necessarily work. |
Created attachment 1153293 [details] kickstart file Description of problem: "boot loader install failed" during install on FC disk with kickstart parameter "--ondisk=/dev/disk/by-id/xxxxxx" Version-Release number of selected component (if applicable): rhev-hypervisor7-ng-3.6-20160429.0 imgbased-0.6-0.1.el7ev.noarch ovirt-hosted-engine-ha-1.3.5.3-1.el7ev.noarch ovirt-hosted-engine-setup-1.3.6.0-1.el7ev.noarch rhevm-appliance-20160428.0-1.x86_64.rhevm.ova How reproducible: 100% Steps to Reproduce: 1. Automatic install FC machine with kickstart file in attachment key parameter: part /boot --size=10000 --ondisk=/dev/disk/by-id/xxxxxx 2. During installation, check bootloader installation Actual results: "boot loader install failed" prompt during install. Expected results: Installation is successful, no error occur. Additional info: