Created attachment 786103 [details] anaconda-tb-jdh2cS Description of problem: The installer accepts a 70 MiB /boot partition with only a warning. The install fails during bootloader installation with: 03:40:58,722 INFO program: Running... grub2-install --no-floppy /dev/sda 03:41:01,791 INFO program: cp: error writing '/boot/grub2/fonts/unicode.pf2': No space left on device 03:41:01,794 INFO program: cp: failed to extend '/boot/grub2/fonts/unicode.pf2': No space left on device 03:41:01,796 DEBUG program: Return code: 1 NB: In Bug 995892, the reporter was using pre-existing partitions from an F9 install that included a ~70 MiB sda2. This appears to be the cause of the install failure reported in Bug 969684, Comment 47. Version-Release number of selected component (if applicable): anaconda-19.30.13-1 Fedora-19-x86_64-DVD.iso How reproducible: Presumably, always. Steps to Reproduce: 1. Pre-partition a VM disc image with a 70 MiB partition (sda2).[1] See below for a parted report. 2. Boot the F19 installer DVD.[2] 3. From Manual Partitioning, configure sda2 to be mounted on /boot. 4. Begin a Gnome desktop install. Actual results: Installer accepts the storage configuration with only a warning. Install fails during bootloader installation. See Bug 995892, Attachment 785947 [details] for a screenshot of the warning. Expected results: Installer rejects a 70 MiB /boot partition. Additional info: See also: Bug 969684, Comment 50. Bug Bug 995892, Comment 18. $ cat parted-usp-free-sda-2.txt Model: ATA QEMU HARDDISK (scsi) Disk /dev/sda: 67108864s Sector size (logical/physical): 512B/512B Partition Table: msdos Disk Flags: Number Start End Size Type File system Flags 63s 2047s 1985s Free Space 1 2048s 2099199s 2097152s primary ntfs 2 2099200s 2242559s 143360s primary ext4 boot 3 2242560s 4339711s 2097152s primary 4 4339712s 67108863s 62769152s extended 5 4341760s 28917759s 24576000s logical 6 28919808s 67108863s 38189056s logical lvm [1] Pre-partitioning was done with gparted in an installed F19 system. [2] Tested with: $ qemu-kvm -m 4096 -hda f19-test-2.img -cdrom ~/xfr/fedora/F19/Fedora-19-x86_64-DVD.iso -vga std -boot menu=on
(In reply to Steve Tyler from comment #0) ... > Actual results: > Installer accepts the storage configuration with only a warning. ... The warning appears in the Installation Summary under Installation Destination: "Warning checking storage configuration" See Bug 995892, Attachment 785947 [details] for a screenshot of the warning.
For the record, a default F9 install allocates ~196 MiB for sda1: >>> 205599744.0/1024**2 196.0751953125 $ virt-cat f9-test-1.img /etc/fedora-release Fedora release 9 (Sulphur) $ virt-filesystems --all --long -a f9-test-1.img Name Type VFS Label MBR Size Parent /dev/sda1 filesystem ext3 /boot - 205599744 - /dev/VolGroup00/LogVol00 filesystem ext3 - - 32010928128 - /dev/VolGroup00/LogVol01 filesystem swap - - 2080374784 - /dev/VolGroup00/LogVol00 lv - - - 32010928128 /dev/VolGroup00 /dev/VolGroup00/LogVol01 lv - - - 2080374784 /dev/VolGroup00 /dev/VolGroup00 vg - - - 34124857344 /dev/sda2 /dev/sda2 pv - - - 34124857344 - /dev/sda1 partition - - 83 205599744 /dev/sda /dev/sda2 partition - - 8e 34151362560 /dev/sda /dev/sda device - - - 34359738368 - Tested with: $ qemu-kvm -m 4096 -hda f9-test-1.img -cdrom ~/xfr/fedora/F9/Fedora-9-x86_64-netinst.iso -vga vmware -boot menu=on
(In reply to Steve Tyler from comment #1) ... > The warning appears in the Installation Summary under Installation > Destination: > "Warning checking storage configuration" > > See Bug 995892, Attachment 785947 [details] for a screenshot of the warning. The warning is also logged in /tmp/anaconda.log. Snippet from the attached anaconda-tb-jdh2cS: ... /tmp/anaconda.log: 08:09:39,922 INFO anaconda: /sbin/anaconda 19.30.13-1 ... 03:16:52,086 WARN anaconda: Your /boot partition is less than 75 megabytes which is lower than recommended for a normal Fedora install. ...
There is a warning provided for a potentially problematic configuration which could nonetheless be valid for certain configurations, and when ignored the configuration caused a problem. That seems pretty ok to me.