Bug 1101031
| Summary: | Failure to install bootloader | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mikolaj Kucharski <mikolaj> | ||||||||||||||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||
| Version: | 20 | CC: | agk, bcl, dnystrom1, g.kaviyarasu, jonathan, katzj, mikolaj, vanmeeuwen+fedora | ||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||
| OS: | Linux | ||||||||||||||||||
| Whiteboard: | |||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||
| Clone Of: | 972906 | Environment: | |||||||||||||||||
| Last Closed: | 2014-05-29 15:05:01 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
Mikolaj Kucharski
2014-05-25 18:40:14 UTC
This problem is still occurring while installing Fedora 19 or 20. Please rerun it with f20 and attach the log files from /tmp/*log to this bug as individual text/plain attachments. Created attachment 899759 [details]
ks.cfg
Created attachment 899760 [details]
anaconda.log
Created attachment 899761 [details]
program.log
Created attachment 899762 [details]
storage.log
Created attachment 899763 [details]
ifcfg.log
Created attachment 899764 [details]
packaging.log
Created attachment 899765 [details]
sensitive-info.log
I have 4 HDDs, 2x500GB and 2x3TB. The pairs are identical. Here is info collected via sshd started in %pre (see ks.cfg) after installation faled: # parted -s /dev/sda -- print Model: ATA ST3500630AS (scsi) Disk /dev/sda: 500GB Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 1 1049kB 2149MB 2147MB primary raid 2 2149MB 4296MB 2147MB primary raid 3 4296MB 4833MB 537MB primary ext4 boot, raid 4 4833MB 500GB 495GB extended 5 4834MB 500GB 495GB logical raid # parted -s /dev/sdb -- print Model: ATA ST3000DM001-1CH1 (scsi) Disk /dev/sdb: 3001GB Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: pmbr_boot Number Start End Size File system Name Flags 1 1049kB 2149MB 2147MB raid 2 2149MB 4296MB 2147MB raid 3 4296MB 4833MB 537MB ext4 raid 4 4833MB 3001GB 2996GB raid as you can see, smaller disks have msdos partition table, but bigger drives have gpt partition table. From program.log it looks that grub2-install runs successfully on small, msdos drive, but fails on big, gpt drive. # chroot /mnt/sysimage/ # grub2-install --no-floppy /dev/sda Installation finished. No error reported. # grub2-install --no-floppy /dev/sdb /usr/sbin/grub2-bios-setup: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible. /usr/sbin/grub2-bios-setup: error: embedding is not possible, but this is required for RAID and LVM install. # grub2-install --no-floppy /dev/sdc Installation finished. No error reported. # grub2-install --no-floppy /dev/sdd /usr/sbin/grub2-bios-setup: warning: this GPT partition label contains no BIOS Boot Partition; embedding won't be possible. /usr/sbin/grub2-bios-setup: error: embedding is not possible, but this is required for RAID and LVM install. You should add a biosboot partition to the large disks: part biosboot --fstype=biosboot --size=1 --ondisk=sdb Also, you shouldn't use --size=1 with --grow, you should set a reasonable minimal size for the partition as a minimum (not really related, but it will cause problems). @bcl, can you elaborate what kind of problems I can expect with --size=1 --grow? Can I just skip --size altogether when using --grow? Thanks, I will test biosboot part on sdb and sdd. Yeah, biosboot partition did the trick. Machine installed properly with: part biosboot --fstype biosboot --size 1 --ondisk sdb --asprimary part biosboot --fstype biosboot --size 1 --ondisk sdd --asprimary # parted -s /dev/sdb -- unit s print Model: ATA ST3000DM001-1CH1 (scsi) Disk /dev/sdb: 5860533168s Sector size (logical/physical): 512B/4096B Partition Table: gpt Disk Flags: pmbr_boot Number Start End Size File system Name Flags 1 2048s 4095s 2048s bios_grub 2 4096s 4198399s 4194304s raid 3 4198400s 8392703s 4194304s raid 4 8392704s 9441279s 1048576s ext4 raid 5 9441280s 5860532223s 5851090944s raid Thank you bcl@redhat for advice. If you could also elaborate more on --grow and --size, I would appreciated it. I cannot see any explanation in documentation what could be wrong with --size 1 and --grow. Blivet uses the initial size in it's calculations for the partition placement so it needs to be a reasonable size before being grown to fit where it is placed. And if it is the / partition is will fail the check to see if there is enough space to install the packages. |